Changes between Version 1 and Version 2 of WikiGuidelines

Timestamp:

04/01/08 15:04:44 (5 years ago)

Author:

simonmar@…

Comment:

--

WikiGuidelines

@@ -7 +7 @@
 Otherwise, some guidelines to keep in mind:
 
-== The wiki and Tickets ==
+== The wiki ==
 
 No Discussion on the Wiki!  Keep discussion on the mailing list and
 use the wiki to document consensus and pros & cons.  It is just fine
-to have conflicting points of view in a ticket or on the wiki, but no
+to have conflicting points of view on the wiki, but no
 back-and-forth discussion (use the mailing list for that).  Create
-"pros" and "cons" sections in the ticket/wik.
+"pros" and "cons" sections to document both sides of the discussion.
 
-== For Tickets ==
+== Tickets ==
 
-For tickets, use EDIT rather than adding "comments".  Link this ticket
-with wiki pages or other tickets which are related, or for which this
-is a counter-proposal.
+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] which can be modified by committee members, and from which the wiki page [wiki:Status] is automatically generated.
 
-Be sure to set the "component" field as "Proposal" and leave the Adopt
-field alone.
+== Creating a proposal from a discussion ==
 
-== Creating a Ticket from a Discussion ==
-
-So for instance, there's a proposal that we modify the comment syntax.
-After some time for discussion on the list, whoever is agitating
-(leading a discussion) should create a new ticket if s/he still
-believes in the suggestion.  The ticket should have
-component:proposal. The pros are that it's going to be simpler for
-students, more consistent with the block comment syntax, and easier to
-implement in editors.  The cons are that we lose a group of possible
-operators, --> for instance, and this in turn may cause some code to
-break.
-
-Put your email address on the tickets so we know who to ask if we have
-any questions.
-
-To create a ticket, go to the wiki and log in.  The user name is guest
-and the password is haskell'.  If you think you'll be doing a lot of
-ticket work, email me for a guest account so that your name will
-automatically appear on the changes.
+It is the responsibility of the committee to keep track of proposals discussed on the mailing list.  If your idea has not been made into a fully-fledged proposal, please notify a committee member and ask them to do so.