Re: Druid repo migration plan

I asked in our original Infra ticket to adjust the mailing lists: https://issues.apache.org/jira/browse/INFRA-16674?focusedCommentId=16535589=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16535589 Unfortunately setting up filters proved challenging in Gmail (gitbox

Re: Druid repo migration plan

IMO, GitHub has good tools already for subscribing to repos, notifications, and issues. I would expect Druid contributors to use those tools and _not_ to join git...@druid.apache.org. I'd imagine the list would only exist for archival purposes (we want a copy of every discussion to be stored

Re: Druid repo migration plan

I see there are notifications not just for commits but for every comment on every issue. That’s going to be overwhelming. I can’t imagine anyone wanting to subscribe to the gitbox list at the current volume. How about only sending comments to people who have watched a particular case? Julian

Re: Druid repo migration plan

I like the idea of a separate list for commits. Keeps the noise down on the dev list. Other projects (e.g. calcite) would name that list “commits”, i.e. comm...@druid.apache.org . If you were to add other repos (e.g. a subversion repo for web site) you could

Re: Druid repo migration plan

+1 to sending to git...@druid.apache.org On Fri, Jul 6, 2018 at 12:17 PM, Gian Merlino wrote: > The repo move has happened: https://github.com/apache/incubator-druid > > My understanding is that now we can and should start prepping license, > notice, etc for a release. And also making sure that

Re: Druid repo migration plan

Here is the ticket, btw: https://issues.apache.org/jira/browse/INFRA-16674. Repo move should be happening real soon now! On Mon, Jul 2, 2018 at 11:55 PM Gian Merlino wrote: > Our infra ticket is progressing along and it looks like we're just about > ready to pull the trigger on moving the repo.

Re: Druid repo migration plan

@julian gotcha, I thought this was a more official vote The Superset GH move INFRA ticket shows how the move can be really tricky/slow/disruptive. There was quite a period of instability for us and a lot of slow back and forth with Apache infra. Hopefully the process has been ironed out since

Re: Druid repo migration plan

+1 Note that usually we would expect voting thread to have a `[VOTE]` prefix in the the email subject. Max On Thu, Jun 21, 2018 at 12:26 AM David Lim wrote: > +1 > > On Thu, Jun 21, 2018 at 12:55 AM, Himanshu wrote: > > > +1 ... Major milestone, thanks > > > > On Wed, Jun 20, 2018, 9:13 PM

Re: Druid repo migration plan

+1 On Thu, Jun 21, 2018 at 12:55 AM, Himanshu wrote: > +1 ... Major milestone, thanks > > On Wed, Jun 20, 2018, 9:13 PM Gian Merlino, wrote: > > > +1; thanks Jon! > > > > On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son wrote: > > > > > +1 > > > > > > Sounds good to me. > > > > > > Jihoon > > > > >

Re: Druid repo migration plan

+1 ... Major milestone, thanks On Wed, Jun 20, 2018, 9:13 PM Gian Merlino, wrote: > +1; thanks Jon! > > On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son wrote: > > > +1 > > > > Sounds good to me. > > > > Jihoon > > > > On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa < > > nbanga...@hortonworks.com>

Re: Druid repo migration plan

+1; thanks Jon! On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son wrote: > +1 > > Sounds good to me. > > Jihoon > > On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa < > nbanga...@hortonworks.com> > wrote: > > > +1 > > > > -- > > Nishant Bangarwa > > > > Hortonworks > > > > On 6/20/18, 3:57 PM,

Re: Druid repo migration plan

+1 Sounds good to me. Jihoon On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa wrote: > +1 > > -- > Nishant Bangarwa > > Hortonworks > > On 6/20/18, 3:57 PM, "Jonathan Wei" wrote: > > Hi all, > > The SGA for Druid has been sorted out, we can get started on migrating > the > old

Re: Druid repo migration plan

+1 -- Nishant Bangarwa Hortonworks On 6/20/18, 3:57 PM, "Jonathan Wei" wrote: Hi all, The SGA for Druid has been sorted out, we can get started on migrating the old Github repo to Apache. Based on the discussion in our previous migration thread (

Druid repo migration plan

Hi all, The SGA for Druid has been sorted out, we can get started on migrating the old Github repo to Apache. Based on the discussion in our previous migration thread ( https://groups.google.com/forum/#!msg/druid-development/q1ip-L8xpBk/GPK1LhC7BQAJ), it seems we favor using our existing Github