policy for membership in MOTU key teams

[Scott Kitterman]

On Wednesday 02 July 2008 02:48, Stephan Hermann wrote:
> Good Morning,
>
> On Fri, 23 May 2008 19:26:40 +0200
>
> Stefan Potyra <sistpoty at ubuntu.com> wrote:
> > Hi,
> >
> > as evolved by the discussion for motu-sru members, I guess it might
> > make sense to have a good general policy.
>
> I would like to see a policy for:
>
> motu-sru / motu-release:
>
> 	* Changing Members every release cycle
>
> Why? It would be a good practice for newer MOTUs to step up and learn
> the "hard release work".
>
> Merging, fixing bugs, syncing for the actual development release is
> good and gives knowledge, but knowing how hard some decisions are is
> much better. Sure, re-elections of older members is possible, but I
> really want to see young blood.

I think some rotation is good, but not wholesale.  I'd support a longer term 
with staggered vacancies so we don't start over entirely.

The other thing is that we are not exactly over-run with volunteers.  I 
volunteered for motu-sru on the 2nd round after we didn't get enough on the 
first.  I've be glad to volunteer for a short initial term on motu-sru to get 
the cycle started.

Scott K