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

Vendor name reservation. #378

Closed
ADmad opened this issue Jan 28, 2014 · 3 comments
Closed

Vendor name reservation. #378

ADmad opened this issue Jan 28, 2014 · 3 comments

Comments

@ADmad
Copy link

ADmad commented Jan 28, 2014

packagist.org should reserve vendor name for matching github user / organisation. For eg. only the user "cakephp" should be allowed to add packages with vendor name "cakephp".

To highlight the problem cakephp/monolog is a package which has not been created by the CakePHP framework team. This can easily confuse a new / inexperienced user into thinking it's an official package.

@AD7six
Copy link

AD7six commented Jan 28, 2014

👍 to the overall idea of preventing anyone from deliberately or accidentally creating packages in other people/organization's namespace.

I think forcing author === github repo author (not sure if that's the suggestion, just wish to clarify) won't work, in part because:

  • the repository path doesn't necessarily have anything to do with the package name
  • authors may have several namespaces, or use a different namespace than their own account name
  • github is only one source of repos, git is only one possible VCS

This probably affects most frameworks e.g. symfony/sis-ejercicio-imagina wasn't created by symfony.

Any reservation logic would need to apply when creating or updating package info on packagist - i.e. here

@stof
Copy link
Contributor

stof commented Jan 28, 2014

duplicate of #163

@ADmad
Copy link
Author

ADmad commented Jan 28, 2014

I think forcing author === github repo author won't work, ....

@AD7six Right, it won't. It's just something that came to mind. Ticket #163 has a better discussion on how to deal with vendor name ownership.

@stof Pretty old ticket and still nothing in the direction of resolving this issue :( This could be a real cause of confusion in future as the number of packages on packagist increases.

@Seldaek Seldaek closed this as completed Jul 1, 2014
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

4 participants