Add intent for using Discussions feature in repo #14399
Conversation
|
The static analysis failure is due to the discussions URL not be active yet |
|
Can we have both the blog and this addition to README? |
|
We discussed not having the blog as the content is not the direction we want to go being too prescriptive and creating a new process for using discussions |
| Individual PowerShell team members may choose to participate in discussions, but the expectation is that community members help drive discussions so that team members | ||
| can focus on issues. | ||
|
|
||
| Create or join a [discussion](https://github.com/PowerShell/PowerShell/discussions). |
There was a problem hiding this comment.
I think we need a reflection between discussion categories and issue areas.
|
This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days. |
|
Adding this feature makes sense only if MSFT team intends (1) to actively participate in discussions and (2) make it the main forum for PowerShell, otherwise it will be just another forum, which does not make sense since there are already many great sites with their audience. |
|
This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days. |
|
@PowerShell/powershell-committee discussed this, we agree with the intent to enabling discussions to move those out of issues. By the nature of Discussions being on GitHub, we believe it's more likely PowerShell team members will participate, but also we want to set no expectation that PowerShell team members are expected to participate. |
There was a problem hiding this comment.
Language looks good for the intent
@iSazonov I represented your position for a while in our conversation within the Committee today, but I was ultimately persuaded by the argument @SteveL-MSFT made in the comment above. More specifically that:
- this is an experiment, and we should keep your question in mind as we decide whether to leave Discussions on
- the proximity of the Discussions tab to the code repo will likely encourage more contribution from PS Team members than other forums, in spite of the lack of requirement
Additionally, I don't think any of this should dissuade folks from using existing discussion forums like SO, PS.org, Discord/Slack UG, Reddit, etc.
|
The static analysis failed because the discussion tab hasn't been enabled. The URL will exist once that's done. |
|
🎉 Handy links: |
PR Summary
Add guidance on intent for enabling Discussions feature
PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.