Open Stack

Interesting view, 

I was thinking that most companies and groups of people, even in open source like to have leadership which clearly knows where they want to "sail the ship" for the next six+ months. And said direction should be something concrete and simple (aka fits in one or 2 sentences). Doesn't that seem like a good thing to have? 

Like for example.

"During my term I will try to make nova more stable and reliable."

Now that goal is at a high enough level that it can be tolerant to developers failing to actually submit any work (to some level) but it is also somewhat measurable so that after 6 months is up people can ask themselves if nova is really anymore stable and if not then maybe said person is not a good project leader. It always acts as a steering force for which types of blueprints people will submit and so on...

How else do people measure whether a  project leader is doing good or bad without this kind of initial goal and evaluation?

Sent from my really tiny device...

On Apr 11, 2013, at 8:55 PM, "Angus Salkeld" <asalkeld at redhat.com> wrote:

> On 12/04/13 00:47 +0000, Joshua Harlow wrote:
>> Ok good to know, I was thinking that the 'state of the project' talk would
>> have a big goal that said PTL can say I will try to do this for these 6
>> months.
>> 
>> Like a presidential campaign :-P
> 
> That sounds odd. Does a PTL have that much impact?
> This is open source, people come with patches that they want, not what
> the PTL wants to accomplish. To me a team of core developers that work
> really well together is much more important. And that is really the
> job of the PTL - to make sure everyone is working well together.
> 
> Whether or not blueprints/features get developed is not (to me) a
> sign of a failing PTL (more likely developers found more import
> things to work on).
> 
> -Angus
> 
>> 
>> Blueprints are nice and all, but they are to 'low-level' imho, in that
>> they are scattered and don't show a unified single 'goal'.
>> 
>> I could image a 'top-level' goal being.
>> 
>> *Fix nova's use of scheduling*
>> 
>> Then all changes done for that 6 months would try to work towards this
>> goal (+- a few other ones that get in).
>> 
>> On 4/11/13 5:39 PM, "Russell Bryant" <rbryant at redhat.com> wrote:
>> 
>>> On 04/11/2013 07:00 PM, Joshua Harlow wrote:
>>>> Howdy all,
>>>> 
>>>> I was talking with a co-worker here @ y! and both of us were thinking
>>>> about how we know what features are planned for the next 6 months.
>>>> 
>>>> I know summits are supposed to be the driver of this, and the talks that
>>>> occur, but after the summit sessions and talks and such is there a
>>>> single place/wiki(?) that each PTL states exactly what they plan to
>>>> accomplish after the input from the summit. I see there
>>>> is http://www.openstack.org/software/roadmap/ which is at a very high
>>>> level.
>>>> 
>>>> Would others feel it is useful to have PTL's write down there goals and
>>>> desires for the next 6 months (not at such a high level as the above
>>>> link).
>>>> This can then be referred to when voting for the next PTL and so forth.
>>>> 
>>>> I just have always sort of felt that it was hard to tell what a PTL's
>>>> goals were for each 6 month interval, and how to compare what they
>>>> did/accomplished vs what they stated they would attempt to do.
>>>> Having a plan that the PTL supports seems to be a good thing in general,
>>>> so that the direction of said project is steered.
>>>> 
>>>> Thoughts?
>>>> Does something like this already exist and I didn't find it?
>>> 
>>> Each project will be having a "state of the project" talk on the last
>>> day of the Summit where some of this will be discussed.  Much of the
>>> Havana plan will be captured in blueprints in the time immediately
>>> following the summit.
>>> 
>>> --
>>> Russell Bryant
>> 
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev