Jump to: navigation, search

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

(Eclipse Foundation-managed GitHub Organizations)
Line 16: Line 16:
 
#: Wait for the Eclipse Webmaster to take ownership and prepare your repositories
 
#: Wait for the Eclipse Webmaster to take ownership and prepare your repositories
 
# Extract the collapsed history commit (now referenced by the '''eclipse_initial''' tag) from each repository as a ZIP file and submit them collectively as your initial contribution
 
# Extract the collapsed history commit (now referenced by the '''eclipse_initial''' tag) from each repository as a ZIP file and submit them collectively as your initial contribution
 
=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.
 
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.
 +
 +
=Moving Existing Repositories=
  
 
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 [http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf intellectual property due diligence rules] from the moment we start the move process.
 
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 [http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf intellectual property due diligence rules] from the moment we start the move process.
Line 37: Line 37:
 
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.
  
=Preparing a Repository=
+
=Collapsing History=
 +
 
 +
As part of the process of preparing your repository, the Eclipse Webmaster will collapse the history of the project into a single commit. The starting point is the commit identified by the '''eclipse_initial''' tag. The state of the repository represented by that commit is collapsed into a single commit that is then given the '''eclipse_initial''' tag.
 +
 
 +
That single commit will then be the starting point for all development by the project team following the move to Eclipse. This means that exactly one branch will "survive" the move; be sure to either merge other branches before the move, or get used to the thought of not having them.
 +
 
 +
The existing commits will remain in the repository, but they will not be easily reachable. For more information, please see [[https://wiki.eclipse.org/GitHub|Migrating a GitHub Repository]].
 +
 
 +
=Timing=
  
 +
All of the commits
 
[[Image:GitHubProvisioning1.png|600px|center]]
 
[[Image:GitHubProvisioning1.png|600px|center]]
  

Revision as of 12:00, 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.

  1. Tag your "initial contribution" commit as eclipse_initial
  2. Complete the New Project Provisioning Request (NPPR) form
    You will be sent a link when your project's creation review is complete
    Be sure to select "GitHub" in the "Code Repository" section
  3. Assign ownership of all project-related repositories to eclipsewebmaster
    Wait for the Eclipse Webmaster to take ownership and prepare your repositories
  4. Extract the collapsed history commit (now referenced by the eclipse_initial tag) from each repository as a ZIP file and submit them collectively as your initial contribution

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.

Moving Existing Repositories

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.

Collapsing History

As part of the process of preparing your repository, the Eclipse Webmaster will collapse the history of the project into a single commit. The starting point is the commit identified by the eclipse_initial tag. The state of the repository represented by that commit is collapsed into a single commit that is then given the eclipse_initial tag.

That single commit will then be the starting point for all development by the project team following the move to Eclipse. This means that exactly one branch will "survive" the move; be sure to either merge other branches before the move, or get used to the thought of not having them.

The existing commits will remain in the repository, but they will not be easily reachable. For more information, please see [a GitHub Repository].

Timing

All of the commits

GitHubProvisioning1.png

Project Creation

GitHubProvisioning2.png