<html><body>
<p><tt><font size="2">Andreas Jaeger <aj@suse.com> wrote on 2013/11/27 05:39:16:<br>
<br>
> Andreas Jaeger <aj@suse.com> </font></tt><br>
<tt><font size="2">> 2013/11/27 05:39</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> Anne Gentle <anne@openstack.org>, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> "openstack-docs@lists.openstack.org" <openstack-docs@lists.openstack.org></font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack-docs] docutils repo?</font></tt><br>
<tt><font size="2">> <br>
> On 11/26/2013 09:07 PM, Anne Gentle wrote:<br>
> > <br>
> > <br>
> > <br>
> > On Tue, Nov 26, 2013 at 1:57 PM, Andreas Jaeger <aj@suse.com<br>
> > <<a href="mailto:aj@suse.com">mailto:aj@suse.com</a>>> wrote:<br>
> > <br>
> > On 11/26/2013 08:31 PM, Andreas Jaeger wrote:<br>
> > > I read that you discussed at the summit a docutils repo and I'd<br>
> > like to<br>
> > > work on implementing all the bits for it - if nobody else has<br>
> > > volunteered yet for it.<br>
> > ><br>
> > > Did you discuss any further things on how to use it? Before I write up<br>
> > > my own ideas, I'd like to read what you already discussed.<br>
> > ><br>
> > > Btw. how can I request a new git repo? I would start this while we<br>
> > still<br>
> > > discuss the specifics...<br>
> > <br>
> > <br>
> > Referenced in:<br>
> > <a href="https://etherpad.openstack.org/p/icehouse-doc-translation">https://etherpad.openstack.org/p/icehouse-doc-translation</a><br>
> > starting line 67<br>
> > <br>
> > <br>
> > Yes, there it is. <br>
> > <br>
> > I think that you just request the repo from the Infrastructure team.<br>
> > There's still some research in the options listed there, and some of<br>
> > which I'm not informed enough to be opinionated about. The main ideas<br>
> > and goals are about translation, autodoc generation, and validation. <br>
> <br>
> I've asked #openstack-infra for help and got pointers on how to request<br>
> a new repo - and since fungi was confused by "docutils" I took the<br>
> proposal from the etherpad and proposed "doctools". The patch is at:<br>
> <a href="https://review.openstack.org/#/c/58623/">https://review.openstack.org/#/c/58623/</a><br>
> <br>
> I created an initial repository consisting of all the content from the<br>
> tools subdirectory of openstack-manuals and pushed it to<br>
> <a href="https://github.com/ajaeger/doctools">https://github.com/ajaeger/doctools</a>. Do you think that's the proper<br>
> initial layout and content? Or should I remove some more files?<br>
> <br>
> <br>
> For building documentation (like openstack-manuals) with Jenkins, I see<br>
> two options:<br>
> Option 1: Have Jenkins checkout the doctools repository every time and<br>
> use that for building - similar to the "devstack-checkout"<br>
> job<br>
> <br>
> Option 2: Copy the tools and all support files to each and every<br>
> repository. We could automate that.<br>
> <br>
> I suggest to investigate whether option 1 is feasible and go for that.<br>
> It gives us the benefit that any change to doctools will immediately be<br>
> reflected in any other repo - and that's a problem as well ;)<br>
> </font></tt><br>
<br>
<tt><font size="2">I support option 1 too.</font></tt><br>
<tt><font size="2">Thank you for taking this work.</font></tt><br>
<br>
<tt><font size="2"><br>
> Moving forward, I'd like to have all our repositories (api-site,<br>
> compute-api, identity-api, image-api, netconn-api, object-api,<br>
> volume-api, operations-guide, openstack-manuals) use proper gates,<br>
> thus extend "test.py" so that it can be used in more places.<br>
> Right now only operations-guide and openstack-manuals are gated - but<br>
> operations-guide uses an old version of the tools.<br>
> <br>
> Andreas<br>
> -- <br>
> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi<br>
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
> <br>
> _______________________________________________<br>
> Openstack-docs mailing list<br>
> Openstack-docs@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
> <br>
</font></tt></body></html>