I think we need lots of people working on the content, not on the tool :-)
El 15/07/2019 a las 12:07, Geertjan Wielenga escribió:
If it ain't broke, don't fix it...
And do we expect lots of people to work on the site just because we switch
from Gradle to Gulp? Do we need lots of people working on the site,
especially since everything's working fine the way it is?
Gj
On Mon, Jul 15, 2019 at 12:05 PM Neil C Smith <neilcsm...@apache.org> wrote:
On Mon, 15 Jul 2019 at 10:51, Antonio <anto...@vieiro.net> wrote:
a) Keep the gradle build system, or
b) Rebuild the website build system using node/npm.
Opinions? Any other thoughts? Wishes?
Most immediate question would be what's the proposed replacement for
the JBake part of this?
Initial thought is the proposal is somewhat half-baked at present! :-)
Sorry, couldn't resist!
A simplified stack that more people understand would be good though.
Whether that is a switch from JVM to JS static site generation or
another SSG stack really depends on preferences and skills of our
community though, IMO.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
