Hackage trustee selection process

[Gershom B]

I agree there is no formal process for selecting trustees, and it would be good to codify one. Good point, David!

I do not think there should be terms — the post is intended to be purely administrative/technical, not one of oversight.

Here is the chain of command: Hackage trustees are delegated powers by hackage admins, who in turn serve under the oversight of the haskell.org committee. They are only supposed to act within their delegated authority, which is determined by the hackage admins in conjunction with the haskell.org committee. They do not form a “committee” or “subcommittee" with any sort of independent collective decision making, though of course they consult on particular technical issues (and thus there is no comparison with the CLC). Importantly, trustees do not set policy for hackage, though they may raise concerns or suggestions which decision-making bodies may consider.

Typically, when a new trustee has been proposed, they have been accepted on the basis of a consensus discussion. The “process” if there is an issue is that the hackage admins and haskell.org committee can act as necessary (up to and including removing trustees), because the trustees do not constitute an independent body, just people with some limited delegated rights on the hackage server.

Speaking of which, we could use more trustees if people want to volunteer. I warn you, it is very boring (but necessary).

-Gershom
On Jun 3, 2020, 6:16 PM -0400, 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/20200604/a1b227bb/attachment-0001.html>