Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rationalise or describe maintainership structure of haskellfoundation on GitHub #113

Open
tomjaguarpaw opened this issue Aug 27, 2021 · 1 comment

Comments

@tomjaguarpaw
Copy link
Contributor

NB: This issue relates to the maintainership structure of the Haskell Foundation GitHub organisation not the website. However, there doesn't seem to be a place to file issues about the organisation itself so I'm choosing this as the best alternative. (If there is such a place please let me know and I'll migrate the issue there.)

I see a couple of issues that would be helpful to address:

  1. There is nowhere to file issues about the organisation itself. Perhaps a repo could be created for this pupose.
  2. The Haskell Foundation Github organisation people list mentions Emily and Evan Relf and no one else. It would be good to rationalise this somewhat. In particular it would be helpful
    1. to coherently determine who needs, or could helpfully hold, exactly what permissions and make sure that they have them (and that no one else has them), and
    2. to document this decision clearly somewhere (perhaps on the repo mentioned in 1)
@goldfirere
Copy link
Contributor

Thanks for bringing this up. It turns out that there are more than 2 members of the org -- but the other 19 members are "private", meaning that non-members (such as @tomjaguarpaw) won't see them listed.

Looking at the membership page, it seems that most of these are additionally members of Teams (https://github.com/orgs/haskellfoundation/teams), useful for organizing HF projects. Currently, there are Teams for School of Haskell (repo: https://github.com/haskellfoundation/HaskellSchool) and for the Matchmaker project (repo: https://github.com/haskellfoundation/matchmaker).

This makes sense to me, but I agree that this should be described somewhere -- and (critically) with information about how individuals can join a team.

I personally don't see the need to create a new repo for meta-level issues, as these will hopefully be few. If we do need a place for such issues, I recommend using https://gitlab.haskell.org/hf/meta/-/issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants