Re: [druid-dev] Apache migration logistics

Hi Parag, You should be able to do it by checking out the repo at https://svn.apache.org/repos/asf/incubator/public and then adding yourself to the file trunk/content/projects/druid.xml. On Wed, Apr 18, 2018 at 11:25 AM, Parag Jain wrote: > I got my apache id

Re: [druid-dev] Apache migration logistics

Oh cool, I didn't realize that. We should stick to https://druid.apache.org/ then. Gian On Mon, Apr 16, 2018 at 10:51 AM, Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > Quick note to say that apache sets up both http://druid.incubator.ap > ache.org/ and http://druid.apache.org/ >

Re: [druid-dev] Apache migration logistics

Also, the sources for the site are at: https://github.com/apache/incubator-druid-website. The branch "asf-git" is served on the site. I think once we migrate http://druid.io/, we could do something similar to what we do on https://github.com/druid-io/druid-io.github.io, where sources are in "src"

Re: [druid-dev] Apache migration logistics

FYI: We received an inquiry about where our web site was, and so we set up a placeholder site at: http://druid.incubator.apache.org/. Last I heard, the SGA paperwork is still being worked on, and after that is done we should start migrating the sources and site. In the meantime should we

Re: [druid-dev] Apache migration logistics

Per https://incubator.apache.org/guides/transitioning_asf.html we need to get SGA/CCLA on file, then we should file a JIRA case similar to https://issues.apache.org/jira/browse/INFRA-15735

Re: [druid-dev] Apache migration logistics

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

Re: [druid-dev] Apache migration logistics

I think rather than subscribing the apache dev list to the google group, it'd be better to do a clean break and disable posting on the google group. The autoreply feature seems to need a business account, which we don't have, but we could turn on "Moderate all messages to the group" and combine

Re: [druid-dev] Apache migration logistics

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

Re: [druid-dev] Apache migration logistics

FYI, to update your information on the status page you need to check out https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/ with your Apache credentials and update the druid.xml file in that directory. On Mon, Mar 12, 2018 at 2:49 PM Gian Merlino wrote: >

Re: [druid-dev] Apache migration logistics

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

Re: [druid-dev] Apache migration logistics

We can register dev@druid.apache.org and us...@druid.apache.org as a user in druid user groups so that going forward any mails that are sent to druid google groups are also received on the apache lists and is on the record. This would be to bridge the gap during the migration only. @Julian, I go

Re: [druid-dev] Apache migration logistics

I don’t know. I don’t think it’s easy. > On Mar 9, 2018, at 7:31 AM, Roman Leventov > 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

Re: [druid-dev] Apache migration logistics

Could archives of druid-dev and druid-users mailing lists be transferred to the new lists? On Thu, Mar 8, 2018 at 8:48 AM, Julian Hyde wrote: > I’m working on it. It turns that I don’t have sufficient karma to create a > git repo, so I’ve put in a request on the incubator

Re: [druid-dev] Apache migration logistics

I’m working on it. It turns that I don’t have sufficient karma to create a git repo, so I’ve put in a request on the incubator list. > On Mar 6, 2018, at 10:12 AM, Xavier Léauté wrote: > > Julian, it looks like you or one of the mentors has to request the source > code

Re: [druid-dev] Apache migration logistics

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