Re: [druid-dev] Apache migration logistics

[Gian Merlino]

Committers: please,

1) If you don't have an apache id already, fill out an ICLA:
https://www.apache.org/dev/new-committers-guide.html#
guide-for-new-committers and then post here and hopefully someone can
figure out how to get you an id?

2) When you have an id, post it here if it's not in
http://incubator.apache.org/projects/druid.html so someone can figure out
how to add you to that, and then also try to sign up to
private-subscr...@druid.apache.org (+ dev-subscr...@druid.apache.org which
you should be on already). If you can't, then also post here, and hopefully
someone can figure _that_ out.

Gian

On Fri, Mar 9, 2018 at 11:28 AM, Xavier Léauté  wrote:

> This thread is already going to both lists, and it looks like responses
> automatically go to both. Would be good to check what happens if we
> subscribe dev@ to the google group. If responding from the apache list
> doesn't automatically add the google group as well, it will be hard to keep
> the group useful.
>
> Agree with Julian a cutoff is necessary anyway, since the google group
> inherently becomes less useful over time, as some information only ends up
> in the apache list.
>
> On Fri, Mar 9, 2018 at 11:14 AM Nishant Bangarwa 
> wrote:
>
>> We can register dev@druid.apache.org and us...@druid.apache.org as a
>> user in druid user groups so that going forward any mails that are sent to
>> druid google groups are also received on the apache lists and is on the
>> record. This would be to bridge the gap during the migration only.
>>
>> @Julian, I go ahead and try setting this up, If this seems reasonable ?
>>
>> On Sat, 10 Mar 2018 at 00:09 Julian Hyde  wrote:
>>
>>> I don’t know. I don’t think it’s easy.
>>>
>>>
>>> On Mar 9, 2018, at 7:31 AM, Roman Leventov >> com> wrote:
>>>
>>> Could archives of druid-dev and druid-users mailing lists be transferred
>>> to the new lists?
>>>
>>> On Thu, Mar 8, 2018 at 8:48 AM, Julian Hyde  wrote:
>>>
 I’m working on it. It turns that I don’t have sufficient karma to
 create a git repo, so I’ve put in a request on the incubator list.


 On Mar 6, 2018, at 10:12 AM, Xavier Léauté  wrote:

 Julian, it looks like you or one of the mentors has to request the
 source code repos. Could you request a gitbox enabled repo?

 Based on https://incubator.apache.org/guides/transitioning_asf.html,
 for the initial migration, we need to involve infra to import the initial
 git history and grant them admin rights to the github repo.

 Charles, it also sound like we won't be able to do any code migration
 util legal signs off on the software grant, could you drive that?

 On Mon, Mar 5, 2018 at 12:52 PM Julian Hyde 
 wrote:

> The dev, users and private mailing lists now exist. You can see the
> archives:
>
> * https://lists.apache.org/list.html?dev@druid.apache.org
> * https://lists.apache.org/list.html?us...@druid.apache.org
> * https://lists.apache.org/list.html?priv...@druid.apache.org
>
> To see the last of these, you need to log in.
>
> There will also be archives at https://mail-archives.
> apache.org/mod_mbox/druid-dev/ etc. (you might need to wait a few
> minutes for the archiver to catch up).
>
> If you are an initial committer or mentor, you are a member of the
> Druid PPMC and you must be on both dev and private lists now. Send a
> message to dev-subscr...@druid.apache.org and private-subscribe@
> geode.apache.org.
>
> Everyone else is welcome to join dev and/or users.
>
> Julian
>
> On Mar 5, 2018, at 11:58 AM, Nishant Bangarwa <
> nishant.mon...@gmail.com> wrote:
>
> Apache Incubator Superset is another example which uses github issues
> - https://github.com/apache/incubator-superset/issues
> For Superset it works as all the github issue interactions are
> captured in ASF owned mailing list via Gitbox Integration.
> See - https://lists.apache.org/list.html?d...@superset.apache.org
>
> For Druid, If everyone agrees we can also choose to capture
> interactions on github issues at an Apache Owned mailing list e.g
> iss...@druid.apache.org and continue to use github issues.
>
> @Jihoon, Thanks for the Airflow migration link, super helpful.
>
>
>
> On Tue, 6 Mar 2018 at 00:44 Jihoon Son  wrote:
>
>> Gian,
>>
>> there was a discussion for using a third-party issue tracker (
>> https://issues.apache.org/jira/browse/LEGAL-249). I think the point
>> is
>>
>> > Okay, it looks like the requirement is just to capture the intent
>> to contribute in ASF-owned infrastructure. That means that the automated
>> process that adds PR information to a JIRA issue or sends it to a 

Re: [druid-dev] Apache migration logistics

[Xavier Léauté]

FYI, to update your information on the status page you need to check out
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/ with
your Apache credentials and update the druid.xml file in that directory.

On Mon, Mar 12, 2018 at 2:49 PM Gian Merlino  wrote:

> Committers: please,
>
> 1) If you don't have an apache id already, fill out an ICLA:
> https://www.apache.org/dev/new-committers-guide.html#guide-for-new-committers 
> and
> then post here and hopefully someone can figure out how to get you an id?
>
> 2) When you have an id, post it here if it's not in
> http://incubator.apache.org/projects/druid.html so someone can figure out
> how to add you to that, and then also try to sign up to
> private-subscr...@druid.apache.org (+ dev-subscr...@druid.apache.org
> which you should be on already). If you can't, then also post here, and
> hopefully someone can figure _that_ out.
>
> Gian
>
> On Fri, Mar 9, 2018 at 11:28 AM, Xavier Léauté 
> wrote:
>
>> This thread is already going to both lists, and it looks like responses
>> automatically go to both. Would be good to check what happens if we
>> subscribe dev@ to the google group. If responding from the apache list
>> doesn't automatically add the google group as well, it will be hard to keep
>> the group useful.
>>
>> Agree with Julian a cutoff is necessary anyway, since the google group
>> inherently becomes less useful over time, as some information only ends up
>> in the apache list.
>>
>> On Fri, Mar 9, 2018 at 11:14 AM Nishant Bangarwa <
>> nishant.mon...@gmail.com> wrote:
>>
>>> We can register dev@druid.apache.org and us...@druid.apache.org as a
>>> user in druid user groups so that going forward any mails that are sent to
>>> druid google groups are also received on the apache lists and is on the
>>> record. This would be to bridge the gap during the migration only.
>>>
>>> @Julian, I go ahead and try setting this up, If this seems reasonable ?
>>>
>>> On Sat, 10 Mar 2018 at 00:09 Julian Hyde  wrote:
>>>
 I don’t know. I don’t think it’s easy.


 On Mar 9, 2018, at 7:31 AM, Roman Leventov <
 roman.leven...@metamarkets.com> wrote:

 Could archives of druid-dev and druid-users mailing lists be
 transferred to the new lists?

 On Thu, Mar 8, 2018 at 8:48 AM, Julian Hyde  wrote:

> I’m working on it. It turns that I don’t have sufficient karma to
> create a git repo, so I’ve put in a request on the incubator list.
>
>
> On Mar 6, 2018, at 10:12 AM, Xavier Léauté 
> wrote:
>
> Julian, it looks like you or one of the mentors has to request the
> source code repos. Could you request a gitbox enabled repo?
>
> Based on https://incubator.apache.org/guides/transitioning_asf.html,
> for the initial migration, we need to involve infra to import the initial
> git history and grant them admin rights to the github repo.
>
> Charles, it also sound like we won't be able to do any code migration
> util legal signs off on the software grant, could you drive that?
>
> On Mon, Mar 5, 2018 at 12:52 PM Julian Hyde 
> wrote:
>
>> The dev, users and private mailing lists now exist. You can see the
>> archives:
>>
>> * https://lists.apache.org/list.html?dev@druid.apache.org
>> * https://lists.apache.org/list.html?us...@druid.apache.org
>> * https://lists.apache.org/list.html?priv...@druid.apache.org
>>
>> To see the last of these, you need to log in.
>>
>> There will also be archives at
>> https://mail-archives.apache.org/mod_mbox/druid-dev/ etc. (you might
>> need to wait a few minutes for the archiver to catch up).
>>
>> If you are an initial committer or mentor, you are a member of the
>> Druid PPMC and you must be on both dev and private lists now. Send a
>> message to dev-subscr...@druid.apache.org and
>> private-subscr...@geode.apache.org.
>>
>> Everyone else is welcome to join dev and/or users.
>>
>> Julian
>>
>> On Mar 5, 2018, at 11:58 AM, Nishant Bangarwa <
>> nishant.mon...@gmail.com> wrote:
>>
>> Apache Incubator Superset is another example which uses github issues
>> - https://github.com/apache/incubator-superset/issues
>> For Superset it works as all the github issue interactions are
>> captured in ASF owned mailing list via Gitbox Integration.
>> See - https://lists.apache.org/list.html?d...@superset.apache.org
>>
>> For Druid, If everyone agrees we can also choose to capture
>> interactions on github issues at an Apache Owned mailing list e.g
>> iss...@druid.apache.org and continue to use github issues.
>>
>> @Jihoon, Thanks for the Airflow migration link, super helpful.
>>
>>
>>
>> On Tue, 6 Mar 2018 at 00:44 Jihoon Son