You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Geertjan Wielenga <ge...@googlemail.com> on 2016/10/17 06:48:07 UTC
Website transition
Hi all,
Now that we have mailing lists and Wiki -- a next step is to have a
website, i.e., primarily to list the features of Apache NetBeans and to
make the documentation and tutorials available, i.e., to have a place to
move the relevant parts of netbeans.org.
Or is the Wiki also going to be functioning as the website?
Not clear on that -- this would be good to have clarified and set up.
Thanks,
Geertjan
Re: Website transition
Posted by Raphael Bircher <rb...@gmail.com>.
Hi Geertjan, *
Am 10/17/2016 um 8:48 AM schrieb Geertjan Wielenga:
> Hi all,
>
> Now that we have mailing lists and Wiki -- a next step is to have a
> website, i.e., primarily to list the features of Apache NetBeans and to
> make the documentation and tutorials available, i.e., to have a place to
> move the relevant parts of netbeans.org.
>
> Or is the Wiki also going to be functioning as the website?
No, as far as i know, the Website has to be on the website servers. This
has mainly performance reasons. And I assum that NetBeans has a load of
hits per day. If you have this all on the wiki, you will crash it ;-)
Regards Raphael
Re: Website transition
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Oct 18, 2016 at 1:02 PM, Geertjan Wielenga
<ge...@googlemail.com> wrote:
>...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....
Assuming preserving that history is important, you might move it to a
separate archive.netbeans.org domain to preserve it - maybe just
static HTML to keep things simple.
If you choose that option I recommend having redirects from the old
URLs as there are probably tons of links in the wild.
-Bertrand
Re: Website transition
Posted by Geertjan Wielenga <ge...@googlemail.com>.
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
case.
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.
Gj
On Tue, Oct 18, 2016 at 12:56 PM, Daniel Gruno <hu...@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
> 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.
>
> 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
> machines)
> 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,
> Daniel
>
> >
> > 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 <to...@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
> >> <bd...@apache.org>:
> >>
> >>> On Tue, Oct 18, 2016 at 10:12 AM, Anton Epple <to...@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
> >>
> >>
> >>
> >
>
>
Re: Website transition
Posted by Daniel Gruno <hu...@apache.org>.
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 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.
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
machines)
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,
Daniel
>
> 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 <to...@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....
>>
>> \u2039Toni
>>
>>
>> Am 18.10.16, 10:16 schrieb "Bertrand Delacretaz" unter
>> <bd...@apache.org>:
>>
>>> On Tue, Oct 18, 2016 at 10:12 AM, Anton Epple <to...@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
>>
>>
>>
>
Re: Website transition
Posted by Geertjan Wielenga <ge...@googlemail.com>.
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 <to...@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
> <bd...@apache.org>:
>
> >On Tue, Oct 18, 2016 at 10:12 AM, Anton Epple <to...@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
>
>
>
Re: Website transition
Posted by Anton Epple <to...@eppleton.de>.
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
<bd...@apache.org>:
>On Tue, Oct 18, 2016 at 10:12 AM, Anton Epple <to...@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
Re: Website transition
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Oct 18, 2016 at 10:12 AM, Anton Epple <to...@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
Re: Website transition
Posted by Anton Epple <to...@eppleton.de>.
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).
Toni
Am 18.10.16, 08:59 schrieb "Bertrand Delacretaz" unter
<bd...@apache.org>:
>On Mon, Oct 17, 2016 at 11:17 PM, Geertjan Wielenga
><ge...@googlemail.com> wrote:
>> ...the question will be where the infrastructure and content for
>>netbeans.org will
>> live...
>
>Both should be on apache.org infrastructure, similar to the NetBeans code.
>
>GitHub mirrors are fine but the canonical repository must be on Apache
>infrastructure - I'd say this means generating the content from an
>Apache repository, but our infra team might clarify.
>
>plugins.netbeans.org is different as that's about distributing
>binaries, so there are different concerns.
>
>-Bertrand
Re: Website transition
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Oct 17, 2016 at 11:17 PM, Geertjan Wielenga
<ge...@googlemail.com> wrote:
> ...the question will be where the infrastructure and content for netbeans.org will
> live...
Both should be on apache.org infrastructure, similar to the NetBeans code.
GitHub mirrors are fine but the canonical repository must be on Apache
infrastructure - I'd say this means generating the content from an
Apache repository, but our infra team might clarify.
plugins.netbeans.org is different as that's about distributing
binaries, so there are different concerns.
-Bertrand
Re: Website transition
Posted by Sven Reimers <sv...@gmail.com>.
Hi,
I just had a look and it seems Apache Groovy ist hosting
http://www.groovy-lang.org on github....
hmmm
Sven
On Mon, Oct 17, 2016 at 11:17 PM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Can an example be provided of a project that has a developer site on Apache
> and a user site somewhere else? Just to see the difference in the info,
> though I think someone provided such an example before but I can't remember
> what it was.
>
> Ideally, we'd move out of Oracle's systems completely -- i.e., we'll have
> netbeans.apache.org for the developer info (I guess this would be javadoc
> and other documentation for developing Apache NetBeans?) and netbeans.org
> for user documentation. The latter we have already right now. So then the
> question will be where the infrastructure and content for netbeans.org
> will
> live -- would this be comparable to plugins.netbeans.org in the sense that
> it would need to be hosted by another organization of some kind?
>
> Can the website for netbeans.apache.org be set up, for the
> developer/project facing website, who must do that and when does that
> happen in the process?
>
> Thanks,
>
> Geertjan
>
>
> On Mon, Oct 17, 2016 at 3:00 PM, Emilian Bold <em...@gmail.com>
> wrote:
>
> > @Daniel this is the first time I hear this!
> >
> > Yes, Oracle will grant the netbeans.org domain, it's part of the
> Incubator
> > proposal (https://wiki.apache.org/incubator/NetBeansProposal ):
> >
> > Oracle owns trademark registrations for the NetBeans mark in the U.S. and
> > > EU, and would donate those, including the name "NetBeans" and the "
> > > netbeans.org" domain, to the Apache Foundation, along with other
> > > artifacts, including the U.S. copyright registrations related to
> > NetBeans.
> > > The trademark and copyright transfers would be detailed in separate
> > > documents.
> >
> >
> >
> >
> > --emi
> >
> > On Mon, Oct 17, 2016 at 3:57 PM, Daniel Gruno <hu...@apache.org>
> > wrote:
> >
> > > On 10/17/2016 10:47 AM, Emilian Bold wrote:
> > > > BTW, in order to maintain our search engine ratings, we should
> migrate
> > as
> > > > much as possible from netbeans.org to the new domain and use 301
> > > redirects.
> > >
> > > 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.
> > >
> > > With regards,
> > > Daniel.
> > >
> > > >
> > > > https://support.google.com/webmasters/answer/93633?hl=en
> > > >
> > > > This can be a gradual process, as we move a tutorial or something we
> > add
> > > a
> > > > 301 on netbeans.org for that URL. The final 301 should be from the
> > > > netbeans.org toplevel domain.
> > > >
> > > > This Google doc also seems helpful
> > > > https://support.google.com/webmasters/topic/6029673?hl=
> > > en&ref_topic=6001951
> > > >
> > > >
> > > >
> > > > --emi
> > > >
> > > > On Mon, Oct 17, 2016 at 11:35 AM, Sven Reimers <
> sven.reimers@gmail.com
> > >
> > > > wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> +1 for a solution like GitHub pages. I would prefer asciidoc (I
> think
> > > the
> > > >> groovy guys are working along such a process already)
> > > >>
> > > >> Sven
> > > >>
> > > >> Am 17.10.2016 10:09 schrieb "Bertrand Delacretaz" <
> > > bdelacretaz@apache.org
> > > >>> :
> > > >>
> > > >>> Hi,
> > > >>>
> > > >>> On Mon, Oct 17, 2016 at 8:48 AM, Geertjan Wielenga
> > > >>> <ge...@googlemail.com> wrote:
> > > >>>> ...Now that we have mailing lists and Wiki -- a next step is to
> > have a
> > > >>>> website...
> > > >>>
> > > >>> Quoting Daniel Gruno (our infra mentor) from a previous thread
> here:
> > > >>>
> > > >>>> As for web site, there's the choice between a static site where we
> > > just
> > > >>>> have a pubsub system (you commit html to svn or git and it gets
> > > >>>> published), or we can have a build bot generate the site with
> > whatever
> > > >>>> tech we want and just commit the...markdown/rst/whatever docs we
> > use,
> > > >>>> kind'a like GitHub pages etc.
> > > >>>
> > > >>> I think something like GitHub pages (running on asf infrastructure,
> > > >>> that's a requirement) is the most convenient, but I suppose
> existing
> > > >>> content will be migrated and that might have an impact which option
> > is
> > > >>> best.
> > > >>>
> > > >>> -Bertrand
> > > >>>
> > > >>
> > > >
> > >
> > >
> >
>
--
Sven Reimers
* Senior Expert Software Architect
* Java Champion
* NetBeans Dream Team Member: http://dreamteam.netbeans.org
* Community Leader NetBeans: http://community.java.net/netbeans
Desktop Java:
http://community.java.net/javadesktop
* JUG Leader JUG Bodensee: http://www.jug-bodensee.de
* Duke's Choice Award Winner 2009
* XING: https://www.xing.com/profile/Sven_Reimers8
* LinkedIn: http://www.linkedin.com/in/svenreimers
Re: Website transition
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Can an example be provided of a project that has a developer site on Apache
and a user site somewhere else? Just to see the difference in the info,
though I think someone provided such an example before but I can't remember
what it was.
Ideally, we'd move out of Oracle's systems completely -- i.e., we'll have
netbeans.apache.org for the developer info (I guess this would be javadoc
and other documentation for developing Apache NetBeans?) and netbeans.org
for user documentation. The latter we have already right now. So then the
question will be where the infrastructure and content for netbeans.org will
live -- would this be comparable to plugins.netbeans.org in the sense that
it would need to be hosted by another organization of some kind?
Can the website for netbeans.apache.org be set up, for the
developer/project facing website, who must do that and when does that
happen in the process?
Thanks,
Geertjan
On Mon, Oct 17, 2016 at 3:00 PM, Emilian Bold <em...@gmail.com>
wrote:
> @Daniel this is the first time I hear this!
>
> Yes, Oracle will grant the netbeans.org domain, it's part of the Incubator
> proposal (https://wiki.apache.org/incubator/NetBeansProposal ):
>
> Oracle owns trademark registrations for the NetBeans mark in the U.S. and
> > EU, and would donate those, including the name "NetBeans" and the "
> > netbeans.org" domain, to the Apache Foundation, along with other
> > artifacts, including the U.S. copyright registrations related to
> NetBeans.
> > The trademark and copyright transfers would be detailed in separate
> > documents.
>
>
>
>
> --emi
>
> On Mon, Oct 17, 2016 at 3:57 PM, Daniel Gruno <hu...@apache.org>
> wrote:
>
> > On 10/17/2016 10:47 AM, Emilian Bold wrote:
> > > BTW, in order to maintain our search engine ratings, we should migrate
> as
> > > much as possible from netbeans.org to the new domain and use 301
> > redirects.
> >
> > 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.
> >
> > With regards,
> > Daniel.
> >
> > >
> > > https://support.google.com/webmasters/answer/93633?hl=en
> > >
> > > This can be a gradual process, as we move a tutorial or something we
> add
> > a
> > > 301 on netbeans.org for that URL. The final 301 should be from the
> > > netbeans.org toplevel domain.
> > >
> > > This Google doc also seems helpful
> > > https://support.google.com/webmasters/topic/6029673?hl=
> > en&ref_topic=6001951
> > >
> > >
> > >
> > > --emi
> > >
> > > On Mon, Oct 17, 2016 at 11:35 AM, Sven Reimers <sven.reimers@gmail.com
> >
> > > wrote:
> > >
> > >> Hi all,
> > >>
> > >> +1 for a solution like GitHub pages. I would prefer asciidoc (I think
> > the
> > >> groovy guys are working along such a process already)
> > >>
> > >> Sven
> > >>
> > >> Am 17.10.2016 10:09 schrieb "Bertrand Delacretaz" <
> > bdelacretaz@apache.org
> > >>> :
> > >>
> > >>> Hi,
> > >>>
> > >>> On Mon, Oct 17, 2016 at 8:48 AM, Geertjan Wielenga
> > >>> <ge...@googlemail.com> wrote:
> > >>>> ...Now that we have mailing lists and Wiki -- a next step is to
> have a
> > >>>> website...
> > >>>
> > >>> Quoting Daniel Gruno (our infra mentor) from a previous thread here:
> > >>>
> > >>>> As for web site, there's the choice between a static site where we
> > just
> > >>>> have a pubsub system (you commit html to svn or git and it gets
> > >>>> published), or we can have a build bot generate the site with
> whatever
> > >>>> tech we want and just commit the...markdown/rst/whatever docs we
> use,
> > >>>> kind'a like GitHub pages etc.
> > >>>
> > >>> I think something like GitHub pages (running on asf infrastructure,
> > >>> that's a requirement) is the most convenient, but I suppose existing
> > >>> content will be migrated and that might have an impact which option
> is
> > >>> best.
> > >>>
> > >>> -Bertrand
> > >>>
> > >>
> > >
> >
> >
>
Re: Website transition
Posted by Emilian Bold <em...@gmail.com>.
@Daniel this is the first time I hear this!
Yes, Oracle will grant the netbeans.org domain, it's part of the Incubator
proposal (https://wiki.apache.org/incubator/NetBeansProposal ):
Oracle owns trademark registrations for the NetBeans mark in the U.S. and
> EU, and would donate those, including the name "NetBeans" and the "
> netbeans.org" domain, to the Apache Foundation, along with other
> artifacts, including the U.S. copyright registrations related to NetBeans.
> The trademark and copyright transfers would be detailed in separate
> documents.
--emi
On Mon, Oct 17, 2016 at 3:57 PM, Daniel Gruno <hu...@apache.org> wrote:
> On 10/17/2016 10:47 AM, Emilian Bold wrote:
> > BTW, in order to maintain our search engine ratings, we should migrate as
> > much as possible from netbeans.org to the new domain and use 301
> redirects.
>
> 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.
>
> With regards,
> Daniel.
>
> >
> > https://support.google.com/webmasters/answer/93633?hl=en
> >
> > This can be a gradual process, as we move a tutorial or something we add
> a
> > 301 on netbeans.org for that URL. The final 301 should be from the
> > netbeans.org toplevel domain.
> >
> > This Google doc also seems helpful
> > https://support.google.com/webmasters/topic/6029673?hl=
> en&ref_topic=6001951
> >
> >
> >
> > --emi
> >
> > On Mon, Oct 17, 2016 at 11:35 AM, Sven Reimers <sv...@gmail.com>
> > wrote:
> >
> >> Hi all,
> >>
> >> +1 for a solution like GitHub pages. I would prefer asciidoc (I think
> the
> >> groovy guys are working along such a process already)
> >>
> >> Sven
> >>
> >> Am 17.10.2016 10:09 schrieb "Bertrand Delacretaz" <
> bdelacretaz@apache.org
> >>> :
> >>
> >>> Hi,
> >>>
> >>> On Mon, Oct 17, 2016 at 8:48 AM, Geertjan Wielenga
> >>> <ge...@googlemail.com> wrote:
> >>>> ...Now that we have mailing lists and Wiki -- a next step is to have a
> >>>> website...
> >>>
> >>> Quoting Daniel Gruno (our infra mentor) from a previous thread here:
> >>>
> >>>> As for web site, there's the choice between a static site where we
> just
> >>>> have a pubsub system (you commit html to svn or git and it gets
> >>>> published), or we can have a build bot generate the site with whatever
> >>>> tech we want and just commit the...markdown/rst/whatever docs we use,
> >>>> kind'a like GitHub pages etc.
> >>>
> >>> I think something like GitHub pages (running on asf infrastructure,
> >>> that's a requirement) is the most convenient, but I suppose existing
> >>> content will be migrated and that might have an impact which option is
> >>> best.
> >>>
> >>> -Bertrand
> >>>
> >>
> >
>
>
Re: Website transition
Posted by Daniel Gruno <hu...@apache.org>.
On 10/17/2016 10:47 AM, Emilian Bold wrote:
> BTW, in order to maintain our search engine ratings, we should migrate as
> much as possible from netbeans.org to the new domain and use 301 redirects.
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.
With regards,
Daniel.
>
> https://support.google.com/webmasters/answer/93633?hl=en
>
> This can be a gradual process, as we move a tutorial or something we add a
> 301 on netbeans.org for that URL. The final 301 should be from the
> netbeans.org toplevel domain.
>
> This Google doc also seems helpful
> https://support.google.com/webmasters/topic/6029673?hl=en&ref_topic=6001951
>
>
>
> --emi
>
> On Mon, Oct 17, 2016 at 11:35 AM, Sven Reimers <sv...@gmail.com>
> wrote:
>
>> Hi all,
>>
>> +1 for a solution like GitHub pages. I would prefer asciidoc (I think the
>> groovy guys are working along such a process already)
>>
>> Sven
>>
>> Am 17.10.2016 10:09 schrieb "Bertrand Delacretaz" <bdelacretaz@apache.org
>>> :
>>
>>> Hi,
>>>
>>> On Mon, Oct 17, 2016 at 8:48 AM, Geertjan Wielenga
>>> <ge...@googlemail.com> wrote:
>>>> ...Now that we have mailing lists and Wiki -- a next step is to have a
>>>> website...
>>>
>>> Quoting Daniel Gruno (our infra mentor) from a previous thread here:
>>>
>>>> As for web site, there's the choice between a static site where we just
>>>> have a pubsub system (you commit html to svn or git and it gets
>>>> published), or we can have a build bot generate the site with whatever
>>>> tech we want and just commit the...markdown/rst/whatever docs we use,
>>>> kind'a like GitHub pages etc.
>>>
>>> I think something like GitHub pages (running on asf infrastructure,
>>> that's a requirement) is the most convenient, but I suppose existing
>>> content will be migrated and that might have an impact which option is
>>> best.
>>>
>>> -Bertrand
>>>
>>
>
Re: Website transition
Posted by Emilian Bold <em...@gmail.com>.
BTW, in order to maintain our search engine ratings, we should migrate as
much as possible from netbeans.org to the new domain and use 301 redirects.
https://support.google.com/webmasters/answer/93633?hl=en
This can be a gradual process, as we move a tutorial or something we add a
301 on netbeans.org for that URL. The final 301 should be from the
netbeans.org toplevel domain.
This Google doc also seems helpful
https://support.google.com/webmasters/topic/6029673?hl=en&ref_topic=6001951
--emi
On Mon, Oct 17, 2016 at 11:35 AM, Sven Reimers <sv...@gmail.com>
wrote:
> Hi all,
>
> +1 for a solution like GitHub pages. I would prefer asciidoc (I think the
> groovy guys are working along such a process already)
>
> Sven
>
> Am 17.10.2016 10:09 schrieb "Bertrand Delacretaz" <bdelacretaz@apache.org
> >:
>
> > Hi,
> >
> > On Mon, Oct 17, 2016 at 8:48 AM, Geertjan Wielenga
> > <ge...@googlemail.com> wrote:
> > > ...Now that we have mailing lists and Wiki -- a next step is to have a
> > > website...
> >
> > Quoting Daniel Gruno (our infra mentor) from a previous thread here:
> >
> > > As for web site, there's the choice between a static site where we just
> > > have a pubsub system (you commit html to svn or git and it gets
> > > published), or we can have a build bot generate the site with whatever
> > > tech we want and just commit the...markdown/rst/whatever docs we use,
> > > kind'a like GitHub pages etc.
> >
> > I think something like GitHub pages (running on asf infrastructure,
> > that's a requirement) is the most convenient, but I suppose existing
> > content will be migrated and that might have an impact which option is
> > best.
> >
> > -Bertrand
> >
>
Re: Website transition
Posted by Sven Reimers <sv...@gmail.com>.
Hi all,
+1 for a solution like GitHub pages. I would prefer asciidoc (I think the
groovy guys are working along such a process already)
Sven
Am 17.10.2016 10:09 schrieb "Bertrand Delacretaz" <bd...@apache.org>:
> Hi,
>
> On Mon, Oct 17, 2016 at 8:48 AM, Geertjan Wielenga
> <ge...@googlemail.com> wrote:
> > ...Now that we have mailing lists and Wiki -- a next step is to have a
> > website...
>
> Quoting Daniel Gruno (our infra mentor) from a previous thread here:
>
> > As for web site, there's the choice between a static site where we just
> > have a pubsub system (you commit html to svn or git and it gets
> > published), or we can have a build bot generate the site with whatever
> > tech we want and just commit the...markdown/rst/whatever docs we use,
> > kind'a like GitHub pages etc.
>
> I think something like GitHub pages (running on asf infrastructure,
> that's a requirement) is the most convenient, but I suppose existing
> content will be migrated and that might have an impact which option is
> best.
>
> -Bertrand
>
Re: Website transition
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Mon, Oct 17, 2016 at 8:48 AM, Geertjan Wielenga
<ge...@googlemail.com> wrote:
> ...Now that we have mailing lists and Wiki -- a next step is to have a
> website...
Quoting Daniel Gruno (our infra mentor) from a previous thread here:
> As for web site, there's the choice between a static site where we just
> have a pubsub system (you commit html to svn or git and it gets
> published), or we can have a build bot generate the site with whatever
> tech we want and just commit the...markdown/rst/whatever docs we use,
> kind'a like GitHub pages etc.
I think something like GitHub pages (running on asf infrastructure,
that's a requirement) is the most convenient, but I suppose existing
content will be migrated and that might have an impact which option is
best.
-Bertrand
Re: Website transition
Posted by Raphael Bircher <rb...@gmail.com>.
Hi all
Am 10/17/2016 um 8:48 AM schrieb Geertjan Wielenga:
> Hi all,
>
> Now that we have mailing lists and Wiki -- a next step is to have a
> website, i.e., primarily to list the features of Apache NetBeans and to
> make the documentation and tutorials available, i.e., to have a place to
> move the relevant parts of netbeans.org.
I wonder what you have now as website framework?
Regards Raphael