Haketilo

Not a very nice one either it seems :/.

While I don't think the overlap is semantically close enough or widely recognized enough to be an issue, it will also be horrendous trying to change the name once this project is truly established.

Any decision needs to be made soon, in my opinion. There are two options:

• Pick a name (Hachette or otherwise), check there's nothing uncomfortably similar also called that, and hope none of the projects that share it do anything too unsavory.
• Choose a statistically unlikely name, like "Nginx". This could be very enjoyable and gives us the option of a very meaningful, even personal, name, at the cost of possibly scaring away new users and having it regularly misspelled.

Remember the Hydra idea? Maybe "Hydrette"? Or "Lernette"?

That idea was very good- it seems like a promising path!

I would support the genuinely lovely Hydrette if not for it apparently being famous as a brand of "Prebiotic Vaginal Moisturizer". Lernette seems not to have any particularly significant takers, however, and definitely gets a "yes" from me!

Another option perhaps is Hydrilla- the pure-Latin form of "Little Hydra"? While it too is already in use, the primary sense seems to be a genus of aquatic plants which (hopefully) won't cause any issues.

Lol

I think I like Hydrilla marginally more that Lernette. Let's wait for at least one more opinion. Maybe from Colby?

I like Hachette. Pretty good chance it's in the clear, at least in the US, I think. The Hachette Group is a brand, whereas our Hachette is a "product", and the fields differ wildly. Low (essential no) risk of confusion.

Their trademark application is also overly broad, with it already being canceled for several fields:

https://tmsearch.uspto.gov/bin/showfield?f=doc&state=4805:8a93ao.2.3

(I'm not entirely sure, but that link is probably ephemeral and will die soon. Oh well.)

If it's a problem, we could maybe apply to be a member project and get services from sfconservancy. Worse case scenario is that we get a cease-and-desist and then decide to change it instead of fighting it. That's really not such a big deal. We'd have more time to come up with a name (or possibly merge/take over LibreJS by that point?).

I don't really like the other proposals.

Alas, you were right; the link is dead. Your judgment on that point is however evidence enough, and I agree we're most probably safe with Hachette.

My concern is that- regardless of what the name ends up being- we should be prepared to commit to it. A rebranding exercise, while possible, seems to me a painful undertaking for an established project (perhaps only out of lack of experience, it must be said).

Ok, so it stays as "Hachette"

EDIT: How about naming the extension "Hachette" and the repo "Hydrilla"?

How about naming the extension "Hachette" and the repo "Hydrilla"?

I'm certainly happy with that- we really do need a different name for the repository software.

jahoti wrote:

I'm certainly happy with that- we really do need a different name for the repository software.

Once we create something more (e.g. a Hydrilla-enabled http proxy), we shall need more names. We can collect ideas here :)

PS. (off-topic): Btw, jahoti, I am away from my main computer for 2 days and I have no access to my private key here. I shall read and respond to all encrypted email tomorrow, once I'm back. Sorry for the inconvenience

Once we create something more (e.g. a Hydrilla-enabled http proxy), we shall need more names. We can collect ideas here :)

Very true- in keeping with the apparent theme, how do we feel about sticking with names that start with "H"?

PS. (off-topic): Btw, jahoti, I am away from my main computer for 2 days and I have no access to my private key here. I shall read and respond to all encrypted email tomorrow, once I'm back. Sorry for the inconvenience

No inconvenience at all- there was nothing urgent!

Hachette just got renamed as per a request from RMS. The new name is "Haketilo"