Proposal: Change name? about whoops

[filp]

Thanks @taylorotwell, good to know.

Library will be renamed between today 12PM & 11AM GMT, to filp/whoops.

[celtric]

I think it should be changed. No ideas so far for the name, but as I'm pretty hungry right now, I propose Seitan Error Handler (kidding, I actually hate seitan).

[bobdenotter]

Personally, i don't give a damn what it's called (haha, see what I did there?), but I could see why somebody would refrain from using this library. Either because they don't like the name themselves, or even because they think somebody else might take offense.

I think this had been an ongoing discussion for Frederico C. Knabben's editor for years, which didn't go away until they changed it. So, yes, I agree it should be renamed.

Perhaps call it 'Meh', short for "My error handler"?

[carbontwelve]

While nobody in my office took offence and we chose to use this based simply upon its usefulness I would agree that a name change would probably help because some people out there feel they have a god given right to not be offended and thus avoiding that will benefit the project and possibly increase the number of people who would use it.

[sevenpointsix]

Personally, I wouldn't see a name change as necessary. Partly because "damnit" isn't, ultimately, very offensive (although this is obviously subjective) but mainly, the name of your PHP error handler is unlikely to be plastered all over anything you're showing to people outside your immediate team.

Obviously, this won't be the case for everyone, but I'd suspect that quite often, the name "damnit" will be grouped in with other "technical" terms that most people on a project won't want anything to do with ("Laravel", "composer", "API", "ORM" and so on). In my experience (which is admittedly building websites for non-technical clients and companies), the people I'm working for wouldn't want to hear anything about the "error handler" I was using, let alone care what it's called.

Incidentally if we're getting into etymology, "damnit" is very rarely used in British English, it's mainly a US spelling.

👍

Rename it to Whoops, or something.

Like others, I don't really care, it'll just be awkward describing its use to overly sensitive managers or clients, etc.

[schickling]

I like the current name!

[taylorotwell]

I would change it.

[filp]

@kherge I like Whoops! Kinda fits the spirit behind my original choice of "Damnit", without the possibly offensive/sensitive aspect.

What do you all think?

[taylorotwell]

"Whoops" sounds good!

On Mar 16, 2013, at 1:42 PM, Filipe Dobreira [email protected] wrote:

@kherge I like Whoops! Kinda fits the spirit behind my original choice of "Damnit", without the possibly offensive/sensitive aspect.

What do you all think?

—
Reply to this email directly or view it on GitHub.

[filp]

Just did a quick test with renaming in a seperate branch, and it's a painless process, but do any of you have experience with migrating a library to a new name between github and composer/packagist? @taylorotwell, @kherge perhaps?

[taylorotwell]

I know once a package is past a certain number of installs on Packagist it can not be deleted. Or, at least that used to be case. However, I have been able to e-mail the Packagist maintainers and have them remove a package for me before after explaining the circumstances.

[filp]

Merged in 8e26d08 🍪

Now to handle all the loose ends, such as the undeletable packagist package.

C'est la vie. Thanks for the help everyone!