On Fri, Oct 28, 2011 at 7:18 PM, Stefano Maffulli stef...@openstack.org wrote:
On Fri, 2011-10-28 at 13:17 -0700, Joseph Heck wrote:
There's some newer documentation that we just created at
keystone.openstack.org related to setting up and configuring Keystone.
Look into the page at
On Fri, 2011-10-28 at 13:17 -0700, Joseph Heck wrote:
There's some newer documentation that we just created at
keystone.openstack.org related to setting up and configuring Keystone.
Look into the page at http://keystone.openstack.org/configuring.html,
which also has detail on how to configure
I like the idea - but I don't know what it would take to create it. I don't
think openstack.org or docs.openstack.org content sites are managed in a repo.
I believe I heard that Todd Morey was managing those sites, but I might be
wrong.
-joe
On Oct 28, 2011, at 4:38 PM, Stefano Maffulli
On Fri, 2011-10-28 at 19:26 -0400, Jay Pipes wrote:
All the core projects have developer-specific docs at
http://$PROJECT.openstack.org.
got it. I still wonder whether we should find a better home for these
docs and include them in a more visible path.
For example, if it was under
Stef -
As Jay mentioned, I was following the pattern that the core projects already
had in place.
The documentation embedded in the project (which is specifically aimed at
contributors) is in this setup. I haven't yet updated the docbook pieces (which
become docs.openstack.org HTML PDF)
Stef and others - the audience determines which website serves them best. Sites
with projectname.openstack.org are specifically for Python devs who need to get
a dev environment going.
The site segmentation is described on wiki.openstack.org/Documentation/HowTo.
Anne Gentle
Content Stacker
6 matches
Mail list logo
