Seems like the convention is to have a `First-Time-Issue` to help first time contributors find easy issues they can work on to start learning about the project and make their first contribution. Label is created, this PR adds documentation. The `Hackathon`/`Hacktoberfest` label (changes depending on time of year) wasn't documented previously and added to issue management doc.
Fix https://github.com/PowerShell/PowerShell/issues/8562
Leverage GitHub ability to have multiple options when user clicks "New Issue" to have better issues opened and direct users to Docs repo and UserVoice for Windows PowerShell issues.
* Fix broken installation links in README.md
* fix remaining broken links due to removal of breakingchanges and knownissues docs
* Remove en-us culture from docs links in readme
* Remove last en-us culture link from issue template
- Update contribution guidelines to make updating the changelog required
- add a checklist to PR template
Comment by @SteveL-MSFT :
> Everyone should understand that we are always open to feedback and nothing is set in stone. Based on a team discussion, one of the biggest costs for a release is creating the ChangeLog hence updating this document to push it to the contributor most aware of why the changes are being made and ideally how it's useful to end users.
* Update coding guidelines to make it more concrete and useful in a review process.
* Add a section about security
* Address comments
* Update .spelling
* Address more comments
* Address comment about the security section
* Fix 'i.e.' and 'e.g.'
* Update .spelling
* One more tweak
* Add motivation for using 'nameof'
Update pull-request-process to clarify role/responsibility of author and reviewers based on recent feedback from team and community. Also moved it to `.github/CONTRIBUTING.md` so that all related information can be found at one place.
Adds fenced code blocks / output blocks to the `Steps to reproduce`, `Expected behavior` and `Actual behavior` sections, so as to facilitate proper formatting.
Fix#3952.
* Remove PR template, update guidelines for PR
* Update testing-guidelines.md
* Add clarification on when to use runtime/compiletime checks
* Update issue label descriptions
Now that we've gotten enough of a sign-off
from everyone involved in the governance
process, the docs need to be reworked to use a
consistent terminology set, links, and directory
structure.
