I know you've got a naming convention going on but having modules named "nodeaccess" (long standing and well maintained) and "node_access" is a really bad idea.

Comments

Dave Reid’s picture

Title: poor title » Duplicate module?

I was also wondering what makes this module different from the nodeaccess module?

emptyvoid’s picture

I want to have a honest and thought provoking discussion on this topic. However I won't be able to provide an quality response until later in the week (and perhaps the weekend). There are several reasons as to why we didn't choose to use the existing module(s). Some of the considerations may be moot at this point, while others have to do with integration, usability, and expandability. Again, I will provide a detailed post on this subject that outlines the decisions and rational behind not using the existing modules provided within the community.

So, please wait until I can find the time to compose myself and provide my thoughts in an articulate and honest manor.

Thanks,

WorldFallz’s picture

No problem-- post back when you can. Just one thing though-- the issue isnt so much that you didn't choose to use an existing module. That decision is entirely up to you. However, posting a new module to drupal.org named "node_access" when there is already a module named "nodeaccess" (even regardless of whether or not functionality overlaps) is both careless and confusing. That's the real issue.

Looking forward to your thoughts when you can post back.

fp’s picture

Update?

Flying Drupalist’s picture

Subscribe.

christefano’s picture

Title: Duplicate module? » the name of the Node Access (node_access) project is confusing

I agree with #3 and the title of this issue needs to be changed. The project's name is very bad to begin with and using a name that's so similar to another module just makes it worse. Please rename this project to something else.

danielb’s picture

I vote for swipht_access or swift_access

I don't even like the fact that the original nodeaccess project is called nodeaccess, because when I talk about it I have to say "the node access module" vs "the drupal node access system", and because I have made a number of modules that use the drupal node access system people keep asking me "but isn't there already a node access module" argh....

Luckily their module is now so generically drupal in it's approach that it deserves such a default title.

WisTex’s picture

I agree a better name would be in order.

emptyvoid’s picture

Personally I agree with the post from mdekkers

http://drupal.org/node/608556

"I would just like to say that I am not a big fan of this "duplicate module witchhunt" thing. There are many ways that lead to Rome, and more then anything else, it stifles innovation to no end, and strongly encourages an unhealthy sense of group-think. pounard is graciously sharing with the community some of the work he has been doing in his company, and both pounard as well as his company should be thanked for this generosity, not told to "take it away elsewhere, we already do this kind of thing" - whilst the end functionality might already be available, there might be a specific use-case that is satisfied, a prettier code base, or just an approach that sits much better with a given user.

And yes - I am aware of the whole "we can't confuse the poor user" argument. Well, if you create a system exclusively tuned for the lowest common denominator, then your system will become the lowest common denominator. I, for one, am happy that there are different modules out there that do the same thing - it makes it oodles easier for me to decide to go with contributed code, or roll my own. If there was only one of each, I would be rolling my own most of the time.

Thanks, pounard, for giving me the choice. "

If you read the project page, I state why this module was built and a list of the best alternative modules to accomplish the same issue.

I respect your opinion on the matter but to be honest once a module is committed to cvs it will not be going away any time soon, unless it is totally abandoned (even though there are still modules for 4.7 in the repo that clearly haven't been updated for 4 years).

christefano’s picture

The "duplicate module witch hunts" are unfortunate (and I was one of the more outspoken people against the culture that was brewing around the formerly-named "Duplicate Module Hall of Fame" group). That being said, the "once a module is committed to cvs" argument isn't very convincing. Other modules (Flag, Mail Comment, etc.) have changed their names and the world has kept turning. I'd feel very differently if this module were a backport of a Drupal 7 API but that's not the case here. "Node Access" is quite simply a terrible name for a contributed module.

danielb’s picture

Yeah it's not about similar functionality, it's the bloody name. Confuses me everytime and makes it difficult to talk with other drupal people about node access without then giving a monologue about which node access concept you are refering to.

rougekris’s picture

EDITED