Joe, I added those in. IMHO, our wiki should just "export" content and then it gets "styled" up and be put on cloudstack.org.
Take a look at cxf landing page vs the wiki. Their landing page is nothing more than dressed up wiki. Landing page: http://cxf.apache.org/ wiki: https://cwiki.apache.org/CXF/ This has a few benefits: - Reduces the things we have to keep track of to a minimum. - Familiar platform for people who want to write things targeted to the end user/cloud operator. - End user/cloud operator has a natural way to dig deeper. Our collaborations should happen on the mailing list but once a consensus is achieved someone should write something on the wiki. This is similar to how we're doing the FSes currently. David has gotten admin privilege to allow us to customize the html export of our wiki. I haven't had any time to look at it though (partly because I can only tinker with it through David since I have no such karma so it's slow for me to get started.) --Alex > -----Original Message----- > From: Joe Brockmeier [mailto:j...@zonker.net] > Sent: Wednesday, February 13, 2013 8:55 AM > To: CloudStack Developers > Subject: [DISCUSS][WIKI] Do we need a top-level Releases page? > > Hey all, > > I spent a few minutes updating the information on the Releases page on > the wiki: > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases > > (I was actually hunting for something else) > > Do we really need to duplicate all the information that is already on > the main Website here? > > IMHO, the wiki should be for developer docs and things that change > quickly, or that require collaborative editing (e.g., weekly newsletter, > or events information). We shouldn't have "static" information on the > wiki that should be on the main Website. > > (The Newbie/What is CloudStack? section also strikes me as something > that should be maintained on cloudstack.org, not the wiki.) > > Any objections? > > Best, > > jzb > -- > Joe Brockmeier > j...@zonker.net > Twitter: @jzb > http://www.dissociatedpress.net/
