You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Joe Bowser <bo...@gmail.com> on 2012/01/03 20:08:16 UTC
Cordova-Android now up-to-date in the ASF Git Repo
Hey
I've synced up the changes for Cordova-Android, and after going through the
process, I think it makes sense if each platform maintainer just does a
push up to their respective repositories the changes that they have been
maintaining to date. This way, we can be sure that most people are set up
to commit to the new repositories, and I won't have to sift through things
that I'm unfamiliar with. I see that Patrick has already done this with
weinre, which tipped me off.
Are we doing this right?
Joe
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Bryce Curtis <cu...@gmail.com>.
Olivier,
I took a look at your pull request and commented on it. I will create
cordova-android on github today, so you can do a new pull request on
that repository.
Bryce
On 1/4/12 9:48 AM, Olivier Brand wrote:
> All,
>
> I have a pull request in callback android. What should we/ you do?
>
> Olivier
>
> Olivier
>
> On Jan 3, 2012, at 12:04, Simon MacDonald<si...@gmail.com> wrote:
>
>> I've been able to setup and build cordova-android. Wondering the same
>> thing as Bryce, how do we handle pull requests, etc?
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>>
>>
>> On Tue, Jan 3, 2012 at 2:56 PM, Bryce Curtis<cu...@gmail.com> wrote:
>>> I was able to set up git and clone, so Android must be good. Are we ready
>>> to use the apache git for commits from now on? How are pull requests made
>>> and what is the easiest way to commit/approve them?
>>>
>>>
>>> On 1/3/12 1:27 PM, Patrick Mueller wrote:
>>>> On Tue, Jan 3, 2012 at 14:08, Joe Bowser<bo...@gmail.com> wrote:
>>>>
>>>>> I've synced up the changes for Cordova-Android, and after going through
>>>>> the
>>>>> process, I think it makes sense if each platform maintainer just does a
>>>>> push up to their respective repositories the changes that they have been
>>>>> maintaining to date. This way, we can be sure that most people are set
>>>>> up
>>>>> to commit to the new repositories, and I won't have to sift through
>>>>> things
>>>>> that I'm unfamiliar with. I see that Patrick has already done this with
>>>>> weinre, which tipped me off.
>>>>>
>>>>> Are we doing this right?
>>>>
>>>> I think this is exactly what we want to do, modulo having to do global
>>>> "mark read"s on the torrent of emails flowing into my new filtered
>>>> "commits" label in GMail. :-) Would be nice to get a single push's
>>>> commit's bundled into one message, but I reckon this flood is a one-time
>>>> thing, so ... no worries.
>>>>
>>>> Actually, just checked the email, and they're coming from "
>>>> callback-commits@incubator.apache.org" - I suppose we should create new
>>>> ml's for the 3 "callback" ml's we have, to "cordova" ones.
>>>>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Olivier Brand <ol...@passbox.com>.
All,
I have a pull request in callback android. What should we/ you do?
Olivier
Olivier
On Jan 3, 2012, at 12:04, Simon MacDonald <si...@gmail.com> wrote:
> I've been able to setup and build cordova-android. Wondering the same
> thing as Bryce, how do we handle pull requests, etc?
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
>
> On Tue, Jan 3, 2012 at 2:56 PM, Bryce Curtis <cu...@gmail.com> wrote:
>> I was able to set up git and clone, so Android must be good. Are we ready
>> to use the apache git for commits from now on? How are pull requests made
>> and what is the easiest way to commit/approve them?
>>
>>
>> On 1/3/12 1:27 PM, Patrick Mueller wrote:
>>>
>>> On Tue, Jan 3, 2012 at 14:08, Joe Bowser<bo...@gmail.com> wrote:
>>>
>>>> I've synced up the changes for Cordova-Android, and after going through
>>>> the
>>>> process, I think it makes sense if each platform maintainer just does a
>>>> push up to their respective repositories the changes that they have been
>>>> maintaining to date. This way, we can be sure that most people are set
>>>> up
>>>> to commit to the new repositories, and I won't have to sift through
>>>> things
>>>> that I'm unfamiliar with. I see that Patrick has already done this with
>>>> weinre, which tipped me off.
>>>>
>>>> Are we doing this right?
>>>
>>>
>>> I think this is exactly what we want to do, modulo having to do global
>>> "mark read"s on the torrent of emails flowing into my new filtered
>>> "commits" label in GMail. :-) Would be nice to get a single push's
>>> commit's bundled into one message, but I reckon this flood is a one-time
>>> thing, so ... no worries.
>>>
>>> Actually, just checked the email, and they're coming from "
>>> callback-commits@incubator.apache.org" - I suppose we should create new
>>> ml's for the 3 "callback" ml's we have, to "cordova" ones.
>>>
>>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Simon MacDonald <si...@gmail.com>.
I've been able to setup and build cordova-android. Wondering the same
thing as Bryce, how do we handle pull requests, etc?
Simon Mac Donald
http://hi.im/simonmacdonald
On Tue, Jan 3, 2012 at 2:56 PM, Bryce Curtis <cu...@gmail.com> wrote:
> I was able to set up git and clone, so Android must be good. Are we ready
> to use the apache git for commits from now on? How are pull requests made
> and what is the easiest way to commit/approve them?
>
>
> On 1/3/12 1:27 PM, Patrick Mueller wrote:
>>
>> On Tue, Jan 3, 2012 at 14:08, Joe Bowser<bo...@gmail.com> wrote:
>>
>>> I've synced up the changes for Cordova-Android, and after going through
>>> the
>>> process, I think it makes sense if each platform maintainer just does a
>>> push up to their respective repositories the changes that they have been
>>> maintaining to date. This way, we can be sure that most people are set
>>> up
>>> to commit to the new repositories, and I won't have to sift through
>>> things
>>> that I'm unfamiliar with. I see that Patrick has already done this with
>>> weinre, which tipped me off.
>>>
>>> Are we doing this right?
>>
>>
>> I think this is exactly what we want to do, modulo having to do global
>> "mark read"s on the torrent of emails flowing into my new filtered
>> "commits" label in GMail. :-) Would be nice to get a single push's
>> commit's bundled into one message, but I reckon this flood is a one-time
>> thing, so ... no worries.
>>
>> Actually, just checked the email, and they're coming from "
>> callback-commits@incubator.apache.org" - I suppose we should create new
>> ml's for the 3 "callback" ml's we have, to "cordova" ones.
>>
>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Andrew Lunny <al...@gmail.com>.
On 3 January 2012 11:56, Bryce Curtis <cu...@gmail.com> wrote:
> I was able to set up git and clone, so Android must be good. Are we ready
> to use the apache git for commits from now on? How are pull requests made
> and what is the easiest way to commit/approve them?
I'm not sure if JIRA supports anything close to pull requests - I have a
couple of PATCH issues here:
https://issues.apache.org/jira/browse/CB-146
https://issues.apache.org/jira/browse/CB-147
The patch files were generated by git format-patch. They can be applied by
running "git am", eg
cd cordova-android
git am 0001-adding-JUnit-dependency.patch
>
>
> On 1/3/12 1:27 PM, Patrick Mueller wrote:
>
>> On Tue, Jan 3, 2012 at 14:08, Joe Bowser<bo...@gmail.com> wrote:
>>
>> I've synced up the changes for Cordova-Android, and after going through
>>> the
>>> process, I think it makes sense if each platform maintainer just does a
>>> push up to their respective repositories the changes that they have been
>>> maintaining to date. This way, we can be sure that most people are set
>>> up
>>> to commit to the new repositories, and I won't have to sift through
>>> things
>>> that I'm unfamiliar with. I see that Patrick has already done this with
>>> weinre, which tipped me off.
>>>
>>> Are we doing this right?
>>>
>>
>> I think this is exactly what we want to do, modulo having to do global
>> "mark read"s on the torrent of emails flowing into my new filtered
>> "commits" label in GMail. :-) Would be nice to get a single push's
>> commit's bundled into one message, but I reckon this flood is a one-time
>> thing, so ... no worries.
>>
>> Actually, just checked the email, and they're coming from "
>> callback-commits@incubator.**apache.org<ca...@incubator.apache.org>"
>> - I suppose we should create new
>> ml's for the 3 "callback" ml's we have, to "cordova" ones.
>>
>>
>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Patrick Mueller <pm...@gmail.com>.
On Tue, Jan 3, 2012 at 15:12, Brian LeRoux <b...@brian.io> wrote:
> my plan to spend some time updating our wiki w/ our process.
> essentially its the same as today except we treat the ASF repo as
> canonical, review commits from outside and ensure they have a CLA, etc
So do day-to-day work against GitHub repos, then when ready to go into
Apache, get reviewed, then pull/push the commits?
I think there are apache svn repos shadowed at GitHub. Assuming we could
do something similar with the ASF git repo (ie, shadow it to GitHub), could
this take the place of a new set of GitHub repos?
--
Patrick Mueller
http://muellerware.org
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Filip Maj <fi...@adobe.com>.
BlackBerry is up to date as well.
On 12-01-03 12:12 PM, "Brian LeRoux" <b...@brian.io> wrote:
>my plan to spend some time updating our wiki w/ our process.
>essentially its the same as today except we treat the ASF repo as
>canonical, review commits from outside and ensure they have a CLA, etc
>
>On Tue, Jan 3, 2012 at 11:56 AM, Bryce Curtis <cu...@gmail.com>
>wrote:
>> I was able to set up git and clone, so Android must be good. Are we
>>ready
>> to use the apache git for commits from now on? How are pull requests
>>made
>> and what is the easiest way to commit/approve them?
>>
>>
>> On 1/3/12 1:27 PM, Patrick Mueller wrote:
>>>
>>> On Tue, Jan 3, 2012 at 14:08, Joe Bowser<bo...@gmail.com> wrote:
>>>
>>>> I've synced up the changes for Cordova-Android, and after going
>>>>through
>>>> the
>>>> process, I think it makes sense if each platform maintainer just does
>>>>a
>>>> push up to their respective repositories the changes that they have
>>>>been
>>>> maintaining to date. This way, we can be sure that most people are
>>>>set
>>>> up
>>>> to commit to the new repositories, and I won't have to sift through
>>>> things
>>>> that I'm unfamiliar with. I see that Patrick has already done this
>>>>with
>>>> weinre, which tipped me off.
>>>>
>>>> Are we doing this right?
>>>
>>>
>>> I think this is exactly what we want to do, modulo having to do global
>>> "mark read"s on the torrent of emails flowing into my new filtered
>>> "commits" label in GMail. :-) Would be nice to get a single push's
>>> commit's bundled into one message, but I reckon this flood is a
>>>one-time
>>> thing, so ... no worries.
>>>
>>> Actually, just checked the email, and they're coming from "
>>> callback-commits@incubator.apache.org" - I suppose we should create new
>>> ml's for the 3 "callback" ml's we have, to "cordova" ones.
>>>
>>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Brian LeRoux <b...@brian.io>.
my plan to spend some time updating our wiki w/ our process.
essentially its the same as today except we treat the ASF repo as
canonical, review commits from outside and ensure they have a CLA, etc
On Tue, Jan 3, 2012 at 11:56 AM, Bryce Curtis <cu...@gmail.com> wrote:
> I was able to set up git and clone, so Android must be good. Are we ready
> to use the apache git for commits from now on? How are pull requests made
> and what is the easiest way to commit/approve them?
>
>
> On 1/3/12 1:27 PM, Patrick Mueller wrote:
>>
>> On Tue, Jan 3, 2012 at 14:08, Joe Bowser<bo...@gmail.com> wrote:
>>
>>> I've synced up the changes for Cordova-Android, and after going through
>>> the
>>> process, I think it makes sense if each platform maintainer just does a
>>> push up to their respective repositories the changes that they have been
>>> maintaining to date. This way, we can be sure that most people are set
>>> up
>>> to commit to the new repositories, and I won't have to sift through
>>> things
>>> that I'm unfamiliar with. I see that Patrick has already done this with
>>> weinre, which tipped me off.
>>>
>>> Are we doing this right?
>>
>>
>> I think this is exactly what we want to do, modulo having to do global
>> "mark read"s on the torrent of emails flowing into my new filtered
>> "commits" label in GMail. :-) Would be nice to get a single push's
>> commit's bundled into one message, but I reckon this flood is a one-time
>> thing, so ... no worries.
>>
>> Actually, just checked the email, and they're coming from "
>> callback-commits@incubator.apache.org" - I suppose we should create new
>> ml's for the 3 "callback" ml's we have, to "cordova" ones.
>>
>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Bryce Curtis <cu...@gmail.com>.
I was able to set up git and clone, so Android must be good. Are we
ready to use the apache git for commits from now on? How are pull
requests made and what is the easiest way to commit/approve them?
On 1/3/12 1:27 PM, Patrick Mueller wrote:
> On Tue, Jan 3, 2012 at 14:08, Joe Bowser<bo...@gmail.com> wrote:
>
>> I've synced up the changes for Cordova-Android, and after going through the
>> process, I think it makes sense if each platform maintainer just does a
>> push up to their respective repositories the changes that they have been
>> maintaining to date. This way, we can be sure that most people are set up
>> to commit to the new repositories, and I won't have to sift through things
>> that I'm unfamiliar with. I see that Patrick has already done this with
>> weinre, which tipped me off.
>>
>> Are we doing this right?
>
> I think this is exactly what we want to do, modulo having to do global
> "mark read"s on the torrent of emails flowing into my new filtered
> "commits" label in GMail. :-) Would be nice to get a single push's
> commit's bundled into one message, but I reckon this flood is a one-time
> thing, so ... no worries.
>
> Actually, just checked the email, and they're coming from "
> callback-commits@incubator.apache.org" - I suppose we should create new
> ml's for the 3 "callback" ml's we have, to "cordova" ones.
>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Patrick Mueller <pm...@gmail.com>.
On Tue, Jan 3, 2012 at 14:08, Joe Bowser <bo...@gmail.com> wrote:
> I've synced up the changes for Cordova-Android, and after going through the
> process, I think it makes sense if each platform maintainer just does a
> push up to their respective repositories the changes that they have been
> maintaining to date. This way, we can be sure that most people are set up
> to commit to the new repositories, and I won't have to sift through things
> that I'm unfamiliar with. I see that Patrick has already done this with
> weinre, which tipped me off.
>
> Are we doing this right?
I think this is exactly what we want to do, modulo having to do global
"mark read"s on the torrent of emails flowing into my new filtered
"commits" label in GMail. :-) Would be nice to get a single push's
commit's bundled into one message, but I reckon this flood is a one-time
thing, so ... no worries.
Actually, just checked the email, and they're coming from "
callback-commits@incubator.apache.org" - I suppose we should create new
ml's for the 3 "callback" ml's we have, to "cordova" ones.
--
Patrick Mueller
http://muellerware.org
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Patrick Mueller <pm...@gmail.com>.
On Tue, Jan 3, 2012 at 14:08, Joe Bowser <bo...@gmail.com> wrote:
> Hey
>
Another thing folks might want to do is change their git email address to
their apache.org email address. I would assume, at some point, we will
turn back on "committer must have an apache email address" commit checks.
Might as well get ready for it.
Instructions here: https://git-wip-us.apache.org/
I went ahead and changed my global git config; then added my
apache.orgemail address to GitHub, and also added that email address
to gravatar :-)
--
Patrick Mueller
http://muellerware.org
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Filip Maj <fi...@adobe.com>.
>> Is there a reason to move everything over to the github.com/cordova
>> organization? From my understanding the Apache git repo will be mirrored
>> over to github.com/apache - and will have other niceties like
>> automatically forwarding pull requests to the Apache dev mailing list
>>for
>> us.
>>
>
>Agree. There's definitely benefit to having fewer repositories/web
>sites/organization roles to deal with, if we can avoid it.
>
>The question is, what do we lose by NOT having a github/cordova
>organization/repos. And surely, we can create one later, if we really
>need
>one, right?
I think the most important thing is a point of interaction for the rest of
our community specifically within GitHub. Apache has already set up the
pull request niceties, etc. The move from github.com/phonegap to /callback
didn't hurt our community *that* badly, so doing one more should be
alright, too.
I don't think we lose anything.
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Patrick Mueller <pm...@gmail.com>.
On Wed, Jan 4, 2012 at 17:43, Filip Maj <fi...@adobe.com> wrote:
> Is there a reason to move everything over to the github.com/cordova
> organization? From my understanding the Apache git repo will be mirrored
> over to github.com/apache - and will have other niceties like
> automatically forwarding pull requests to the Apache dev mailing list for
> us.
>
Agree. There's definitely benefit to having fewer repositories/web
sites/organization roles to deal with, if we can avoid it.
The question is, what do we lose by NOT having a github/cordova
organization/repos. And surely, we can create one later, if we really need
one, right?
--
Patrick Mueller
http://muellerware.org
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Filip Maj <fi...@adobe.com>.
Is there a reason to move everything over to the github.com/cordova
organization? From my understanding the Apache git repo will be mirrored
over to github.com/apache - and will have other niceties like
automatically forwarding pull requests to the Apache dev mailing list for
us.
In the coming weeks we'll be moving everything over to the Apache
organization anyways right?
On 12-01-04 2:00 PM, "Shazron" <sh...@gmail.com> wrote:
>Sigh - I screwed up again. Will fix
>
>On Wed, Jan 4, 2012 at 1:49 PM, Becky Gibson <gi...@gmail.com>
>wrote:
>> Hmm, seems like more than the tags are missing in the cordova-ios repo
>>- I
>> don't see any directories. And the readme looks like what it should be
>>for
>> callback, NOT cordova???
>>
>> -becky
>>
>> On Wed, Jan 4, 2012 at 4:04 PM, Shazron <sh...@gmail.com> wrote:
>>
>>> Oops, I missed that for cordova-ios. Fixed.
>>>
>>> On Wed, Jan 4, 2012 at 12:58 PM, Bryce Curtis <cu...@gmail.com>
>>> wrote:
>>> > Should tags be copied over too?
>>> >
>>> >
>>> > On 1/3/12 2:50 PM, Shazron wrote:
>>> >>
>>> >> I'll start with moving callback/callback-ios to cordova/cordova-ios
>>> >> today and pushing issues to Jira and closing the issues in
>>> >> callback-ios
>>> >>
>>> >> On Tue, Jan 3, 2012 at 11:19 AM, Brian LeRoux<b...@brian.io> wrote:
>>> >>>
>>> >>> yes --- we should retire the github.com/callback and get
>>> >>> github.com/cordova going too
>>> >>>
>>> >>> anyone want to tack that? I can add you to the org
>>> >>>
>>> >>> On Tue, Jan 3, 2012 at 11:08 AM, Joe Bowser<bo...@gmail.com>
>>>wrote:
>>> >>>>
>>> >>>> Hey
>>> >>>>
>>> >>>> I've synced up the changes for Cordova-Android, and after going
>>> through
>>> >>>> the
>>> >>>> process, I think it makes sense if each platform maintainer just
>>>does
>>> a
>>> >>>> push up to their respective repositories the changes that they
>>>have
>>> been
>>> >>>> maintaining to date. This way, we can be sure that most people
>>>are
>>> set
>>> >>>> up
>>> >>>> to commit to the new repositories, and I won't have to sift
>>>through
>>> >>>> things
>>> >>>> that I'm unfamiliar with. I see that Patrick has already done
>>>this
>>> with
>>> >>>> weinre, which tipped me off.
>>> >>>>
>>> >>>> Are we doing this right?
>>> >>>>
>>> >>>> Joe
>>> >
>>> >
>>>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Shazron <sh...@gmail.com>.
Sigh - I screwed up again. Will fix
On Wed, Jan 4, 2012 at 1:49 PM, Becky Gibson <gi...@gmail.com> wrote:
> Hmm, seems like more than the tags are missing in the cordova-ios repo - I
> don't see any directories. And the readme looks like what it should be for
> callback, NOT cordova???
>
> -becky
>
> On Wed, Jan 4, 2012 at 4:04 PM, Shazron <sh...@gmail.com> wrote:
>
>> Oops, I missed that for cordova-ios. Fixed.
>>
>> On Wed, Jan 4, 2012 at 12:58 PM, Bryce Curtis <cu...@gmail.com>
>> wrote:
>> > Should tags be copied over too?
>> >
>> >
>> > On 1/3/12 2:50 PM, Shazron wrote:
>> >>
>> >> I'll start with moving callback/callback-ios to cordova/cordova-ios
>> >> today and pushing issues to Jira and closing the issues in
>> >> callback-ios
>> >>
>> >> On Tue, Jan 3, 2012 at 11:19 AM, Brian LeRoux<b...@brian.io> wrote:
>> >>>
>> >>> yes --- we should retire the github.com/callback and get
>> >>> github.com/cordova going too
>> >>>
>> >>> anyone want to tack that? I can add you to the org
>> >>>
>> >>> On Tue, Jan 3, 2012 at 11:08 AM, Joe Bowser<bo...@gmail.com> wrote:
>> >>>>
>> >>>> Hey
>> >>>>
>> >>>> I've synced up the changes for Cordova-Android, and after going
>> through
>> >>>> the
>> >>>> process, I think it makes sense if each platform maintainer just does
>> a
>> >>>> push up to their respective repositories the changes that they have
>> been
>> >>>> maintaining to date. This way, we can be sure that most people are
>> set
>> >>>> up
>> >>>> to commit to the new repositories, and I won't have to sift through
>> >>>> things
>> >>>> that I'm unfamiliar with. I see that Patrick has already done this
>> with
>> >>>> weinre, which tipped me off.
>> >>>>
>> >>>> Are we doing this right?
>> >>>>
>> >>>> Joe
>> >
>> >
>>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Becky Gibson <gi...@gmail.com>.
Hmm, seems like more than the tags are missing in the cordova-ios repo - I
don't see any directories. And the readme looks like what it should be for
callback, NOT cordova???
-becky
On Wed, Jan 4, 2012 at 4:04 PM, Shazron <sh...@gmail.com> wrote:
> Oops, I missed that for cordova-ios. Fixed.
>
> On Wed, Jan 4, 2012 at 12:58 PM, Bryce Curtis <cu...@gmail.com>
> wrote:
> > Should tags be copied over too?
> >
> >
> > On 1/3/12 2:50 PM, Shazron wrote:
> >>
> >> I'll start with moving callback/callback-ios to cordova/cordova-ios
> >> today and pushing issues to Jira and closing the issues in
> >> callback-ios
> >>
> >> On Tue, Jan 3, 2012 at 11:19 AM, Brian LeRoux<b...@brian.io> wrote:
> >>>
> >>> yes --- we should retire the github.com/callback and get
> >>> github.com/cordova going too
> >>>
> >>> anyone want to tack that? I can add you to the org
> >>>
> >>> On Tue, Jan 3, 2012 at 11:08 AM, Joe Bowser<bo...@gmail.com> wrote:
> >>>>
> >>>> Hey
> >>>>
> >>>> I've synced up the changes for Cordova-Android, and after going
> through
> >>>> the
> >>>> process, I think it makes sense if each platform maintainer just does
> a
> >>>> push up to their respective repositories the changes that they have
> been
> >>>> maintaining to date. This way, we can be sure that most people are
> set
> >>>> up
> >>>> to commit to the new repositories, and I won't have to sift through
> >>>> things
> >>>> that I'm unfamiliar with. I see that Patrick has already done this
> with
> >>>> weinre, which tipped me off.
> >>>>
> >>>> Are we doing this right?
> >>>>
> >>>> Joe
> >
> >
>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Shazron <sh...@gmail.com>.
Oops, I missed that for cordova-ios. Fixed.
On Wed, Jan 4, 2012 at 12:58 PM, Bryce Curtis <cu...@gmail.com> wrote:
> Should tags be copied over too?
>
>
> On 1/3/12 2:50 PM, Shazron wrote:
>>
>> I'll start with moving callback/callback-ios to cordova/cordova-ios
>> today and pushing issues to Jira and closing the issues in
>> callback-ios
>>
>> On Tue, Jan 3, 2012 at 11:19 AM, Brian LeRoux<b...@brian.io> wrote:
>>>
>>> yes --- we should retire the github.com/callback and get
>>> github.com/cordova going too
>>>
>>> anyone want to tack that? I can add you to the org
>>>
>>> On Tue, Jan 3, 2012 at 11:08 AM, Joe Bowser<bo...@gmail.com> wrote:
>>>>
>>>> Hey
>>>>
>>>> I've synced up the changes for Cordova-Android, and after going through
>>>> the
>>>> process, I think it makes sense if each platform maintainer just does a
>>>> push up to their respective repositories the changes that they have been
>>>> maintaining to date. This way, we can be sure that most people are set
>>>> up
>>>> to commit to the new repositories, and I won't have to sift through
>>>> things
>>>> that I'm unfamiliar with. I see that Patrick has already done this with
>>>> weinre, which tipped me off.
>>>>
>>>> Are we doing this right?
>>>>
>>>> Joe
>
>
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Bryce Curtis <cu...@gmail.com>.
Should tags be copied over too?
On 1/3/12 2:50 PM, Shazron wrote:
> I'll start with moving callback/callback-ios to cordova/cordova-ios
> today and pushing issues to Jira and closing the issues in
> callback-ios
>
> On Tue, Jan 3, 2012 at 11:19 AM, Brian LeRoux<b...@brian.io> wrote:
>> yes --- we should retire the github.com/callback and get
>> github.com/cordova going too
>>
>> anyone want to tack that? I can add you to the org
>>
>> On Tue, Jan 3, 2012 at 11:08 AM, Joe Bowser<bo...@gmail.com> wrote:
>>> Hey
>>>
>>> I've synced up the changes for Cordova-Android, and after going through the
>>> process, I think it makes sense if each platform maintainer just does a
>>> push up to their respective repositories the changes that they have been
>>> maintaining to date. This way, we can be sure that most people are set up
>>> to commit to the new repositories, and I won't have to sift through things
>>> that I'm unfamiliar with. I see that Patrick has already done this with
>>> weinre, which tipped me off.
>>>
>>> Are we doing this right?
>>>
>>> Joe
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Shazron <sh...@gmail.com>.
I'll start with moving callback/callback-ios to cordova/cordova-ios
today and pushing issues to Jira and closing the issues in
callback-ios
On Tue, Jan 3, 2012 at 11:19 AM, Brian LeRoux <b...@brian.io> wrote:
> yes --- we should retire the github.com/callback and get
> github.com/cordova going too
>
> anyone want to tack that? I can add you to the org
>
> On Tue, Jan 3, 2012 at 11:08 AM, Joe Bowser <bo...@gmail.com> wrote:
>> Hey
>>
>> I've synced up the changes for Cordova-Android, and after going through the
>> process, I think it makes sense if each platform maintainer just does a
>> push up to their respective repositories the changes that they have been
>> maintaining to date. This way, we can be sure that most people are set up
>> to commit to the new repositories, and I won't have to sift through things
>> that I'm unfamiliar with. I see that Patrick has already done this with
>> weinre, which tipped me off.
>>
>> Are we doing this right?
>>
>> Joe
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Brian LeRoux <b...@brian.io>.
yes --- we should retire the github.com/callback and get
github.com/cordova going too
anyone want to tack that? I can add you to the org
On Tue, Jan 3, 2012 at 11:08 AM, Joe Bowser <bo...@gmail.com> wrote:
> Hey
>
> I've synced up the changes for Cordova-Android, and after going through the
> process, I think it makes sense if each platform maintainer just does a
> push up to their respective repositories the changes that they have been
> maintaining to date. This way, we can be sure that most people are set up
> to commit to the new repositories, and I won't have to sift through things
> that I'm unfamiliar with. I see that Patrick has already done this with
> weinre, which tipped me off.
>
> Are we doing this right?
>
> Joe
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Viras <vi...@users.sourceforge.net>.
just to clarify: should I commit to github or to some apache git repository?
Sorry if I missed that part but somehow I'm confused by the git@apache
and github discussion ;)!
Best,
Wolfgang
Am 04.01.2012 14:28, schrieb Shazron:
> done - check your access for cordova/cordova-qt
>
> On Tue, Jan 3, 2012 at 11:32 PM, Viras <vi...@users.sourceforge.net> wrote:
>> Hi,
>>
>> I would volunteer to move the callback-qt repository to apache.org.
>> However I'm not sure if we have a git-repo for it already, and if yes
>> how I can get committer access (yes I already signed the iCLA).
>>
>> Best,
>> Wolfgang
>>
>> Am 03.01.2012 20:08, schrieb Joe Bowser:
>>> Hey
>>>
>>> I've synced up the changes for Cordova-Android, and after going through the
>>> process, I think it makes sense if each platform maintainer just does a
>>> push up to their respective repositories the changes that they have been
>>> maintaining to date. This way, we can be sure that most people are set up
>>> to commit to the new repositories, and I won't have to sift through things
>>> that I'm unfamiliar with. I see that Patrick has already done this with
>>> weinre, which tipped me off.
>>>
>>> Are we doing this right?
>>>
>>> Joe
>>>
>>
>> --
>> GOFG - Get On Fat Guy
>> http://www.gofg.at/ - powered by PhoneGap
>
--
GOFG - Get On Fat Guy
http://www.gofg.at/ - powered by PhoneGap
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Shazron <sh...@gmail.com>.
done - check your access for cordova/cordova-qt
On Tue, Jan 3, 2012 at 11:32 PM, Viras <vi...@users.sourceforge.net> wrote:
> Hi,
>
> I would volunteer to move the callback-qt repository to apache.org.
> However I'm not sure if we have a git-repo for it already, and if yes
> how I can get committer access (yes I already signed the iCLA).
>
> Best,
> Wolfgang
>
> Am 03.01.2012 20:08, schrieb Joe Bowser:
>> Hey
>>
>> I've synced up the changes for Cordova-Android, and after going through the
>> process, I think it makes sense if each platform maintainer just does a
>> push up to their respective repositories the changes that they have been
>> maintaining to date. This way, we can be sure that most people are set up
>> to commit to the new repositories, and I won't have to sift through things
>> that I'm unfamiliar with. I see that Patrick has already done this with
>> weinre, which tipped me off.
>>
>> Are we doing this right?
>>
>> Joe
>>
>
> --
> GOFG - Get On Fat Guy
> http://www.gofg.at/ - powered by PhoneGap
Re: Cordova-Android now up-to-date in the ASF Git Repo
Posted by Viras <vi...@users.sourceforge.net>.
Hi,
I would volunteer to move the callback-qt repository to apache.org.
However I'm not sure if we have a git-repo for it already, and if yes
how I can get committer access (yes I already signed the iCLA).
Best,
Wolfgang
Am 03.01.2012 20:08, schrieb Joe Bowser:
> Hey
>
> I've synced up the changes for Cordova-Android, and after going through the
> process, I think it makes sense if each platform maintainer just does a
> push up to their respective repositories the changes that they have been
> maintaining to date. This way, we can be sure that most people are set up
> to commit to the new repositories, and I won't have to sift through things
> that I'm unfamiliar with. I see that Patrick has already done this with
> weinre, which tipped me off.
>
> Are we doing this right?
>
> Joe
>
--
GOFG - Get On Fat Guy
http://www.gofg.at/ - powered by PhoneGap