Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Alex.Huang@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Alex Huang <Alex.Huang@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Wed, 13 Feb 2013 15:24:08 -0800
Subject: RE: [DISCUSS][WIKI] Do we need a top-level Releases page?
Thread-Topic: [DISCUSS][WIKI] Do we need a top-level Releases page?
Thread-Index: Ac4KCvoF5pIMLONYRZKBwUJKF2t2hwANMYVQ
Message-ID: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA4D00AB3@SJCPMAILBOX01.citrite.net>
References: 
 <1360774519.8317.140661190977241.3DA58643@webmail.messagingengine.com>
In-Reply-To: 
 <1360774519.8317.140661190977241.3DA58643@webmail.messagingengine.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Joe,

I added those in.  IMHO, our wiki should just "export" content and then it =
gets "styled" up and be put on cloudstack.org. =20

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.=20

Our collaborations should happen on the mailing list but once a consensus i=
s achieved someone should write something on the wiki.  This is similar to =
how we're doing the FSes currently. =20

David has gotten admin privilege to allow us to customize the html export o=
f 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 sl=
ow for me to get started.)

--Alex

> -----Original Message-----
> From: Joe Brockmeier [mailto:jzb@zonker.net]
> Sent: Wednesday, February 13, 2013 8:55 AM
> To: CloudStack Developers
> Subject: [DISCUSS][WIKI] Do we need a top-level Releases page?
>=20
> Hey all,
>=20
> I spent a few minutes updating the information on the Releases page on
> the wiki:
>=20
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
>=20
> (I was actually hunting for something else)
>=20
> Do we really need to duplicate all the information that is already on
> the main Website here?
>=20
> 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.
>=20
> (The Newbie/What is CloudStack? section also strikes me as something
> that should be maintained on cloudstack.org, not the wiki.)
>=20
> Any objections?
>=20
> Best,
>=20
> jzb
> --
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/