Jump to: navigation, search

Difference between revisions of "Git/External Mirrors"

< Git
(Teams)
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
Eclipse uses GitHub as a source of mirrors.
 
Eclipse uses GitHub as a source of mirrors.
     https://github.com/organizations/eclipse
+
     https://github.com/eclipse
  
We populate the information from a script that runs over the portal.eclipse.org metadata
+
GitHub populates the mirrors from a script that generates a list of repositories from project metadata:
 
     http://eclipse.org/projects/git-repos.php
 
     http://eclipse.org/projects/git-repos.php
 +
 +
The script is run manually on a periodic basis. We nudge GitHub every once-in-a-while (monthly or so) to run the script and update the mirrors. If your repository has not been mirrored, open a bug against Eclipse Foundation/Community/Git to ask us to initiate a nudge. Do not expect us to badger the nice folks at GitHub daily or in a piecemeal manner. We won't do it.
  
 
The script uses the project metadata as specified in the [http://portal.eclipse.org Developer Portal]. The implementation is quite robust; you can specify your project's Git repositories (one per line) in any of the following formats:
 
The script uses the project metadata as specified in the [http://portal.eclipse.org Developer Portal]. The implementation is quite robust; you can specify your project's Git repositories (one per line) in any of the following formats:
Line 10: Line 12:
 
* */gitroot/*
 
* */gitroot/*
 
* <nowiki>http://git.eclipse.org/c/*</nowiki>
 
* <nowiki>http://git.eclipse.org/c/*</nowiki>
 +
 +
(Note that you'll have to replace the wildcards above with absolute values for each of your project's repositories; '''do not include wildcard characters in the values you specify''').
  
 
Example:
 
Example:
Line 16: Line 20:
  
 
The script (and other uses of this information at eclipse.org) will normalize the value you provide into an appropriate value.
 
The script (and other uses of this information at eclipse.org) will normalize the value you provide into an appropriate value.
 +
 +
==Teams==
 +
If you actually want to push and pull into a GitHub repository, we'll need to make a team for your project. Open a bug against Community/Git and we'll help you out. Note that we can set up a GitHub team and can make changes here and there, but we are unable to automatically mirror changes in the project committers at this time.
 +
 +
The GitHub mirror is not strictly subject to the same access restrictions as the eclipse.org repositories. The Eclipse Foundation considers the GitHub teams to be self-regulating. We will help where we can, but the GitHub mirrors are not considered to be eclipse.org property. If there are problems within the teams, they can be addressed by the Eclipse Organization's GitHub administrators (one of whom is conveniently a member of the Eclipse Foundation staff).
 +
 +
For Eclipse projects, the Git repository on eclipse.org must be considered the "central" or "main" repository for the project code. Contributions can be accepted into the GitHub mirror, but anything that flows back into the equivalent eclipse.org repository is subject to the Eclipse IP Due Diligence Process.
 +
 +
[[Category:Git]][[Category:Portal]]

Revision as of 11:35, 19 November 2012

Eclipse uses GitHub as a source of mirrors.

    https://github.com/eclipse

GitHub populates the mirrors from a script that generates a list of repositories from project metadata:

    http://eclipse.org/projects/git-repos.php

The script is run manually on a periodic basis. We nudge GitHub every once-in-a-while (monthly or so) to run the script and update the mirrors. If your repository has not been mirrored, open a bug against Eclipse Foundation/Community/Git to ask us to initiate a nudge. Do not expect us to badger the nice folks at GitHub daily or in a piecemeal manner. We won't do it.

The script uses the project metadata as specified in the Developer Portal. The implementation is quite robust; you can specify your project's Git repositories (one per line) in any of the following formats:

(Note that you'll have to replace the wildcards above with absolute values for each of your project's repositories; do not include wildcard characters in the values you specify).

Example:

Git-repo-list.png

The script (and other uses of this information at eclipse.org) will normalize the value you provide into an appropriate value.

Teams

If you actually want to push and pull into a GitHub repository, we'll need to make a team for your project. Open a bug against Community/Git and we'll help you out. Note that we can set up a GitHub team and can make changes here and there, but we are unable to automatically mirror changes in the project committers at this time.

The GitHub mirror is not strictly subject to the same access restrictions as the eclipse.org repositories. The Eclipse Foundation considers the GitHub teams to be self-regulating. We will help where we can, but the GitHub mirrors are not considered to be eclipse.org property. If there are problems within the teams, they can be addressed by the Eclipse Organization's GitHub administrators (one of whom is conveniently a member of the Eclipse Foundation staff).

For Eclipse projects, the Git repository on eclipse.org must be considered the "central" or "main" repository for the project code. Contributions can be accepted into the GitHub mirror, but anything that flows back into the equivalent eclipse.org repository is subject to the Eclipse IP Due Diligence Process.