QtCS2021 - Improve the contributor experience

From Qt Wiki
Revision as of 14:49, 22 June 2021 by Kkoehne (talk | contribs)
Jump to navigation Jump to search


Session Summary

Back in 2019 we had the discussion around the contribution experience, from which we gather many good ideas: some of them were never addressed, but others have been implemented, like for example the Qt project website and the Community Manager position that was open.

This session will try to address many of the open topics we had from that session looking at "What we could do" to keep improving the experience in topics like:

  • What we can learn from the KDE contribution experience
  • First contribution and initial setup
  • Gerrit improvements, plugins, etc
  • Creation of "good first issues" in JIRA
  • ...and all the good ideas you probably have.

Update: Together with Eddy, we had a session on how to contribute to Qt, I recommend you to quickly check the slides (there are some videos with audio in the middle), so you can get some ideas on steps we could improve: https://qtinfo.dev/akademy2021_contribute/

Session Owners

  • Cristián Maureira-Fredes (cristian.maureira-fredes@qt.io)

Notes

Feedback on https://qt-project.org

  • Information is pretty 'crammed'. More overview documentation?
    • No 'why' part. _Why_ would I want to contribute?
    • Have separate page for the motivational part & link to it?

First time contribution experience

Move to Github integration?

Gerrit

  • Can we improve gerrit experience?
    • codereview.qt-project.org is already 2 versions behind upstream
    • 'Find reviewer' plugin?
    • Have we checked with other communities?
      • Check with other gerrit users, like libreoffice?
      • KDE Experience with move from fabricator to gitlab was very positive
        • Much better known workflow
      • Gerrit command line always feels a bit weird (git push <to strange branch>)
        • This is at the core of gerrit though; user base
  • Feedback from first time users
    • Usage of bots are not obvious; what to do when it claims stuff?
    • Existence of CI; flow should be better visualized
    • All explained somewhere in the guidelines, but not really self-explainatory