(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 commit that changes both source code and the web site. And it prevents the source repo from becoming really large (generated web sites can be large if you deploy 100M of generated java doc each release). You don’t want every contributor to have to download a huge git repo. Julian > On Apr 16, 2018, at 8:48 AM, Gian Merlino <g...@apache.org> wrote: > > 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 similar to what we do on > https://github.com/druid-io/druid-io.github.io, where sources are in "src" > and the built site is in "master". Except when using ASF infra, it makes > more sense to put the sources in "master" and the built site in "asf-git". > > > On Sun, Apr 15, 2018 at 3:58 PM, Julian Hyde <jh...@apache.org> wrote: > >> There has been some back-channel discussion about the web site. >> >> Druid has a good and successful web site outside of Apache, namely >> druid.io <http://druid.io/>. We cannot start transitioning that site >> until the legal IP transfer has completed. In the mean time, we were left >> without a web site: requests to http://druid.apache.org/ < >> http://druid.apache.org/> and http://druid.incubator.apache.org/ < >> http://druid.incubator.apache.org/> would receive an HTTP 404. >> >> Gian has created a simple web site in Apache that has hyperlinks to >> druid.io <http://druid.io/> and references the current user list >> druid-u...@googlegroups.com <mailto:druid-u...@googlegroups.com>. Links >> to outside Apache regarded as a breach of Apache branding policy and are >> frowned upon; but as a mentor I totally understand why they are necessary: >> Druid has a great community, and we must protect that community during the >> transition to Apache. >> >> The current web site is good enough for the short-term, but let’s get a >> proper branding-compliant web site up and running as soon as we can. Let’s >> make it one of the “top three” tasks listed in each board report. >> >> I see [1] that Gian is pushing to move traffic from >> druid-...@googlegroups.com <mailto:druid-...@googlegroups.com> to this >> dev list. That effort is most welcome, also. >> >> Julian >> >> [1] https://groups.google.com/d/msg/druid-development/q1ip- >> L8xpBk/hDCYaIsQCgAJ <https://groups.google.com/d/ >> msg/druid-development/q1ip-L8xpBk/hDCYaIsQCgAJ> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
