New CLC proposal process

[Andrew Lelechenko]

As https://github.com/haskell/core-libraries-committee/blob/main/README.md <https://github.com/haskell/core-libraries-committee/blob/main/README.md> says, CLC owns, but does not maintain core libraries as long as they are kept in order by appointed maintainers. If you find a core library abandoned and neglected, raise an issue with CLC.

Otherwise proposals affecting core libraries should be discussed with respective maintainers first. They can seek CLC opinion on controversial changes, but are not obliged to. 

I suppose HF Tech Track could be a helpful body to ask a non-binding opinion on changes with a wider scope.

Best regards,
Andrew

> On 31 Oct 2021, at 00:08, Julian Ospald <hasufell at posteo.de> wrote:
> 
> Do I understand correctly that the CLC only governs base now?
> 
> If not, where does one raise other issues that potentially affect core libraries?
> 
> On October 30, 2021 8:13:18 PM UTC, Andrew Lelechenko <andrew.lelechenko at gmail.com> wrote:
> I'm happy to announce that Core Libraries Committee has completed post-election reboot and now has a new home at https://github.com/haskell/core-libraries-committee <https://github.com/haskell/core-libraries-committee> and a new GitHub-based process: https://github.com/haskell/core-libraries-committee/blob/main/PROPOSALS.md <https://github.com/haskell/core-libraries-committee/blob/main/PROPOSALS.md>.
> 
> From now on proposals to change base should be raised as GitHub issues instead of emails to libraries at .
> 
> Best regards,
> Andrew

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211031/1bb95d4c/attachment.html>