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.wiele...@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 <emilian.b...@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 <humbed...@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.reim...@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" <
> > > bdelacre...@apache.org
> > > >>> :
> > > >>
> > > >>> Hi,
> > > >>>
> > > >>> On Mon, Oct 17, 2016 at 8:48 AM, Geertjan Wielenga
> > > >>> <geertjan.wiele...@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

Reply via email to