Jump to: navigation, search

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

(Moving Existing Repositories)
(Eclipse Foundation-managed GitHub Organizations)
Line 8: Line 8:
  
 
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 [[Development Resources/Initial Contribution|initial contribution]]. The history may remain obscured in the original repository, but it must be hidden from casual attempts to clone or pull.
 
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 [[Development Resources/Initial Contribution|initial contribution]]. The history may remain obscured in the original repository, but it must be hidden from casual attempts to clone or pull.
 +
 +
# Tag your "initial contribution" commit as '''eclipse_initial'''
 +
# Complete the New Project Provisioning Request (NPPR) form
 +
#: You will be sent a link when your project's creation review is complete
 +
# Assign ownership of your project repositories to '''eclipsewebmaster'''
 +
#: Wait for the Eclipse Webmaster to take ownership and prepare your repository
 +
# Extract the collapsed history commit (now referenced by the '''eclipse_initial''' tag) as a ZIP file and submit it as your initial contribution
  
 
=Moving Existing Repositories=
 
=Moving Existing Repositories=

Revision as of 12:45, 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
  3. Assign ownership of your project repositories to eclipsewebmaster
    Wait for the Eclipse Webmaster to take ownership and prepare your repository
  4. Extract the collapsed history commit (now referenced by the eclipse_initial tag) as a ZIP file and submit it 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.

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