QtCS2021 - Improve the contributor experience: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 20: Line 20:


==Notes==
==Notes==
(Taken by kakoehne)


===Feedback on https://qt-project.org===
===Feedback on https://qt-project.org===
Line 48: Line 50:
** See animated gif at https://wiki.qt.io/Qt_for_Python
** See animated gif at https://wiki.qt.io/Qt_for_Python


=== Move to Github integration? ===


===Gerrit===
=== Gerrit ===
* Can we improve gerrit experience?
* Can we improve gerrit experience?
** codereview.qt-project.org is already 2 versions behind upstream
** codereview.qt-project.org is already 2 versions behind upstream
Line 64: Line 65:
** Usage of bots are not obvious; what to do when it claims stuff?
** Usage of bots are not obvious; what to do when it claims stuff?
** Existence of CI; flow should be better visualized
** Existence of CI; flow should be better visualized
** Whom to add to a reviewer?
** All explained somewhere in the guidelines, but not really self-explainatory
** All explained somewhere in the guidelines, but not really self-explainatory
* Accept contributions also from github?
** Aim is to have one process for everyone!
** gitlab/gerrit integration bridge (https://gerrithub.io)?
*** Still requires learning gerrit for non-trivial commits (commit series)
=== Move to Github/Gitlab? ===
* What's stopping us?
** Check with other communities
(Notes by Aleix Pol)
=== JIRA ===
* Seems quite okay
* Would it be possible to have shared filters? Quick links?
* TODO Create an issue to have certain filters installed by default
* Prioritization a bit off?
* Logging in
** It's a bit hard to see if you're logged in
** You don't get back to where you were after logging in (https://bugreports.qt.io/browse/QTBI-2079)
=== Communications===
* We have Matrix bridges for the qt-cs channel, we should have also for the other relevant channels to the Qt Project
** We could consider making the KDE matrix instance an official way to join our channels.
* Mailing lists
** We are not using the last version of mailman and it looks a bit old. Updating could be nice.

Latest revision as of 08:15, 23 June 2021


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

(Taken by kakoehne)

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


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
    • Whom to add to a reviewer?
    • All explained somewhere in the guidelines, but not really self-explainatory
  • Accept contributions also from github?
    • Aim is to have one process for everyone!
    • gitlab/gerrit integration bridge (https://gerrithub.io)?
      • Still requires learning gerrit for non-trivial commits (commit series)

Move to Github/Gitlab?

  • What's stopping us?
    • Check with other communities

(Notes by Aleix Pol)

JIRA

  • Seems quite okay
  • Would it be possible to have shared filters? Quick links?
  • TODO Create an issue to have certain filters installed by default
  • Prioritization a bit off?
  • Logging in

Communications

  • We have Matrix bridges for the qt-cs channel, we should have also for the other relevant channels to the Qt Project
    • We could consider making the KDE matrix instance an official way to join our channels.
  • Mailing lists
    • We are not using the last version of mailman and it looks a bit old. Updating could be nice.