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

Package naming #3

Closed
frankdejonge opened this issue Aug 19, 2013 · 13 comments
Closed

Package naming #3

frankdejonge opened this issue Aug 19, 2013 · 13 comments

Comments

@frankdejonge
Copy link
Member

I can see this being a helpful tool for lots of developers, but there's also grunt.js, which is super popular and dominates the name "grunt". I don't really see why the package is not named differently. Even the gruntfile is the same name, so I doubt this is a coincidence, right?

My two cents would be to rename the package and respect the other tool's namespace, even if it is from another language.

@toopay
Copy link
Member

toopay commented Aug 19, 2013

I am aware of that, but here some (ironic) facts :

So the name conflict was really a coincidence, believe it or not :)

I already used this library before i publish it as a composer package recently, that means i had Gruntfile files scattered across several (old) projects, so changing all of this references could be a lil bit pain for me.

But sure i noticed name conflict could be confusing for some people. Maybe we could rename this. Lets see if other people bothered by these issue, but honestly i didn't.

@frankdejonge
Copy link
Member Author

Well, you can put me down for a +1 then. I use grunt.js so I'd be required to alias your tool anyway (for global usage). Not to nitpick, but to be precise, you're referencing a 0.4.0 tag, before that the tool was already widespread and used by many.

@nickcernis
Copy link

I agree that the name could be problematic. (It's a shame that you thought of it first – I hate it when that happens!)

If you're open to renaming it, perhaps "Shunt" would work? Or "SSHunt"? Both allude to the use of SSH and the idea of nudging files and commands across to a remote server.

@jonathanmarvens
Copy link

@toopay Grunt.js has been around since 2011, and I personally have been using it for more than a year now. A rename would be quite awesome.

@thomaswelton
Copy link

Yeah, took me a few reads to be 100% sure this wasn't Grunt.js related.
You even have the same Gruntfile naming convention. Spooky. And confusing.

@rjkip
Copy link

rjkip commented Oct 11, 2013

👍 Would improve discoverability for your project as searches from Grunt always lead to the JS tool. Would prevent confusion regarding the Gruntfile and Gruntfile.js. Shunt sounds good, but anything else than Grunt is okay. :)

@toopay
Copy link
Member

toopay commented Oct 11, 2013

@ALL Expect package re-name next week. cc @philsturgeon

@frankdejonge
Copy link
Member Author

👍

@jonathanmarvens
Copy link

👍 .

@philsturgeon
Copy link
Member

Awesome


Sent from Mailbox for iPhone

On Fri, Oct 11, 2013 at 4:23 PM, Jonathan Barronville
notifications@github.com wrote:

👍 .

Reply to this email directly or view it on GitHub:
#3 (comment)

@toopay toopay closed this as completed in e983b1a Oct 16, 2013
@toopay
Copy link
Member

toopay commented Oct 16, 2013

New stable release now using Shunt as namespace. Thanks @nickcernis for the suggested name.

@philsturgeon you may need to update the grunt package info within php-loep front-page.

@frankdejonge
Copy link
Member Author

@toopay updated 30dc4c428fc8bab27ef2f72291ac94ddf94ec8d5

@toopay
Copy link
Member

toopay commented Oct 16, 2013

@FrenkyNet thanks man.

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

7 participants