Meta - recognizing community engagement
Very random notes from discussions at the Manchester 2022 sprint, in no particular order. Feel free to add more.
-
infra/gitlab#43 When someone opens an issue on Gitlab for the first time, add a "new-contributor" label (apparently Drupal are working with Gitlab about this? but it will take a while, and adding a label is simple) -
infra/gitlab#43 Post "new-contributor" alerts in a mattermost channel, where people interested could follow and help engaging with the request -
Contributor listing on the website (there is already an issue for this somewhere, we were waiting after SearchKit, but that's now usable for our requirements) -
(very old problem) people willing to be pinged on certain topics - Joe uses email filters for subscribing to specific labels?
- Justin mentioned it would be nice to have a ping in new issues, after 2 weeks if no engagement, to try to keep it alive and moving forward (and that ping could ping more people based on tags or keywords)
What we already do (please complete this list):
- Jaap does Gitlab issue triage, and tries to be more attentive to first-time contributors
- Eileen, Seamus and DaveD keep a very close eye on Github pull-requests, and often spend a lot of time helping with the "other 50%" required for a PR to be merged.
- Developer trainings at in-person events
- Monthly release blog posts mention who contributed code and commented on PRs.
- Monthly release blog posts mention new extensions (still a form of recognition)
- Dev-digest will try to bring some attention to specific issues that need wider feedback