You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment @garyb and I are de facto maintainers for most of the PureScript Contributors libraries. Few of those libraries meet the minimum library requirements for documentation, tests, or curated issue trackers. Maintaining 40+ libraries here along with the libraries we maintain in the Halogen organization, personally, or that Gary helps maintain in the PureScript organization is not possible at the level of quality these libraries deserve.
Once things like #1 are taken care of and I've had a chance to do the scaffolding for all the libraries in the organization, I think it might be useful to do an 'adoption drive' for a selection of the Contributor libraries. Essentially, we'd select eligible libraries, clean them up as much as possible, and then make a post on Discourse asking if new maintainers are interested ("Your chance to join the Contributors org!")
The new maintainers would be expected to meet the maintainers' expectations, and to put in a good faith effort, but they wouldn't be permanently tied to the library. Any Contributors maintainer should be able to step down at any time if they need to.
This might help us locate a few new maintainers for libraries in this organization that are being used but don't have someone who uses the library currently maintaining it.
The text was updated successfully, but these errors were encountered:
At the moment @garyb and I are de facto maintainers for most of the PureScript Contributors libraries. Few of those libraries meet the minimum library requirements for documentation, tests, or curated issue trackers. Maintaining 40+ libraries here along with the libraries we maintain in the Halogen organization, personally, or that Gary helps maintain in the PureScript organization is not possible at the level of quality these libraries deserve.
Once things like #1 are taken care of and I've had a chance to do the scaffolding for all the libraries in the organization, I think it might be useful to do an 'adoption drive' for a selection of the Contributor libraries. Essentially, we'd select eligible libraries, clean them up as much as possible, and then make a post on Discourse asking if new maintainers are interested ("Your chance to join the Contributors org!")
The new maintainers would be expected to meet the maintainers' expectations, and to put in a good faith effort, but they wouldn't be permanently tied to the library. Any Contributors maintainer should be able to step down at any time if they need to.
This might help us locate a few new maintainers for libraries in this organization that are being used but don't have someone who uses the library currently maintaining it.
The text was updated successfully, but these errors were encountered: