On 08/16/2017 09:25 PM, Curtis wrote:
On Wed, Aug 16, 2017 at 12:03 AM, Jay Pipes 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 Wed, Aug 16, 2017 at 12:03 AM, Jay Pipes 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 ge
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!
Ch
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://eavesdro
15 Août 2017 17:49:20
> Objet: [Openstack-operators] [nfv-telecom] Suspending meetings while we
> consider moving to being a sub group in LCOO
>
> Hi All,
>
> We've been having NFV-Telecom meetings for OpenStack Operators for a
> while now, but never quite reached a t
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 gr
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 deployme