This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCD22BC247D3AD6203A456859 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 08/22/2012 08:47 AM, Dan Yasny wrote:
=20 Wiki pages are used by engineering, mainly to describe features and projects. I really want the hooks to have a consumable look to them, just like https://extensions.gnome.org/ or http://gallery.zimbra.com/ or marketplace.redhat.com =20 This will have to be built, and will take a lot of effort, so I don't expect too many changes there, once it's up and running, and the entry barrier is negligible, compared to the amount of work I'll be putting in there anyway. =20 So if Wiki is the only choice, we'll have to use wiki, but if it's possible to do this in a nicer, more mature-looking way, I'd rather go there
It's not that the wiki is the only choice, I just didn't see an explanation in the discussion as to why it won't suffice. I reckon I see your point now. My only concern is if you can get the design resources to make the look&feel. However, using WordPress at least gets you the same look&feel as the rest of the site (including when it is updated.) BTW, WordPress isn't a requirement either - you could build this another way, but WordPress has some conveniences, including making it much simpler for other people to help with maintenance. Are these 'hooks' only going to be for VDSM? Or could there be others for other components? I'm asking because hooks.ovirt.org is a generic namespace, vs. vdsm-hooks.ovirt.org etc. Just want to make sure we don't lock ourselves in to a name usage that we may not always want. I'll add Dan as an Editor for the WordPress instance - you can always start a page and rename it if the naming changes. I'll hold-off on requesting the DNS addition to see what the answers to my questions are. - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enigCD22BC247D3AD6203A456859 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFQNRz02ZIOBq0ODEERAvfvAKCHFW/YqDH++6X4PKavXrYHXpo0/QCfV88e Mfz9wXRIUBQfn1wfzf6vZ1g= =zoYV -----END PGP SIGNATURE----- --------------enigCD22BC247D3AD6203A456859--