... | ... | @@ -2,26 +2,18 @@ |
|
|
|
|
|
|
|
|
|
|
|
Each proposal has a unique name, a good choice being the name used for the compiler flag, which is usually the same as the name of the extension in the `Language.Haskell.Extensions` type.
|
|
|
To create a new proposal:
|
|
|
|
|
|
|
|
|
|
|
|
Wiki pages for proposals are named `"Proposal/<name>"`.
|
|
|
|
|
|
|
|
|
|
|
|
Each proposal on the wiki is expected to follow this standard form.
|
|
|
We may move these fields into the ticket system in due course; for now
|
|
|
we use the wiki.
|
|
|
|
|
|
- Choose a unique name for the proposal (e.g. [HierarchicalModules](hierarchical-modules)). A good choice being the name used for the compiler flag, which is usually the same as the name of the extension in the `Language.Haskell.Extensions` type.
|
|
|
- Create a wiki page, named "Proposal/\<name\>". Use the template below.
|
|
|
- Create a [ New Ticket](http://hackage.haskell.org/trac/haskell-prime/newticket), with the proposal name in the subject. Set the "state" to "discussion", select the appropriate "type" and "section", and fill in the "owner" field.
|
|
|
- Point to the ticket from the wiki page
|
|
|
|
|
|
```wiki
|
|
|
= Proposal: <name> =
|
|
|
|
|
|
|| Type || [extension | removal | change] ||
|
|
|
|| Status || [discussion | complete | accepted (revision)] ||
|
|
|
|| Owner || <name(s)> ||
|
|
|
|| Section || <the section(s) of the Report this applies to, or N/A> ||
|
|
|
|| Ticket || #999 ||
|
|
|
|| Dependencies || names of other proposals on which this one depends ||
|
|
|
|| Related || names of related (e.g. alternative) proposals ||
|
|
|
|
... | ... | |