Open Stack

The mentoring / bandwidth aspect is a really good point.

--Rob

On 30 January 2016 at 11:10, Sean Dague <sean at dague.net> wrote:
> My concern is that all of this is too late in the cycle.
>
> From my understanding this is a time to get a lot of folks (especially
> new folks) together to work on bugs in the tracker. During the M3 -> RC
> period most teams are in a deep focus stage to make sure nothing major
> was missed, and only fixing critical things. Which lands this at the
> worst possible time in our cycle for engaging new folks.
>
> I get quite concerned when such a call to the community is made, a lot
> of the core teams that need to look at the stuff are heads down and
> ignore these new contributions, and these new contributors walk away
> feeling unwelcomed. Not because don't want them to be, but because this
> is the time when attention to wider contributions is at it's minimum.
>
> This really seems like it should be more of a Milestone 1 activity when
> the state of the project trees is more loose and open, and core team
> members have a bit more of a breather for mentoring.
>
>         -Sean
>
> On 01/29/2016 08:13 PM, Robert Collins wrote:
>> All the options seem fine to me. I don't think we want to be in the
>> business of arbitrating bottom-up events; but possibly the major
>> deadlines etc weren't clear enough? Shane - where you aware of the
>> conflicting dates [and thus didn't consider the conflict important],
>> or didn't realise there were conflicting dates?
>>
>> -Rob
>>
>> On 30 January 2016 at 08:26, Doug Hellmann <doug at doughellmann.com> wrote:
>>> TC Members,
>>>
>>> This week a "Global Bug Smash" event involving quite a few of our
>>> larger contributing companies was announced as scheduled for March
>>> 2-4 [1]. Those dates overlap exactly with our feature freeze deadline
>>> for Mitaka, so I contacted the organizers of the event (some of
>>> whom are copied on this thread) about rescheduling the event. After
>>> explaining my concerns, I suggested that the event move to the
>>> following week, possibly March 7-9.
>>>
>>> Most everyone was understanding about the conflict. Shane Wang seems
>>> to be the main person coordinating the event, and he thought it was
>>> very possible it could be rescheduled. He did want to get the TC's
>>> opinion of the new date. I've added the topic to our agenda for
>>> Tuesday's meeting [2], but also wanted to give everyone notice of
>>> that in case you have questions that Shane or I can answer before
>>> then.
>>>
>>> For now it would be most helpful to have a clear indication of your
>>> preference for Mar 2-4 or 7-9, though I'll be happy with any dates
>>> between Mar 7-11, if for some reason 7-9 doesn't actually work for
>>> the organizers. At some point, I would also like to brainstorm ideas
>>> for avoiding this sort of scheduling conflict in the future, but
>>> that can come after we've dealt with the more immediate issue.
>>>
>>> Doug
>>>
>>>
>>> [1] http://lists.openstack.org/pipermail/openstack-dev/2016-January/085196.html
>>> [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
>>>
>>> _______________________________________________
>>> OpenStack-TC mailing list
>>> OpenStack-TC at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
>>
>>
>>
>
>
> --
> Sean Dague
> http://dague.net
>
>
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
>



-- 
Robert Collins <rbtcollins at hpe.com>
Distinguished Technologist
HP Converged Cloud