haskell/stackage
1
0
Fork 0
mirror of https://github.com/commercialhaskell/stackage.git synced 2026-01-22 12:11:56 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Updated Maintainers Agreement (markdown)

snoyberg 2014-10-29 04:16:22 -07:00
parent 20e1067d41
commit 5b81691139
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Maintainers-Agreement.md

@ -7,13 +7,14 @@ This Wiki page is meant to foster discussion of what such a social contract woul
Getting your package included in Stackage is simple:
* Create a fork on Github.
* Add your packages to Stackage.Config.
* Try to build; if this fails due to your packages, fix those failures.
* Once everything builds correctly, commit and send a pull request to this repo.
* Add your packages to Stackage.Config, following the format of other contributors.
* Commit and send a pull request.
Previously, we recommended trying to build the Stackage set yourself before sending a pull request. That's no longer necessary. Just send a pull request, and if there's a problem, the maintainer (currently: Michael Snoyman) will let you know.
Unlike the Haskell Platform, Stackage does not place quality requirements on packages. In theory, any package that compiles will be accepted to the Stackage package set. However, the maintainer must agree to follow the social contract spelled out in this document.
Note: while it's highly encouraged that the actual package maintainer is also the Stackage maintainer, this is not necessary.
Note: while it's highly encouraged that the actual package maintainer is also the Stackage maintainer, this is not necessary. You do not even need the package maintainer's approval to submit to Stackage, though it's a good idea to drop him/her a note.
## Upper bounds