Today we are lucky to have mikehalm of Weblion join up with us following cjohansen of the same. I think Mike is very motivated to make this project move forward. KurtB has also gathered up my old notes on deliverables and baked them into the wiki. I made our first strawman simplistic success story.
It is important for everyone involved to understand that what we are creating is a working group factory method, not a bunch of working groups. We want to paint a picture of what kind of working groups are worthy of Plone Foundation endorsement.
cbc thanks for the chops… When I think of a factory method. I think of a repeatable process that can be replicated. I hope that is what you are thinking of as well. Most of the deliverable have focused on components that might be part of what identifies a working group. Some would be mandatory and some would be optional. I would think that we need a somewhat specific process that should be associated with these deliverables too. What would you envision such a process to involve?
Comment by mikehalm on June 3, 2008 at 9:49 am
Mike,
Version 4 of Define Deliverables had the comment at the top:
“List out things a working group might need to create success. The deliverables are actually the order and procedures for creating those things rather than the things themselves.”
I think this addresses your concern. It was edited out in your changes for Version 5 of Define Deliverables. I have restored it to the current version along with some answers to questions about optionals.
It may be advisable to use the email list for such questions rather than the wiki itself.
Note regarding some options: this project is about tailoring Plone for specific industry groups. It is not a marketing task, although marketeers are certain to market the products of such a process. I want to be careful not to expand the scope of this project into marketing.
Cheers, Chris
Comment by cbc on June 3, 2008 at 10:13 am