Haskell Prime: Ticket Query
http://ghc.haskell.org/trac/haskellprime/query?status=closed&col=id&col=resolution&col=summary&col=owner&col=reporter&order=owner
Haskell PrimeenUSHaskell Prime/images/HaskellLogo_2.jpg
http://ghc.haskell.org/trac/haskellprime/query?status=closed&col=id&col=resolution&col=summary&col=owner&col=reporter&order=owner
Trac 1.0.1
http://ghc.haskell.org/trac/haskellprime/ticket/130
http://ghc.haskell.org/trac/haskellprime/ticket/130#130: NoNPlusKPatternsSat, 25 Jul 2009 00:44:02 GMTigloo<p>
Proposal: <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/NoNPlusKPatterns">NoNPlusKPatterns</a>.
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/130#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/132
http://ghc.haskell.org/trac/haskellprime/ticket/132#132: StricterLabelledFieldSyntaxSun, 26 Jul 2009 00:03:04 GMTigloo<p>
Proposal: <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/StricterLabelledFieldSyntax">StricterLabelledFieldSyntax</a>
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/132#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/7
http://ghc.haskell.org/trac/haskellprime/ticket/7#7: for each extension, fulfill criteriaFri, 11 Nov 2005 23:29:51 GMTijones<p>
This ticket should be fleshed out once we defined the criteria for inclusion of extensions. Break into subtasks, for instance have a define task and an implement task for each extension.
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/7#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/8
http://ghc.haskell.org/trac/haskellprime/ticket/8#8: brainstorm design space to build concrete informationSat, 26 Nov 2005 01:05:03 GMTijones<p>
Gather basic concrete information about <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/HaskellExtensions">HaskellExtensions</a>, <a class="missing wiki">HaskellLibraries?</a>, and backward compatibility in order to inform a discussion about the scope of the committee.
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/8#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/9
http://ghc.haskell.org/trac/haskellprime/ticket/9#9: craft Haskell' announcementSat, 26 Nov 2005 01:07:20 GMTijones<p>
The announcement was on <a class="extlink" href="http://www.haskell.org//pipermail/haskellcafe/2006January/014036.html"><span class="icon"></span>haskell cafe</a>, haskell, and comp.lang.functional.
</p>
<h2 id="FinalDraft">Final Draft</h2>
<p>
Subject: Haskell': Kicking off the process of defining the next Haskell standard.
</p>
<p>
let haskell' = succ haskell98 in
</p>
<p>
Announcing the Haskell' ("HaskellPrime") process. A short time ago,
I asked for volunteers to help with the next Haskell standard. A
brave group has spoken up, and we've organized ourselves into a
committee in order to coordinate the community's work. It will be the
committee's task to bring together the very best ideas and work of the
broader community in an "opensource" way, and to fill in any gaps in
order to make Haskell' as coherent and elegant as Haskell 98.
</p>
<p>
Our task is broadly defined by our mission statement:
</p>
<blockquote>
<p>
The Haskell programming language is moreorless 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.
</p>
</blockquote>
<blockquote>
<p>
Haskell' will be a conservative refinement of Haskell 98. It will
be the work of this committee to adopt a set of language
extensions and modifications and to standardize a new set of
libraries.
</p>
</blockquote>
<blockquote>
<p>
We will strive to only include triedandtrue language features,
and to define them at least as rigorously as Haskell 98 was
defined. This standard will reflect the realities of developing
practical applications in the Haskell language. We will work closely
with the rest of the Haskell community to create this standard.
</p>
</blockquote>
<p>
Your Haskell' Committee is as follows (slightly munged email addresses
follow):
</p>
<ul><li>Manuel M T Chakravarty <chak at cse.unsw.edu.au>
</li><li>John Goerzen <jgoerzen at complete.org>
</li><li>Bastiaan Heeren <bastiaan at cs.uu.nl>
</li><li>Isaac Jones <ijones at galois.com>
</li><li>John Launchbury <john at galois.com>
</li><li>Andres Loeh <loeh at iai.unibonn.de>
</li><li>Simon Marlow <simonmar at microsoft.com>
</li><li>John Meacham <john at repetae.net>
</li><li>Ravi Nanavati <ravi at bluespec.com>
</li><li>Henrik Nilsson <nhn at cs.nott.ac.uk>
</li><li>Ross Paterson <ross at soi.city.ac.uk>
</li><li>Simon PeytonJones <simonpj at microsoft.com>
</li><li>Don Stewart <dons at cse.unsw.edu.au>
</li><li>Audrey Tang <autrijus at gmail.com>
</li><li>Simon J. Thompson <S.J.Thompson at kent.ac.uk>
</li><li>Malcolm Wallace <Malcolm.Wallace at cs.york.ac.uk>
</li><li>Stephanie Weirich <sweirich at cis.upenn.edu>
</li></ul><p>
The editors are Isaac Jones and John Launchbury.
</p>
<p>
Feel free to contact any of us with any concerns or questions. If you
don't know who to direct your questions to, email Isaac Jones
ijones@….
</p>
<p>
Community involvement is vital to our task, and there will be a way
for members of the community to make formal proposals. In the opening
phases, please use these more informal resources to help us coordinate
Haskell':
</p>
<ul><li>The haskellprime 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.
<a class="extlink" href="http://haskell.org/mailman/listinfo/haskellprime"><span class="icon"></span>http://haskell.org/mailman/listinfo/haskellprime</a>
</li></ul><ul><li>A wiki / issue tracking system to document consensus and to track
ongoing tasks. 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 committee!
<a class="extlink" href="http://hackage.haskell.org/trac/haskellprime"><span class="icon"></span>http://hackage.haskell.org/trac/haskellprime</a>
</li></ul><ul><li>A darcs code 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:
<a class="extlink" href="http://hackage.haskell.org/trac/haskellprime/wiki/SourceCode"><span class="icon"></span>http://hackage.haskell.org/trac/haskellprime/wiki/SourceCode</a>
</li></ul><p>
Please join us in making Haskell' a success.
</p>
<p>
your,
</p>
<blockquote>
<p>
Haskell' Committee
</p>
</blockquote>
<p>
p.s. Please feel free to forward this announcement to appropriate forums.
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/9#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/10
http://ghc.haskell.org/trac/haskellprime/ticket/10#10: finalize mission statementSat, 26 Nov 2005 01:09:15 GMTijones<p>
Finalize a <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/MissionStatement">MissionStatement</a>. Details may have to be worked out in future iterations.
</p>
<p>
The current mission statement may be OK for the committee, but it lacks background that the "general public" would be interested in. We should state the problem we're trying to solve and for the sake of who. That's the <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/PublicMissionStatement">PublicMissionStatement</a> and <a class="closed ticket" href="http://ghc.haskell.org/trac/haskellprime/ticket/75" title="task: create public mission statement (closed: fixed)">75</a>.
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/10#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/11
http://ghc.haskell.org/trac/haskellprime/ticket/11#11: initiate discussion on refining scope of committeeThu, 01 Dec 2005 20:05:53 GMTijones<p>
Currently we are <a class="closed ticket" href="http://ghc.haskell.org/trac/haskellprime/ticket/8" title="task: brainstorm design space to build concrete information (closed: fixed)">brainstorming</a> but we will soon need to start to narrow the scope. Open tickets related to that are listed under the "Scope Defined" <a class="report" href="http://ghc.haskell.org/trac/haskellprime/report/3">milestone</a>. Here are some suggestions from Henrik about how to have this discussion:
</p>
<p>
... Here are some concrete points that could be discussed:
</p>
<ol><li>What should the time frame for the Haskell' effort be?
</li><li>Who are the users, what are their perceived needs, and how
do we prioritize?
</li><li>Informed by 1 and 2, is Haskell' mainly a consolidation effort,
or should the scope be wider?
</li><li>Informed by all of the above, is it possible to agree on
some basic criteria that extensions and changes would have
to meet in order to somewhat bound the size of the part
of the design space that needs to be explored?
</li></ol>Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/11#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/40
http://ghc.haskell.org/trac/haskellprime/ticket/40#40: add proposal(s) / flesh out info about the followingFri, 16 Dec 2005 23:38:03 GMTijones<p>
The following either have no info, unclear info, or no clear proposal. As these are fleshed out, please remove from list by editing this bug:
</p>
<ul><li><a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/IncoherentInstances">IncoherentInstances</a>
</li><li><a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/LibraryVersioning">LibraryVersioning</a>
</li><li><a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/NewLibraryCandidates">NewLibraryCandidates</a>
</li><li><a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/PartialTypeSigs">PartialTypeSigs</a>
</li></ul>Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/40#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/46
http://ghc.haskell.org/trac/haskellprime/ticket/46#46: double check that all MinorFixes are listed as proposals, and minorFri, 16 Dec 2005 23:48:41 GMTijones<p>
see <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/MinorFixes">MinorFixes</a>.
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/46#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/75
http://ghc.haskell.org/trac/haskellprime/ticket/75#75: create public mission statementFri, 06 Jan 2006 23:42:34 GMTijones<p>
Resolution: Just added intro to the <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/MissionStatement">MissionStatement</a>.
</p>
<p>
See <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/PublicMissionStatement">PublicMissionStatement</a>. The committee has a <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/MissionStatement">MissionStatement</a>, but it lacks some background. The background is obvious to committee members, but we need a more public statement which includes this background, and perhaps links to Haskell and such. That's <a class="closed ticket" href="http://ghc.haskell.org/trac/haskellprime/ticket/75" title="task: create public mission statement (closed: fixed)">75</a>.
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/75#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/83
http://ghc.haskell.org/trac/haskellprime/ticket/83#83: update CreateProposal to include general guidelinesTue, 31 Jan 2006 17:36:29 GMTijones<p>
see <a class="wiki" href="http://ghc.haskell.org/trac/haskellprime/wiki/CreateProposal">CreateProposal</a>. Include guidelines for the community making tickets. My related email below:
</p>
<pre class="wiki">
 = Some Guidelines =

 Use the mailing list for _discussion_ and to reach a consensus. Use
 the tickets to _document_ the consensus as a proposal. 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.

 It is just fine to have conflicting points of view in a ticket, but no
 backandforth discussion (use the mailing list for that). Create
 "pros" and "cons" sections in the ticket. Edit the ticket rather than
 adding "comments". Link this ticket with wiki pages or other tickets
 which are related, or for which this is a counterproposal.

 Be sure to set the "component" field as "Proposal" and leave the Adopt
 field alone.

 = Example =

 So for instance, there's a proposal that we modify the comment syntax.
 After some time for discussion on the list, Thomas (cc'd) should
 create a new ticket if he still believes in his 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.
</pre>Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/83#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/93
http://ghc.haskell.org/trac/haskellprime/ticket/93#93: bring together various classrelated tickets into something coherentTue, 14 Feb 2006 17:39:08 GMTijones<p>
see <a class="query" href="http://ghc.haskell.org/trac/haskellprime/query?component=Proposal&summary=%7Eclass&summary=%7Einstance">this query</a>.
</p>
<p>
Which proposals should be grouped together? What are the most important ones? What are their use cases, and can they be covered by different proposals?
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/93#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/12
http://ghc.haskell.org/trac/haskellprime/ticket/12#12: write public guidelines for wiki editingThu, 01 Dec 2005 21:55:47 GMTijones<p>
Closed by creation of <a class="missing wiki">CoordinationTools?</a>.
</p>
<p>
See also the descriptions of various resources from the <a class="closed ticket" href="http://ghc.haskell.org/trac/haskellprime/ticket/9" title="task: craft Haskell' announcement (closed: fixed)">public announcement draft</a>. Guidelines may include:
</p>
<ul><li>Discussion happens on the mailing lists (haskellprime, haskellcafe)
</li><li>Organization of ideas happens in the wiki (no backandforth discussion)
<ul><li>flesh this out more?
</li></ul></li><li>Issues or things to be decided on are tracked with tickets
</li><li>Experiments to source code happen in the code repository
</li></ul>Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/12#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/1
http://ghc.haskell.org/trac/haskellprime/ticket/1#1: define community feedback processFri, 11 Nov 2005 22:57:25 GMTijonesResultshttp://ghc.haskell.org/trac/haskellprime/ticket/1#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/2
http://ghc.haskell.org/trac/haskellprime/ticket/2#2: decide on infrastructure privacy / secrecy policiesFri, 11 Nov 2005 22:58:15 GMTijones<h2 id="InitialProposal">Initial Proposal</h2>
<ul><li>A private mailing list (haskellprimeprivate)
<ol><li>committee only subscription (and archive)
</li><li>unmoderated for committee members
</li></ol></li></ul><ul><li>A public mailing list  (haskelprime) for technical discussion
<ol><li>publicly available for subscriptions (and archive)
</li><li>unmoderated for committee members
</li><li>moderated for noncommittee members, in order to keep traffic low. I feel that if a major flamewar NEEDS to happen, it can happen on haskellcafe.
</li></ol></li></ul><ul><li>A wiki / issue tracking system <a class="extlink" href="http://haskell.galois.com/cgibin/haskellprime/trac.cgi/wiki"><span class="icon"></span>http://haskell.galois.com/cgibin/haskellprime/trac.cgi/wiki</a>
<ol><li>publicly readable
</li><li>committee writable
</li><li>folks who ask for an account will get one (and lose it if they're abusive). the main reason for not letting the wiki be worldwritable is spam.
</li></ol></li></ul><ul><li>A code repository
<ol><li>publicly readable
</li><li>anyone can submit changes, Isaac will be gatekeeper. We'll use darcs, so this is pretty easy. That's more of a technical issue than a policy one, since there isn't a machine that we all have accounts on.
</li></ol></li></ul>Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/2#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/3
http://ghc.haskell.org/trac/haskellprime/ticket/3#3: define criteria for including extensionsFri, 11 Nov 2005 23:00:45 GMTijones<p>
Formally specified? nyearsold? used in various libraries? See thread for discussion "officially opening the discussion on scope"
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/3#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/4
http://ghc.haskell.org/trac/haskellprime/ticket/4#4: define criteria for including librariesFri, 11 Nov 2005 23:01:14 GMTijones<p>
Do we want to do an entire library standard?
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/4#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/5
http://ghc.haskell.org/trac/haskellprime/ticket/5#5: define policy on backward compatibilityFri, 11 Nov 2005 23:01:41 GMTijonesResultshttp://ghc.haskell.org/trac/haskellprime/ticket/5#changelog
http://ghc.haskell.org/trac/haskellprime/ticket/6
http://ghc.haskell.org/trac/haskellprime/ticket/6#6: release of compilers with HaskellPrime modeFri, 11 Nov 2005 23:08:31 GMTijones<p>
Such a compiler will implement all of the extensions and include the libraries.
</p>
<p>
May break this tickets into subtickets for each compiler.
</p>
Resultshttp://ghc.haskell.org/trac/haskellprime/ticket/6#changelog