Encourage more community contributors
Background and Problem to Solve
There is a company goal to increase the number of code contributors. As the Release stage, we want to contribute to this goal and make it easier for contributors, especially first time contributors. We discussed this as a topic in a team brainstorm session.
Ideas from team brainstorm
- Make our contributions more visible from the community perspective (e.g. blog posts, interacting more with DevRel)
- Have top 10-30 issues marked as "accepting community contributions", but not too many, since they can be overwhelming
- Provide more guidance/nurturing on what contributors could be doing. Consider providing a technical approach (that Shinya does often times in an issue)
- Post top 5 ideas, recording of office hours in Gitter channel and everywhere else
- Discuss above in office hours
- Get a contributor to record a video walkthrough of their feature
- Check out Backstage from Spotify and Shipper from Booking as references for community involvement
- We want to position ourselves as a team working on deployments that contributors can work with; put our faces more out there as a team
Next Steps
-
Add grooming ~"good for new contributors" issues to the planning process Add grooming contributor issues (gitlab-com/www-gitlab-com!99164 - closed) -
Schedule and plan the next office hours
Edited by Chris Balane