justinmclean commented on code in PR #174: URL: https://github.com/apache/comdev-site/pull/174#discussion_r1547092975
########## source/pmc/community-growth.md: ########## @@ -0,0 +1,90 @@ +--- +title: Community Growth +tags: ["pmc","committers","community"] +--- + +Growing your project community takes work. This document makes practical +suggestions of how to encourage people to get involved in your project. + +## Publish a roadmap + +Volunteers can work on whatever they want, and so we have a tendency to +not want to tell them what to work on. However, publishing a roadmap, or +even a wishlist of features or improvements that are desired, can give +people an idea of where they might be able to get involved. + +This also gives a clear sense that the project has ambitions, and is +going somewhere, rather than that it is stagnating. + +It can be very challenging to keep a roadmap current. Having a mechanism +for tagging open issues with `proposal` or `roadmap` and +automatimatically extracting that into a web page can help with this. + +## Periodically publish the open issue list + +Your ticket tracker allows you to periodically summarize the open +issues. Sending this to the dev@ list reminds people that there are +things to work on, and gives them permission, and encouragement, to do +so. + +Consider creating [good first +issues](/committers/good-first-issues.html) as a place for new +contributors to get started. Review Comment: GitHub automatically does this for you https://github.com/apache/pekko/contribute just substitute pekko for any Apache project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
