Open Stack

Today we were thinking a little bit about the patches work we have to
do/we have on flight. And their dependencies.

http://fileshare.ajo.es/QoS/P6290039.jpg

This is how it looks like (probably missing stuff).

Notation:

  * Green are single patches (in some cases those can/should be divided)
  * Red are blocks which we could more or less do in parallel
  * Orange is optional stuff.


Today Ihar and I have been able to use some time for the top left block 
to merge stubs for the api extension and service, even if are not final, 
but still installable, so we can create the experimental jobs.

First thing we could do in the morning could be to iterate over the 
diagram and assign a local "tenant" for the blocks, which could serve as 
a reference for remote collaborators to ask/participate via IRC :)




Vikram Choudhary wrote:
> Thanks for arranging this Miguel. Looking forward to contribute in the best
> way we can 😀
> On 26-Jun-2015 3:33 pm, "Miguel Angel Ajo"<mangelajo at redhat.com>  wrote:
>
>> Hi everybody,
>>
>>      Next week, from Tue (Jul 29th) to Thu (Jun 2nd), a few of us will be
>> physically [1] attending the neutron QoS coding sprint in Ra'anana (Israel)
>>
>> @ the Red Hat office.
>>
>>      And a few others have expressed their will to join us remotely
>> (Thanks!!) :)
>>
>>      I guess a reasonable format for the sprint is in the form of short
>> meetings followed by coding hours.
>>
>>      We thought it was good to sync with others during the first day on the
>> neutron meeting (Tue / Jul 29th, 14:00 UTC #openstack-meeting) about any
>> progress, blockers or doubts, so we have requested a timeslot for it :)
>>
>>       All the other days, we also plan to sync on #openstack-neutron @
>> ~14:00 UTC with the remote participants.
>>
>> TL;DR ...
>>
>>      In an effort to collaborate I'm extending [1] to include the list of
>> patches we're working on,
>> please list any of them missing in there.
>>
>>      Since we live in different timezones I believe we can let others
>> address small/nit/not big structural changes which may need discussion by
>> the people on other timezones, and we can use a locking mechanism with the
>> etherpad+#openstack-neutron to say who's working in a patch.
>>
>>      By the way, I think the value of gathering is that we can all be
>> together to discuss and iterate very quickly, so during the Israel working
>> hours I believe we may (generally) prioritize the people physically
>> attending the sprint to work on patches to avoid blocking on depending
>> parts.
>>
>>
>> Thanks everybody, and sorry for the long message :)
>>
>>
>> [1] https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint
>>
>>
>>
>>
>
> __________________________________________________________________________
> 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