proposal: Few Curation, Automatic PR, Global CI

[rvion]

@paf31 Let's imagine that

• pursuit db is used as the the list of packages database (no specific curation for now, global db)

• purescript-package-db basically do:

  foreach topologically sorted puresuit packages
     pull latest package version 
     bower update all dependencies to latest version
     try to build
     if not successfull -> open a github issue(s) with build failure detail
     if successfull but declared constraint not uptodate -> open PR with constraint update
     if clever suggestion found -> open an issue or PR
  

  (bower has commands to update all deps to latests versions, or check if a package has out of date deps)

• purescript-package-db can tracks package quality: it checks the package level of documentation, number of warnings, etc. It could invite people to better document things, remove warning, etc in automatics PR

• purescript-package-db could produce a bower constraint file for all packages working well together (named like latest-2016-08-05). (same as stackage)

• on pursuit, we could show if

  • deps are out of date ( orange if it builds fine with dependencies version bump, red it it doesn't compile with after version bump)
  • number of warning
  • various quality stats

• IMO automatic PR automatically are much more useful than curation for now. purescript-package-db could invite package author to help fixing dependant packages breaking after an update, etc. Stackage is a good inspiration, but since purescript ecosystem is not so mature yet, this kind of global CI would help the package ecosystem to mature faster.

• without curation, no need for things like https://github.com/paf31/purescript-package-db/issues/3 right now

• purescript-package-db could prioritize open source effort based on download count, reverse dependencies, etc, and suggest volunteers specific packages to work on