New Libraries Proposal process

[Carter Schonwald]

Where was this discussed or proposed? All libraries process needs to start
on the libraries mailing list. And soemtimes Perhaps moving to clc list for
resolving tie breaking on controversial choices.

The libraries archive goes back pretty far and email threading seems to
scale far better for participating in complex discussions than does githubs
comment collapsing on large discussions.

On Fri, Sep 11, 2020 at 3:20 PM chessai <chessai1996 at gmail.com> wrote:

> All,
>
>
> There is a new Libraries Proposal process, inspired by the GHC Proposals
> process.
>
> Core Library APIs are critical. It's easy for a sensible proposal to
> languish or simply get dropped on the floor; and (in the other direction) a
> bit too easy for a proposal to make it into the core libraries without
> receiving the scrutiny it deserves. Most of the proposals that have been
> made on this mailing list, become lost to the archives. It's not easy for
> anyone to answer the question "what decisions has the CLC made recently?"
> without trawling a huge email archive.
>
> Of course, this is mostly for breaking changes or "big" introductions; we
> don't need a full proposal over something tiny, e.g. "a module from vector
> is missing a fold". That would be more appropriate on vector's issue
> tracker, and left to the maintainers to deal with.
>
> I encourage anyone interested to get started by reading the README at
> https://github.com/haskell-core/core-libraries-proposals.
>
>
>
> _______________________________________________
>
> Libraries mailing list
>
> Libraries at haskell.org
>
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20200911/5cefc2b9/attachment.html>