Open Stack

Thanks Carol.  This is reflected in the updated workflow[1] (post summit).  The gaps and overlap analysis meeting would be held using the #openstack-cp channel initially and then, depending on the outcome, there could be a cross-project meeting setup for that team in the cross-project channel.

[1] https://wiki.openstack.org/wiki/ProductTeam/User_Stories

Thanks,
Shamail 

> On May 10, 2016, at 11:45 AM, Barrett, Carol L <carol.l.barrett at intel.com> wrote:
> 
> Forwarding to the Product WG mail list...Cross project team meetings will no longer be held, instead someone can call a meeting when needed. We'll need to figure out how to work with this new structure.
> 
> Thanks
> Carol 
> 
> 
> -----Original Message-----
> From: Mike Perez [mailto:thingee at gmail.com] 
> Sent: Monday, May 09, 2016 9:31 PM
> To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
> Subject: [openstack-dev] [cross-project] The Future of Meetings
> 
> Hey all,
> 
> When we first discussed the future of cross-project meetings at the Tokyo summit, we walked out with the idea of beginning to have ad-hoc meetings instead of one big meeting with all big tent projects.
> 
> Now that we have some process in place [1] (unfortunately still under review), we can begin that idea.
> 
> I will no longer be announcing the weekly cross-project meeting being skipped.
> Instead people who are interested in fixing some cross-project issue or feature may do so by introducing a meeting for that initiative [1] to take place in the #openstack-meeting-cp channel. Together, this group of project will create a spec or guideline [2].
> 
> For some initiatives you may know which OpenStack projects are involved with it. You can find people who are interested in helping with cross-project initiatives for their respected project by viewing the CPL page [3]. As noted in their duties, they will either be the person to attend the meeting and give feedback in the spec/guideline on behalf of their project, or find someone to knowledgeable in the initiative and the project [4].
> 
> If warranted, we can have a cross-project wide meeting, but I see these becoming unnecessary.
> 
> Some examples of cross-project initiatives happening are:
> 
> * The service catalog TNG [5]
> * Quotas - Delimiter [6]
> 
> I think this will allow cross-project initiatives to continue to flow in a more a natural way.
> 
> Please reach out to me if you have any questions. Thanks!
> 
> [1] - https://review.openstack.org/#/c/301822/4/doc/source/cross-project.rst
> [2] - https://review.openstack.org/#/c/295940/5/doc/source/cross-project.rst
> [3] - https://wiki.openstack.org/wiki/CrossProjectLiaisons#Cross-Project_Spec_Liaisons
> [4] - http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons
> [5] - https://wiki.openstack.org/wiki/ServiceCatalogTNG
> [6] - https://launchpad.net/delimiter
> 
> --
> Mike Perez
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> _______________________________________________
> Product-wg mailing list
> Product-wg at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg