<div dir="ltr">A model I have been using is: informal chat AND official meetings on IRC, but for the latter I also email the link to the minutes and log to the mailing list so that agreements are easy to find (e.g. actions and #agreed items). If nothing else it helps me prepare for the next meeting each time!<div><br></div><div>Chris</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 16, 2017 at 1:55 PM, Edgar Magana <span dir="ltr"><<a href="mailto:edgar.magana@workday.com" target="_blank">edgar.magana@workday.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jay,<br>
<br>
Your request has been indeed a topic that we have discussed in the past. During the last UC IRC meeting the UC requested to all Working Groups and Teams under the umbrella of the UC to report their activities via IRC . Please, take a look to our last Monday meeting minutes:<br>
<a href="http://eavesdrop.openstack.org/meetings/uc/2017/uc.2017-08-14-18.02.log.html" rel="noreferrer" target="_blank">http://eavesdrop.openstack.<wbr>org/meetings/uc/2017/uc.2017-<wbr>08-14-18.02.log.html</a><br>
<br>
So, do not worry all WG/Teams will use IRC to report their activities. They will still use any other communication mechanism or technology to make progress in their goals if they desire that. Finally, we have also enabled the #openstack-uc channel to record all conversations.<br>
<br>
Thanks,<br>
<br>
Edgar<br>
<div><div class="h5"><br>
On 8/15/17, 11:03 PM, "Jay Pipes" <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br>
<br>
Hi Curtis, Andrew U, Jamie M,<br>
<br>
May I request that if the telco working group merges with the LCOO, that<br>
we get regular updates to the openstack[-operator|-dev] mailing list<br>
with information about the goings-on of LCOO? Would be good to get a<br>
bi-weekly or even monthly summary.<br>
<br>
Other working groups host their meetings on IRC and publish status<br>
reports to the mailing lists fairly regularly. I personally find this<br>
information quite useful and would be great to see a similar effort from<br>
LCOO.<br>
<br>
All the best,<br>
-jay<br>
<br>
On 08/15/2017 11:49 AM, Curtis wrote:<br>
> Hi All,<br>
><br>
> We've been having NFV-Telecom meetings for OpenStack Operators for a<br>
> while now, but never quite reached a tipping point in terms of<br>
> attendance to "get things done" so to speak.<br>
><br>
> The point of the group had been to find OpenStack Operators who are<br>
> tasked with designing/operating NFV deployments and help them, but<br>
> were never really able to surface enough of us to move forward. I want<br>
> to be super clear that this group was for OpenStack Operators, and<br>
> isn't a comment on any other NFV related groups in and around<br>
> OpenStack...simply just people like me who deploy NFV clouds based on<br>
> OpenStack.<br>
><br>
> We are currently considering moving to be a subgroup in LCOO, but<br>
> that's just one idea. In the future, if we can surface more OpenStack<br>
> Operators doing NFV work maybe we revisit.<br>
><br>
> If anyone has strong feelings around this, please do reply and let me<br>
> know of any ideas/comments/criticism, otherwise we'll probably move to<br>
> discussing with LCOO.<br>
><br>
> Thanks to all those who attended meetings in the past, it's much appreciated,<br>
> Curtis.<br>
><br>
> ______________________________<wbr>_________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.<wbr>openstack.org</a><br>
</div></div> > <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=bZyB7R-t_eqqqR6lPt0-KRSt00wVbo3A7CHy4_oQHEk&s=QtsCWHLqVgD6CN8v7POve3MHv9xGABS08HzbjE_TTWI&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=http-3A__lists.<wbr>openstack.org_cgi-2Dbin_<wbr>mailman_listinfo_openstack-<wbr>2Doperators&d=DwIGaQ&c=<wbr>DS6PUFBBr_<wbr>KiLo7Sjt3ljp5jaW5k2i9ijVXllEdO<wbr>ozc&r=G0XRJfDQsuBvqa_<wbr>wpWyDAUlSpeMV4W1qfWqBfctlWwQ&<wbr>m=bZyB7R-t_eqqqR6lPt0-<wbr>KRSt00wVbo3A7CHy4_oQHEk&s=<wbr>QtsCWHLqVgD6CN8v7POve3MHv9xGAB<wbr>S08HzbjE_TTWI&e=</a><br>
<span class=""> ><br>
<br>
______________________________<wbr>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.<wbr>openstack.org</a><br>
</span> <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=bZyB7R-t_eqqqR6lPt0-KRSt00wVbo3A7CHy4_oQHEk&s=QtsCWHLqVgD6CN8v7POve3MHv9xGABS08HzbjE_TTWI&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=http-3A__lists.<wbr>openstack.org_cgi-2Dbin_<wbr>mailman_listinfo_openstack-<wbr>2Doperators&d=DwIGaQ&c=<wbr>DS6PUFBBr_<wbr>KiLo7Sjt3ljp5jaW5k2i9ijVXllEdO<wbr>ozc&r=G0XRJfDQsuBvqa_<wbr>wpWyDAUlSpeMV4W1qfWqBfctlWwQ&<wbr>m=bZyB7R-t_eqqqR6lPt0-<wbr>KRSt00wVbo3A7CHy4_oQHEk&s=<wbr>QtsCWHLqVgD6CN8v7POve3MHv9xGAB<wbr>S08HzbjE_TTWI&e=</a><br>
<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.<wbr>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-operators</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Chris Morgan <<a href="mailto:mihalis68@gmail.com" target="_blank">mihalis68@gmail.com</a>></div>
</div>