Can we deprecate the Fern theme?

since one is a module and the other is a theme, I don't foresee problems.

Modules and themes share the same URI namespace, however. The Fern theme is at http://drupal.org/project/fern, and I'm guessing that's the desired path of this new module as well.

Thats correct, to an extent
at project/fern.

Page not found

It is now just stating that the shortname is in use. The project name is available

Sorry, my title was cached.

The first email I have ever received on this subject was posted at 19:40 last night, and already the two of them are trying to bump a project still in use by hundreds of sites.

I suspect I'd be more likely to consider helping them if they hadn't opened this thread with a bare-faced lie.

[That, and the theme in question, while old, is still quite popular and entirely able to be upgraded. And they didn't bother to look for an existing project before deciding on a duplicate name, which is hardly my bloody problem.]

jh

Oh, and one more thing

The author of the project, http://drupal.org/user/211387, has already created the CVS folder

Yeah, fourteen minutes before sending his first-ever email to me.

Err, ok

For the record: I wish there was a good way to validate the addition of new directories to CVS. If there was, we could prevent people from adding directories in CVS unless they had a pre-existing project node. That would prevent collisions like this, since people would have to try to make the project node first, and hit the existing validation on project nodes. Sadly, CVS just does not make this possible. :( Unlike commits, tags, etc, there's no server hook that lets you validate and prevent the "cvs add" command on a directory or the "cvs import" command. :( LAME!

That said, last I knew, core itself freaks out if you have both a theme and a module with the same name. So, it's a feature not a bug that all projects share the same namespace on d.o...

Anyway, given that the fern theme exists and the owner apparently intends to keep using it, the answer to the original question "can I have the 'fern' project name?" is a resounding "No". You messed up by duplicating an existing project name by not doing your homework first, and we're not going to reward you with the /project/fern project for that. Since the project namespace is first-come-first-serve, you're out of luck.

So, the best you can hope for at this point is to rename your module to something other than "fern", and use that. If you need help renaming the files in CVS, I'm willing to make that happen, but otherwise, you just need to start over with a name that's not already in use.

p.s. In the future, please do not make and delete test project nodes. A few folks in IRC were complaining that you were "spamming" by creating these dummy projects. In general, "test" content on d.o is highly frowned upon. Thanks.

handelaar: I understand that you have some reason to be upset, but Senpai is a respected member of the community. Calling him a liar in your first communication here seems unnecessary to me.

Core freaks out if a project and a theme are the same name? That's completely absurd, and it sounds like things need to be re-thought. drupal.org/project/fern goes to a Page Not Found, and therefore it should be able to be used.

Last I checked, project.module was not part of core either.

As for spamming test projects, I find it hard to believe that creating 1 project with repository space that was my own for a recently deleted project(Pownce.com is shutting down) is even close to spamming, so spare me on that exaggeration.

And no, I wont Change the name of my project because someone is hot headed about a question I asked my friend, and then blew up because other exaggerations were used.

I was able to create my project so this ticket might as well be closed.

http://freebsd-info.activeventure.org/cvs/cvs.info.commitinfo.html

Core freaks out if a project and a theme are the same name?

That's right. Google for "drupal module theme same name" and you'll find:
#84695: Hooks mess up when theme and module have same name
http://drupal.org/node/143020
http://www.nicklewis.org/node/993
http://www.shooflydesign.org/buzz/past/drupal_development_dont_give_modu...

drupal.org/project/fern goes to a Page Not Found

http://drupal.org/project/fern lands at a real page -- don't know what you mean.

Last I checked, project.module was not part of core either.

True, but irrelevant to this discussion. I said it's too bad we can't have more validation on CVS to prevent collisions. Then I said that because of the limitations in core (linked to above) that make trouble if you have a module and theme with the same name, it's a feature not a bug in project* (in contrib, running on d.o) that forces all projects to use the same namespace.

And no, I wont Change the name of my project because someone is hot headed about a question I asked my friend, and then blew up because other exaggerations were used.

That's not why you have to change the name of your project. You have to use a different name since "fern" is already taken. All the other heat generated in this issue is apparently raising various people's temperature, but not dealing with the underlying problem.

I was able to create my project so this ticket might as well be closed.

By calling it http://drupal.org/project/fernest -- great. Namespace collision avoided. However, please rename your module file, too. It's confusing and will be annoying for your users if the main module name doesn't match the directory or the project URL, and it'll prevent people from hitting problems if they happen to want to use your code and the "fern" theme on the same site some day.

Finally, the "closed" status is usually used for things that were fixed for 2 weeks. "won't fix" is a more accurate status for this request, since the answer to "Can we deprecate the Fern theme?" is "No". Not because anyone's pissed off at anyone else, but because the "fern" theme was here first and they're still using that name.

Cheers,
-Derek

Re #15: that's for validating commits. We already do that. files and directories are treated differently by CVS. If you had to run "cvs commit" when you add a directory, that would be useful. But, you don't -- if you "cvs add directory", there's no hook to validate or prevent the action.

merlinofchaos: He claimed, unambiguously, that I'd been mailed 'several times'. That's a lie, and one which was confirmed as such by kylebrowning (on whose behalf he was acting) last night.

'Unnecessary' isn't the word I'd use, no.