-
-
Notifications
You must be signed in to change notification settings - Fork 476
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
Support for "organization" (shared access) accounts #461
Comments
+1 |
1 similar comment
+1 |
👍 It's a shame that a 1 year old issue hasn't even been addressed. |
Then go address it. |
Wow, I never thought of that. But maybe, just maybe, I meant that no one from the core team even had the time to tag or close the issue as won't implement. |
There you go. |
+1 for this or supporting GitHub's organizations. As for now, we have GitHub organization with two users but only one can use the organization vendor name. |
@timiwahalahti add the second user as maintainer on one of the existing package using this vendor name, and they will be able to use it for other packages (this is how vendor name restrictions work) |
@stof thanks for pointing that out! <3 I think that's enough and organization accounts in packagist isn't needed. But this should be documented, because right now there really isn't any instructions about vendor name restrictions. |
Organization support is still a good idea IMO. I would like to do a POC of that when I'll get more time. |
+1 |
It would be very nice if the MediaWiki user account (https://packagist.org/users/mediawiki/) allowed multiple individual users to be granted management rights rather than requiring shared password access. I'm thinking of something more like GitHub organizations (eg https://github.com/wikimedia/) than the current user account system. This might actually fit nicely with the functionality for namespace reservation requested in #163.
The text was updated successfully, but these errors were encountered: