2015-10-08 4:06 GMT-07:00 Nigel Magnay <[email protected]>: > +1 > > I'd imagined something like www.git-scm.com. They've had over 100 > individual contributors. >
Yep, another static site backed by Git ... oh wait, it's actually a Rails app. Hmm. > I'd completely bin comments. I don't see why the site needs to *host* a > blog - why can't it just be links to Jenkins articles elsewhere. > http://jenkins-ci.org/node is one of the few channels that we have to reach to users. So I hope everyone agrees that we should continue that, regardless of where it ends up to be. The reason I advocate for putting it together with the website is (1) that's where it is today, and (2) this is one of the contents for which we want more contributors, so git+PR model helps. > Bigger requirements just end up sucking you towards the cpu-suck, > security-nightmare and 'who has review/approve and commit bits' CRM > nightmares like Wordpress. > > On Thu, Oct 8, 2015 at 12:45 AM, Daniel Beck <[email protected]> wrote: > >> So from aggregating existing comments it looks to me like the following >> seems to be at least a reasonable basis for further discussion: >> >> * Use a static site generator with a Git repo on GitHub as the source for >> the site. Goal: Allow community to contribute content. >> [Updated Confluence could also work, but would retain the problems of >> unreviewed content, comments, and non-plain text editing.] >> * Have actual content, like good documentation, especially for getting >> started. This includes moving some of the wiki's content into the site. >> * Feature the blog [and possibly the event calendar] more prominently. >> * Do not have "comments everywhere", limit to specific sections like the >> blog. >> * Make it easy to contribute, possibly through having an "Edit" ("Improve >> this page"?) link on every page, if possible. >> >> Comments? >> >> -- >> 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/0146B189-5C80-4098-A05C-CE833E5CF5B2%40beckweb.net >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CAPYP83TihgMF9gEGQXnpXF9%3DK6ETy2eNVhi-9sajXCgNC%2B4oMg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPYP83TihgMF9gEGQXnpXF9%3DK6ETy2eNVhi-9sajXCgNC%2B4oMg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kohsuke Kawaguchi -- 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/CAN4CQ4wKmEt3%2BAg3EwRiySfgTpBs60AqWOxnR7-0fd-0COg%3DLQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
