So, Project* and Version Control API can still be categorized in the "Developer" category. However, modules that are concerned with project management but not with traditionally scoped "development" have nowhere to go.

Specifically, I just created the Project administration category, Time budget and Project forecast modules, neither of which I am comfortable with putting into the developer category. Project administration category also fits into "Administration", and Time budget might also fit into "User management", but that's certainly not the whole story.

I kindly ask you to create a new "Project management" category where Project*, Case Tracker, Version Control API, Storm, the modules mentioned above and probably more can find a peaceful home. If it deserves its own section in the admin overview (in use by three different module families mentioned here, including Project*) then it also deserves its own category on drupal.org, imho.

Thanks,
Jakob

Comments

sethfreach’s picture

sethfreach commented

+1

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Sure, I don't see a reason not to do this. Would love it if one of the Project* maintainers could chime in though. Then I can go ahead and make the change.

dww’s picture

dww
we/he/they
commented

In general, having a list of all the modules that would belong to a new category is necessary to make a decision like this. If it's only 3 or 4, no way, since having 400 module categories with 3-5 modules each isn't much better than what we have now. But, O(10) or more, seems like it's worth a smaller, separate category.

That said, I'm not convinced that Version Control API, CVS integration, version_control_*, etc, belong in a "Project management" group. I wouldn't put up a big fight against it, and "Project management" is better than wherever they are now... ;) But, IMHO, version control != (necessarily) project management.

So, +0 overall, I guess. ;)

jpetso’s picture

jpetso commented

You're right, Version Control API is probably not the most ideal candidate. I'll have a look if I can get a larger overview of modules that deserve to go into that category - didn't look very closely before as I posted this just because of a felt gap instead of sound empirical data.

silverwing’s picture

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

Queue Cleanup

with comments 3 & 4 I'll mark this as wont fix