-0800
To: Brian Waldon
Cc: "openstack@lists.launchpad.net (openstack@lists.launchpad.net)"
Subject: Re: [Openstack] Extension Documentation
>I totally agree with Anne that the documentation in this "split up"
>format is very hard to both find and parse. It's not
Inline:
-Original Message-
From: Anne Gentle
Date: Fri, 9 Dec 2011 08:17:15 -0600
To: Jorge Williams
Cc: "openstack@lists.launchpad.net (openstack@lists.launchpad.net)"
Subject: Re: [Openstack] Extension Documentation
>Hi everyone -
>Overall I support this effort and h
I totally agree with Anne that the documentation in this "split up" format is
very hard to both find and parse. It's not inaccurate, so much as it leaves a
gaping hole in understanding what is and isn't available when you have 9+
documents to read and they're not really interlinked.
The effort
Hey Anne,
Great feedback! As for number 8, I think the nova-api team might be the best
group to be tasked with reviewing code and documentation for any extensions
proposed to Nova's codebase. And we can absolutely discuss this at the meeting
today!
Brian
On Dec 9, 2011, at 9:17 AM, Anne Gent
Hi everyone -
Overall I support this effort and have discussed it at length with the
Rackers working on it.
I'd really like to get feedback from everyone who thinks they'll
consume this type of information. I don't find it easy to use from an
API consumer's perspective, but it is an absolute must
Hi All,
I've started putting together a site to hold extension documentation. You can
see it here:
http://docs.rackspace.com/openstack-extensions/
The idea is to have a repository for all extensions, whether the extension is
an OpenStack extension or a vendor specific extension. It makes sen
6 matches
Mail list logo
