#0: Plone Improvement Process
- Contents
A proposal for a Plone Improvement Process.
- Proposed by
- andym
- Proposal type
- Process
- State
- completed
Motivation
A major problem with Plone 1.0 was that there was no clearly defined end point. Features were not specified and no-one knew when it was finished. Furthermore there was no clear development process, it seemed people would add features as they saw fit.
Now 1.0 is out and Plone is moving to a more regular release schedule the need for a very minimal amount of process as to the contents of each release is needed. This is common in the open source projects Plone is connected with CMF, Zope and Python.
Proposal
All new features to Plone should have either a bug in the collector (ie: its a bug or a very minor feature) or a PLIP. Involved parties would write a PLIP explaining what they want to do and why. This would be in the public domain so everyone could see what is happening and where.
Implementation
If accepted for a certain version the status of the PLIP would be changed to reflect that. As the project progresses the PLIP would be updated.
When the all the PLIP's for that version have been done, the project can be completed. This PLIP archive will serve as an invaluable reference for features.
