Plone Improvement Proposal News & Articles

The Plone (news, site) project has launched a user feedback system for collecting Plone improvement ideas. This tool allows Plone users to suggest, discuss, and vote on ways the open source CMS can be improved.

While the project doesn't promise that every idea will be implemented, they intend to use this system to understand what Plone users want to see added and improved. In particular, the team recommends that anyone interested in contributing to the project should take a look and see what ideas are the most in demand and sound like something they may want to work on.

If you find something and end up working on a significant new feature or change, then you'll pull together a Plone Improvement Proposal, or PLIP. This PLIP will be reviewed by the Framework Team assigned to the major release you're aiming for (as an example, the deadline for Plone 4 PLIPs just passed).

For more information:

• See the FAQ "How to suggest a feature for Plone"
• Submit and browse Plone improvement ideas
• Read the official idea system launch posting

The Plone (news, site) 4 Framework Team has put out a call for Plone Improvement Proposals (PLIPs). PLIPs are necessary for any improvements that are larger than a bug fix and should only be submitted if you either plan to do the coding yourself, or pull together people to write it.

Plone 4 will bring Plone up to date with current technologies, while making it easier to work with for integrators and end users. As this release is meant as an intermediate step toward the radically updated Plone 5, hold any changes that "significantly alter backwards compatibility, visuals or APIs" until then.

Turn in your PLIP submissions by 0700 UTC (3am EDT) on 20 June 2009. To do so, look over previous PLIPs as a guide to what format to use, create a ticket with the type PLIP, and then enter your proposal.

Include information such as:

• Why is the change important?
• How will this change be achieved?
• What downsides are there to this change being adopted?

When it's ready for consideration, set the milestone to 4.0. From there, you will receive feedback from the Framework Team. The team will then vote on submissions and set deadlines for when they must be ready. The code must be complete by the stated deadline to be included in the release.