Changes between Version 72 and Version 73 of WikiStart

Jul 7, 2009 1:01:35 PM (8 years ago)
Simon Marlow


  • WikiStart

    v72 v73  
    55The [ Haskell] programming language is more-or-less divided into two "branches". The [ Haskell 98] standard is the "stable" branch of the language, and that has been a big success. A lot of progress has been made over the last few years in the "research" branch of the Haskell language. It is constantly advancing, and we feel that it is time for a new standard which reflects those advancements.
    7 [wiki:Haskell'] (pronounced "Haskell Prime") will be a relatively conservative refinement of Haskell 98.  It will be the work of this [wiki:Committee committee] to adopt a set of language extensions and modifications and to standardize a new set of libraries. We maintain a set of [wiki:Principles] to help guide our choices.
     7[wiki:Haskell'] (pronounced "Haskell Prime") is an ongoing process to produce revisions to the Haskell standard, incorporating mature language extensions and well-understood modifications to the language.  New revisions of the language are expected once per year, with the first revision ("Haskell 2010") due to be released in late 2009.  Certain revisions will be denoted "major versions", which are intended to be supported for longer periods.  The latest major revision is still Haskell 98.
     9Haskell' is a distributed, community-supported effort.  While the committee has the final say as to which modifications are incorporated into each revision, the modifications themselves are defined through open discussion amongst the community.  More details are in the [wiki:Process] page.
    1011== Resources ==
    1213These are the resources that the community and committee are using during development of [wiki:Haskell'].
     15 * The [wiki:Process] documents the process by which we produce new language revisions.
    1417 * The [ haskell-prime mailing list]: all technical discussion will take place here, or (if other meetings take place) be reported here. Anyone can subscribe, and any subscriber can post questions and comments, and participate in discussions. Anyone can read the list archives.
    16  * This wiki: to document consensus. This system is publicly readable, but only committee writable so that we may present it as the "official" output of the committee. If you ever feel that the wiki is not accurate as to the consensus, please alert the [wiki:Committee committee]!  See WikiGuidelines.
    18  * The [wiki:Status] page documents the current status of each proposal or issue.  This page is automatically generated from the darcs repository at [].
    20  * The [ Haskell Prime Report] is under construction, and the online version is kept automatically updated.
     19 * This wiki: to document proposals. This system is publicly readable, but only writable by proposal owners.
    2221 * The [wiki:SourceCode haskell-prime code repository]: a darcs repository for experiments, proposed libraries,and complex examples. [ darcs] is a decentralized system, so anyone can use it, but patches should be sent to [ Isaac Jones].
    2423== Status ==
    26 (March 2008)  After a quiet 12 months or so, we are gathering momentum again, and the committee is beginning to make concrete decisions.  To see what has been decided, keep an eye on the [wiki:Status] page. 
     25Haskell 2010 is due to be released in late 2009.  The set of changes to be incorporated will be announced at the [ Haskell Symposium], September 3 2009.
    28 To help make the process more agile, we are no longer using tickets to manage issues.  Instead, the list of current proposals is kept in the Haskell source file [], from which the [wiki:Status] page is automatically generated.  We are still using the wiki to document proposals, and we also intend to document the rationale for each decision here on the wiki.
     27== Get Involved ==
     29Haskell' is a community-driven process.  Here are some of the things you can do to get involed:
     31 * Join the [ haskell-prime mailing list], and contribute to the discussion.
     33 * If you have a pet idea for a change to the language, try floating it on the mailing list (you might want to check whether
     34   it already has a proposal page first).
     36 * If you favor one of the proposals that isn't implemented, implement it!  Proposals with an implementation are much more
     37   likely to be accepted, as experience with an implementation tends to expose interactions that are otherwise hard to forsee.
     39 * Help to refine an existing proposal to the point where it can be accepted.  See the [wiki:Process] page for more information.
    3041== Proposals ==
    3243 * [wiki:Status List of proposals]
    33  * [wiki:CreateProposal How to create a proposal]
    3545== Principles ==
    4858== Administrative details ==
    50  * FocusGroups are subcommittees which focus intently on particularly important topics.
    51  * [wiki:Haskell' The Haskell' name]
    5260 * [wiki:Committee The Haskell' committee]
    5361 * ToolSupport for syntactic change
    5462 * [wiki:TracStartPage Help on using this wiki]
     64== Older stuff that needs updating ==
     66 * FocusGroups are subcommittees which focus intently on particularly important topics.
     67 * [wiki:Haskell' The Haskell' name]
    5568 * Previous [wiki:Status'] page
     69 * The [ Haskell Prime Report] is under construction, and the online version is kept automatically updated.
     70 * [wiki:CreateProposal How to create a proposal]