@@ -8,6 +8,19 @@ The idea behind Stackage is that, if all packages work with the newest versions
9Packages in Stackage are not patched: all package changes occur upstream in Hackage.
9Packages in Stackage are not patched: all package changes occur upstream in Hackage.
11+## Github and Notifications
13+Stackage uses Github notifications to reduce overhead of contacting individual
14+package maintainers through various channels. As a package maintainer, you will
15+receive notifications for a number of reasons, package build failures of
16+different sorts, blockages and bounds issues, etc.
18+Please note, Github does some throttling on the number people that can be
19+notified within one issue. This means that on issues created with a large
20+number of packages affected, maintainers may not receive a notification. This
21+is not ideal, but Stackage is largely a manual process and done on a best
11## Adding a package
24## Adding a package
13Anyone can add any package to Stackage but you may only add packages under your own name. It's highly encouraged that the actual package maintainer is also the Stackage maintainer, if that is not the case you should drop the package maintainer a note first.
26Anyone can add any package to Stackage but you may only add packages under your own name. It's highly encouraged that the actual package maintainer is also the Stackage maintainer, if that is not the case you should drop the package maintainer a note first.