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

FYI: Related effort: haskell-pkg-janitors #4

Open
andreasabel opened this issue May 10, 2023 · 1 comment
Open

FYI: Related effort: haskell-pkg-janitors #4

andreasabel opened this issue May 10, 2023 · 1 comment

Comments

@andreasabel
Copy link

Hi @haskell-github-trust,
seems like you are doing something analogous to @haskell-pkg-janitors and @haskell-party. I like these communal efforts, removing hindrance to maintenance. @haskell-pkg-janitors is quite old, but after its foundation not much happened. Recently, I started an effort to renew it:

Maybe we can link to each others organisations...

@jamesdbrock
Copy link
Member

Hi @andreasabel thanks for the note! Yes I'm aware of those orgs and I link to them https://github.com/haskell-github-trust#other-organizations

It's terrible that there are now three orgs like this. There should be one. I don't want to start a new org. Let's try to combine our efforts.

haskell-pkg-janitors

Here are the problems with haskell-pkg-janitors:

  1. It has no members.
  2. There is no way to join the org.
  3. There is no way to publish packages from the org.
  4. The name. Sorry. I'm still maintaining my packages and I don't want to put them in an org that makes it sound like they're discarded rubbish.

Are you sure that this a good approach for renewal?

to renew this organization, archive dead projects and prune inactive members.

I suggest that to renew haskell-pkg-janitors, a better approach would be a promiscuous invitation campaign for new members.

Due, I assume, to those problems, haskell-party was started.

haskell-party

Here are the problems with haskell-party:

  1. It has no members.
  2. There is no way to join the org. Nothing has happened for a year. I begged to join the org two months ago in multiple forums.
  3. The proposal has too many permission layers of “board member,” “stewards,“ “admins,” et cetera.

haskell-github-trust

All members are Owners and have permission to do everything, including delete the whole org. This org is trust-based instead of permission-based. Maybe this will result in spectacular failure? I want to try it this way since the other ways don't seem to be thriving. I sent you an Ownership invite.

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