@@ -43,6 +43,21 @@ dependencies, you may send a pull request without testing first.
43You should also read the [maintainers
43You should also read the [maintainers
44agreement](https://github.com/fpco/stackage/wiki/Maintainers-Agreement).
44agreement](https://github.com/fpco/stackage/wiki/Maintainers-Agreement).
46+Package Author Guidelines
47+-------------------------
49+There are some basic rules to get your package to play nice with Stackage. Here
50+are some quick guidelines to hopefully make this easier:
52+* Make sure that your code is buildability and testable from Hackage. Often
53+ times, authors test their builds locally, but the tarball that gets uploaded
54+ to Hackage is missing some necessary files.
55+* Make your code compatible with the newest versions of all dependencies.
56+* Make your code compatible with the versions of libraries that ship with GHC ([more information on lenient lower bounds](https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
58+There are certainly many other tips that could be added here. If you think of
59+any, please send a pull request!
46Build the package set
61Build the package set
47---------------------
62---------------------