bcfe4dab3b
* Add new product to products.yml * Move directory to its new location and rename it * Update new index page * Remove old category from GitHub product index * Add collaboration category * Add membership category * Add roles category * Add teams category * Add team discussion category * Add repo access category * Add project board access category * Add app management category * Add org settings category * Add improved org perms category * Add category for OAuth app restrictions * Add org security category * Add SAML category * Add SAML access category * Add git access category * Add redirects and update links for collaboration category * Add redirects and update links to team discussions content * Add redirects and update links to SAML access category * Update links to org security category and add redirects * Add redirects for app managers content * Add redirects for project board category * Add redirects and update links for the repo access category * Add redirects for git access category * Add redirects and update links for membership category * Add redirects and update links for org settings category * Fix links * Add redirects and update links to org access category * Add redirects and upate links to SSO category * Add redirects to improved org perms category * Add redirects and update links to teams category * Add redirects and update links to oauth apps category * Fix links * Fix links * Fix links
50 lines
3.4 KiB
Markdown
50 lines
3.4 KiB
Markdown
---
|
|
title: Best practices for community conversations on GitHub
|
|
shortTitle: Best practices for community conversations
|
|
intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to a discussion when you are ready to scope out the work.'
|
|
versions:
|
|
free-pro-team: '*'
|
|
---
|
|
|
|
{% data reusables.discussions.beta %}
|
|
|
|
### Community conversations in {% data variables.product.prodname_discussions %}
|
|
|
|
Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository and gather diverse feedback and ideas more quickly. You can help drive a productive conversation by:
|
|
|
|
- Asking pointed questions and follow-up questions to garner specific feedback
|
|
- Capture a diverse experience and distill it down to main points
|
|
- Open an issue to take action based on the conversation, where applicable
|
|
|
|
For more information about opening an issue and cross-referencing a discussion, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)."
|
|
|
|
### Learning about conversations on GitHub
|
|
|
|
You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have.
|
|
|
|
You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and spike out a project's specific details before committing it to an issue, which can then be scoped. Discussions are useful for teams if:
|
|
- You are in the discovery phase of a project and are still learning which director your team wants to go in
|
|
- You want to collect feedback from a wider community about a project
|
|
- You want to keep bug fixes, feature requests, and general conversations separate
|
|
|
|
Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see "[About issues](/articles/about-issues)." Pull requests allow you to comment directly on proposed changes. For more information, see "[About pull requests](/articles/about-pull-requests)" and "[Commenting on a pull request](/articles/commenting-on-a-pull-request)."
|
|
|
|
{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
|
|
|
|
### Following contributing guidelines
|
|
|
|
Before you open a discussion, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project.
|
|
|
|
For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
|
|
|
|
### Next steps
|
|
|
|
To continue learning about {% data variables.product.prodname_discussions %} and quickly create a discussion for your community, see "[Quickstart for {% data variables.product.prodname_discussions %}](/discussions/quickstart)."
|
|
|
|
### Further reading
|
|
|
|
- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"
|
|
- "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)"
|
|
- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"
|
|
- "[Writing on {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)"
|