Changes between Version 6 and Version 7 of CreateProposal

Apr 1, 2008 11:44:46 PM (10 years ago)
Simon Marlow



  • CreateProposal

    v6 v7  
    55 1. Post it to the MailingList.  Use the MailingList for discussion and to reach a consensus.
    6  1. If you don't have a wiki account, [/trac/haskell-prime/login Log in] with username guest and password haskell' to [/trac/haskell-prime/newticket create] and edit tickets.
    7  1. after some discussion, create a new ticket (or modify an existing one) to document the consensus as a proposal.  See WikiGuidelines.
    8  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.
    9  1. Watch for threads that outlive their usefulness as a discussion. Document the disagreements on the wiki.
     6 1. Once a concensus has been reached, try to write down the proposal as completely and precisely as possible.
     7 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 [wiki:Status] page, please notify a committee member and ask them to do so.
    11 == How to modify an existing proposal ==
    12  1. if the proposal is in a ticket, modify it directly
    13  1. otherwise, if you don't have write access to the wiki, discuss your change request on the mailing list
    14  1. or just modify the ticket that references that wiki page, requesting the change be made there.
     9== Tickets ==
     11We 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 [] which can be modified by committee members, and from which the wiki page [wiki:Status] is automatically generated.
    1613== For the Committee ==
    18 A semi-official proposal has two parts:
     15A proposal has two parts:
    2017 * A wiki page describing the issue.  The page should be linked from:
    2522  out with this section, but it will be added when the details have been worked out).
    27  * A ticket, with component set to "Proposal".  The ticket content should simply point to the wiki page, and
    28    the wiki page should likewise link back to the ticket.  The ticket fields should be set as follows:
    29    * Type: modification, enhancement, removal, etc
    30    * Component: Should always be Proposal.
    31    * Impact: how much impact on the language and implementations?
    32    * Adopt: Do we want it?  Please don't mark stuff as "definitely" yet.
    33    * Priority: How important is it to address this issue (mostly left as
    34      default)
    35    * Owner: the person most responsible for this proposal, or "none".
    36  * Please be very observant of new tickets and ideas from folks on the mailing list that should go in the wiki.
     24 * An entry in the file `status.hs` in the darcs repository at [].
     25   (if you find you can't push patches to that repository, please tell [ me]).
     27 * Please be very observant of new ideas from folks on the mailing list that should go in the wiki.