A technical note that I also posted in the "migration logistics" thread:
the sources for the site are at
https://github.com/apache/incubator-druid-website. The branch "asf-git" is
served on the site https://druid.incubator.apache.org/. I think once we
migrate http://druid.io/, we could do something
(Speaking not as a mentor, just someone who has deployed sites on ASF
infrastructure.)
What makes most sense to me is to put the web site source in master along with
the source code, and to put the generated site in a different git repo (not
just a different branch). It allows you to make a com
We have a bit of a hybrid setup today: the docs (a big part of the site)
are in the main "druid" repo. The rest of the site (landing page, news
page, download page) are in a separate website repo. It makes sense to me
because we want to version the docs along with the code, but we _don't_
want to v
3 repos makes sense to me. I believe that ASF infra can handle it.
And you have a one-time opportunity to clean out cruft from your source code
repo as you move to ASF.
Julian
> On Apr 16, 2018, at 9:58 AM, Gian Merlino wrote:
>
> We have a bit of a hybrid setup today: the docs (a big part o
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/
>