Hi Nick, To give you an alternative:
* Use the ASF incubator Git repo servers as the primary * Use the GitHub mirror process to share a mirror of milagro (this is read only) * Community members raise PR's on GitHub * Committers download patches from the PR and use 'git am' to apply the patch to a local copy then push to the ASF git server E.g. https://github.com/apache/libcloud This gives you the community visibility and engagement but keeps the source controlled within the ASF servers and credentials. This is a typical process for other TLPs Anthony On Fri, Jan 29, 2016 at 2:55 AM, Nick Kew <[email protected]> wrote: > Sorry folks, I've been out of action with a Lurgy. > Trying to catch up on the backlog. > > We have a chicken-and-egg situation with setting > up a Git repo, which should be the last of the > main bootstrapping tasks before we can properly > get going. > > In setting up a git repo, we have the option to > import an existing repo. I'd like to use that to > import from github (and request apache<->github > mirroring so github users can work there, submit > pull requests, etc). But to do so, I need to know > exactly what's to be imported, and that we have a > software grant for it. > > Alternatively, if there isn't a direct correspondence > to existing github/Certivox/ repos, we can create a > new empty repo and import stuff manually. > > What's the current situation with the repos at github? > > -- > Nick Kew
