OK, I get it now. Though, there's a big difference between "the user-facing
part of the web site can live at netbeans.org" and "you may use netbeans.org
for user-facing web site".
I.e., the question is where the content will LIVE -- and the impression
created, suddenly, was that everything could stay exactly as it currently
is, except for the developer/project facing content. That is, thus, not the
Personally, knowing the netbeans.org website reasonably well, from the
inside, I can say we do not want to migrate the website as a whole. Rather,
we should move the most current tutorials (I would suggest from 8.0
onwards) and the latest feature documentation to Apache and then archive
the entire netbeans.org content, so that anyone who wants to go back into
the past can do so, while we'll be able to focus on the most relevant
content. Should there be a big call for older documentation to be included
on Apache, we can include that too. But, there's simply heaps of
documentation and interviews and articles on old or dead features, hidden
in the bowels of netbeans.org, that make no sense to move to Apache.
Good to have this cleared up.
On Tue, Oct 18, 2016 at 12:56 PM, Daniel Gruno <humbed...@apache.org> wrote:
> On 10/18/2016 12:53 PM, Geertjan Wielenga wrote:
> > 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
> > I'm trying to understand what we must do with netbeans.org. From
> > 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
> > 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
> > I'm just trying to understand them and need some help with that.
> Bertrand and I are in agreement, but we are focusing on different
> topics. Let me expand :
> Infrastructure: All web sites MUST be on ASF hardware (our IPs, our
> Domain names: You may use netbeans.org for user-facing web site, and
> netbeans.apache.org for the developer site. both must, as stated above,
> be hosted at the ASF on our web servers.
> With regards,
> > 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
> > 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
> >> 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