Difference between revisions of "QtChampions"

From Qt Wiki
Jump to: navigation, search
(Nominating Andre Hartman)
(Nominating Richard)
Line 72: Line 72:
 
|Developer/Fixer
 
|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 QtSerialPort 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.
 
|One of the most productive [https://codereview.qt-project.org/q/owner:aha_1980 contributors] to the Qt Project. He actively maintains the QtSerialPort 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.
 
|}
 
|}
  

Revision as of 12:04, 8 November 2019

Qt Champion 200.png

This page will be used for nominations for the 2019 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 15th December 2019 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
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 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 reviews patches in various Qt modules.

I think all that qualifies him to be a Qt Champion.

His patches and his reviews

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 contributions is already impressive: Changes he actively participates on much more changes as reviewer: Reviews, 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 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 contributions (a lot of bug fixes and cleanups) and reviews, he also answers the difficult questions in the Qt Forum, where he additionally acts as moderator.

This over-average activity is exactly what we expect from a Qt Champion.

tasuku.suzuki Content Creator 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.

André Hartmann (aha_1980) Developer/Fixer One of the most productive contributors to the Qt Project. He actively maintains the QtSerialPort module, and contributes many fixes to Qt Creator, and also to Qt. His 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 many improvements, and of course reviewed all the changes for Qbs. He also introduced a CI system for verifying all the changes that are pushed to Gerrit.

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=2019-01-01 | grep Author | grep -v qt.io | sort | uniq -c | sort -n