-
Notifications
You must be signed in to change notification settings - Fork 23
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
What's in a name? #22
Comments
Yeah the name struck me as very strange as well. I know the book/movie is a somewhat well-known classic (I mean, I only noticed the name because I'd heard of the Stanley Kubrick movie), but... what on earth do bulk database operations have to do with "a middle-aged literature professor [...] obsessed with a 12-year-old girl"? |
I absolutely agree. Is this project still active or can we just deprecate it? In case it is still active, I propose we change the name and then first deprecated the older packages on nuget.org and later hide them completely. /cc @yukozh |
@yukozh Can this package/project please be renamed this month? I pitch the name |
@yukozh Any update on the progress so far? |
@yukozh Please rename the project and package until 2023-11-30. Otherwise, I will take the necessary actions myself without any further warning or dialog about it. To make it perfectly clear, why we (PomeloFoundation) do not want to be associated with a project/package name like this one, here the first paragraph of the Wikipedia article about the book with the same title:
It is also highly unlikely that anyone wants to ship a package of this project with the current name to a customer. /cc @bgrainger |
Other than a handful of commits from Nov-Jan, it looked like this project was completely inactive. One possible way forward would be to just archive the project, but that still leaves the name associated with "PomeloFoundation". It looks like I wonder if it might be simplest to:
This doesn't remove the association of the name with PomeloFoundation but (a) that might not even be possible without contacting NuGet to get the packages taken down, and (b) it makes it clear that this package is not endorsed without requiring a lot of renaming work. |
I'm not usually one to have issue with names of packages, but... wewlad.
I'm looking to use this package in a professional environment in combination with Pomelo, and the fact that it's called Lolita makes things a touch awkward. I mean, I like Nabokov as much as the next guy, but yikes. I'm just trying to do some bulk updates without writing raw SQL, not get into a discussion with my boss and co-workers about the nuances of package names and their relation to a hugely influential and controversial work of 1950s erotic fiction.
Is there any practical scope to reconsider the naming of this package?
The text was updated successfully, but these errors were encountered: