|Version 3 (modified by ijones, 9 years ago) (diff)|
How to create a proposal
If you have an idea:
- Post it to the MailingList. Use the MailingList for *discussion* and to reach a consensus.
- after some discussion, create a new ticket (or modify an existing one) to _document_ the consensus as a proposal.
- You may want to post the wiki page you create back to the thread so that the thread participants can review and edit it. If you get no support on the mailing list for an idea, please think twice about whether or not to create a ticket for it.
- Watch for threads that outlive their usefulness as a discussion. Document the disagreements on the wiki.
For the Committee
A semi-official proposal has two parts:
- A wiki page describing the issue. The page should be linked from:
The wiki page should have a section Proposal containing the formal proposal (most proposals don't start out with this section, but it will be added when the details have been worked out).
- A ticket, with component set to "Proposal". The ticket content should simply point to the wiki page, and
the wiki page should likewise link back to the ticket. The ticket fields should be set as follows:
- Type: modification, enhancement, removal, etc
- Component: Should always be Proposal.
- Impact: how much impact on the language and implementations?
- Adopt: Do we want it? Please don't mark stuff as "definitely" yet.
- Priority: How important is it to address this issue (mostly left as default)
- Owner: the person most responsible for this proposal, or "none".
- Please be very observant of new tickets and ideas from folks on the mailing list that should go in the wiki.