This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA1045AC21057BAB95BC096E5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable BTW, I transposed letters in your name, so I just remade the account. On 08/22/2012 12:06 PM, Dan Yasny wrote:
=20 =20 ----- Original Message -----
From: "Karsten 'quaid' Wade" <kwade@redhat.com> To: "Dan Yasny" <dyasny@redhat.com> Cc: infra@ovirt.org Sent: Wednesday, 22 August, 2012 8:55:00 PM Subject: Re: vdsm hooks pages at ovirt.org =20 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=20 http://gallery.zimbra.com/ or marketplace.redhat.com =20 This will have to be built, and will take a lot of effort, so I=20 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 =20 It's not that the wiki is the only choice, I just didn't see an=20 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=20 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.) =20 BTW, WordPress isn't a requirement either - you could build this=20 another way, but WordPress has some conveniences, including making it much simpler for other people to help with maintenance. =20 What other way would that be? I'm open for suggestions, since this is quite new to me too
For example, we could setup /hooks as an actual sub-directory that Apache serves up. The directory could be populated with a different publishing framework, hand-built pages, etc. It could be automatically generated from a git checkout, etc. It all comes down to what the VDSM folks want to have and maintain. Using WordPress is easy, though: Infra maintains it for the projects, it has built-in authentication, it has the same design as the rest of the site, etc.
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. =20 Makes sense. We might also have a simpler repository for API and SDK scripts, instead of people keeping their own githubs all over the place, but hooks are important because they allow you to expand the functionality of oVirt in a very broad range of features
Does this mean hooks.ovirt.org is fine to use, and could be used by non-VDSM projects? I'm fine with api.ovirt.org, sdk.ovirt.org, etc. Just want to make sure we are thinking about them in a nice information-architecture as well as program-support ways.
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. =20 OK, is there a place I can read up on getting started with wordpress? Used to play with Joomla a few years ago, but nothing too serious
WordPress is essentially a blog engine, but it has other features that allow it to be a CMS - stand-alone (static) pages, categories, etc. This is a good place to start: http://codex.wordpress.org/Getting_Started_with_WordPress It's a very popular website framework so there is a lot out there about how to use it. For myself, it's usually my favorite piece of software as a user, which says a lot because I loathe webapps. :) (It's pretty great as a sysadmin, too.) - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enigA1045AC21057BAB95BC096E5 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/ iD8DBQFQNUQF2ZIOBq0ODEERAuNbAJ4nT6g0qJU9clxkNTc9N2S6N/EaTQCgn9P2 sLHcCpWJArFH6cJLZbasWig= =rPiS -----END PGP SIGNATURE----- --------------enigA1045AC21057BAB95BC096E5--