From: Alexander L. <li...@pl...> - 2004-04-06 14:17:43
|
On Tue, 6 Apr 2004 15:50:27 +0200, Francesco Ciriaci <cir...@ti...= > =20 wrote: > PloneWorkflows is a Plone Product that adds 4 build-in workflows for =20 > Plone to > choose from. > 1) Community WF is just Default Plone right now. This is fine, although we should take the opportunity to rename "visible"= =20 to "public draft". > 2) Intranet WF is a new version of Private Plone Workflow > 3) SimplePublicaton WF is a simple two step workflow > 4) OneState WF is a stupid yet useful workflow w/out workflow > > 0.6 works fine, but we need testing, and also some mor testing ;) You rock. :) > I also added some non technical documentation recenty. > > PWF needs to be integrated into Plone one day, and w/ private plone > customization policy. I see no need for a customization policy if we can easily swap out the =20 workflows? Anyway, the next step should be to: a) Create a PLIP that describes the steps needed and announce it b) Wait a few days for any comments on the PLIP c) start a 'plipXX-plone-selectable-workflows' as a branch off HEAD d) Do the integration, and start testing when it's close enough for it to= =20 make sense e) Write migrations for existing workflows e) Merge to HEAD when Andy/Sidnei has given approval > last but not least we need to build a really simple 'workflow control =20 > panel' > to allow site managers to choose their favourite workflow. I will help out with this once we get it as a branch in the Plone CVS. --=20 __________________________________________________________________ Alexander Limi =C2=B7 Interaction Architect =C2=B7 Plone Soluti= ons Development =C2=B7 Training =C2=B7 Support =C2=B7 http://www.plonesolut= ions.com __________________________________________________________________ Plone Co-Founder =C2=B7 http://plone.org =C2=B7 Connecting Cont= ent |