I think that's precisely what I asked them, right? I asked if we could
preserve this stuff, and it sounds like if you grant the access, they can
move it under Apache without losing the forks/watchers/etc.

On Fri, Apr 22, 2016 at 12:50 PM, Maxime Beauchemin <
[email protected]> wrote:

> I'm not migrating the Github repository until we figure out how to
> preserve links, stars, forks and watches. Joining Apache should not get in
> the way of the goals we're trying to achieve by joining Apache (generate
> awareness, making it easy to get involved and collaborate, ...)
>
> For the Apache infra people, they should already be aware of this Github
> feature that preserves all of that:
>
>
> The fact that they would not be aware of the existence of that feature
> makes me a bit scared to click the red button.
> ​
>
> Max
>
> On Fri, Apr 22, 2016 at 12:28 PM, Chris Riccomini <[email protected]>
> wrote:
>
>> Hey all,
>>
>> I checked in with INFRA. Conversation is below the fold. @Maxime, it
>> sounds
>> like we can preserve stuff if we can grant some of the root Apache people
>> access to the repo so that they can do the move. Does that sound do-able
>> on
>> your end?
>>
>> Cheers,
>> Chris
>>
>> -----
>> Chris Riccomini
>> 11:51 AM
>> Hey all
>> Had a question about incubator git migration
>> Daniel Takamori (pono)
>> 11:51 AM
>> Shoot.
>> Chris Riccomini
>> 11:52 AM
>> Airflow is currently on Github and has >2000 stars, > 200 watchers, and
>> >500 forks
>> if we migrate to github.com/apache/incubator-airflow
>> is there a way that we can maintain these?
>> they lend a lot of legitimacy to the project
>> Daniel Takamori (pono)
>> 11:52 AM
>> @Humbedooh has the most experience interfacing with GitHub
>> Chris Riccomini
>> 11:52 AM
>> can we assign ownership of the source repo to apache? (it's currently
>> under
>> AirBNB's repo on github)
>> Daniel Takamori (pono)
>> 11:52 AM
>> It might be possible to do that if we contact GitHub, I don't know of
>> anyway we could do that on our side.
>> Changing ownership and changing the name seems possible though.
>> David Nalley
>> 11:56 AM
>> if AirBNB can temporarily make one of the root@ folks an admin that has
>> karma to transfer repos on the AirBNB team we can transfer pretty easily.
>> Chris Riccomini
>> 11:58 AM
>> @ke4qqq I believe we can have them do that
>> @ke4qqq let me check with them
>>
>> On Thu, Apr 21, 2016 at 9:59 PM, Bolke de Bruin <[email protected]>
>> wrote:
>>
>> > Maybe mirror the incubator repo "in" the current Airbnb repo as well?
>> >
>> > Sent from my iPhone
>> >
>> > > On 22 apr. 2016, at 03:00, Chris Riccomini <[email protected]>
>> > wrote:
>> > >
>> > > Perhaps we can ask Infra.
>> > >
>> > > On Thu, Apr 21, 2016 at 5:52 PM, Chris Riccomini <
>> [email protected]>
>> > > wrote:
>> > >
>> > >> @Maxime, I doubt it will preserve any of that. :(
>> > >>
>> > >> On Thu, Apr 21, 2016 at 5:44 PM, Maxime Beauchemin <
>> > >> [email protected]> wrote:
>> > >>
>> > >>> Will the method of transfer preserve the 2500+ stars, 200+ watches
>> and
>> > >>> 500+
>> > >>> forks? What about connectivity of people's git "remote" references?
>> > >>>
>> > >>> I know that the normal method for transferring a repo from an org to
>> > >>> another works nicely in that regard. Is that the case here? If not,
>> > what's
>> > >>> the rational for the alternative method?
>> > >>>
>> > >>> Stars/forks and watches are assets that we should preserve.
>> > >>>
>> > >>> Thanks,
>> > >>>
>> > >>> Max
>> > >>>
>> > >>> On Thu, Apr 21, 2016 at 5:15 PM, Chris Riccomini <
>> > [email protected]>
>> > >>> wrote:
>> > >>>
>> > >>>> Hey Jakob/Hitesh,
>> > >>>>
>> > >>>> One question that did come up about code migration was whether we
>> need
>> > >>> to
>> > >>>> migrate the code now, or whether we can wait until graduation. I'm
>> > >>> nearly
>> > >>>> 100% certain that we need to migrate now.
>> > >>>>
>> > >>>> One gripe with this is that the repo is currently
>> `incubator-airflow`,
>> > >>> but
>> > >>>> will presumably just become `airflow` after graduation, which means
>> > >>> ANOTHER
>> > >>>> migration. I recall the graduation migration being fairly
>> light-weight
>> > >>>> (they just rename the repo), but I wanted to follow up on this to
>> > check.
>> > >>>>
>> > >>>> Cheers,
>> > >>>> Chris
>> > >>
>> > >>
>> >
>>
>
>

Reply via email to