QtChampions: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Added comment for nominator tasuku.suzuki)
(Updating ready for the 2020 nominations)
Line 1: Line 1:
[[Image:Qt_Champion_200.png|400px]]
[[Image:Qt_Champion_200.png|400px]]


This page will be used for nominations for the 2019 [[Qt Champions]].
This page will be used for nominations for the 2020 [[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 15th December 2019 and then ask the current Qt Lifetime Champions to evaluate the nominees.
We’ll keep the nominations open until the 6th December 2020 and then ask the current Qt Lifetime Champions to evaluate the nominees.


'''The categories''' for nomination are:
'''The categories''' for nomination are:


* Community Builder  
*Community Builder
* Content Creator  
*Content Creator
* Quality Assurer  
*Quality Assurer
* Developer
*Developer
* Fixer
*Fixer
* Ambassador
*Ambassador
* Rookie of the year
*Rookie of the year
* Maverick
*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.
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.
Line 24: Line 24:
In the below table please add the following information of the person you wish to nominate for a Qt Champion title:
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)
*Qt Account username (or codereview name)
* Category or Title to be nominated for
*Category or Title to be nominated for
* Reasons for nomination (max. 300 words, please provide links to relevant material if possible)
*Reasons for nomination (max. 300 words, please provide links to relevant material if possible)


{| class="wikitable"
{| class="wikitable"
! Username || Title category || Reason for nomination
!Username||Title category||Reason for nomination
|- |
|Denis Shienkov
(denis.shienkov)
| Maverick
| Denis has been a contributor to the Qt project since 2011.
 
He is approver, the author and maintainer of the QtSerialPort module and has contributed to many other modules as well.
 
As an active user of the Qbs build system, he stepped in when this project was handed to the community and provided over 100 [https://codereview.qt-project.org/q/owner:denis.shienkov patches] to improve this project,  especially in regard to bare metal programming.
 
A noticeable amount of patches also went to Qt Creator, foremost to integrate the new Qbs features into that IDE. And last but not least he [https://codereview.qt-project.org/q/reviewer:denis.shienkov+-owner:denis.shienkov reviews] patches in various Qt modules.
 
I think all that qualifies him to be a Qt Champion.
|-
|Orgad Shaneh
(orgads)
|Developer/Fixer
|Once again the most productive external contributor to Qt Creator.
 
He joined the Qt project in 2011 and is approver as well as the maintainer of Creators Version Control module.
 
While the list of his [https://codereview.qt-project.org/q/owner:orgads contributions] is already impressive, he actively participates on much more changes as [https://codereview.qt-project.org/q/reviewer:orgads+-owner:orgads reviewer], and that is just the continuation of the last years.
 
He always has an eye for polishing the rough edges and to improve processes. Instead of writing bugreports, he often provides a ready-to-merge solution on Gerrit.
 
For all that reasons, he deserves the title for the highest degree.
|-
|Christian Ehrlicher
(christian.ehrlicher)
|Fixer/Developer
|He is a member for a long time, but started contributing to Qt massively two years ago. Since then he has also become approver and is well known in the community for his friendly and constructive nature.
He not only shares his immense knowledge with [https://codereview.qt-project.org/q/owner:ch.ehrlicher contributions] (a lot of bug fixes and cleanups) and [https://codereview.qt-project.org/q/reviewer:ch.ehrlicher+-owner:ch.ehrlicher reviews], he also answers the difficult questions in the Qt Forum, where he additionally acts as [https://forum.qt.io/user/christian-ehrlicher moderator].
 
This over-average activity is exactly what we expect from a Qt Champion.
|-
|-
|Tasuku Suzuki
|
(tasuku.suzuki)
|
|Content Creator/Developer
|
/Community Builder
|He's the creator of https://qtlite.com/ , an amazing website to help you create a minimal configuration for your Qt build, show you the impact of features in typical builds, which combinations are currently known to not work, etc. The site is easy to use, engaging and encourages to contribute back straight to Gerrit.
 
Also, he is as known as one of the famous Qt developers in Japan. If he is creating some software or service with Qt and then he finds a Qt bug, he leaves that software coding alone and he modifies that bug first. (ex: Improve some functions of QtCreator [https://codereview.qt-project.org/c/qt-creator/qt-creator/+/269226 this], [https://codereview.qt-project.org/c/qt-creator/qt-creator/+/268057 this] and [https://codereview.qt-project.org/c/qt-creator/qt-creator/+/264905 this]) As a result, his company became a No.6 contributing company on Qt's contribution ranking on 8th July this year. And this is just his achievement because his company's developer was him alone. ([https://translate.google.co.jp/translate?sl=ja&tl=en&u=https://qt5.jp/2019/07/qtcs-qtbase-contribution/ LINK: his web site])
 
Finally this year, He returned back to chairman of the Qt User community in Japan. He originally led the Qt user group for many years. And he left the leadership to one of the community members a few years ago. The monthly Qt meetups in Japan continued during that time, but this time he returned to the chairman he will contribute to the spread of Qt as a user group. Specifically, it seems that he is planning like following activities. "Dissemination activities throughout Japan as a user group", "Enhancement of online information about Qt", "Creating an environment that can help each other of Qt software developer", "Provide a place for interaction between Qt users" ([https://translate.google.co.jp/translate?sl=ja&tl=en&u=https://qt5.jp/2019/09/2019-japan-qt-users-group/ LINK: his web site])
 
In conclusion, I'd say that he is such a pretty good Qt geek.
|-
|André Hartmann (aha_1980)
|Developer/Fixer
|One of the most productive [https://codereview.qt-project.org/q/owner:aha_1980 contributors] to the Qt Project. He actively maintains the QtSerialBus module, and contributes many fixes to Qt Creator, and also to Qt. His [https://codereview.qt-project.org/q/reviewer:aha_1980+-owner:aha_1980 reviews] are very helpful, and he also notices changes of newcomers, and kindly reviews them.
|-
|Richard Weickelt
|Developer/Rookie
|When the Qbs project was handed over to the community, Richard took it and actively maintains the project. He brought [https://codereview.qt-project.org/q/owner:richard%2540weickelt.de many improvements], and of course [https://codereview.qt-project.org/q/reviewer:richard%2540weickelt.de+-owner:richard%2540weickelt.de reviewed] all the changes for Qbs. He also introduced a CI system for verifying all the changes that are pushed to Gerrit.
|-
|Johann Specht
(jsulm)
|Community Builder
|The user with the third-best reputation (only behind the two current lifetime champions) is [https://forum.qt.io/user/jsulm jsulm].
Always available to answer all kinds of questions, from very basic up to the really hard ones.
 
As a moderator, he also keeps the conversations calm and the forum clean of spam.
|}
|}


Criteria for Qt Champions:
Criteria for Qt Champions:


* Community Builder
*Community Builder
** Being a forum maintainer / helping people on forums
**Being a forum maintainer / helping people on forums
** Managing mailing lists / helping on the mailing lists
**Managing mailing lists / helping on the mailing lists
** Helping Qt newcomers find their way around the project
**Helping Qt newcomers find their way around the project
** Running Qt study groups
**Running Qt study groups
** Running local Qt meetups
**Running local Qt meetups
* Content Creator
*Content Creator
** Finding, writing and sharing use-cases of Qt in unexpected places
**Finding, writing and sharing use-cases of Qt in unexpected places
** Creating video material of Qt (demos, guides, other material)
**Creating video material of Qt (demos, guides, other material)
** Authoring articles and even books
**Authoring articles and even books
** Fixing documentation issues
**Fixing documentation issues
** Creating examples and snippets
**Creating examples and snippets
** Being a wiki gardener / editor
**Being a wiki gardener / editor
* Quality Assurer
*Quality Assurer
** Bug triager
**Bug triager
** Being in the bug squad
**Being in the bug squad
** Verifying and closing bugs
**Verifying and closing bugs
** Help in package testing
**Help in package testing
** Help in unit testing
**Help in unit testing
** Being in the community beta testing program
**Being in the community beta testing program
* Developer
*Developer
** Providing new features for Qt
**Providing new features for Qt
** Create stunning Qt applications
**Create stunning Qt applications
** Share Qt application creation knowledge  
**Share Qt application creation knowledge
* Fixer
*Fixer
** Fixing bugs in Qt  
**Fixing bugs in Qt
** Providing patches to Qt  
**Providing patches to Qt
* Ambassador
*Ambassador
** Spread the Qt word in blogs, social media, videoblogs
**Spread the Qt word in blogs, social media, videoblogs
** Find and help newcomers to Qt
**Find and help newcomers to Qt
** Working to bring Qt to students
**Working to bring Qt to students
** Present Qt at events
**Present Qt at events
* Rookie of the Year
*Rookie of the Year
** First code commit during the past year
**First code commit during the past year
** Active and positive contribution to the Qt project
**Active and positive contribution to the Qt project
* Maverick
*Maverick
** Has made a significant impact on the project
**Has made a significant impact on the project
** Might not have always followed the rules to the point, but gets the job done
**Might not have always followed the rules to the point, but gets the job done


== What is expected of a Qt Champion ==
==What is expected of a Qt Champion==


A Qt Champion is there to show what the Qt Community is best at.
A Qt Champion is there to show what the Qt Community is best at.
Line 141: Line 83:
The Qt Champion is friendly and has shown active participation with the Qt project.
The Qt Champion is friendly and has shown active participation with the Qt project.


== Limited time only ==
==Limited time only==


Once you are given the title of Qt Champion, you will hold the title for a year.
Once you are given the title of Qt Champion, you will hold the title for a year.
Line 147: Line 89:
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.
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? ==
==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.
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.


== Tools to help figure this out ==
==Tools to help figure this out==


To find the top non-Qt-company contributors in a repo:
To find the top non-Qt-company contributors in a repo:


git log --since=2019-01-01 | grep Author  | grep -v qt.io  | sort | uniq -c | sort -n
git log --since=2020-01-01 | grep Author  | grep -v qt.io  | sort | uniq -c | sort -n

Revision as of 08:42, 5 November 2020

Qt Champion 200.png

This page will be used for nominations for the 2020 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 6th December 2020 and then ask the current Qt Lifetime Champions to evaluate the nominees.

The categories for nomination are:

  • Community Builder
  • Content Creator
  • Quality Assurer
  • Developer
  • Fixer
  • 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

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 new features for Qt
    • Create stunning Qt applications
    • Share Qt application creation knowledge
  • Fixer
    • Fixing bugs in Qt
    • Providing patches to Qt
  • 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.

Tools to help figure this out

To find the top non-Qt-company contributors in a repo:

git log --since=2020-01-01 | grep Author | grep -v qt.io | sort | uniq -c | sort -n

Retrieved from "https://wiki.qt.io/index.php?title=QtChampions&oldid=37490"