Open Stack

We (OSIC) will be participating in the discussion and recently were discussing the WGs status with another WG if that is any consolation.

--
Melvin Hillsman
Ops Technical Lead
OpenStack Innovation Center
mrhillsman at gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659
Learner | Ideation | Belief | Responsibility | Command
http://osic.org

> On Feb 7, 2017, at 13:37, Jimmy Mcarthur <jimmy at tipit.net> wrote:
> 
> Got it. I've notified Rocky and given her permissions to add her WG submission. 
> 
> Thanks for the guidance!
> Jimmy
> 
>> Edgar Magana February 7, 2017 at 10:23 AM
>> Jimmy,
>>  
>> It seems that we have a good engagement for this WG. I will advocate for allocating space during the Summit if possible.
>>  
>> Thanks,
>>  
>> Edgar
>>  
>> From: Jimmy McArthur <jimmy at openstack.org>
>> Date: Tuesday, February 7, 2017 at 7:28 AM
>> To: "user-committee at lists.openstack.org" <user-committee at lists.openstack.org>
>> Subject: [User-committee] Request for Log Working Group
>>  
>> Hi all -
>> 
>> The request below came into speaker support and we need to address. However, I don't know if this is an active  WG or not. Can anyone clarify?
>> 
>> Cheers!
>> Jimmy
>> 
>> Rochelle.GroberFriday 17:36
>>  
>> Hi.
>> 
>> I am the Co-chair for the moribund Log Working group. I am resurrecting it and will be handing it over to a diverse team of DevOps who have committed to move forward with logging improvements via PWG, specs, and implementation. But, I can't submit a WG/Team request because I the WG is not "active." At least I think that is the reason. Unless I’m just supposed to title it Working Group/Team Space and pick presentation and and Arch&Ops and explain our need in the summary section. I’m not sure.
>> 
>> We have a formal session (and likely informal ones) scheduled for the Ops meetup in Milan. We would like to continue the momentum by meeting for more F2F progress at the Boston summit.
>> 
>> If you could help, it would be appreciated.
>> 
>> Thanks, 
>> --Rocky
>> 
>> _______________________________________________
>> User-committee mailing list
>> User-committee at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>> Jimmy McArthur February 7, 2017 at 9:28 AM
>> Hi all -
>> 
>> The request below came into speaker support and we need to address. However, I don't know if this is an active  WG or not. Can anyone clarify?
>> 
>> Cheers!
>> Jimmy
>> 
>> Rochelle.Grober
>> Friday 17:36
>>  
>> Hi.
>> 
>> I am the Co-chair for the moribund Log Working group. I am resurrecting it and will be handing it over to a diverse team of DevOps who have committed to move forward with logging improvements via PWG, specs, and implementation. But, I can't submit a WG/Team request because I the WG is not "active." At least I think that is the reason. Unless I’m just supposed to title it Working Group/Team Space and pick presentation and and Arch&Ops and explain our need in the summary section. I’m not sure.
>> 
>> We have a formal session (and likely informal ones) scheduled for the Ops meetup in Milan. We would like to continue the momentum by meeting for more F2F progress at the Boston summit.
>> 
>> If you could help, it would be appreciated.
>> 
>> Thanks, 
>> --Rocky
>> 
>> _______________________________________________
>> User-committee mailing list
>> User-committee at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
> 
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20170207/1d90b162/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4661 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20170207/1d90b162/attachment-0001.bin>