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

Potential naming conflict. #1

Open
amcgregor opened this issue Jun 8, 2016 · 1 comment
Open

Potential naming conflict. #1

amcgregor opened this issue Jun 8, 2016 · 1 comment

Comments

@amcgregor
Copy link

amcgregor commented Jun 8, 2016

Hello,

I'm the author and maintainer of the WebCore web framework, in production use since 2009 or so. My Google Alerts notified me of the creation of your project here and registration of it on Packagist. Due to PHP being a web development language, I see a strong potential for a naming conflict to have potentially confusing impact on end-users. That is, web developers. After Apple's WebKit (which has a "core" module) and a company named Webcor (a construction industry company), my own WebCore is the third result in Duckduckgo (un-customized) results.

I would be extremely grateful if this naming conflict could be resolved, and the pain of re-naming a project tree is something I have felt on this particular project in the past (the "marrow" org on Github here formerly being "pulp", re-named due to conflict).

Thank you for your consideration,
— Alice, Marrow Open Source Collective

(Edited to add: wow, Google is fast! Only four hours…)

@amcgregor
Copy link
Author

@ChimneySweep13 Any chance I could get a response on this issue before you go too far down the rabbit hole of populating this org with packages?

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

1 participant