Our process could be improved.
we reviewed a few bundles a week over the course of a few weeks.
Basically, I or Alan would announce what bundles we were looking at and
when the next phone call would be by email. Since the process for each
bundles was not specifically owned by anyone, the coverage of attention
was a bit scattered imho and alot of time was wasted in rambling
conference calls. cie la vie.
Since you have more bundles and more people, dividing the bundles among
general areas of expertise might be a good idea. If everyone owns the
review of 2 or 3 bundles you should be well covered and then you have a
point of contact for the bundle authors. Not unlike SoC.
Key to the process is to draft as many people from outside the voting
FWT to look at bundles and get their input. Good job wiggy with the
announcement. This could be a good time to rouse up some enthusiasm
about actually cranking out P3.
I recommend using a file in the svn bundle root as a comment trail: it
is automatically web published, everyone should check out every bundle,
all plone devs have write access to it, and conflict are merged(rather
than blotted out or lost as in a plone doc or email thread). We used
an email for each bundle that the group appended to by replying(post vote).
The worst part was getting people to make opinions in a timely fashion;
I would recommend getting all opinions before the vote if possible.
Having collected as many comments as possible before the vote makes
voting faster and reporting the outcome easier. We voted on the
phone(sort of a waste of time imho); you might choose to use svn or
email.
Afterwards, someone (Marten in this case) compiles the votes and the
various suggestions for next step and opinions into a usable report for
that set of bundles and posts the report to plone-dev. In the case of
a rejection, someone should compile an explanation for the author of the
package including what would need to be do for inclusion and a timeline
for getting those things done.
lather, rinse, repeat.
Once you have completed this process for all the bundles, write wiggy a
final report filled with guiding wisdom, make an announcement that you
are disbanding as the voting board of the FWT, have a beer, scotch or
coffee and at your leisure choose your successors for the next release.
-w
Martin Aspeli wrote:
So, the bundle deadline passed, and I almost got some sleep. I'm
guessing a few bundles will trickle in still (Vincenzo is on holiday,
for example, but promised to look at workflow)
Members from last year - how did you go about actually undertakign the
reviews?
We have bundles at http://svn.plone.org/svn/plone/review/ (and one at
svn.plone.org/svn/collective/easycommenting/bundles/2.5/
<http://svn.plone.org/svn/collective/easycommenting/bundles/2.5/>
since Kai doesn't have commit privs yet).
This matches up pretty well to what we see in
http://plone.org/roadmap, with a few exceptions. Most of these are
excusable (AJAX dependencies that make no sense until we've sorted out
that can of worms, trivial things that probably don't need much review
- we'll have to take it on a case-by-case basis).
I know Wichert is away for 5 days, and Vincenzo is on holiday (until
the middle/end of the week?). I'd be nice if we could come up with a
process, though.
Martin
------------------------------------------------------------------------
_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
