Difference between revisions of "Haskell Platform"

Revision as of 14:34, 11 August 2014

The Haskell Platform is a single, standard Haskell development environment for everyone. It offers a set of blessed libraries and tools, to save you the task of picking and choosing which core Haskell libraries to use.

Learn more about the Haskell Platform ⇒

What's in the platform

See the official Haskell Platform Changelog.

Trouble shooting

Report bugs on GitHub: Haskell Platform Issues.

Developers

New Haskell Platform Wiki
Old Trac wiki

Buttons

We have some buttons to let your friends know about the Haskell Platform.

Use this html in your site:

<a href="http://haskell.org/platform"> <img src="http://raw.githubusercontent.com/haskell/haskell-platform/master/website/icons/button-100.png"></a>

Use this html in your site:

<a href="http://hackage.haskell.org/platform"> <img src="http://raw.githubusercontent.com/haskell/haskell-platform/master/website/icons/button-64.png"></a>

SVG source for the button: http://haskell.org/haskellwiki/Image:Button.svg

Icons

Icons for the platform installer and desktop.

Legal

The cherry blossom image used in the 2011 HP release is licensed CC by tanakawho

@@ Line 1: / Line 1: @@
+{{HP}}
-'''Haskell: Batteries Included'''
+The Haskell Platform is a single, standard [[Haskell]] development environment for everyone. It offers a set of blessed libraries and tools, to save you the task of picking and choosing which core Haskell libraries to use.
-__NOTOC__
+[http://haskell.org/platform/contents.html Learn more about the Haskell Platform ⇒]
-The Haskell Platform (HP) is the name of a new "blessed" library suite on which to build further Haskell libraries and applications, by taking the best libraries from the nearly 800 libraries of [http://hackage.haskell.org haskell.org]. It provides a comprehensive, stable and quality tested base for Haskell projects to work from.
+__TOC__
-[[Image:Small-package-bubbles.png|Libraries in the platform, with area based on number of libraries that depend on it]] [[Image:Haskell-graph.png|Graph of library dependencies. The platform is the center of the graph]]
-== Developers ==
+== What's in the platform ==
+See the official [http://www.haskell.org/platform/changelog.html Haskell Platform Changelog].
-Haskell Platform core team:
-* Duncan Coutts (Well Typed)
-* Don Stewart (Galois)
-== Resources ==
+== Trouble shooting ==
+Report bugs on GitHub:
-* [http://code.haskell.org/haskell-platform Haskell Platform project repository].
-* [http://trac.haskell.org/haskell-platform/ Project bug tracker]
+[https://github.com/haskell/haskell-platform/issues Haskell Platform Issues].
-== Documentation ==
+=== Developers ===
-* [http://cgi.cse.unsw.edu.au/~dons/blog/2008/07/29#batteries The Haskell Platform Proposal] for the 2008 Haskell Symposium
-* [http://blog.well-typed.com/2008/09/slides-from-the-haskell-platform-talk/ Slides from the Haskell Platform talk]
-* [http://blog.well-typed.com/2008/09/hackage-hacking-and-demo/ Haskell Platform discussion]
-* Bryan O'Sullivan's [http://www.serpentine.com/blog/2008/09/26/some-notes-on-the-future-of-haskell-and-fp/ writeup] of the future of Haskell discussion
-* [http://thread.gmane.org/gmane.comp.lang.haskell.cvs.ghc/28062/focus=28807 A discussion] took place in June and July 2008 about the direction of the HLP.
-* [http://haskell.org/~duncan/ghc/%23ghc-2008-07-16.log More occurred during the #ghc meeting]
+* New [https://github.com/haskell/haskell-platform/wiki/ Haskell Platform Wiki]
-===Quality Control===
+* Old [http://trac.haskell.org/haskell-platform/ Trac wiki]
+== Buttons ==
-Inclusion or exclusion in the platform will be drive by metrics, objective measurements we can extract from code. Determining appropriate metrics is a milestone.
+We have some buttons to let your friends know about the Haskell Platform.
-* cabal-installable libraries with haddocks.
-* The set of HP packages + core libs must be closed. That is all haskell dependencies must be from within the HP packages or core libs. Dependencies on C libs can be external.
-* All packages in a particular HP version must have a consistent install plan.
+[http://haskell.org/platform http://raw.githubusercontent.com/haskell/haskell-platform/master/website/icons/button-100.png]
-That means only one version of each package and all dependencies on packages must be satisfied by the version in the HP package set.
+Use this html in your site:
-There is code in cabal-install to check the last two requirements.
+<code>
-Other possible ideas for quality standards we might want to require:
+<nowiki>
+<a href="http://haskell.org/platform">
+<img src="http://raw.githubusercontent.com/haskell/haskell-platform/master/website/icons/button-100.png"></a>
+</nowiki>
+</code>
+[http://haskell.org/platform http://raw.githubusercontent.com/haskell/haskell-platform/master/website/icons/button-64.png]
-* Uses base library types, to force API standardisation
-* exposed module names must follow the hierarchical module name convention, meaning they must be in an appropriate place in the module namespace. In particular, no clash of module names should occur within the HP.
+Use this html in your site:
-=== Glue layers ===
+<code>
-Unlike the OCaml Batteries proposal, there will be no new glue layer to combine libraries, instead, we rely on the large base library to provide the standard interface types.
+<nowiki>
+<a href="http://hackage.haskell.org/platform">
+<img src="http://raw.githubusercontent.com/haskell/haskell-platform/master/website/icons/button-64.png"></a>
+</nowiki>
+</code>
+SVG source for the button: http://haskell.org/haskellwiki/Image:Button.svg
-As addition to the platform is a social process, we can use this as a hurdle to require base library conformance for new libraries to be admitted. If a library reinvents, for example, a time format, or an exception handling mechanism, the platform process will force standardisation on the base API before admition can proceed.
-=== Other heuristics ===
+=== Icons ===
-Packages set for inclusion should:
+Icons for the platform installer and desktop.
-* Have a maintainer
-* Have a bug tracker
-* Use the correct versioning
-* Build with cabal
-* Work on all arches.
+[[Image:Platform-100.png]]
-Further goals:
+[[Image:Platform-64.png]]
-* -Wall clean
-* 100% coverage
-* Have real world use.
-* Answer a notable set of build dependencies.
-== Distribution format ==
+=== Legal ===
-* Source distribution
-* .tar.gz bundle compatible with extra-libs
-* Windows Installed
-* Native distro packages
+* The cherry blossom image used in the 2011 HP release is [http://www.flickr.com/photos/28481088@N00/3291086383/ licensed CC by tanakawho]
-The HP will be the first '''meta-package''' on hackage, that depends on the platform library set. With this,
-    cabal install haskell-platform
+[[Category:HaskellPlatform]]
-will be possible.
-== Version policy ==
-yyyy.major.minor,
-* odd major numbers indicate unstable branches
-* minor numbers indicate bug fixes only, no API changes.
-Examples:
-* 2008.0.0 -- first biannual major stable release
-* 2008.0.1 -- minor release, bug fix only
-* 2008.1   -- unstable branch leading to next major release
-* 2008.2.0 -- second annual major release, API changes
-* 2008.2.1 -- bug fixes
-* 2008.3   -- unstable branch of 2008
-* 2009.0.0 -- first release in 2009.
-== Related ==
-* [http://docs.python.org/lib/lib.html Python libraries]
-* [http://live.gnome.org/ReleasePlanning Gnome's release process]
-* [http://live.gnome.org/ReleasePlanning/ModuleProposing How to propose modules for GNOME]
-* [http://dutherenverseauborddelatable.wordpress.com/2008/08/29/ocaml-batteries-included-release-0-where-it-should-all-have-begun/ OCaml Batteries]
-[[Category:Community]]