ASF will allow it, other projects already showed interest and at ApacheCon they made it public that they will allow it to any project
My incubator project OpenWhisk is the first one to work out all the kinks For now let know everyone that wants write access, specially those that are repo owners and usually in charge of merging PRs to: 1. associate your github id in id.apache.org profile 2. enable 2FA in Github.com 3. show up properly under whimsy https://whimsy.apache.org/roster/committee/cordova Once the repos are transferred, a Github team will be created cordova-committers and folks that go thru gitbox setup will be added to this team, this team will have write access to all github.com/apache/cordova* repos Once transferred need to make it clear to all committers to reconfigure their git upstream, and no longer write to git-wip other projects that moved over like traffic server, went ahead and migrated all the JIRA Issues to Github Issues, a topic for another thread :-) let me know how I can help, will be glad --Carlos On Tue, Jun 6, 2017 at 6:30 PM Steven Gill <stevengil...@gmail.com> wrote: > Yay! Hope ASF allows us to finally do this! > > On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj <maj....@gmail.com> wrote: > > > My one comment is OMG YISS! > > > > On Mon, Jun 5, 2017 at 6:41 PM, Shazron <shaz...@gmail.com> wrote: > > > The Apache Cordova Project Management Committee (PMC) has consensus > that > > we > > > should move primary development of Apache Cordova to Github, from > > Apache's > > > servers (role would be reversed, Apache would then be the mirror now). > > > > > > We are already processing pull requests through Github, although > without > > > write access we couldn't label, or close PRs directly. Enabling of > Issues > > > in Github (to replace JIRA) would be a separate matter, and would > likely > > be > > > on a per-repo basis. > > > > > > Moving is achieved by invitation to the Apache Gitbox project: > > > https://gitbox.apache.org/ (don't get excited if you can log in and > > link, > > > your repo needs to be whitelisted) > > > > > > We would have to file INFRA issues in JIRA to get approval for the > move. > > > > > > We are suggesting a multi-part migration: > > > > > > 1. Top platforms (ios, android, windows, browser) > > > 2. Tools (lib, cli, coho, fetch, common etc) --> we might need a lib > > > breakout first, this is ongoing work > > > 3. All plugins > > > > > > The rest would be on a "as needed" basis. > > > > > > Comments, if any? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
