I'm dividing up the website conversation into several tracks. See this Wiki page <https://wiki.jenkins-ci.org/display/JENKINS/2.0+Website> for the overall structure.
And in particular, in this thread let's focus on identifying pillars. In the original proposal that I made, which is captured very well in Daniel's wiki page <https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Daniel+Beck>, the key pillars of the website are: - Channels for us devs to engage the user community. Most notably blog. - Documentation for new users till they get up & running; feature highlights and curated getting started guide - Plugins, though I classified this under "things to do in the future" category Gus made a pitch <https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Gus+Reiber> that interaction among users should be the main pillar, which got a lot of push back. In the same pitch, he said downloads, plugins, and events are the other key pillars. Bobby made a comment that he sees the extensibility part of the website a key pillar because it speaks to the principle & DNA of this community. Hopefully I captured it correctly. Let's keep the discussion going here. -- 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/CAN4CQ4xNDWM9bM1PGpDAzp_oeoRB8BY5gYHX4A2yvwJXt05%3Dqg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
