Changes between Version 1 and Version 4 of Ticket #9

Jan 14, 2006 12:51:53 AM (9 years ago)


  • Ticket #9 – Description

    v1 v4  
    33== Draft Announcement == 
    4 Haskell': Committee for the next Haskell standard formed 
     4Haskell': Kicking off the process of defining the next Haskell standard. 
    66let haskell' = succ haskell98 in 
    8 Announcing the Haskell' Committee.  A few weeks ago, I asked for 
    9 volunteers to help form a committee for an effort to put together the 
    10 next Haskell standard.  Our task is broadly defined by our mission 
    11 statement: 
     8Announcing the Haskell' process.  A short time ago, I asked for 
     9volunteers to help with the next Haskell standard.  A brave group has 
     10spoken up, and we've organized ourselves into a committee in order to 
     11coordinate the community's work.  It will be the committee's task to 
     12bring together the very best ideas and work of the broader community 
     13in an "open-source" way, and to fill in any gaps in order to make 
     14Haskell' as coherent and elegant as Haskell 98. 
     16Our task is broadly defined by our mission statement: 
    1318    Haskell' will be a conservative refinement of Haskell 98. It will 
    1621    libraries. 
    18     We will strive to only include tried-and-true language 
    19     features. This standard will reflect the realities of developing 
    20     practical applications in the Haskell language. We will work 
    21     closely with the rest of the Haskell community to create this 
    22     standard. 
     23    We will strive to only include tried-and-true language features, 
     24    and to define them at least as rigorously as Haskell 98 was 
     25    defined. This standard will reflect the realities of developing 
     26    practical applications in the Haskell language. We will work closely 
     27    with the rest of the Haskell community to create this standard. 
    24  FIX: INSERT final MissionStatement 
    26  FIX: INSERT More specifics of scope 
     30 FIX: INSERT final PublicMissionStatement 
    2832Your Haskell' Committee is as follows (slightly munged email addresses 
    31  * John Launchbury <john _at_> 
    32  * Isaac Jones <ijones _at_ 
    33  * Autrijus Tang <autrijus _at_> 
    34  * John Meacham <john _at_> 
    35  * Henrik Nilsson <nhn _at_> 
    36  * Simon Peyton-Jones <simonpj _at_> 
    37  * Ravi Nanavati <ravi _at_> 
    38  * John Goerzen <jgoerzen _at_> 
    39  * Ross Paterson <ross _at_> 
    40  * Manuel M T Chakravarty <chak _at_> 
    41  * Malcolm Wallace <Malcolm.Wallace _at_> 
    42  * Bastiaan Heeren <bastiaan _at_> 
    43  * Simon Marlow" <simonmar _at_> 
    44  * Andres Loeh <loeh _at_> 
    45  * Don Stewart <dons _at_> 
    46  * Stephanie Weirich <sweirich _at_> 
    47  * S.J.Thompson <S.J.Thompson _at_> 
     35 * Manuel M T Chakravarty <chak at> 
     36 * John Goerzen <jgoerzen at> 
     37 * Bastiaan Heeren <bastiaan at> 
     38 * Isaac Jones <ijones at> 
     39 * John Launchbury <john at> 
     40 * Andres Loeh <loeh at> 
     41 * Simon Marlow <simonmar at> 
     42 * John Meacham <john at> 
     43 * Ravi Nanavati <ravi at> 
     44 * Henrik Nilsson <nhn at> 
     45 * Ross Paterson <ross at> 
     46 * Simon Peyton-Jones <simonpj at> 
     47 * Don Stewart <dons at> 
     48 * Audrey Tang <autrijus at> 
     49 * Simon J. Thompson <S.J.Thompson at> 
     50 * Malcolm Wallace <Malcolm.Wallace at> 
     51 * Stephanie Weirich <sweirich at> 
    4953The editors are Isaac Jones and John Launchbury. 
    51 The following resources are provided for the community and the 
    52 committee to perform this work. 
     55Feel free to contact any of us with any concerns or questions.  If you 
     56don't know who to direct your questions to, email Isaac Jones 
     57[email protected] 
    54  * The Haskell-cafe mailing list for public technical discussion: 
     59Community involvement is vital to our task, and there will be a way 
     60for members of the community to make formal proposals.  In the opening 
     61phases, however, please use these more informal resources to help us 
     62coordinate Haskell': 
    57  * A Haskell' mailing list, which is read-only for the public, but 
    58    anyone can subscribe to read it, and anyone can access the 
    59    archives.  This is only to keep list traffic manageable for the 
    60    committee.  Many committee members read haskell-cafe, and Isaac 
    61    will be sure to bring issues from the list to the committee where 
    62    appropriate.  You can always email a committee member if you want 
    63    to bring up an issue or make a proposal.  If you post to the 
    64    mailing list, it'll be held for moderation, and Isaac may allow it 
    65    through. 
     64 * A Haskell' mailing list for discussion.  Open to anyone to 
     65   subscribe and any subscriber can post questions and comments, and 
     66   participate in discussions. 
    67  * A wiki / issue tracking system.  This system is publicly readable, 
    68    but again, only committee writable.  This is actually just in order 
    69    to keep spam off of the wiki.  If you want an account, please email 
    70    Isaac Jones <[email protected]>. 
     69 * A wiki / issue tracking system to document consensus and to track 
     70   ongoing tasks.  This system is publicly readable, but only 
     71   committee writable so that we may present it as the "official" 
     72   output of the committee.  If you ever feel that the wiki is not 
     73   accurate as to the consensus, please alert the committee! 
    7275   FIX: See [ticket:12 ticket on wiki guidlines]. 
    7477 * A darcs code repository for experiments, proposed libraries,and 
    7578   complex examples.  darcs is a decentralized system, so anyone can use 
    76    it, but patches should be sent to Isaac Jones. 
     79   it, but patches should be sent to Isaac Jones: