Confusing naming for Nodewords / Node (key)words / Meta tags module

I prefer the name "Meta tags" as the module does more then just add "node (key)words" from which the name originates. In all links or documentation, the term "Meta tags" should be used in order to avoid confusion.

So, I've looked over the code and replaced "nodewords" into "meta tags" everywhere where the user is presented with it. When the code or documentation discusses the module name or code, "nodewords" is still used.

Setting this as "by design".

You still cant use two separate names to identify the same module. If Meta tags is to be used as the identifier, then the project directory needs to be renamed to "metatags" and all documentation, code, project page should reflect this change. Consistency is important, and sooner or later any support pages will pick up the change and update as Drupal updates.

I've looked over the code and replaced "nodewords" into "meta tags" everywhere where the user is presented with it. When the code or documentation discusses the module name or code, "nodewords" is still used.

However, the module page says: Meta tags is the preferred name.

I think this makes things most confusing (especially for first time drupallers) and therefore agree with BioALIEN: either "nodewords" or "meta tags" should be used for everything, and not some kind of mix.

yes, i think so, too. For consistency the project should be renamed to "metatags", "meta-tags" or "meta_tags".

But then, alter all tables, variables and so on, too.

[facetious]
While we're at it, can we please rename 'categories' into 'taxonomies' ... or 'taxonomy.module' into 'category.module'. I don't mind which, but it's really confusing having the menu item and documentation say one thing and the module code say another.

A simple search & replace should do it, right ?
[/facetious]

;-)

I will release a "metatags.module" for Drupal 6 and then the "nodewords.module" one.

This is still the issue, and - at least to me - quite annoying sometimes...

Is it really so complicated to make the naming more consistent (and, intuitive)? I mean, if "Meta Tags" is somehow chosen (as it seems), why not simply rename module to metatags and this should be it...

It is actually quite hard to rename CVS branches. Basically, if it was done (requires super-admin on CVS tree and some mojo) then it leaves everyone who has the old checkout without an upgrade path.
Annoying, and I agree is should be possible in a perfect world, but it's certainly non-trivial.
Possible a symlink may help, but even that is a very hairy work-around.

A clean break, maybe between D5 and D6 may be the answer. I dunno. Requires bigger CVS-fu than I can imagine.

dww knows how :-)

Or just ditch the existing project, start a new one with the correct name and shift all your focus on supporting D6 branch. Plaster a big notice on the old project page to direct users to the new module and location. Job done!

That's more or less what I've had in mind... ;-)

Maybe to publish just another (last) version with the current name, to get the attraction of admins (put a big warning displayed somewhere at the admin screen). Who will not notice it, obviously doesn't care much about... The others will reinstall (replace) the module and this shall be it. Then, with a big notice, we can leave the present project to slowly cease...

BTW, I remember some project went through that about a year ago (maybe a bit more), but unfortunately don't remember exactly which one it was (maybe to get some advises about from the maintainer...).