1) Source repos: Even though we need to migrate source repos to ASF git, we could potentially keep using a Github pull request based workflow. One example of a project that has a github-based workflow is Airflow, see https://cwiki.apache.org/confluence/display/AIRFLOW/Committers%27+Guide (search for "asfgit" examples). The workflow is different: pull requests are closed, not merged, and a bot does the commit out of band. I'm not sure if this is the only way to do it or if there are other options. Do we want to do this (I think yes)?
4) Current status: has anyone requested ASF mailing lists, git repos, a JIRA project, a wiki, and a web site yet? If not is anyone interested in volunteering?
--
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%2BrPSbZknzU5pg88Q7zFwC6z7oNWhqC8PAe2i42_Ahp018txbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
2) Issue tracking: Is there an ability to mass import Github issues into Apache JIRA? Maybe we should do some spring cleaning of Github issues first.
3) Druid 0.12.0: I'd like to release this before migrating anything, since the vote is almost done anyway, and it seems like our first incubating release might take a while (there is a lot of stuff to migrate). So maybe we can shoot for 0.13.0 being the first Apache release.
5) Order of migration: My feeling is it makes sense to move the source repos first, then website, then mailing lists. Or maybe we want to move the dev list first before anything else. I do think it makes sense to move the user list last, since it could be confusing to have a user list on Apache infra without having the project fully moved over there.
For reference our proposal is at: https://wiki.apache.org/incubator/DruidProposal. And our migration status page is at: http://incubator.apache.org/projects/druid.html.Gian
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CACZNdYBt8BxoSb9Tz2GjKsSX5C3h7bFiczaH9u%2B2JbXcKzFBjQ%40mail.gmail.com.
The GitBox thing sounds cool - is Kafka migrated to it yet and do you know if it's working out well? Seems like we'd want to get on board with that from the start since we already do everything on Github.GianOn Mon, Mar 5, 2018 at 12:22 PM, Xavier Léauté <xav...@confluent.io> wrote:1) Source repos: Even though we need to migrate source repos to ASF git, we could potentially keep using a Github pull request based workflow. One example of a project that has a github-based workflow is Airflow, see https://cwiki.apache.org/confluence/display/AIRFLOW/Committers%27+Guide (search for "asfgit" examples). The workflow is different: pull requests are closed, not merged, and a bot does the commit out of band. I'm not sure if this is the only way to do it or if there are other options. Do we want to do this (I think yes)?ASF recently started offering GitBox (https://gitbox.apache.org/setup/) which enabled 2-way sync between github and asf git, which lets projects use GitHub based workflows. as of December if wasn't GA yet, but many projects already requested it. Apache Kafka recently switched to it (https://lists.apache.org/thread.html/3ef19c439e978993d1e40f0f30cc0126e79761b7b8910400fb7f18bb@%3Cdev.kafka.apache.org%3E, https://issues.apache.org/jira/browse/INFRA-15676), I can look into this.4) Current status: has anyone requested ASF mailing lists, git repos, a JIRA project, a wiki, and a web site yet? If not is anyone interested in volunteering?I can look into the repo situation. If I can request the other things as part of the same process, I'll do it as well.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CA%2BrPSbZknzU5pg88Q7zFwC6z7oNWhqC8PAe2i42_Ahp018txbA%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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CACZNdYAfEMEzZUXS3GEPMzGMaM4ONyv4O%3DuNrVYjmGYfQ-w0Rw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CA%2BrPSbZmxnkyD%2BPEax-fOx4qAubJkideNEjTSkm9Xyi7eJJ8eA%40mail.gmail.com.
2) Issue tracking: Is there an ability to mass import Github issues into Apache JIRA? Maybe we should do some spring cleaning of Github issues first.I think it is also possible to use github issues now with ASF projects. e.g I noticed rocketMQ is trying to migrate to github issues from JIRA here - https://issues.apache.org/jira/browse/INFRA-16128. Based on the JIRA comments it seems what needs to be done there is to have a VOTE on the official apache mailing lists and request Apache Infra team to enable github issues.3) Druid 0.12.0: I'd like to release this before migrating anything, since the vote is almost done anyway, and it seems like our first incubating release might take a while (there is a lot of stuff to migrate). So maybe we can shoot for 0.13.0 being the first Apache release.+1 on this.5) Order of migration: My feeling is it makes sense to move the source repos first, then website, then mailing lists. Or maybe we want to move the dev list first before anything else. I do think it makes sense to move the user list last, since it could be confusing to have a user list on Apache infra without having the project fully moved over there.I think mailing lists should be the first one as for many things we may need to have an official VOTE thread and reach a consensus on the official mailing list. As a stop gap, We can look into setting up forwarding logic for all mails from druid-dev and druid-user mailing lists to the apache lists during the migration process. Looks like It should possible by subscribing apache mailing list email to google groups (https://docs.helpscout.net/article/77-google-groups).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.
--For reference our proposal is at: https://wiki.apache.org/incubator/DruidProposal. And our migration status page is at: http://incubator.apache.org/projects/druid.html.Gian
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/CACZNdYBt8BxoSb9Tz2GjKsSX5C3h7bFiczaH9u%2B2JbXcKzFBjQ%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/CABs1683Ho%3DQBqbAHPvEc9E5Vj3tH0ts4VMTHQrD-Y2MCCKo9CA%40mail.gmail.com.
> I think it is also possible to use github issues now with ASF projects. e.g I noticed rocketMQ is trying to migrate to github issues from JIRA here - https://issues.apache.org/jira/browse/INFRA-16128. Based on the JIRA comments it seems what needs to be done there is to have a VOTE on the official apache mailing lists and request Apache Infra team to enable github issues.Cool, that is good to know. I guess at some point we should decide if we want to migrate to Apache JIRA or stick with Github issues. I assume we would at least need to move our issues from github.com/druid-io/druid to github.com/apache/druid. Does anyone know if the policy on this stuff is written down somewhere?> I think mailing lists should be the first one as for many things we may need to have an official VOTE thread and reach a consensus on the official mailing list. As a stop gap, We can look into setting up forwarding logic for all mails from druid-dev and druid-user mailing lists to the apache lists during the migration process. Looks like It should possible by subscribing apache mailing list email to google groups (https://docs.helpscout.net/article/77-google-groups).>> 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.Gian
On Mon, Mar 5, 2018 at 12:55 PM, Nishant Bangarwa <nishant...@gmail.com> wrote:
2) Issue tracking: Is there an ability to mass import Github issues into Apache JIRA? Maybe we should do some spring cleaning of Github issues first.I think it is also possible to use github issues now with ASF projects. e.g I noticed rocketMQ is trying to migrate to github issues from JIRA here - https://issues.apache.org/jira/browse/INFRA-16128. Based on the JIRA comments it seems what needs to be done there is to have a VOTE on the official apache mailing lists and request Apache Infra team to enable github issues.3) Druid 0.12.0: I'd like to release this before migrating anything, since the vote is almost done anyway, and it seems like our first incubating release might take a while (there is a lot of stuff to migrate). So maybe we can shoot for 0.13.0 being the first Apache release.+1 on this.5) Order of migration: My feeling is it makes sense to move the source repos first, then website, then mailing lists. Or maybe we want to move the dev list first before anything else. I do think it makes sense to move the user list last, since it could be confusing to have a user list on Apache infra without having the project fully moved over there.I think mailing lists should be the first one as for many things we may need to have an official VOTE thread and reach a consensus on the official mailing list. As a stop gap, We can look into setting up forwarding logic for all mails from druid-dev and druid-user mailing lists to the apache lists during the migration process. Looks like It should possible by subscribing apache mailing list email to google groups (https://docs.helpscout.net/article/77-google-groups).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.
--For reference our proposal is at: https://wiki.apache.org/incubator/DruidProposal. And our migration status page is at: http://incubator.apache.org/projects/druid.html.Gian
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CACZNdYBt8BxoSb9Tz2GjKsSX5C3h7bFiczaH9u%2B2JbXcKzFBjQ%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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs1683Ho%3DQBqbAHPvEc9E5Vj3tH0ts4VMTHQrD-Y2MCCKo9CA%40mail.gmail.com.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CACZNdYBotYZ-AKy5HqG2%3DYV0nm3_C9AEUe_YUvd87XeBUeakEw%40mail.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.
> 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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5SCw%40mail.gmail.com.
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...@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.
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 view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CACZfFK7%2BdPggO12_y5qmhNfjtvW6kVqaG2L%3Djsh5euqJ-i2jQQ%40mail.gmail.com.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.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.
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....@gmail.com> wrote:
The dev, users and private mailing lists now exist. You can see the archives:
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-su...@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...@gmail.com> wrote:
Apache Incubator Superset is another example which uses github issues - https://github.com/apache/incubator-superset/issuesFor Superset it works as all the github issue interactions are captured in ASF owned mailing list via Gitbox Integration.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 <ghoo...@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.Jihoon2018년 3월 5일 (월) 오전 10:47, Nishant Bangarwa <nishant...@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.
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 view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org.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 unsubscribe from this group and stop receiving emails from it, send an email to druid-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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.
I don’t know. I don’t think it’s easy.
On Mar 9, 2018, at 7:31 AM, Roman Leventov <roman.l...@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....@gmail.com> wrote:
The dev, users and private mailing lists now exist. You can see the archives:
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-su...@druid.apache.org and private-...@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...@gmail.com> wrote:
Apache Incubator Superset is another example which uses github issues - https://github.com/apache/incubator-superset/issuesFor Superset it works as all the github issue interactions are captured in ASF owned mailing list via Gitbox Integration.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 <ghoo...@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.Jihoon2018년 3월 5일 (월) 오전 10:47, Nishant Bangarwa <nishant...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5SCw%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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.gmail.com.
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...@gmail.com> wrote:
We can register d...@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....@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....@gmail.com> wrote:
The dev, users and private mailing lists now exist. You can see the archives:
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-su...@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...@gmail.com> wrote:
Apache Incubator Superset is another example which uses github issues - https://github.com/apache/incubator-superset/issuesFor Superset it works as all the github issue interactions are captured in ASF owned mailing list via Gitbox Integration.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 <ghoo...@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.Jihoon2018년 3월 5일 (월) 오전 10:47, Nishant Bangarwa <nishant...@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.
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.
--
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/CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%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 view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CA%2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.gmail.com.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.
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...@gmail.com> wrote:
We can register d...@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....@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....@gmail.com> wrote:
The dev, users and private mailing lists now exist. You can see the archives:
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-su...@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...@gmail.com> wrote:
Apache Incubator Superset is another example which uses github issues - https://github.com/apache/incubator-superset/issuesFor Superset it works as all the github issue interactions are captured in ASF owned mailing list via Gitbox Integration.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 <ghoo...@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.Jihoon2018년 3월 5일 (월) 오전 10:47, Nishant Bangarwa <nishant...@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.
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.
--
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/CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%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 view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CA%2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.gmail.com.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.
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-su...@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...@gmail.com> wrote:
We can register d...@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....@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.l...@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....@gmail.com> wrote:
The dev, users and private mailing lists now exist. You can see the archives:
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-...@druid.apache.org (+ dev-su...@druid.apache.org which you should be on already). If you can't, then also post here, and hopefully someone can figure _that_ out.GianOn 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...@gmail.com> wrote:We can register d...@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....@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.l...@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....@gmail.com> wrote:
The dev, users and private mailing lists now exist. You can see the archives:
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-su...@druid.apache.org and private-...@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...@gmail.com> wrote:Apache Incubator Superset is another example which uses github issues - https://github.com/apache/incubator-superset/issuesFor Superset it works as all the github issue interactions are captured in ASF owned mailing list via Gitbox Integration.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 <ghoo...@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...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5SCw%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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.gmail.com.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CA%2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.gmail.com.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CACZNdYBUASnu5jYHUs_UD47NUPTgGhqAKHgvzfsTpe1gt5GEHw%40mail.gmail.com.
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-su...@druid.apache.org and private-...@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...@gmail.com> wrote:
Apache Incubator Superset is another example which uses github issues - https://github.com/apache/incubator-superset/issuesFor Superset it works as all the github issue interactions are captured in ASF owned mailing list via Gitbox Integration.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 <ghoo...@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.Jihoon2018년 3월 5일 (월) 오전 10:47, Nishant Bangarwa <nishant...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5SCw%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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CA%2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.gmail.com.
--
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-development/CACZNdYBUASnu5jYHUs_UD47NUPTgGhqAKHgvzfsTpe1gt5GEHw%40mail.gmail.com.
On Mar 27, 2018, at 5:20 PM, Gian Merlino <gianm...@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.
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
CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5S<https://groups.google.com/d/msgid/druid-development/
Cw%40mail.gmail.com?utm_medium=email&utm_source=footer>
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-developm...@googlegroups.com.
To post to this group, send email to
druid-de...@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.<https://groups.google.com/d/msgid/druid-development/
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-developm...@googlegroups.com.
To post to this group, send email to
druid-de...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/
CABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.gmail.comCABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.<https://groups.google.com/d/msgid/druid-development/
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-developm...@googlegroups.com.
To post to this group, send email to
druid-de...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/
54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com?utm_<https://groups.google.com/d/msgid/druid-development/
medium=email&utm_source=footer>
send.
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,
an email to druid-developm...@googlegroups.com.
To post to this group, send email to
druid-de...@googlegroups.com.
To view this discussion on the web visit
2BrPSbbtFogY%3D%2BofXim0Nx7%3DwiMeNEpWoQmk5LK-YaaAa45%https://groups.google.com/d/msgid/druid-development/CA%
3DxQ%40mail.gmail.com2BrPSbbtFogY%3D%2BofXim0Nx7%3DwiMeNEpWoQmk5LK-YaaAa45%<https://groups.google.com/d/msgid/druid-development/CA%
3DxQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
send.
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,an email to druid-developm...@googlegroups.com.
To post to this group, send email to
druid-de...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/
3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org?utm_<https://groups.google.com/d/msgid/druid-development/
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-developm...@googlegroups.com.
googlegroups.comTo post to this group, send email to druid-development@
.
To view this discussion on the web visit
3DwdPA2BhCFqYWO6CXFZ%3Djh5AWOJqLbP_2G1RimHCZWYFTA%40mail.gmail.comhttps://groups.google.com/d/msgid/druid-development/CAB5L%3DwdPA2BhCFqYWO6CXFZ%3Djh5AWOJqLbP_2G1RimHCZWYFTA%<https://groups.google.com/d/msgid/druid-development/CAB5L%
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-developm...@googlegroups.com.
googlegroups.comTo post to this group, send email to druid-development@
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/
A4F427A9-44FD-4C64-B68A-557126705DC7%40gmail.comA4F427A9-44FD-4C64-B68A-557126705DC7%40gmail.com?utm_<https://groups.google.com/d/msgid/druid-development/
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-developm...@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.comCABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.<https://groups.google.com/d/msgid/druid-development/
gmail.com?utm_medium=email&utm_source=footer>
Groups.--
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Googlean"Druid Development" group.
To unsubscribe from this group and stop receiving emails from it, send.email to druid-developm...@googlegroups.com.
To post to this group, send email to druid-de...@googlegroups.com
To view this discussion on the web visit
2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.gmail.comhttps://groups.google.com/d/msgid/druid-development/CA%2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.<https://groups.google.com/d/msgid/druid-development/CA%
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-developm...@googlegroups.com.
To post to this group, send email to druid-de...@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>
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
>>>>>>>> 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
>>>>>>>> .
>>>>>>>
>>>>>>>
>>>>>>>> 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
>>>>>> 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
>>>>>> To view this discussion on the web visit
>>>>>> .
>>>>>> 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
>>>>> 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
>>>>> To view this discussion on the web visit
>>>>> .
>>>>>
>>>>> 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
>>>> .
>>>> 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
>>>> .
>>>> 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
>>> .
>>> 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
>> .
>
>
>> 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
send an email to druid-development+unsubscribe@googlegroups.com.
To post to this group, send email to
To view this discussion on the web visithttps://groups.google.com/d/msgid/druid-development/
CABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5SCw%40mail.gmail.comCABs168096baBaAm941w%2BP8u6Ziqi08BauzYFQvZ6ozkk8E5S<https://groups.google.com/d/msgid/druid-development/
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/
CACZfFK7%2BdPggO12_y5qmhNfjtvW6kVqaG2L%3Djsh5euqJ-i2jQQ%40mail.gmail.comCACZfFK7%2BdPggO12_y5qmhNfjtvW6kVqaG2L%3Djsh5euqJ-i2jQQ%40mail.gmail.<https://groups.google.com/d/msgid/druid-development/
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/
CABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.gmail.comCABs1682ACVnKvgXsuXN%3DDiJu7RsjTxuL0Q%3DoZxc9wy85YfxGLg%40mail.<https://groups.google.com/d/msgid/druid-development/
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/
54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com54C2027F-E632-4DD5-B56E-CB4B62933C16%40gmail.com?utm_<https://groups.google.com/d/msgid/druid-development/
medium=email&utm_source=footer>send.
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,
an email to druid-development+unsubscribe@googlegroups.com.
To post to this group, send email to
To view this discussion on the web visit
2BrPSbbtFogY%3D%2BofXim0Nx7%3DwiMeNEpWoQmk5LK-YaaAa45%
3DxQ%40mail.gmail.com2BrPSbbtFogY%3D%2BofXim0Nx7%3DwiMeNEpWoQmk5LK-YaaAa45%<https://groups.google.com/d/msgid/druid-development/CA%
3DxQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
send.
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,
an email to druid-development+unsubscribe@googlegroups.com.
To post to this group, send email to
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/
3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org3824007F-F046-4E11-AF3C-04F43D242C97%40apache.org?utm_<https://groups.google.com/d/msgid/druid-development/
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@
3DwdPA2BhCFqYWO6CXFZ%3Djh5AWOJqLbP_2G1RimHCZWYFTA%40mail.gmail.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/CAB5L%3DwdPA2BhCFqYWO6CXFZ%3Djh5AWOJqLbP_2G1RimHCZWYFTA%<https://groups.google.com/d/msgid/druid-development/CAB5L%
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.comA4F427A9-44FD-4C64-B68A-557126705DC7%40gmail.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/A4F427A9-44FD-4C64-B68A-557126705DC7%40gmail.com?utm_<https://groups.google.com/d/msgid/druid-development/
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.CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.gmail.comTo view this discussion on the web visit
https://groups.google.com/d/msgid/druid-development/CABs1683hX6qZEc8MzkpBXu5rq3DwY07sS1YrNtv4JeW9G7h8fQ%40mail.<https://groups.google.com/d/msgid/druid-development/
gmail.com?utm_medium=email&utm_source=footer>
Groups.--
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Googlean"Druid Development" group.
To unsubscribe from this group and stop receiving emails from it, send
To post to this group, send email to druid-development@googlegroups.com
.
To view this discussion on the web visit
2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.gmail.com2BrPSbaXvqfv2OEMMUTuwZfhS1uiE9LmAeqo4J1proWFpA00gA%40mail.<https://groups.google.com/d/msgid/druid-development/CA%
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
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.
Quick note to say that apache sets up both http://druid.incubator.apache.org/ and http://druid.apache.org/ to point to the same place. I'd recommend always referencing and using http://druid.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.