Jump to: navigation, search

Difference between revisions of "Social Coding/Hosting a Project at GitHub"

(Moving a Repository)
(Moving Existing Repositories)
Line 21: Line 21:
 
For each repository, first locate and click the "Settings"; scroll down to the "Danger Zone".
 
For each repository, first locate and click the "Settings"; scroll down to the "Danger Zone".
  
[[Image:GitHub-Transfer1.png|center|Ride into the "Danger Zone"]]
+
[[Image:GitHub-Transfer1.png|center|frame|none|Ride into the "Danger Zone"]]
  
 
Click "Transfer" in the "Transfer Ownership" block.
 
Click "Transfer" in the "Transfer Ownership" block.
  
[[Image:GitHub-Transfer2.png|center|Assign ownership to <strike>Goose</strike> the Eclipse Webmaster]]
+
[[Image:GitHub-Transfer2.png|center|frame|none|Assign ownership to <strike>Goose</strike> the Eclipse Webmaster]]
  
 
As instructed, type the name of the repository, and enter '''eclipsewebmaster''' as the new owner.
 
As instructed, type the name of the repository, and enter '''eclipsewebmaster''' as the new owner.

Revision as of 11:38, 29 November 2013

Eclipse Foundation-managed GitHub Organizations

The Eclipse Foundation manages several organizations on GitHub; one for each of the forges.

When you move your project to Eclipse, all existing related GitHub repositories must be moved into the corresponding GitHub organization. As part of the intellectual property (IP) due diligence process, each repository's history must be collapsed into a single commit that will be used as the project's initial contribution. The history may remain obscured in the original repository, but it must be hidden from casual attempts to clone or pull.

Moving Existing Repositories

The timing of the move is important. Once you start this process, you and your existing team will not be able to commit to the repository. As your project committers complete their paperwork, they will be given necessary permissions to work with the repository.

Note that the committers listed in your project proposal are permitted to continue working and creating new commits after this process has started. They must follow the Eclipse Foundation's intellectual property due diligence rules from the moment we start the move process.

The first step is to assign ownership of the repository to the Eclipse Foundation's Webmaster.

Use the GitHub web interface to transfer ownership of each project repository to eclipsewebmaster.

For each repository, first locate and click the "Settings"; scroll down to the "Danger Zone".

Ride into the "Danger Zone"

Click "Transfer" in the "Transfer Ownership" block.

Assign ownership to Goose the Eclipse Webmaster

As instructed, type the name of the repository, and enter eclipsewebmaster as the new owner.

Preparing a Repository

GitHubProvisioning1.png

Project Creation

GitHubProvisioning2.png