<div dir="ltr">Hi Anne,<br><br>Thanks for the input, it makes it easier for us to come to a common conclusion on the review process for training guides.<br><br>I agree with Anne that there will be enough heads for two +2's in our team.<br><br>Regards,<br>Pranav<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 15, 2014 at 12:59 AM, Tom Fifield <span dir="ltr"><<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 14/12/14 23:04, Anne Gentle wrote:<br>
><br>
> On Sun, Dec 14, 2014 at 3:42 AM, Frans Thamura <<a href="mailto:frans@meruvian.org">frans@meruvian.org</a><br>
</span><span class="">> <mailto:<a href="mailto:frans@meruvian.org">frans@meruvian.org</a>>> wrote:<br>
><br>
> hi all<br>
><br>
> has been months<br>
><br>
> i am working with training guide and installation guide and now the<br>
> training lab<br>
><br>
> i wish we /can have dedicated mailing list to ask this question<br>
><br>
> and i am planing roadshows to school showing this material, and let<br>
> students work and try this.<br>
><br>
> the training lab concept is more easier to anyone to start rather the<br>
> installation guide<br>
><br>
><br>
> can we have a <a href="mailto:training@list.openstack.org">training@list.openstack.org</a><br>
</span>> <mailto:<a href="mailto:training@list.openstack.org">training@list.openstack.org</a>> or <a href="mailto:education@list.openstack.org">education@list.openstack.org</a><br>
> <mailto:<a href="mailto:education@list.openstack.org">education@list.openstack.org</a>>?<br>
><br>
<br>
Hi Frans,<br>
<br>
I think the appropriate list for this would be<br>
<a href="mailto:community@lists.openstack.org">community@lists.openstack.org</a> , as it is related to community events.<br>
<br>
<br>
Regards,<br>
<br>
Tom<br>
<span class=""><br>
<br>
<br>
><br>
> Hi Frans,<br>
> I can see the need you have being slightly different from the people who<br>
> are on the docs list.<br>
><br>
> Let's see what community managers think.<br>
><br>
> Anne<br>
><br>
><br>
><br>
> I still also confuse, if we make this event how it related to user<br>
> group ( i cc the user group).<br>
><br>
> because that i know, if we not have user group, the roadshow can<br>
> become ilegal , because put openstack logo (cost $10.000/year)<br>
><br>
> Frans<br>
> --<br>
> Frans Thamura (曽志胜)<br>
> Shadow Master and Lead Investor<br>
> Meruvian.<br>
> Integrated Hypermedia Java Solution Provider.<br>
><br>
</span>> Mobile: <a href="tel:%2B628557888699" value="+628557888699">+628557888699</a> <tel:%2B628557888699><br>
<span class="">> Blog: <a href="http://blogs.mervpolis.com/roller/flatburger" target="_blank">http://blogs.mervpolis.com/roller/flatburger</a> (id)<br>
><br>
> FB: <a href="http://www.facebook.com/meruvian" target="_blank">http://www.facebook.com/meruvian</a><br>
> TW: <a href="http://www.twitter.com/meruvian" target="_blank">http://www.twitter.com/meruvian</a> / @meruvian<br>
> Website: <a href="http://www.meruvian.org" target="_blank">http://www.meruvian.org</a><br>
><br>
> "We grow because we share the same belief."<br>
><br>
><br>
> On Sun, Dec 14, 2014 at 2:21 PM, Roger Luethi<br>
</span><span class="">> <<a href="mailto:rl@patchworkscience.org">rl@patchworkscience.org</a> <mailto:<a href="mailto:rl@patchworkscience.org">rl@patchworkscience.org</a>>> wrote:<br>
> > On Sat, 13 Dec 2014 11:11:42 -0600, Anne Gentle wrote:<br>
> >> Oh definitely can +2 your own patches early on and with small<br>
> teams. I<br>
> >> still do so for API docs. It has only been this last year or so<br>
> where I've<br>
> >> gotten to the point where I get two others to +2 my patches in<br>
> >> openstack-manuals.<br>
> ><br>
> > In that case requiring 2x +2 for non-trivial patches would<br>
> formalize what<br>
> > we've been doing pretty much since the repo existed. Fine, let's<br>
> do it.<br>
> ><br>
> > Thanks for the explanations, Anne.<br>
> ><br>
> > Roger<br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-docs mailing list<br>
> > <a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
</span>> <mailto:<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a>><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<div class="HOEnZb"><div class="h5">><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-docs mailing list<br>
> <a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
><br>
<br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</div></div></blockquote></div></div>