<div dir="ltr">Jeremy, <div><br></div><div>Thank you for explanation, I missed this point before. </div><div><br></div><div>Best regards,</div><div>Boris Pavlovic </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 20, 2015 at 6:06 PM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1, Jeremy. Excellent points.<span class="HOEnZb"><font color="#888888"><br>
<br>
-jay</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 04/20/2015 10:59 AM, Jeremy Stanley wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<CAD85om3RJg4fDHDKPZpmcboF+=<a href="mailto:AkNM9wQo08BAs0eoV8DeYNGQ@mail.gmail.com" target="_blank">AkNM9wQo08BAs0eoV8DeYNGQ@mail.gmail.com</a>><br>
<br>
On 2015-04-17 16:26:29 +0300 (-0300), Boris Pavlovic wrote:<br>
[...]<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Move meetings from #openstack-meeting to #openstack-rally chat.<br>
</blockquote>
[...]<br>
<br>
Please don't. This means anyone who wants to be around in case an<br>
important topic comes up in your meeting has to leave themselves<br>
subscribed to an additional channel, and increases the chances your<br>
meetings will conflict time-wise with others. Using the official<br>
meeting channels increases the ability of the community at large to<br>
be more involved in those discussions.<br>
<br>
The new project requirements[1] only say "The project has regular<br>
meetings on IRC and those meetings are logged" but it seems like an<br>
oversight to me that it doesn't say they should happen in official<br>
meeting channels (at least once the project's application has been<br>
accepted). The structure reform resolution[2] did mention "use<br>
#openstack-meeting channels for their team meetings" so I think it's<br>
the implied intent there, at least. I've proposed a governance<br>
change[3] in hopes of making this clear for others in the future,<br>
and updated our Meetings wiki article[4] with an additional sentence<br>
in the preamble describing the benefits and linking to related<br>
resources.<br>
<br>
[1] <a href="http://governance.openstack.org/reference/new-projects-requirements.html" target="_blank">http://governance.openstack.org/reference/new-projects-requirements.html</a><br>
[2] <a href="http://governance.openstack.org/resolutions/20141202-project-structure-reform-spec.html" target="_blank">http://governance.openstack.org/resolutions/20141202-project-structure-reform-spec.html</a><br>
[3] <a href="https://review.openstack.org/175427" target="_blank">https://review.openstack.org/175427</a><br>
[4] <a href="https://wiki.openstack.org/wiki/Meetings" target="_blank">https://wiki.openstack.org/wiki/Meetings</a><br>
<br>
</blockquote>
<br></div></div><div class="HOEnZb"><div class="h5">
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>