Fwd: [NOTICE] Upcoming changes to project web sites hosted via Git

[antonio <an...@vieiro.net>]

Hi all,

We'll need to modify the current mechanism for updating the NetBeans 
website. Deadline is June the 1st.

Maybe it's a good time to revamp/redesign the site and/or even review 
the current publishing mechanism. IIRC we had some fancy desktop designs 
(no mobile) without any SCSS counterparts, right?

Kind regards,
Antonio

P.S.:

An assorted & incomplete list of alternate build systems we may want to 
explore:

- Jekyll/Asciidoc : https://github.com/asciidoctor/jekyll-asciidoc
- https://antora.org/
- Asciidoctor gradle plugin 
https://asciidoctor.org/docs/asciidoctor-gradle-plugin/
- Asciidoctor-ant Task https://github.com/asciidoctor/asciidoctor-ant
- Node/NPM?



-------- Forwarded Message --------
Subject: [NOTICE] Upcoming changes to project web sites hosted via Git
Date: Mon, 5 Apr 2021 20:06:15 +0200
From: Daniel Gruno <hu...@apache.org>
To: Users <us...@infra.apache.org>

TL;DR: If your project uses subversion or .asf.yaml for publishing your 
project web site, you're fine. If not, please read this act before June 1st:


Hi folks,
I order to simplify workflows and the amount of services we have to 
maintain, we've decided to phase out gitwcsub in favor of stageD. What 
this means in plain English is that all project web sites hosted from a 
git repository MUST have publishing settings in a .asf.yaml file for 
them to update web sites in the future.

This change will take effect around June 1st, giving projects two months 
to complete the transition. In about four weeks, we'll be sending emails 
directly to every project that is still using the old gitwcsub methods 
for their web sites, encouraging them to switch before we decommission 
the service.

Once the gitwcsub service has been shut off, projects that haven't 
switched won't be able to update their web sites until they perform the 
switch.

For projects wishing to proactively switch, the change is minimal. All 
you need to do is have a file called .asf.yaml at the base of your web 
site repository (or the branch in your git repo that hosts your web 
site), with the following snippet inside:

publish:
   whoami: asf-site


This is, of course, assuming your published branch is the standard 
asf-site branch. It could be master or something else.

Projects wishing to check where we are currently collecting their web 
sites from, can go to https://infra-reports.apache.org/site-source/ and 
see all our sources for the web sites. The column on your right will 
tell if you are using .asf.yaml for your web site or not.

For more information on .asf.yaml and its features (such as staging web 
sites etc), please see https://s.apache.org/asfyaml

With regards,
Daniel on behalf of ASF Infra.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists