Re: [druid-dev] Apache migration logistics

[Gian Merlino <gi...@gmail.com>]

FYI: We received an inquiry about where our web site was, and so we set up
a placeholder site at: http://druid.incubator.apache.org/.

Last I heard, the SGA paperwork is still being worked on, and after that is
done we should start migrating the sources and site.

In the meantime should we consider setting a cutoff date for shutting down
druid-development@googlegroups.com list, in favor of dev@druid.apache.org?
We have been encouraging people to use the latter list for a few weeks now.
Maybe one more week: April 23?

On Tue, Mar 27, 2018 at 6:19 PM, Julian Hyde <jh...@gmail.com> wrote:

> Per https://incubator.apache.org/guides/transitioning_asf.html we need to
> get SGA/CCLA on file, then we should file a JIRA case similar to
> https://issues.apache.org/jira/browse/INFRA-15735 or htt
> ps://issues.apache.org/jira/browse/INFRA-12261 to do the import.
>
> Julian
>
>
> On Mar 27, 2018, at 5:20 PM, Gian Merlino <gi...@gmail.com> wrote:
>
> Hi, today I found myself wondering about migration of source repos.
>
> Does anyone know if we've got our GitBox git repo set up? And who we need
> to talk to about getting the druid-io repos transferred to the apache org
> in github such that we can do source control in an Apache-certified-okay
> way? It sounded like we are going to be able to keep using GitHub PRs and
> issues. So I'm hoping we can do this process:
> https://help.github.com/articles/about-repository-transfers/ which lets us
> keep all the issues, watchers, & stars intact.
>
> On Mon, Mar 12, 2018 at 3:25 PM, Xavier Léauté <xa...@confluent.io>
> wrote:
>
> 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 <gi...@imply.io> 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-subscribe@druid.apache.org (+ dev-subscribe@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é <xa...@confluent.io>
> 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.monu51@gmail.com> wrote:
>
> We can register dev@druid.apache.org and users@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 <jh...@gmail.com>
>
> wrote:
>
>
> I don’t know. I don’t think it’s easy.
>
>
> On Mar 9, 2018, at 7:31 AM, Roman Leventov <
> roman.leventov@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 <jh...@apache.org> 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é <xa...@confluent.io>
> 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 <jh...@gmail.com>
> 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?users@druid.apache.org
> * https://lists.apache.org/list.html?private@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-subscribe@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.monu51@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?dev@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
> issues@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 <gh...@gmail.com> 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
>
> mailing
>
> list is fine.
>
> In short, it looks like allowed (Apache Fluo is using Github issue
> tracker (https://github.com/apache/fluo/issues)), but it should be
> captured by another issue tracker system owned by ASF. If so, I
>
> think it's
>
> better to use ASF Jira.
>
> BTW, here is a link to a doc how Airflow migrated to Apache (
> https://cwiki.apache.org/confluence/pages/viewpage.
>
> action?pageId=62693993).
>
> I think it's helpful.
>
> Jihoon
>
> 2018년 3월 5일 (월) 오전 10:47, Nishant Bangarwa <
>
> nishant.monu51@gmail.com>님이
>
> 작성:
>
> So i would propose to setup forwarding to apache lists as first
> step and request everyone to migrate to apache lists, migrate
>
> source code
>
> then website. After sufficient time has passed when everyone has
>
> migrated
>
> to apache mailing lists, Officially stop using the google groups
>
> mailing
>
> list.
>
> How about moving the dev list first and moving the user list
> later? I can see the reason for migrating the dev list early (so
>
> we can do
>
> votes and such) but to me it makes sense to not move the user
>
> list right
>
> away, at least until the web site has been migrated. That way
>
> when we send
>
> a mail to the user list saying "hi everyone please go over to
>
> apache land
>
> now" there is some stuff already waiting over there.
>
>
> Sounds good to me. We can move the dev list first and user list at
> a later point.
>
>
> --
>
> You received this message because you are subscribed to the Google
>
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to
> druid-development@googlegroups.com.
>
> To view this discussion on the web visit
>
> https://groups.google.com/d/msgid/druid-development/
>
> CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5SCw%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/
>
> CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5S
> Cw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>
> .
>
>
>
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to
> druid-development@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/
>
> CACZfFK7%2BdPggO12_y5qmhNfjtvW6kVqaG2L%3Djsh5euqJ-i2jQQ%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/
>
> CACZfFK7%2BdPggO12_y5qmhNfjtvW6kVqaG2L%3Djsh5euqJ-i2jQQ%40mail.gmail.
> com?utm_medium=email&utm_source=footer>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to
> druid-development@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/
>
> CABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/
>
> CABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.
> gmail.com?utm_medium=email&utm_source=footer>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to
> druid-development@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/
>
> 54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/
>
> 54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com?utm_
> medium=email&utm_source=footer>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it,
>
> send
>
> an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to
> druid-development@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/CA%
>
> 2BrPSbbtFogY%3D%2BofXim0Nx7%3DwiMeNEpWoQmk5LK-YaaAa45%
> 3DxQ%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/CA%
>
> 2BrPSbbtFogY%3D%2BofXim0Nx7%3DwiMeNEpWoQmk5LK-YaaAa45%
> 3DxQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it,
>
> send
>
> an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to
> druid-development@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/
>
> 3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org
>
> <https://groups.google.com/d/msgid/druid-development/
>
> 3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org?utm_
> medium=email&utm_source=footer>
>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to druid-development@
>
> googlegroups.com
>
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/CAB5L%
>
> 3DwdPA2BhCFqYWO6CXFZ%3Djh5AWOJqLbP_2G1RimHCZWYFTA%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/CAB5L%
>
> 3DwdPA2BhCFqYWO6CXFZ%3Djh5AWOJqLbP_2G1RimHCZWYFTA%
> 40mail.gmail.com?utm_medium=email&utm_source=footer>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to druid-development@
>
> googlegroups.com
>
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/
>
> A4F427A9-44FD-4C64-B68A-557126705DC7%40gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/
>
> A4F427A9-44FD-4C64-B68A-557126705DC7%40gmail.com?utm_
> medium=email&utm_source=footer>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to druid-development@
>
> googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/
>
> CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/
>
> CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.
> gmail.com?utm_medium=email&utm_source=footer>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google
>
> Groups
>
> "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
>
> an
>
> email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to druid-development@googlegroups.com
>
> .
>
>
> To view this discussion on the web visit
>
> https://groups.google.com/d/msgid/druid-development/CA%
>
> 2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/CA%
>
> 2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.
> gmail.com?utm_medium=email&utm_source=footer>
>
> .
>
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to druid-development@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/druid-development/CACZNdYBUASnu5jYHUs_
>
> UD47NUPTgGhqAKHgvzfsTpe1gt5GEHw%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/druid-development/
>
> CACZNdYBUASnu5jYHUs_UD47NUPTgGhqAKHgvzfsTpe1gt5GEH
> w%40mail.gmail.com?utm_medium=email&utm_source=footer>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to druid-development@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/druid-development/FCAA4000-4233-470E-BB72-A7F443601E8B%40gmail.com
> <https://groups.google.com/d/msgid/druid-development/FCAA4000-4233-470E-BB72-A7F443601E8B%40gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

Re: [druid-dev] Apache migration logistics

[Gian Merlino <gi...@apache.org>]

Also, the sources for the site are at:
https://github.com/apache/incubator-druid-website. The branch "asf-git" is
served on the site. I think once we migrate http://druid.io/, we could do
something similar to what we do on
https://github.com/druid-io/druid-io.github.io, where sources are in "src"
and the built site is in "master". Except in the ASF infra, it makes more
sense to put the sources in "master" and the built site in "asf-git".

On Sun, Apr 15, 2018 at 7:56 AM, Gian Merlino <gi...@gmail.com> wrote:

> FYI: We received an inquiry about where our web site was, and so we set up
> a placeholder site at: http://druid.incubator.apache.org/.
>
> Last I heard, the SGA paperwork is still being worked on, and after that
> is done we should start migrating the sources and site.
>
> In the meantime should we consider setting a cutoff date for shutting down
> druid-development@googlegroups.com list, in favor of dev@druid.apache.org?
> We have been encouraging people to use the latter list for a few weeks now.
> Maybe one more week: April 23?
>
> On Tue, Mar 27, 2018 at 6:19 PM, Julian Hyde <jh...@gmail.com>
> wrote:
>
>> Per https://incubator.apache.org/guides/transitioning_asf.html we need
>> to get SGA/CCLA on file, then we should file a JIRA case similar to
>> https://issues.apache.org/jira/browse/INFRA-15735 or http
>> s://issues.apache.org/jira/browse/INFRA-12261 to do the import.
>>
>> Julian
>>
>>
>> On Mar 27, 2018, at 5:20 PM, Gian Merlino <gi...@gmail.com> wrote:
>>
>> Hi, today I found myself wondering about migration of source repos.
>>
>> Does anyone know if we've got our GitBox git repo set up? And who we need
>> to talk to about getting the druid-io repos transferred to the apache org
>> in github such that we can do source control in an Apache-certified-okay
>> way? It sounded like we are going to be able to keep using GitHub PRs and
>> issues. So I'm hoping we can do this process:
>> https://help.github.com/articles/about-repository-transfers/ which lets
>> us
>> keep all the issues, watchers, & stars intact.
>>
>> On Mon, Mar 12, 2018 at 3:25 PM, Xavier Léauté <xa...@confluent.io>
>> wrote:
>>
>> 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 <gi...@imply.io> 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-subscribe@druid.apache.org (+ dev-subscribe@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é <xa...@confluent.io>
>> 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.monu51@gmail.com> wrote:
>>
>> We can register dev@druid.apache.org and users@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 <jh...@gmail.com>
>>
>> wrote:
>>
>>
>> I don’t know. I don’t think it’s easy.
>>
>>
>> On Mar 9, 2018, at 7:31 AM, Roman Leventov <
>> roman.leventov@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 <jh...@apache.org> 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é <xa...@confluent.io>
>> 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 <jh...@gmail.com>
>> 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?users@druid.apache.org
>> * https://lists.apache.org/list.html?private@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-subscribe@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.monu51@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?dev@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
>> issues@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 <gh...@gmail.com> 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
>>
>> mailing
>>
>> list is fine.
>>
>> In short, it looks like allowed (Apache Fluo is using Github issue
>> tracker (https://github.com/apache/fluo/issues)), but it should be
>> captured by another issue tracker system owned by ASF. If so, I
>>
>> think it's
>>
>> better to use ASF Jira.
>>
>> BTW, here is a link to a doc how Airflow migrated to Apache (
>> https://cwiki.apache.org/confluence/pages/viewpage.
>>
>> action?pageId=62693993).
>>
>> I think it's helpful.
>>
>> Jihoon
>>
>> 2018년 3월 5일 (월) 오전 10:47, Nishant Bangarwa <
>>
>> nishant.monu51@gmail.com>님이
>>
>> 작성:
>>
>> So i would propose to setup forwarding to apache lists as first
>> step and request everyone to migrate to apache lists, migrate
>>
>> source code
>>
>> then website. After sufficient time has passed when everyone has
>>
>> migrated
>>
>> to apache mailing lists, Officially stop using the google groups
>>
>> mailing
>>
>> list.
>>
>> How about moving the dev list first and moving the user list
>> later? I can see the reason for migrating the dev list early (so
>>
>> we can do
>>
>> votes and such) but to me it makes sense to not move the user
>>
>> list right
>>
>> away, at least until the web site has been migrated. That way
>>
>> when we send
>>
>> a mail to the user list saying "hi everyone please go over to
>>
>> apache land
>>
>> now" there is some stuff already waiting over there.
>>
>>
>> Sounds good to me. We can move the dev list first and user list at
>> a later point.
>>
>>
>> --
>>
>> You received this message because you are subscribed to the Google
>>
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to
>> druid-development@googlegroups.com.
>>
>> To view this discussion on the web visit
>>
>> https://groups.google.com/d/msgid/druid-development/
>>
>> CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5SCw%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/
>>
>> CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5S
>> Cw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>
>> .
>>
>>
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to
>> druid-development@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/
>>
>> CACZfFK7%2BdPggO12_y5qmhNfjtvW6kVqaG2L%3Djsh5euqJ-i2jQQ%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/
>>
>> CACZfFK7%2BdPggO12_y5qmhNfjtvW6kVqaG2L%3Djsh5euqJ-i2jQQ%40mail.gmail.
>> com?utm_medium=email&utm_source=footer>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to
>> druid-development@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/
>>
>> CABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/
>>
>> CABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.
>> gmail.com?utm_medium=email&utm_source=footer>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to
>> druid-development@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/
>>
>> 54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/
>>
>> 54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com?utm_
>> medium=email&utm_source=footer>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it,
>>
>> send
>>
>> an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to
>> druid-development@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/CA%
>>
>> 2BrPSbbtFogY%3D%2BofXim0Nx7%3DwiMeNEpWoQmk5LK-YaaAa45%
>> 3DxQ%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/CA%
>>
>> 2BrPSbbtFogY%3D%2BofXim0Nx7%3DwiMeNEpWoQmk5LK-YaaAa45%
>> 3DxQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it,
>>
>> send
>>
>> an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to
>> druid-development@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/
>>
>> 3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org
>>
>> <https://groups.google.com/d/msgid/druid-development/
>>
>> 3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org?utm_
>> medium=email&utm_source=footer>
>>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to druid-development@
>>
>> googlegroups.com
>>
>> .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/CAB5L%
>>
>> 3DwdPA2BhCFqYWO6CXFZ%3Djh5AWOJqLbP_2G1RimHCZWYFTA%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/CAB5L%
>>
>> 3DwdPA2BhCFqYWO6CXFZ%3Djh5AWOJqLbP_2G1RimHCZWYFTA%
>> 40mail.gmail.com?utm_medium=email&utm_source=footer>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to druid-development@
>>
>> googlegroups.com
>>
>> .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/
>>
>> A4F427A9-44FD-4C64-B68A-557126705DC7%40gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/
>>
>> A4F427A9-44FD-4C64-B68A-557126705DC7%40gmail.com?utm_
>> medium=email&utm_source=footer>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to druid-development@
>>
>> googlegroups.com.
>>
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/
>>
>> CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/
>>
>> CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.
>> gmail.com?utm_medium=email&utm_source=footer>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google
>>
>> Groups
>>
>> "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>>
>> an
>>
>> email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to druid-development@googlegroups.com
>>
>> .
>>
>>
>> To view this discussion on the web visit
>>
>> https://groups.google.com/d/msgid/druid-development/CA%
>>
>> 2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/CA%
>>
>> 2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.
>> gmail.com?utm_medium=email&utm_source=footer>
>>
>> .
>>
>>
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to druid-development@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/druid-development/CACZNdYBUASnu5jYHUs_
>>
>> UD47NUPTgGhqAKHgvzfsTpe1gt5GEHw%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/druid-development/
>>
>> CACZNdYBUASnu5jYHUs_UD47NUPTgGhqAKHgvzfsTpe1gt5GEH
>> w%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Druid Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to druid-development+unsubscribe@googlegroups.com.
>> To post to this group, send email to druid-development@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/druid-development/FCAA4000-4233-470E-BB72-A7F443601E8B%40gmail.com
>> <https://groups.google.com/d/msgid/druid-development/FCAA4000-4233-470E-BB72-A7F443601E8B%40gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

Re: [druid-dev] Apache migration logistics

[Gian Merlino <gi...@imply.io>]

Oh cool, I didn't realize that. We should stick to https://druid.apache.org/
then.

Gian

On Mon, Apr 16, 2018 at 10:51 AM, Maxime Beauchemin <
maximebeauchemin@gmail.com> wrote:

> Quick note to say that apache sets up both http://druid.incubator.ap
> ache.org/  and http://druid.apache.org/
> <http://druid.incubator.apache.org/> to point to the same place. I'd
> recommend always referencing and using  http://druid.apache.org/
> <http://druid.incubator.apache.org/> for SEO and future-proofing purposes.
>
> Max
>
> --
> You received this message because you are subscribed to the Google Groups
> "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to druid-development+unsubscribe@googlegroups.com.
> To post to this group, send email to druid-development@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/druid-development/e8c99afa-b879-431b-a0b5-
> 64fab278b182%40googlegroups.com
> <https://groups.google.com/d/msgid/druid-development/e8c99afa-b879-431b-a0b5-64fab278b182%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>