Open andreasabel opened 1 year ago
Please, let me know if I can help anyhow. I'm fine with public membership.
Maybe we should come up with a standard for this org. E.g. adding Haskell-CI to every project sounds like a good janitorial task...
I suggest also doing something about the first half of https://github.com/orgs/haskell-pkg-janitors/discussions/3
I like to renew this organization, archive dead projects and prune inactive members. First, taking stock:
We got some new projects recently:
One old project is actively maintained:
Project that haven't seen activity recently:
Projects that haven't seen activity in more than a decade:
https://github.com/haskell-pkg-janitors/vacuum transferred by @kfish This package has been maintained from https://github.com/thoughtpolice/vacuum and is now archived there. It hasn't seen any maintenance by @haskell-pkg-janitors, as witnessed by the diff: https://github.com/kfish/vacuum/compare/master...haskell-pkg-janitors:vacuum:master
https://github.com/haskell-pkg-janitors/feed @simonmichael contributed some commits on 2012-01-13, but maintenance has continued at https://github.com/haskell-party/feed
https://github.com/haskell-pkg-janitors/rss @basvandijk (2011-2012): This project is actually maintained at its original fork https://github.com/haskell-hvr/rss
I am pruning everyone that hasn't been active in a full decade.
Should you be interested in contributing in the near future and be (re-)added to this project, please let me know, and state your contribution plans (e.g. co-/fallback maintainer for X, hosting new package Y).
Membership will be public only (for accountability).
While this organization is small: Members have write access to any project, but should respect active maintainers.