TOP POSTING because holy mega-thread batman! :) What I see happening here is solutions being mixed up with problem statements
The top-level goals, in my opinion are (in no particular order):
* Make a good usable site, that looks good and connects visitors with the
information that is relevant to them as quickly as is possible (note: this
does not necessitate that all content lives on-site)
* Enable members of the community, ourselves included, to quickly and easily
manage and contribute content to the site
These aren't mutually exclusive goals.
I think this thread has been good in surfacing lots of ideas and opinions about
jenkins-ci.org, but what I'd like to do now is spend a little bit of time doing
like Daniel did and throw up a prototype or two. I have some ideas around
asciidoctor(.org) and an actual site-build process which can morph static
content into a more "live" site.
Anyways, if you're passionate about the subject, fleshing out ideas and
proposals in confluence is IMHO the best path forward.
Cheers
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/20151009213413.GG2353%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
