So, I've changed jclouds into an org and folks should have access to make changes needed to redirect repos and run the project with minimal changes for now.
It seems clear from others there's no sense in making new orgs, so let's drop the idea. Thanks for the participation folks! -A On Mon, May 6, 2013 at 9:46 AM, Adrian Cole <[email protected]> wrote: > Hi, team. > > Folks have expressed interest in continuing use of github for the purpose > of review. I've discussed a plan for how we can transition and figured it > best to repost it here. The idea is to have a place for legacy code > updates to occur from until the end of the year, and make space for the > next line of collaboration. > > Current status: > > jclouds on github is an account controlled only by me. This includes the > repositories being imported into the ASF prefixed with incubator- > > Ideal status (subject to debate): > > jclouds on github is an org with representative members correlating to the > PPMC. It contains forked repositories from the authoritative sources in > apache. > jclouds-legacy on github is an org with representative members correlating > to the PPMC. Its repositories are the old ones, which were transferred to > it. These repositories and the account are marked as deprecated. > > I've already provisioned the org jclouds-legacy, and migrating repos to it > is pretty trivial. Converting the existing jclouds account to an org is > very easy. In other words, this process from a technical POV is stupidly > simple. > > This all in mind, let's chat about any blocking concerns. If there aren't > any, we should start the process so that we can start using github as a > collaboration point for code updates into the ASF. > > you're on! >
