Jay,

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:
http://eavesdrop.openstack.org/meetings/uc/2017/uc.2017-08-14-18.02.log.html

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.

Thanks,

Edgar

On 8/15/17, 11:03 PM, "Jay Pipes" <jaypi...@gmail.com> wrote:

    Hi Curtis, Andrew U, Jamie M,
    
    May I request that if the telco working group merges with the LCOO, that 
    we get regular updates to the openstack[-operator|-dev] mailing list 
    with information about the goings-on of LCOO? Would be good to get a 
    bi-weekly or even monthly summary.
    
    Other working groups host their meetings on IRC and publish status 
    reports to the mailing lists fairly regularly. I personally find this 
    information quite useful and would be great to see a similar effort from 
    LCOO.
    
    All the best,
    -jay
    
    On 08/15/2017 11:49 AM, Curtis wrote:
    > Hi All,
    > 
    > We've been having NFV-Telecom meetings for OpenStack Operators for a
    > while now, but never quite reached a tipping point in terms of
    > attendance to "get things done" so to speak.
    > 
    > The point of the group had been to find OpenStack Operators who are
    > tasked with designing/operating NFV deployments and help them, but
    > were never really able to surface enough of us to move forward. I want
    > to be super clear that this group was for OpenStack Operators, and
    > isn't a comment on any other NFV related groups in and around
    > OpenStack...simply just people like me who deploy NFV clouds based on
    > OpenStack.
    > 
    > We are currently considering moving to be a subgroup in LCOO, but
    > that's just one idea. In the future, if we can surface more OpenStack
    > Operators doing NFV work maybe we revisit.
    > 
    > If anyone has strong feelings around this, please do reply and let me
    > know of any ideas/comments/criticism, otherwise we'll probably move to
    > discussing with LCOO.
    > 
    > Thanks to all those who attended meetings in the past, it's much 
appreciated,
    > Curtis.
    > 
    > _______________________________________________
    > OpenStack-operators mailing list
    > OpenStack-operators@lists.openstack.org
    > 
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=
 
    > 
    
    _______________________________________________
    OpenStack-operators mailing list
    OpenStack-operators@lists.openstack.org
    
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=
 
    

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to