Add project type for "Other" projects

I'm against generic "other" categories, but would support something like "Drupal initiatives"

IMO, "Other" is very appropriate here. Things like Drush don't fall into the "Drupal initiatives" category, but the other categories don't accurately describe it either.

I am not a fan of "Other" either, as it doesn't explain what's in it. It also won't help people decide how to tag their project.

tvn pointed this issue out when I posted #1982692: Create a separate 'project type' tag for Community related matters.

Does "Community initiatives" work as a catch-all or do we need an additional tag to describe projects such as Drush? What are the other differentiators here? Code vs non-code?

I like "Community initiatives" ... and would propose a "Utilities/Tools" category for Drush and other similar items.

Drush and friends need #322626: META: Package and version non-modules for download.

This seems like something else... "Community initiatives" or something is probably fine. Although, I wonder what's wrong about considering things like governance, conflict_resolution, marketing, etc "Drupal.org projects"?

I seem to recall 'drupal.org projects' was set up for for code and issue queues specifically related to *.drupal.org. Right now it's difficult to find what you're looking for in that type.

Once we solve the problem of sandbox projects being selected as drupal.org projects, maybe it won't be so difficult to find things.

I'd also be happy to discuss renaming "Drupal.org projects" to "Community projects" or similar, since that covers most of the bases.

The dream of "look here for all the issues queues for stuff that effect Drupal.org itself" is totally unworkable, since a bunch of d.o issues are (and must) be handled in the queues for the modules that d.o uses. I still think the only real solution to that is #192714: Add a "Report a problem" link in d.o navigation block (in order to help avoid duplicate issues). ;)

So, I'm not sure "Drupal.org projects" is actually helpful. I think of it more as "stuff the Drupal community cares about that isn't code." So, renaming it to "Community initiatives" or something would be okay with me I guess. Although are the infra and webmaster queues really "Community initiatives"?

/me shrugs...

I see "Drupal.org projects" as projects that deal with the day-to-day management of the .drupal.org sites, including code and content moderation. "Community initiatives" are projects that go beyond the .drupal.org control (such as Drupal Camps) or are designed to extend functionality or awareness of Drupal.

I recently created a sandbox that was for an Asciidoc-flavored markdown version of some API documentation tutorials currently residing under https://drupal.org/developing/api.

I have no idea what classification this project would fall into. The docs for "drupal.org" type say:

Drupal.org is maintained by volunteers and the Drupal Association. These projects organize work on Drupal.org itself. For more about how Drupal.org works, see the FAQ.

That doesn't fit -- it was an experiment in making new versions of some docs that live on drupal.org, not organizing work on drupal.org itself.

And it isn't a "utility". Maybe it would have been a "community initiative" in its initial stages (while we were doing the conversion), but eventually the idea was that it would have been a set of documentation that we displayed on api.drupal.org (that was the plan; it failed; it was a sandbox after all).

So...there isn't currently a single one of the project categories that fits this project.

#2474007: Add a “General” project type to Drupal.org was appropriated as a catch-all for non-module/theme/etc projects. And “Drupal.org projects” were renamed to “Community projects” at some point, to make it more-clear that it is a good home for usually-non-code community organization projects.