Re: Proposal: Change to library proposal process

On 5 January 2011 13:01, Johan Tibell wrote:

On Wed, Jan 5, 2011 at 1:53 PM, Duncan Coutts wrote:

...

At the moment I think we too often refer changes to the libs review process when they don't change an API and it would be fine for some suitable individual to review the patch and apply directly. So, yes I agree we should have maintainers (individuals or teams) for the core libs, but that API additions/changes should still go through a community API review process. The maintainers can help contributors with that process, indeed if the maintainer thinks the change is sensible they could lead that process themselves.

I don't think anyone would be willing to be a maintainer under those conditions. Any volunteers?

Really? There are several people who quite often make direct changes to base and containers including Simon, Ian, Ross and Malcolm. There are several other libs that have maintainers but where any substantive API change would also effectively require some community review and consensus, for example I don't expect Don and I could get away with making big changes to the bytestring API. Duncan