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.
My summary of the tech track discussion so far is that: - There's a proposal on the table best summarized in this post <https://groups.google.com/d/msg/jenkinsci-dev/EMbE3a4u8nA/WtgeVPcdCgAJ> and then in this Wiki page. <https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Daniel+Beck> This proposal seems to have a good support - Some others are pushing back on the plan - Content contributions would be too hard in this scheme (post <https://groups.google.com/d/msg/jenkinsci-dev/EMbE3a4u8nA/vokW1T-0CgAJ> ) - Running static site generator can be harder than you think I think Tyler is suggesting that he wants to create a prototype. Please continue the discussion in this thread... -- 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/CAN4CQ4ys0fc%3DfnT%2BLFw8Pr5iVo3Gdm%3DTfjy1eL%3DYYHAs3ckthg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
