Open Stack

Hi,

After reading the User Committee document [0] and re-reading this
email, I think I have a better idea of what you were asking.

In our last Operators Telecom/NFV meeting we reviewed the document and
all agreed that we would fall under the User Committee and that we are
likely a functional team as opposed to a working group [1].

As a team we would like to move forward in ensuring we are meeting the
OpenStack communities requirements.

Thanks,
Curtis.

[0]: https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit
[1]: http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-07-13-15.00.html

On Mon, Jul 11, 2016 at 10:58 AM, Curtis <serverascode at gmail.com> wrote:
> On Mon, Jul 11, 2016 at 9:49 AM, Edgar Magana <edgar.magana at workday.com> wrote:
>> Curtis,
>>
>> Do you see this WG under the umbrella of the User Committee or the Technical Committee? I am trying to gather all the WGs under the UC in order to add them into our charter. Please, clarify where do you see this WG.
>
> Hi Edgar,
>
> I think it would be great to be under the UC. I believe your previous
> email specifically said not new groups, so I put it to the side in my
> mind for the time being, but would be happy to work through whatever
> measures are required to be in compliance. :)
>
> Thanks,
> Curtis.
>
>> For the UC charter details, we are working on this document for the charter:
>> https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit?usp=sharing
>>
>> Per my email:
>> http://lists.openstack.org/pipermail/user-committee/2016-July/001089.html
>>
>> UC needs to approve and validate all WGs under its umbrella and obviously provide them support and resources from the Foundation, like space during the summit and/or potential sponsor for WG activities.
>>
>> Thanks,
>>
>> Edgar
>>
>> On 7/9/16, 10:56 AM, "Curtis" <serverascode at gmail.com> wrote:
>>
>> Hi All,
>>
>> First, sorry about the weird tags on this email, but one of the things
>> we decided last meeting was to use the tag [telecom-nfv] for this
>> working group. Next time I email I'll just use that tag. (Note:
>> telecom not telco.)
>>
>> The second thing we did was work on a mission statement [1]. A
>> volunteer kindly put together an intial "strawperson" mission
>> statement so that we could at least have something to edit and think
>> about--a place to start.
>>
>> Also the OPNFV team has created an IRC channel they are using for
>> openstack related discussions [2].
>>
>> We will have our 4th bi-weekly meeting next Weds [3]; hope to see you there.
>>
>> Thanks,
>> Curtis.
>>
>> [1]: https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_ops-2Dtelecom-2Dnfv-2Dmission-2Dstatement&d=CwICAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lFkl4r7oVhlHxsqAJcKB8385I-Z1mfqqVR7ot1ZrNnQ&s=d6OkuIqGHdW0Uy9ixANQXfXT2xnOpFbf1Ppw9-BpQ-4&e=
>> [2]: https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_2016-2DJuly_010960.html&d=CwICAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lFkl4r7oVhlHxsqAJcKB8385I-Z1mfqqVR7ot1ZrNnQ&s=O69O8WwufDsepuqeKiyJlKYIcJ9WcYe-8H0SYxOoon4&e=
>> [3]: https://urldefense.proofpoint.com/v2/url?u=http-3A__eavesdrop.openstack.org_-23OpenStack-5FOperators-5FTelco-5Fand-5FNFV-5FWorking-5FGroup&d=CwICAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lFkl4r7oVhlHxsqAJcKB8385I-Z1mfqqVR7ot1ZrNnQ&s=73fuMMVfRkikDNBgZnRmV4nkrcKojzMUyvE80Kblls4&e=
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=CwICAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lFkl4r7oVhlHxsqAJcKB8385I-Z1mfqqVR7ot1ZrNnQ&s=qkP8FsietFuSX1M294FsIcJhHx4zwsRhvr9NbImyGNY&e=
>>
>>
>
>
>
> --
> Blog: serverascode.com



-- 
Blog: serverascode.com