Document Actions
Using Improvement Proposals Effectively
Improvement Proposals (like Plone's PLIPs and Python's PEPs) are documents that you or others can write for your project to outline new features or designs. They give fellow developers and users a way to understand what features might be coming, and to organize which improvements will land in which versions.
pupq
Plone Software Center allows you to list your product on plone.org, show releases, manage your documentation, handle improvement plans, and more--all without forcing you into any particular development process or repository. We intend for this to become the canonical repository for Plone products. This tutorial walks through the benefits of PSC and demonstrates how to make the most of it.
Page
5
of
7.
You can add improvement proposals to your "Roadmap" folder. Most of the fields here aren't required, and the very-broken-down entry system may not be appropriate for simpler projects or proposals.
IPs are autonumbered, and list by which release lists the IP in its "related proposals" field.
There is a simple workflow for improvement proposals to manage where the IP is in its process.
You can assign local roles in the releases and proposal folders, if you want people to be able to submit proposals but not assign them to releases without your approval. This is also the reason you associate Improvement Proposals to a release from inside the release, and not the other way around.
by
pupq
—
last modified
May 8, 2005 - 23:56
Contributors:
Alexander Limi
All content is copyright Plone Foundation and the individual contributors.
