Confirm
1,351
edits
Changes
Add archive suggestions
=== Do I need to be an owner to create repositories? ===
No. If a person has read/write access to another repository in that organization they can make more repositories in that organization. However, it's preferred that you create repositories in the context of a team. Teams are created [https://github.com/orgs/mozilla/teams here], if necessary. Once you have created a repo, you can configure it to give rights to members of particular teams.
=== We're done with this project - what should we do with the repository? ===
That is really up to the team. However, if you have forks or other active user participation, it's a good idea to be clear about the status of Mozilla's commitment to the project. Your options include:
* Delete the repo (obviously the worst alternative).
* Add the [http://unmaintained.tech/ Unmaintained] badge to the readme
* Archive the repository, using [https://help.github.com/articles/about-archiving-repositories/ GitHub's suggestions].
'''PLEASE''' make sure the repository is clearly licensed before leaving it. Without a license, many other folks can not build upon your work.
=== Are there requirements for when or how I should create a new team? ===
