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

Stronger owner controls #48

Closed
huonw opened this issue Nov 21, 2014 · 2 comments
Closed

Stronger owner controls #48

huonw opened this issue Nov 21, 2014 · 2 comments
Labels
A-accounts C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works

Comments

@huonw
Copy link
Member

huonw commented Nov 21, 2014

Currently any owner can add and (more dangerously) remove any other one, which is open for abuse; e.g. add someone as an owner, have a falling out, and they can remove the main maintainer and squat the package name for themselves.

Possible improvements off the top of my head:

  • have a distinguished owner (the initial uploader by default) who cannot be removed as an owner by anyone but themselves and is in control of transferring distinguishedness to some other owner
  • keep a chronology of when owners were added, and owners can only be removed by people who have been owners longer (this is similar to the system reddit uses for moderators)
@lilyball
Copy link

How about just having a 2-level split of "owner" vs "maintainer". Owners can modify the owner list, whereas maintainers can just publish/yank versions.

@carols10cents carols10cents added C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works A-accounts labels Dec 15, 2016
@sgrif
Copy link
Contributor

sgrif commented Jan 24, 2019

Hey folks, this is definitely still something we'd like to see addressed. We discussed this issue during the issue triage meeting today, and we think this will need to go through an RFC for any significant changes to be accepted here. Right now we're cleaning out some of the older issues that haven't seen recent activity. Since this is one of those issues, I'm going to close this.

I would like to re-iterate that we do want to see improvements here, and anyone interested in working on this should definitely raise it at a team meeting, and we'd be happy to help someone draft an RFC if interested.

@sgrif sgrif closed this as completed Jan 24, 2019
Turbo87 pushed a commit that referenced this issue Dec 8, 2022
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Turbo87 added a commit that referenced this issue Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-accounts C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works
Projects
None yet
Development

No branches or pull requests

4 participants