Hackage trustee selection process

[Carter Schonwald]

This is a great idea! Or at least I’m in favor of exploring what that would
mean.

(I’ve a few other things on my plate this week and next from oss and work
perspectives, but in the face of it, it seems reasonable. )

I will note that because of how hackage is dependent on both resources
explicitly under the responsibility of the haskell dot org committee (the
domain name and some of the hosting infra ), it May in part be joint remit
with the dot org committee.  Clc does come into play for community
standards and best practices I suppose?

On Wed, Jun 3, 2020 at 6:16 PM David Feuer <david.feuer at gmail.com> wrote:

> At present, there is no process for selecting Hackage trustees, there are
> no designated terms for them, and there is no process for removing them.
> This strikes me as most unfortunate. We trust that these folks will manage
> Hackage for the benefit of the community, but there is no process the
> community can rely on for ensuring the right people have trustee powers.
> Can we fix this situation?
>
> A couple specific suggestions:
>
> 1. Perhaps the Hackage trustees can adopt organizational standards similar
> to those of the Core Library Committee to get things going quickly.
>
> 2. Perhaps the CLC should be able to designate a certain number of its own
> members as Hackage trustees.
> _______________________________________________
> 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/20200603/221831d0/attachment.html>