Hi folks,
would it be any possible to have same benefit for stackforge-hosted
projects..?
Thank you,
On Fri, Mar 28, 2014 at 6:02 PM, Anne Gentle a...@openstack.org wrote:
On Thu, Mar 27, 2014 at 6:25 PM, Joe Gordon joe.gord...@gmail.com wrote:
Hi All,
Now that nova and qa are
Hi,
I would second that - if there was a way stackforge projects could use
it, that would be great.
Graham
On Tue, 2014-04-22 at 18:52 +0400, Mike Scherbakov wrote:
Hi folks,
would it be any possible to have same benefit for stackforge-hosted
projects..?
Thank you,
On Fri, Mar
Joe Gordon wrote:
Now that nova and qa are beginning to use specs repos [0][1]. Instead of
being forced to read raw RST or relying on github [3], we want a domain
where we can publish the fully rendered sphinxdocs based specs (rendered
with oslosphinx of course). So how about:
Thierry Carrez wrote:
specs instead of docs because docs.openstack.org
http://docs.openstack.org should only contain what is actually
implemented so keeping specs in another subdomain is an attempt to avoid
confusion as we don't expect every approved blueprint to get implemented.
Great
On Thu, Mar 27, 2014 at 6:25 PM, Joe Gordon joe.gord...@gmail.com wrote:
Hi All,
Now that nova and qa are beginning to use specs repos [0][1]. Instead of
being forced to read raw RST or relying on github [3], we want a domain
where we can publish the fully rendered sphinxdocs based specs
Hi All,
Now that nova and qa are beginning to use specs repos [0][1]. Instead of
being forced to read raw RST or relying on github [3], we want a domain
where we can publish the fully rendered sphinxdocs based specs (rendered
with oslosphinx of course). So how about:
