Perhaps I misunderstood the notion of "maintainer". To me that
signifies someone who makes decisions about API evolution. Indeed in
your original Discourse post[1] you suggested that the new
maintainer(s) would be deciding whether or not to merge API-changing
PRs such as adding genArray[2]. To my mind decisions like that should
be made by the CLC or other similar body.
So, if "maintainer" means "daily routine: updating for new GHC
versions, supporting test suite / benchmarks, releasing and
synchronising with GHC developers" then +1 to these volunteers.
Thanks!
If "maintainer" means "making API decisions on what is a critical
ecosystem package" then -1.
Tom
[1]
https://discourse.haskell.org/t/any-volunteers-to-maintain-array/5188
[2]
https://gitlab.haskell.org/ghc/packages/array/-/merge_requests/13
On Fri, Oct 21, 2022 at 08:32:39PM +0100, Andrew Lelechenko wrote:
> Tom, these are orthogonal questions. Even if we bring `array` under
> the same approval process as base, `array` still requires
> maintainers for daily routine: updating for new GHC versions,
> supporting test suite / benchmarks, releasing and synchronising with
> GHC developers. It’s unrealistic that CLC members will do this
> themselves.
>
> You are very welcome to raise a proposal to change the treatment of `array`.
>