Document how projects can use GitHub, including issues, wiki, and releases
Submitted by Wayne Beaton @wbeaton
Link to original bug (#485964)
Description
We need to document how projects are expected to use GitHub. We have board approval for projects to use GitHub repositories and Issues with an understanding that the webmaster team is able to provide complete backups of the captured information thereby providing the necessary freedom of action.
Use of repositories is approved by the board of directors. This extends to the use of wiki which is effectively a Git repository that contains documentation.
The use of GitHub Issues is approved by the board of directors. The resolution indicates that PMC approval is required.
GitHub Releases can be used, but the PMI must be used as the canonical location for review documentation. Similarly, the EF-provided download server is the canonical location for distribution of project artifacts.
The handbook is probably the right home for this documentation, but I thought that I'd start the bug here to make sure that we've correctly captured the requirements.