QtChampions: Difference between revisions
(Withdrawn myself for personal reasons) |
(Starting to clean up) |
||
Line 1: | Line 1: | ||
[[Image:Qt_Champion_200.png|400px]] | [[Image:Qt_Champion_200.png|400px]] | ||
This page | This page will be used for nominations for the 2018 [[Qt Champions]]. | ||
'''The nomination process''' is public. To nominate a community member, '''please fill in the details at the end of this wiki page'''. | '''The nomination process''' is public. To nominate a community member, '''please fill in the details at the end of this wiki page'''. | ||
We’ll keep the nominations open until the | We’ll keep the nominations open until the 16th December 2018 and then ask the current Qt Champions to evaluate the nominees. | ||
'''The categories''' for nomination are: | '''The categories''' for nomination are: | ||
Line 29: | Line 29: | ||
{| class="wikitable" | {| class="wikitable" | ||
! Username || Title category || Reason for nomination | ! Username || Title category || Reason for nomination | ||
|- | |- | ||
|orgads||Developer||Orgad is contributing to Qt since 2011 and has provided countless improvements and bug fixes, especially for QtCreator. He is very active (up to now, he has over 375 merged patches this year) but also reviews tons of patches from other developers, looks through the bugreports and answers questions on the mailing list. His helpful nature makes it really fun to work with him and therefore he should be Qt Champion 2017. | |orgads||Developer||Orgad is contributing to Qt since 2011 and has provided countless improvements and bug fixes, especially for QtCreator. He is very active (up to now, he has over 375 merged patches this year) but also reviews tons of patches from other developers, looks through the bugreports and answers questions on the mailing list. His helpful nature makes it really fun to work with him and therefore he should be Qt Champion 2017. | ||
Line 78: | Line 42: | ||
Recommend Mrjj for Qt Champion 2017. | Recommend Mrjj for Qt Champion 2017. | ||
|- | |- | ||
|ekkescorner|| Ambassador | |ekkescorner|| Ambassador | ||
Line 93: | Line 54: | ||
ekke is also active at Twitter (@ekkescorner), Qt Forums and Slack (QtMob) | ekke is also active at Twitter (@ekkescorner), Qt Forums and Slack (QtMob) | ||
|- | |- | ||
| | |kshegunov||Community Builder/Developer||Mr Shegunov has proven his technical knowledge over the years. He's helpful on the community platform especially on the most complex or technical specific problems. He's also actively maintaining a [https://bitbucket.org/nye/qtdaemon library to facilitate daemons/services in Qt] | ||
| | |||
|- | |- | ||
| Ben Lau | | Ben Lau |
Revision as of 11:30, 29 October 2018
This page will be used for nominations for the 2018 Qt Champions.
The nomination process is public. To nominate a community member, please fill in the details at the end of this wiki page.
We’ll keep the nominations open until the 16th December 2018 and then ask the current Qt Champions to evaluate the nominees.
The categories for nomination are:
- Community Builder
- Content Creator
- Quality Assurer
- Developer
- Ambassador
- Rookie of the year
- Maverick
Each category may or may not have a Qt Champion in a given year. The number of Qt Champions is limited. Being nominated does not automatically bring a title, but is a recognition in itself.
We know we have very talented Qt Champions out there, but please nominate a person for one category. You can nominate multiple people for a category, only Rookie of the year and Maverick are strictly limited to one Champion per year. You can nominate any member of the community, including yourself.
In the below table please add the following information of the person you wish to nominate for a Qt Champion title:
- Qt Account username (or codereview name)
- Category or Title to be nominated for
- Reasons for nomination (max. 300 words, please provide links to relevant material if possible)
Username | Title category | Reason for nomination |
---|---|---|
orgads | Developer | Orgad is contributing to Qt since 2011 and has provided countless improvements and bug fixes, especially for QtCreator. He is very active (up to now, he has over 375 merged patches this year) but also reviews tons of patches from other developers, looks through the bugreports and answers questions on the mailing list. His helpful nature makes it really fun to work with him and therefore he should be Qt Champion 2017.
Bug tracker profile: https://bugreports.qt.io/secure/ViewProfile.jspa?name=orgads |
mrjj | Community Builder | MrJJ is active daily on the community platforms. He's helpful and kind to everybody and will provide support both to newcomers and seasoned experts alike
Mrjj is a very nice person and activley involved in Qt Forum everyday, answering to the Questions posted, And being friendly to everyone. having the vast experience in C++, Qt, QML, and being able to explain and his guidance his much effective for everyone. LinkedIn Profile can be viewed : https://dk.linkedin.com/in/jonas-e-hjortlund-01302b6 Recommend Mrjj for Qt Champion 2017. |
ekkescorner | Ambassador | ekke, a former BlackBerry Elite Developer, now is spending all of his time to develop mobile business apps with QtQuickControls2.
ekke is speaking at german and international conferences (including QtWorldSummit) and writing articles for german publications. ekke also provides a blog about Qt for mobile apps on Android and iOS and from time to time writes at Qt Blog. ekke creates more complex real-life example apps - per ex. in 2017: Bluetooth LE Example and Sharing on Android and iOS Example ekke is also active at Twitter (@ekkescorner), Qt Forums and Slack (QtMob) |
kshegunov | Community Builder/Developer | Mr Shegunov has proven his technical knowledge over the years. He's helpful on the community platform especially on the most complex or technical specific problems. He's also actively maintaining a library to facilitate daemons/services in Qt |
Ben Lau | Maverick | Ben Lau is the author of QuickFlux (A Flux implementation) / QuickPromise (Promise in QML) and many others nest Qt library available on Github and QPM.
In the year of 2017, he has released a new library, AsyncFuture, for Qt/C++. It provides a JavaScript’s Promise-alike interface over QFuture. So that QFuture could represent the result of any kind of asynchronous operation, not restricted to use with QtConcurrent only. The API is chainable that could turn multiple step operations into a single QFuture. It is an innovation to make asynchronous programming with C++ in a much more flexible and simple way. Github Profile: http://www.github.com/benlau |
Criteria for Qt Champions:
- Community Builder
- Being a forum maintainer / helping people on forums
- Managing mailing lists / helping on the mailing lists
- Helping Qt newcomers find their way around the project
- Running Qt study groups
- Running local Qt meetups
- Content Creator
- Finding, writing and sharing use-cases of Qt in unexpected places
- Creating video material of Qt (demos, guides, other material)
- Authoring articles and even books
- Fixing documentation issues
- Creating examples and snippets
- Being a wiki gardener / editor
- Quality Assurer
- Bug triager
- Being in the bug squad
- Verifying and closing bugs
- Help in package testing
- Help in unit testing
- Being in the community beta testing program
- Developer
- Providing patches to Qt
- Create stunning Qt applications
- Share Qt application creation knowledge
- Ambassador
- Spread the Qt word in blogs, social media, videoblogs
- Find and help newcomers to Qt
- Working to bring Qt to students
- Present Qt at events
- Rookie of the Year
- First code commit during the past year
- Active and positive contribution to the Qt project
- Maverick
- Has made a significant impact on the project
- Might not have always followed the rules to the point, but gets the job done
What is expected of a Qt Champion
A Qt Champion is there to show what the Qt Community is best at.
The Qt Champion is friendly and has shown active participation with the Qt project.
Limited time only
Once you are given the title of Qt Champion, you will hold the title for a year.
If you achieve the title for three years, you will be entitled for a lifetime title. If you are so committed to the project, you need to be recognised beyond a normal Qt Champion title.
But I get paid to do this! / What if we are a company?
Yes, some of us are paid to work on Qt by our employers. Mostly on the code base, but also testing, documentation and other essential work goes on in the project. Some of the people who do get paid to work on the project do so above and beyond the normal limits of their day jobs (coding all day and helping newcomers in their free time, for example). We need metrics to find these people and provide them with a Qt Champion title too.