Open Stack

Shamail – Are you recommending I put API in the subject line for this to capture the eyes of those folks?

Geoff – Glad you connected with Eric. Agree that WTE and Product Work Group have lots of synergies. The WTE team is meeting ahead of our sessions and one of the topics on that agenda is working with the Product Work Group. You can find the agenda for the WTE meeting at: https://etherpad.openstack.org/p/Win-The-Enterprise-Vancouver-Meetup

Carol

From: Shamail Tahir [mailto:itzshamail at gmail.com]
Sent: Thursday, April 30, 2015 10:22 AM
To: Geoff Arnold
Cc: Barrett, Carol L; product-wg at lists.openstack.org
Subject: Re: [Product] [OpenStack][Product-WG] Email Draft for Vancouver Summit working session

Hi everyone,

Here are the WGs I know about, pls add others:
> Win The Enterprise
> Telco (don't have a dedicated ML, use the dev list)
> HPC (OpenStack-HPC)
> Security (OpenStack-security)
The only other one that I would add would be:  API WG (doesn't have a dedicated ML, use the dev list with [API] tag)

Geoff, we do have a cross working-group meeting planned for Vancouver (our second session) and WTE will definitely be represented.  Carol has been doing a great job of keeping WTE updated on our progress and collaboration opportunities.

Thanks,
Shamail



On Thu, Apr 30, 2015 at 1:16 PM, Geoff Arnold <geoff at geoffarnold.com<mailto:geoff at geoffarnold.com>> wrote:
Definitely add Win the Enterprise.

I talked to Eric Saxe of Oracle at a Meetup yesterday, and we talked about how WtE and product-wg could work together. We assumed that you’d be driving that, Carol, in view of your participation in both, but Eric did feel that it might be useful to have a joint session at some point - either IRC or at the summit.

Geoff

> On Apr 30, 2015, at 10:08 AM, Barrett, Carol L <carol.l.barrett at intel.com<mailto:carol.l.barrett at intel.com>> wrote:
>
> Good Idea Shamail. Here are the WGs I know about, pls add others:
> Win The Enterprise
> Telco (don't have a dedicated ML, use the dev list)
> HPC (OpenStack-HPC)
> Security (OpenStack-security)
>
> I could also include OpenStack general mailing list .
>
> Thanks
> Carol
> -----Original Message-----
> From: Shamail [mailto:itzshamail at gmail.com<mailto:itzshamail at gmail.com>]
> Sent: Thursday, April 30, 2015 9:32 AM
> To: Barrett, Carol L
> Cc: product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>
> Subject: Re: [Product] [OpenStack][Product-WG] Email Draft for Vancouver Summit working session
>
> Hi Carol,
>
> I think those are probably the right mailing lists.  Do we want to include the WG mailing lists explicitly?  I think you will get to the same people through the MLs mentioned below but will it be more relevant for the WGs if they see themselves on the "to:" list?
>
> Thanks,
> Shamail
>
>
>
>> On Apr 30, 2015, at 11:27 AM, Barrett, Carol L <carol.l.barrett at intel.com<mailto:carol.l.barrett at intel.com>> wrote:
>>
>> I want to confirm the mailing list that we want to send this to. My plan is to send to OpenStack-dev, Marketing, user-committee, openstack-operators.
>>
>> What do you think?
>> Thanks
>> Carol
>>
>> -----Original Message-----
>> From: Shamail [mailto:itzshamail at gmail.com<mailto:itzshamail at gmail.com>]
>> Sent: Monday, April 06, 2015 4:46 PM
>> To: Barrett, Carol L
>> Cc: product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>
>> Subject: Re: [Product] [OpenStack][Product-WG] Email Draft for Vancouver Summit working session
>>
>> Hi Carol,
>>
>> This looks great.  We should add specific details (if available) before sending out the message for the working session (date/time, room #, etc.)
>>
>> Which etherpad are you directly people to?  I couldn't find the link but let's make it a new one (e.g. ProductWGVancouverMeetup) since our existing ones are becoming hard to manage.
>>
>> Thanks,
>> Shamail
>>
>>
>>
>>> On Apr 6, 2015, at 12:01 PM, Barrett, Carol L <carol.l.barrett at intel.com<mailto:carol.l.barrett at intel.com>> wrote:
>>>
>>> All  - In our last team meeting, I took the AR to draft an email to send to the OpenStack community to invite and identify community groups that are synergistic with our efforts to develop a multi-release roadmap to our working session at the Vancouver Summit. Pls help improve this communication by reviewing and editing  this draft by 4/13, so we can finalize in our 4/15 team meeting and send out to the community by 4/17.
>>>
>>> Thanks
>>> Carol
>>>
>>> Email Draft:
>>>
>>> The Product Work Group has formed to listen and aggregate feedback on the desired capabilities for the OpenStack platform from developer community (including PTLs), Customers, and Users. Using this feedback we intent to help PTLs and Contributors resolve issues that are either of strategic importance or have broad implications across OpenStack services that will help customers/users be successful with adoption by removing barriers to adoption/operation.
>>>
>>> To achieve this goal, we are striving to create a multi-release OpenStack roadmap based upon the aggregated information through an open, transparent, cross-community collaboration.
>>>
>>> In a working session at the Vancouver Summit, we'd like to refine and finalize our approach to creating this roadmap. We'd like to understand what work groups, user groups or community members are interested in joining us for this session. Please go to this etherpad to tell us who you are and what you're area of interest is.
>>>
>>> You can find more information about the Product work group here: https://wiki.openstack.org/wiki/ProductTeam
>>>
>>>
>>> _______________________________________________
>>> Product-wg mailing list
>>> Product-wg at lists.openstack.org<mailto:Product-wg at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>
> _______________________________________________
> Product-wg mailing list
> Product-wg at lists.openstack.org<mailto:Product-wg at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg



--
Thanks,
Shamail Tahir
Cloud Architect, EMC
t: @ShamailXD
tz: Eastern Time