| ... | ... | @@ -4,21 +4,18 @@ |
|
|
|
If you have an idea:
|
|
|
|
|
|
|
|
1. Post it to the [MailingList](mailing-list). Use the [MailingList](mailing-list) for discussion and to reach a consensus.
|
|
|
|
1. If you don't have a wiki account, [Log in](/trac/haskell-prime/login) with username guest and password haskell' to [create](/trac/haskell-prime/newticket) and edit tickets.
|
|
|
|
1. after some discussion, create a new ticket (or modify an existing one) to document the consensus as a proposal. See [WikiGuidelines](wiki-guidelines).
|
|
|
|
1. 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.
|
|
|
|
1. Watch for threads that outlive their usefulness as a discussion. Document the disagreements on the wiki.
|
|
|
|
1. Once a concensus has been reached, try to write down the proposal as completely and precisely as possible.
|
|
|
|
1. It is the responsibility of the committee to keep track of proposals discussed on the mailing list. If your idea is not listed on the [Status](status) page, please notify a committee member and ask them to do so.
|
|
|
|
|
|
|
|
## How to modify an existing proposal
|
|
|
|
## Tickets
|
|
|
|
|
|
|
|
1. if the proposal is in a ticket, modify it directly
|
|
|
|
1. otherwise, if you don't have write access to the wiki, discuss your change request on the mailing list
|
|
|
|
1. or just modify the ticket that references that wiki page, requesting the change be made there.
|
|
|
|
|
|
|
|
We have been using tickets in the past to keep track of proposals, but that turned out to be rather cumbersome as there are many small issues. So now the status of each proposal is kept in the Haskell source file [ http://darcs.haskell.org/haskell-prime-status/status.hs](http://darcs.haskell.org/haskell-prime-status/status.hs) which can be modified by committee members, and from which the wiki page [Status](status) is automatically generated.
|
|
|
|
|
|
|
|
## For the Committee
|
|
|
|
|
|
|
|
|
|
|
|
A semi-official proposal has two parts:
|
|
|
|
A proposal has two parts:
|
|
|
|
|
|
|
|
- A wiki page describing the issue. The page should be linked from:
|
|
|
|
|
| ... | ... | @@ -29,14 +26,7 @@ A semi-official proposal has two parts: |
|
|
|
> > 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. |
|
|
|
- An entry in the file `status.hs` in the darcs repository at [ http://darcs.haskell.org/haskell-prime-status/](http://darcs.haskell.org/haskell-prime-status/).
|
|
|
|
(if you find you can't push patches to that repository, please tell me).
|
|
|
|
|
|
|
|
- Please be very observant of new ideas from folks on the mailing list that should go in the wiki. |
