I've put the old druid-developm...@googlegroups.com list into read-only mode by enabling moderation for all messages, with the following rejection message when someone's message is rejected:
> Thanks for your interest in Druid development! Druid development discussions have moved to dev@druid.apache.org, as part of our transition to becoming an Apache project. Please subscribe to our new mailing list by emailing dev-subscr...@druid.apache.org and post your message there. You can also check out archives of the new lists at: https://lists.apache.org/list.html?dev@druid.apache.org. I'll keep an eye on the moderation queue and just reject everything that comes in, using that message. On Mon, Apr 23, 2018 at 1:06 PM, Gian Merlino <g...@apache.org> wrote: > Hi Parag, > > You should be able to do it by checking out the repo at > https://svn.apache.org/repos/asf/incubator/public and then adding > yourself to the file trunk/content/projects/druid.xml. > > On Wed, Apr 18, 2018 at 11:25 AM, Parag Jain <pjai...@oath.com.invalid> > wrote: > >> I got my apache id recently, its pjain1 >> Not sure how to add it to the page - http://incubator.apache.org/pr >> ojects/druid.html. If anyone knows, can you please add it. >> Thanks,Parag >> >> On Monday, March 12, 2018, 4:49:41 PM CDT, Gian Merlino < >> g...@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-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é <xav...@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.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 <jhyde.apa...@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é <xav...@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 <jhyde.apa...@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.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 <ghoon...@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.mon...@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% >> 2BP8u6Ziqi08BauzYFQvZ6ozkk8E5S Cw%40mail.gmail.com. >> >> >> 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. >> 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. >> 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. >> 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. >> 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. >> 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. >> 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. >> 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/ CABs1683hX6qZEc8MzkpBXu5rq3DwY >> 07sS1YrNtv4JeW9G7h8fQ%40mail. gmail.com. >> 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% 2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9 >> LmAeqo4J1proWFpA00gA%40mail. gmail.com. >> 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+unsubscr...@googlegroups.com. >> To post to this group, send email to druid-developm...@googlegroups.com. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/druid-development/CACZNdYBUASnu5jYHUs_UD47NUPTgGhqAKHgvz >> fsTpe1gt5GEHw%40mail.gmail.com. >> For more options, visit https://groups.google.com/d/optout. >> >> > >
