-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add SUPPORT guide #1
Comments
@hboutemy @bhamail @eddie-knight - what communication mechanisms do we offer for engagement with the Community Projects? Thoughts:
Comments appreciated. |
A link to create GitHub Issues is helpful. I find issues are helpful because they both create a trigger email (especially if we include @username in the issue templates) and provide a public history on which others can search and comment. A GitHub Issues is also easy to link to a related future PR. |
Personally a fan of keeping things in GitHub. That will mean encouraging maintainers to stay on top if issues and discussions (if we enable those). |
Kind of agree - one place to focus folk. We probably do need to do some cleanup then to "close" or "notify" these other older arenas for discussion... ...but not the scope of this ticket. |
Add a SUPPORT as per https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.
If this is generic it can be added to the
.github
repository as per https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-fileThe text was updated successfully, but these errors were encountered: