Changes between Version 6 and Version 7 of TracHacks/SiteMaintenance

Timestamp:

Feb 12, 2017, 3:30:22 AM (7 years ago)

Author:

Ryan J Ollos

Comment:

Add steps for transferring a repository to the GitHub org.

TracHacks/SiteMaintenance

@@ -1 +1 @@
 = Site Maintenance Procedure
+[[PageOutline(2-5, Contents, pullout)]]
 
 This page documents site maintenance procedures. It is a work in progress.
@@ -24 +25 @@
 * TODO: Determine process for removing deprecated and unmaintained plugins and their associated tickets.
 * TODO: Should plugins be tagged with 'plugin' to distinguish them from users? Should macros similarly be tagged as 'macro' or 'plugin' or both? Same for themes?
+
+== trac-hacks organization on GitHub
+
+The [https://github.com/trac-hacks organization] on GitHub has grown to a reasonable size through proactively contacting plugin author and asking if they'd like to join the organization and/or move their repository to the organization. An example invite is [https://github.com/trac-hacks/trac-LighterTheme/issues/1 here].
+
+Locating Trac plugins on GitHub may get easier over time since the introduction of [https://github.com/blog/2309-introducing-topics topics]. Repositories in the organization should be labeled with the **trac-plugin** topic.
+
+Transferring a repository is better than forking it because it moves all of the issues and pull requests, and sets up a redirect from the old location. If the repository owner wishes to transfer the repository but maintain their own fork, it is better for them to transfer the repository and then create the fork rather than attempting to "give" the repository to the trac-hacks org by forking their repository.
+
+=== Moving a repository to the organization
+
+After a repository owner has decide to move their repository to the organization, complete the following steps:
+
+* Create a [https://github.com/orgs/trac-hacks/teams New Team] with the repository name as the team name. The team should be `Visible`.
+* Add the repository owner to the team. If the owner is not yet a member of the organization this step will send them an invite.
+* Wait for the repository owner to [https://help.github.com/articles/about-repository-transfers/ transfer] their repository to the organization.
+* After the transfer, promote the repository owner to **Team Maintainer**. Skip this step if the repository owner has chosen to transfer the repository to the organization but doesn't wish to maintain the code any longer.
+* Add the repository to the team with **Write** access granted to team members.
+* Label the repository with the **trac-plugin** topic.