Conflicting project name

[darth10]

Please note that I'm not pointing fingers in this issue. It's more of a question to be honest.

This project conflicts with the Pallet Clojure project.
Pallet is still quite active in terms of development, and is used a lot IMHO.
Since Pallet is an older project, would renaming this awesome project not be the right thing to do? 💭

[rdallasgray]

Hi -- thanks for raising this. It's definitely on my mind. The only reason I didn't do this before was that I honestly didn't expect the project to get any attention. It's certainly something I'll consider again now.

[rdallasgray]

I'm going to open this issue up to suggestions for new names. The first decent one I came up with was 'Cellarman'. We want something that goes nicely with Cask, sounds good, and doesn't step on any toes.

[rejeep]

So annoying with name clashes... :)

I agree that something that goes nicely with Cask would be great. Maybe the name of some ale or similar?

[rdallasgray]

'Porter' has a nice double meaning.

[rdallasgray]

@rejeep Also, I'd be interested to hear about your experience with renaming Carton to Cask. Any tips?

[saintaardvark]

How about "Keg" or "Barrel"?

[darth10]

It's nice to hear so many recommendations.
So far we have...

• Cellarman
• Porter
• Keg
• Barrel
• Brewery

@rdallasgray the choice up to you 😄

EDIT: Added 'Brewery'

[rejeep]

@rdallasgray It was actually very painless. Definitely more so than what I expected. What I did was I did the renaming, released a new version and then blogged about the changes. Surprisingly, people adapted very quick. It actually got some unexpected attention from it. The old saying "any press is good press" was correct in this case. :)

[rejeep]

Brewery seems available.

[ghost]

I don't see a problem here that needs fixing. The project is rdallasgray/pallet. One of the awesome early decisions GitHub made was putting everything under a user or (eventually) organization namespace.

If this were written in Clojure, I'd side with @darth10, but it's not. Naming is a hard enough problem without imposing a global namespace on all projects across all languages.

[ghost]

In case the popular opinion is that projects don't look official unless they're under a GitHub organization, and pallet is already used by the Clojure project, then I suggest forking this to cask/pallet and making that the official repo.

[rdallasgray]

Thanks for your comments. My perspective is that a significant proportion of Emacs users will encounter both Pallets, and that's reason enough for this one, being the later to the name, to change.

It isn't up to me whether Pallet can be incorporated into the Cask namespace -- it's up, I guess to @rejeep and the other Cask collaborators (of which I'm not one). I'd be open to it, but I still think a rename would be polite.

[DarwinAwardWinner]

Is Casker too similar to Cask?

[rdallasgray]

I think my choice for this is Porter.

I'm thinking that what would have been the 0.7 release of Pallet will be Porter 1.0. My plan is to create a new repo here with that name and commensurately a new recipe for Melpa. This repo will be abandoned but left alive until it seems that everyone who's interested has moved to the new one.

I welcome any objections/questions/criticism/tips.

[rejeep]

I would recommend just renaming the repo, update the melpa recipe and let users adapt quickly. If you don't people will be stuck with pallet for a long time. It worked great for us when we renamed carton to cask.