It would be nice to add package information, such as 'Access control' to the .info file to group it with other similar modules:

; $Id: node_privacy_byrole.info,v 1.3 2007/11/28 22:48:37 deekayen Exp $
name = Node Privacy By Role
package = Access control
description = Provides node level access control based on role membership.
core = 6.x

Comments

deekayen’s picture

deekayen commented
Status: Active » Closed (won't fix)

If anything, I would make the project Node Privacy Byrole because it has two .module files. I prefer to keep the package tag reserved for projects that actually have more than one module like Util, Views, CCK, or Workflow. I just don't think NPBR is big enough for its own package tag yet.

MGN’s picture

MGN commented

Interesting response. I would have agreed with rs_hull_uk, but I see your point also.

If I look through my modules I see two sets of project groupings: by project and by project type or category:

Contemplates is listed under "CCK" even though its not part of the CCK package
SMTP lands in the project Mail
lightbox2 is under "javascript tools"
tagadelic is under "taxonomy"

and then there are those that are one package/project. Personally, I can see an advantage to having project categories in addition to projects...its logical. Just wondering if there is a standard or best practice for assigning project names? I haven't looked around yet, but I will...

EDIT: deekayen is right. Question is answered http://drupal.org/node/231036

Thanks.