On Mon, Oct 17, 2016 at 2:57 PM, Daniel Gruno wrote: > Provided Oracle grants us netbeans.org, there is no need to move any > URLs. The user-facing part of the web site can live at netbeans.org, > that's not an issue. The only thing that MUST live at > netbeans.apache.org is the developer/project facing web site.
On Tue, Oct 18, 2016 at 8:59 AM, Bertrand Delacretaz wrote: > Both should be on apache.org infrastructure, similar to the NetBeans code. I'm trying to understand what we must do with netbeans.org. From Daniel's response, I take it we will have facilities at Apache where we need to publish developer/project facing information -- i.e., javadoc, build instructions, and more (what else?), while potentially everything else (the user-facing part of the web site) stays precisely where it is. From Bertrand, I understand that we need to also move the user-facing part of the web site to Apache. I'm sure there's no contradiction between these but I'm just trying to understand them and need some help with that. Is there a specific project, e.g., Maven or Groovy, that we can use as a model for how we will do our web site? I'm not sure it matters which choice we make so long as it works and having a specific project we could use as some kind of template might help. Thanks, Gj On Tue, Oct 18, 2016 at 11:12 AM, Anton Epple <toni.ep...@eppleton.de> wrote: > Hi Bertrand, > > I replied, because the earlier messages in this thread suggested that some > projects use github for hosting their website (and the source code for > them) using github pages: > > > I just had a look and it seems Apache Groovy ist hosting > > http://www.groovy-lang.org <http://www.groovy-lang.org/> on github.... > > ‹Toni > > > Am 18.10.16, 10:16 schrieb "Bertrand Delacretaz" unter > <bdelacre...@apache.org>: > > >On Tue, Oct 18, 2016 at 10:12 AM, Anton Epple <toni.ep...@eppleton.de> > >wrote: > >> ...Github hosting of websites is not a good solution for us anyway. It > >>lacks > >> https support for custom domains (only available for github.io > >>domains)... > > > >The websites won't be hosted on GitHub but their "source code" > >(content) might be mirrored there from Apache Git repositories if > >that's useful. > > > >-Bertrand > > >
