Proposal: Change to library proposal process

Simon Peyton-Jones simonpj at
Thu Jan 6 14:52:52 CET 2011

| The changes being proposed by Greg and Johan, as I understand it, would
| amount to the following.  I'm willing to give it a try; we can always go
| back if it doesn't work out.
|   - maintainers are empowered to make API changes.
|   - no formal review process for API changes, although there is an
|     expectation that non-trivial changes would still be discussed on
|     the list beforehand.
|   - we would still have a clearly documented path for contributions
|     and proposals
|   - commit messages are copied to the list, and should
|     detail API changes sufficiently that the community
|     can keep an eye on what is happening and comment.
|   - we get more maintainers (presumably they'll just appear, or
|     something? :-)

To which we might add:

    - only maintainers commit patches

    - each library, especially including the core libraries, has a named 
      maintainer (or a small number of same)

I'd be ok with this. 


More information about the Libraries mailing list