> I generally approve of this idea, as long as Apache INFRA is willing and able to make it happen. I know it’s straightforward to move a git repository from a GitHub project to any other place, but I’m not sure whether it’s possible to move GitHub issues etc. from one project to the next. When Superset made the move, did they just move the repo, or did they move issues/stars/PRs as well? Were Apache INFRA OK with this?
Transferring ownership of the repo would preserve the issues/stars/PRs: https://help.github.com/articles/about-repository-transfers/ The Superset migration (https://issues.apache.org/jira/browse/INFRA-14267) referenced Airflow as a model; based on this comment on the Airflow migration ( https://issues.apache.org/jira/browse/INFRA-11776?focusedCommentId=15261771&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-15261771), ASF INFRA is OK with that kind of migration. It looks like we agree on this plan, so I'll go ahead and file the migration JIRA issue. Thanks, Jon On Thu, Jun 21, 2018 at 4:50 PM, Julian Hyde <[email protected]> wrote: > Max, > > A good pattern for any Apache project is to achieve consensus without > explicit votes. This is what this thread is doing. “+1” is just shorthand > for “I approve”. So, I don’t think a “[VOTE]” prefix is necessary. > > Jon, > > I generally approve of this idea, as long as Apache INFRA is willing and > able to make it happen. I know it’s straightforward to move a git > repository from a GitHub project to any other place, but I’m not sure > whether it’s possible to move GitHub issues etc. from one project to the > next. > > When Superset made the move, did they just move the repo, or did they move > issues/stars/PRs as well? Were Apache INFRA OK with this? > > Julian > > > > On Jun 21, 2018, at 2:05 PM, Maxime Beauchemin < > [email protected]> wrote: > > > > +1 > > > > Note that usually we would expect voting thread to have a `[VOTE]` prefix > > in the the email subject. > > > > Max > > > > On Thu, Jun 21, 2018 at 12:26 AM David Lim <[email protected]> wrote: > > > >> +1 > >> > >> On Thu, Jun 21, 2018 at 12:55 AM, Himanshu <[email protected]> > wrote: > >> > >>> +1 ... Major milestone, thanks > >>> > >>> On Wed, Jun 20, 2018, 9:13 PM Gian Merlino, <[email protected]> wrote: > >>> > >>>> +1; thanks Jon! > >>>> > >>>> On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son <[email protected]> > >> wrote: > >>>> > >>>>> +1 > >>>>> > >>>>> Sounds good to me. > >>>>> > >>>>> Jihoon > >>>>> > >>>>> On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa < > >>>>> [email protected]> > >>>>> wrote: > >>>>> > >>>>>> +1 > >>>>>> > >>>>>> -- > >>>>>> Nishant Bangarwa > >>>>>> > >>>>>> Hortonworks > >>>>>> > >>>>>> On 6/20/18, 3:57 PM, "Jonathan Wei" <[email protected]> wrote: > >>>>>> > >>>>>> Hi all, > >>>>>> > >>>>>> The SGA for Druid has been sorted out, we can get started on > >>>>> migrating > >>>>>> the > >>>>>> old Github repo to Apache. > >>>>>> > >>>>>> Based on the discussion in our previous migration thread ( > >>>>>> > >>>>>> > >>>>> > >>>> https://groups.google.com/forum/#!msg/druid-development/ > >>> q1ip-L8xpBk/GPK1LhC7BQAJ > >>>>>> ), > >>>>>> it seems we favor using our existing Github PR and issues > >>>> workflows. > >>>>>> > >>>>>> I'll file a JIRA ticket requesting transfer of > >>>>>> https://github.com/druid-io/druid to a Gitbox-style Apache > >> repo, > >>>>>> keeping > >>>>>> the existing history of PRs/issues/stars/etc. (e.g., Superset: > >>>>>> https://github.com/apache/incubator-superset) > >>>>>> > >>>>>> Before I do that, I wanted to open this thread for a vote to > >>>> confirm > >>>>>> that > >>>>>> we're all okay with this plan, so please chime in with an > >>> approval > >>>> or > >>>>>> any > >>>>>> concerns that you may have. > >>>>>> > >>>>>> Thanks, > >>>>>> Jon > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
