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

Support for "organization" (shared access) accounts #461

Open
bd808 opened this issue Dec 5, 2014 · 11 comments
Open

Support for "organization" (shared access) accounts #461

bd808 opened this issue Dec 5, 2014 · 11 comments
Labels

Comments

@bd808
Copy link

bd808 commented Dec 5, 2014

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.

@Markcial
Copy link

Markcial commented Jul 6, 2015

+1

1 similar comment
@sdepablos
Copy link

+1

@LeeSaferite
Copy link

👍

It's a shame that a 1 year old issue hasn't even been addressed.

@alcohol
Copy link
Member

alcohol commented Dec 3, 2015

Then go address it.

@LeeSaferite
Copy link

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.

@alcohol alcohol added the Feature label Dec 3, 2015
@alcohol
Copy link
Member

alcohol commented Dec 3, 2015

There you go.

@timiwahalahti
Copy link

+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.

@stof
Copy link
Contributor

stof commented Jun 14, 2016

@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)

@timiwahalahti
Copy link

@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.

@soullivaneuh
Copy link
Contributor

Organization support is still a good idea IMO.

I would like to do a POC of that when I'll get more time.

@fdiasr
Copy link

fdiasr commented Jun 28, 2016

+1

@composer composer locked and limited conversation to collaborators Jun 28, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

9 participants