You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Shazron <sh...@gmail.com> on 2017/06/05 23:41:46 UTC
[NOTICE] Intent on moving to Github
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?
Re: [NOTICE] Intent on moving to Github
Posted by Shazron <sh...@gmail.com>.
I created this Discuss document regarding which platforms/plugins are
moving:
https://github.com/cordova/cordova-discuss/blob/master/proposals/GithubMove.md
On Tue, Jun 13, 2017 at 12:57 PM, Shazron <sh...@gmail.com> wrote:
> Thanks Carlos.
>
> I just filed https://issues.apache.org/jira/browse/INFRA-14347 so watch
> that issue :)
>
> On Wed, Jun 7, 2017 at 6:01 AM, Filip Maj <ma...@gmail.com> wrote:
>
>> That's really helpful Carlos, thanks!
>>
>> On Wed, Jun 7, 2017 at 12:47 AM, Steven Gill <st...@gmail.com>
>> wrote:
>> > Thanks Carlos! Very useful information!
>> >
>> > On Tue, Jun 6, 2017 at 5:28 PM, Carlos Santana <cs...@gmail.com>
>> wrote:
>> >
>> >> 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 <st...@gmail.com>
>> wrote:
>> >>
>> >> > Yay! Hope ASF allows us to finally do this!
>> >> >
>> >> > On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj <ma...@gmail.com> wrote:
>> >> >
>> >> > > My one comment is OMG YISS!
>> >> > >
>> >> > > On Mon, Jun 5, 2017 at 6:41 PM, Shazron <sh...@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-unsubscribe@cordova.apache.org
>> >> > > For additional commands, e-mail: dev-help@cordova.apache.org
>> >> > >
>> >> > >
>> >> >
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
>
Re: [NOTICE] Intent on moving to Github
Posted by Shazron <sh...@gmail.com>.
Thanks Carlos.
I just filed https://issues.apache.org/jira/browse/INFRA-14347 so watch
that issue :)
On Wed, Jun 7, 2017 at 6:01 AM, Filip Maj <ma...@gmail.com> wrote:
> That's really helpful Carlos, thanks!
>
> On Wed, Jun 7, 2017 at 12:47 AM, Steven Gill <st...@gmail.com>
> wrote:
> > Thanks Carlos! Very useful information!
> >
> > On Tue, Jun 6, 2017 at 5:28 PM, Carlos Santana <cs...@gmail.com>
> wrote:
> >
> >> 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 <st...@gmail.com>
> wrote:
> >>
> >> > Yay! Hope ASF allows us to finally do this!
> >> >
> >> > On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj <ma...@gmail.com> wrote:
> >> >
> >> > > My one comment is OMG YISS!
> >> > >
> >> > > On Mon, Jun 5, 2017 at 6:41 PM, Shazron <sh...@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-unsubscribe@cordova.apache.org
> >> > > For additional commands, e-mail: dev-help@cordova.apache.org
> >> > >
> >> > >
> >> >
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [NOTICE] Intent on moving to Github
Posted by Filip Maj <ma...@gmail.com>.
That's really helpful Carlos, thanks!
On Wed, Jun 7, 2017 at 12:47 AM, Steven Gill <st...@gmail.com> wrote:
> Thanks Carlos! Very useful information!
>
> On Tue, Jun 6, 2017 at 5:28 PM, Carlos Santana <cs...@gmail.com> wrote:
>
>> 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 <st...@gmail.com> wrote:
>>
>> > Yay! Hope ASF allows us to finally do this!
>> >
>> > On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj <ma...@gmail.com> wrote:
>> >
>> > > My one comment is OMG YISS!
>> > >
>> > > On Mon, Jun 5, 2017 at 6:41 PM, Shazron <sh...@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-unsubscribe@cordova.apache.org
>> > > For additional commands, e-mail: dev-help@cordova.apache.org
>> > >
>> > >
>> >
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [NOTICE] Intent on moving to Github
Posted by Steven Gill <st...@gmail.com>.
Thanks Carlos! Very useful information!
On Tue, Jun 6, 2017 at 5:28 PM, Carlos Santana <cs...@gmail.com> wrote:
> 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 <st...@gmail.com> wrote:
>
> > Yay! Hope ASF allows us to finally do this!
> >
> > On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj <ma...@gmail.com> wrote:
> >
> > > My one comment is OMG YISS!
> > >
> > > On Mon, Jun 5, 2017 at 6:41 PM, Shazron <sh...@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-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
> >
>
Re: [NOTICE] Intent on moving to Github
Posted by Carlos Santana <cs...@gmail.com>.
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 <st...@gmail.com> wrote:
> Yay! Hope ASF allows us to finally do this!
>
> On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj <ma...@gmail.com> wrote:
>
> > My one comment is OMG YISS!
> >
> > On Mon, Jun 5, 2017 at 6:41 PM, Shazron <sh...@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-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
Re: [NOTICE] Intent on moving to Github
Posted by Steven Gill <st...@gmail.com>.
Yay! Hope ASF allows us to finally do this!
On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj <ma...@gmail.com> wrote:
> My one comment is OMG YISS!
>
> On Mon, Jun 5, 2017 at 6:41 PM, Shazron <sh...@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-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [NOTICE] Intent on moving to Github
Posted by Filip Maj <ma...@gmail.com>.
My one comment is OMG YISS!
On Mon, Jun 5, 2017 at 6:41 PM, Shazron <sh...@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-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org