<div dir="ltr">Inserting Sean's question set (sorry for the copy/paste).<div><br></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">We are starting to hit some questions that I do not have ready answers to.?</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px"> * where to store the data: Tom and I were initially thinking stackforge before incubation. move under the </span><span class="" style="font-family:arial,sans-serif;font-size:12.727272033691406px">openstack</span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"> repo org after incubation as </span><span class="" style="font-family:arial,sans-serif;font-size:12.727272033691406px">training</span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">-</span><span class="" style="font-family:arial,sans-serif;font-size:12.727272033691406px">guides</span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">. fungi and jeblair are questioning a stackforge project publishing to</span><a href="http://docs.openstack.org/" target="_blank" style="font-family:arial,sans-serif;font-size:12.727272033691406px"><span class="">docs</span>.<span class="">openstack</span>.org</a><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"> rather than just </span><span class="" style="font-family:arial,sans-serif;font-size:12.727272033691406px">openstack</span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">-</span><span class="" style="font-family:arial,sans-serif;font-size:12.727272033691406px">manuals</span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">. I do not have a great answer other than I believe Anne is good with that for now. If the </span><span class="" style="font-family:arial,sans-serif;font-size:12.727272033691406px">docs</span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"> PTL and team is okay with this, do I need to ask the TC as well?</span></div>
<div><br></div><div>Yes, stackforge is the right placement. I'm fine with publishing to <a href="http://docs.openstack.org/">docs.openstack.org/</a> -- we used to have <a href="http://docs.openstack.org/incubation/">docs.openstack.org/incubation/</a> -- perhaps that URL is a good place?</div>
<div><br></div><div>I want to back up a bit and make sure we all understand the goals here (many of these are listed in the Incubation Plan also):</div><div>- increase the quality of the training manuals</div><div>- set reader's expectations about the training manuals being community-based</div>
<div>- increase the contributor base and core reviewers</div><div>- ensure reuse of tools and content to avoid duplication of effort while still providing unique deliverables for training purposes</div><div><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px"> * where to house the project: I would like it to stay under the documentation program. Any other ideas?</span></div><div><br></div><div>I think that's the idea, that you'll fit within the Docs program, and your incubation plan below is a great start.</div>
<div><br style="font-family:arial,sans-serif;font-size:12.727272033691406px"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">Find here the all the incubation plan Q&A using the latest TC requirements</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<a href="https://wiki.openstack.org/wiki/Training-guides#Incubation_Plan" target="_blank" style="font-family:arial,sans-serif;font-size:12.727272033691406px">https://wiki.<span class="">openstack</span>.org/wiki/<span class="">Training</span>-<span class="">guides</span>#Incubation_Plan</a><br>
</div><div><br></div><div>Looks good, you might note that your builds use tox and keep updated with the global-requirements list.</div><div><br></div><div>Thanks for asking Sean -- let's get this ramped up.</div><div>
Anne</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 29, 2014 at 8:14 PM, Tom Fifield <span dir="ltr"><<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 30/05/14 01:40, Anne Gentle wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
<br>
<br>
<br>
On Wed, May 28, 2014 at 9:56 PM, Tom Fifield <<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a><br></div><div><div class="h5">
<mailto:<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>>> wrote:<br>
<br>
Hi,<br>
<br>
Sean Roberts, Stefano and I just had a very fruitful discussion<br>
regarding the training manuals project.<br>
<br>
<br>
Thanks you all for discussing.<br>
<br>
<br>
We think that it's time to allow the the training guides to become a<br>
free-standing project of its own accord, and start attracting<br>
significantly more people around it.<br>
<br>
<br>
This will make it easier for contributors who just want to work on<br>
training to find the project, see lists of bugs and tasks relevant<br>
to them*, and also provide a clearer pathway toward becoming<br>
contributors, and eventually core reviewers.<br>
<br>
It will also enable the training guides project to have its own<br>
policies, and allow the repository to be used for investigation of<br>
training infrastructure, such as the recent forays into moodle for<br>
example.<br>
<br>
However, with every change such as this, there are drawbacks, and so<br>
we feel it's important to discuss these as well - and most<br>
importantly get your input.<br>
<br>
For example, while we can continue to re-use tools and content, this<br>
would mean a different review queue and repository - which could<br>
frustrate if you are working across both projects.<br>
<br>
<br>
I hope the intention is to continue to use inclusion of known tested<br>
content from the various other OpenStack repos as needed.<br>
</div></div></blockquote>
<br>
Yup, that's the case.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
<br>
What are your thoughts?<br>
<br>
<br>
Sounds great to me. Thanks all!<br>
Anne<br>
<br>
<br>
<br>
Regards,<br>
<br>
<br>
<br>
Tom<br>
<br>
<br>
* as opposed to the 400 odd in the openstack-manuals tracker!<br>
<br></div>
______________________________<u></u>___________________<br>
Openstack-docs mailing list<br>
Openstack-docs@lists.__<a href="http://openstack.org" target="_blank">opensta<u></u>ck.org</a><br>
<mailto:<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.<u></u>openstack.org</a>><br>
<a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-docs" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-docs</a><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-docs</a>><br>
<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>