[Framework-Team] the end is nye

[Michel Pelletier]

+1 on disolving the team.  I think it's a great idea and lots of other 
folks would jump on board.

Maybe one person should stay on so that the next team doesn't have to 
figure it all again.  I nominate Whit ;)

-Michel

whit morriss wrote:

> Being that primary purpose of the framework team is to review code, 
> some short day after December 1 the plone 2.2 framework team becomes 
> obsolete.   Or at least enters a time of transition.
>
> being the bootstrap team, we get the honor of deciding what happens 
> next and I'm going to make a proposal that should  sound pretty familar.
>
> After December 1, we finish our code review and work with stefan to 
> create a loose release plan (strengths, weakness, risks, how will 
> these things be accomplished).    This plan becomes our final report.  
> Then we choose a new leader for the framework team (I nominate stefan) 
> who then picks the new framework team of people he wants to work with 
> (ie people with whom he can easily teleconference).
>
> I think it's important, especially for this first team, to bow out 
> quickly into the ranks of the developers.
> 1.  having considered the process from the bootstrap stages, we can 
> best support it as developers.  After we indoctrinate the new team, 
> there are automatically twice as many people invested this process and 
> who can explain it to others.
>
>
> 2. we don't want our roles as a framework team member to adversely 
> effect the development dynamic. and hopefully, all of us will being 
> participating in the release.
>
>
> 3. and, we *really* don't want anyone to get the impression that the 
> framework team is responsible for releases or development in the sense 
> of cranking out code and fixing bugs.  that's work we do as 
> developers.   disolving the 2.2 team immediately prevents any confusion.
>
>
> 4. Picking a new framework gets new people involved in the process at 
> what I think is the right time.  Why? because this will be the 
> downtime for code review and the best time to impart what we have 
> learned so far.
> It also is the right time to start looking forward to 2.3.
>
>
> 5. It's alway good to purge the old regime.  we want the new team to 
> feel free to adapt the process to work f
> or them. 
> Our pool is deep in talent but not so in numbers, so I imagine some of 
> the same faces will appear again as the member of the framework moves 
> East and West.   voting members are only a necessity because 
> somebodies got to be responsible for making decisions.
>
> -w
>
>_______________________________________________
>Framework-Team mailing list
>Framework-Team at lists.plone.org
>http://lists.plone.org/mailman/listinfo/framework-team
>  
>