QtChampions

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
KDE Project	Ambassador, Community Builder, Developer	The KDE project has been a large user and promoter of Qt for the past decades. They help contribute with developer out-reach, packaging, bug reports/fixes, as well as a great source of developer recruits for all companies operating in the Qt space. (I know this is not a person, but I think that the project as a whole deserves the recognition of being considered a Champion)

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