Open Stack

It's not about if should happen, but discussing the change. We are very good at communicating within a project. This group can discuss the big changes/ideas from many of the projects. The services split is a good example I think. Nothing to do with the good or bad. 

~sean

> On Dec 23, 2014, at 7:40 AM, Kyle Mestery <mestery at mestery.com> wrote:
> 
>> On Tue, Dec 23, 2014 at 12:38 AM, Sean Roberts <seanroberts66 at gmail.com> wrote:
>> I'd like to set the in person meeting for the week of 26 January in Palo Alto VMware.  Depending on below, we need to decide how long is needed; half day to two days is my guess.
>> 
>> I think this is the most important spec/blueprint right now. Neutron services split https://github.com/openstack/neutron-specs/blob/master/specs/kilo/services-split.rst
> This is already implemented actually, so I'm not sure what discussing would mean here. We're just cleaning up the pieces post-split.
>  
>> I think this is the most important topic to discuss right now. Tagging approach to project maturity, http://ttx.re/the-way-forward.html
>> 
>> We can start the discussion here. I think these topics will be more than enough to make a difference this release.
>> 
>> ~ sean
>> 
>> > On Dec 22, 2014, at 4:56 PM, Stefano Maffulli <stefano at openstack.org> wrote:
>> >
>> > On 12/21/2014 12:56 PM, Colette Alexander wrote:
>> >> This all sounds good - but it also sounds like a lot of continuous work and
>> >> commitment to be a part of the community in ways that haven't yet existed.
>> >> To that end, I wonder how this collaboration might happen. I know there's a
>> >> mid-cycle meetup being planned - is there anything else that might make
>> >> sense for us to do on a more regular (weekly?) basis? I have all of the
>> >> where/how questions about the above list (which is a *great* one) - and one
>> >> question that Allison,Sean and Rob posited at the Summit still sticks in my
>> >> craw: are we all willing, as a group, to share pieces of our
>> >> roadmap/customer feedback & internal prioritization at the open source
>> >> level to help out with this?
>> >
>> > That's a great question and one that I'd love to see answered.
>> >
>> > I'd honestly settle if anyone in this group would identify the most
>> > important specs, for them, and ask to this group for any doubt/question
>> > they have.
>> >
>> > For example, Neutron approved *a lot* of specs for Kilo, the core team
>> > knows they've over-booked their resources. Chances are, a lot of these
>> > specs have high chances of not going to be shipped in Kilo release.
>> >
>> > http://specs.openstack.org/openstack/neutron-specs/
>> >
>> >> It might be a thing that has to develop organically through meetings, but I
>> >> do think developing our own upstream shared space of understanding and ways
>> >> of work will be the first step, before we can provide a unified vision to
>> >> present & help with project work happening upstream.
>> >
>> > Meeting regularly would be good. Any thoughts on the medium and time?
>> >
>> >> I agree wholeheartedly with all of the above, *especially* with the
>> >> not-telling-project teams what to do. I do think some work could/might be
>> >> done by this group during a development cycle with an eye towards
>> >> presenting to developers or teams before the summit for the next
>> >> development cycle. I also think for folks who are on the more program
>> >> spectrum of things (as opposed to product management), meeting or gathering
>> >> mid-cycle to reaffirm resource commitments through the end of the
>> >> development cycle, or all folks gathering to help re-prioritize if projects
>> >> need it, wouldn't be awful either.
>> >
>> > I'll let Sean kick-off the conversation about an in-person meeting some
>> > time before/around kilo-2.
>> >
>> > /stef
>> >
>> > _______________________________________________
>> > Product-wg mailing list
>> > 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
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg