Allow forum posts to be tagged with Project taxonomy terms

actually, this is a high priority that Dries and myself have talked about. however, instead of a per-project forum, we just want to add a new taxonomy (the tags you can associate with a forum post) where each project on the site automatically generates another term. so, when creating forum topics (in any of the existing forums), folks can select which project(s) the post is targetted to...

we just want to add a new taxonomy (the tags you can associate with a forum post)

I thought about suggesting that, but I was afraid someone would say that it would clutter up the "create new forum post" page too much.

When I'm looking for support on a module, I always go to the module's project page first. But, the project page is not in sync with the wealth of information related to that module found in the forum nodes. I'd like to go there and look at all forum posts made about that certain module/theme. I think that would help out those looking for support and those providing support. I also think that it would help create a synergy amongst other module developers.

I think it makes the most sense that the project page be the "homepage" or "portal" for all nodes (support requests, patches, hacks, documentation, examples, showcases) related to the respective module or theme.

right. on the project page, there would be a link to "show me all nodes that have been tagged with this project's taxonomy term" (not with that name, of course). ;)

Is there anything we, the average Drupal.org users, can do to advance this?

Is there any chance on seeing a "view 'support requests' without replies" list?

Will we be able to filter out "support requests" by:
"Installation problems"
"Upgrade problems"
"Post installation"
...
as laid out on the forum structure of the current Drupal.org forum?

I never would have guessed what this issue was about with that title. Maybe this is a bit more explanatory?

The original poster was looking for a separate forum for each project, but then this issue got shifted to keeping the current forum structure but just adding a term for each project that could be associated with forum posts. Personally, I wouldn't be that interested in having a different forum for each project, since at the moment I find forums very difficult to use since there is no email notification functionality available for forum posts on d.o. But clearly this functionality is desired by some, since #225152: Project Forum also requested the same functionality.

In thinking about this, the code for adding per-project forums vs. terms for each project would be almost identical. The difference is that in the first case the term would be added with the Forums vocabulary as the parent, while in the later the term would be added to a new "Project name" vocabulary that was enabled on forums. But as I see it both of these would require implementing hook_nodeapi() and responding when projects are created, deleted, and have their titles changed. In both cases it would also probably be best to add a link in the project overview page (this would be pretty easy now that #218571: add hook_project_page_link_alter(), implement to add security link to all project pages has been committed). In one case this link would point to a forum itself, in the other to the /taxonomy/term/id page I guess (that is, unless we created some kind of view to display the list of forum topics tagged with a certain tag).

My question is where would this code live? I don't see anything here that requires this to be in the project module itself, since I think this could implement hooks for all of the functionality. But maybe it's simple enough to keep in the project module?

aclight directed me to this issue from irc. Personally, I really, really think we should be directing any module-specific support requests to project issue queues - and this looks like a step backwards from that. Additionally I'd rather see a "unanswered support requests", "active support requests" etc. set of views across all projects so that people interested in giving support in general, can do so more easily in project issue queues (where in general a good 60% of support requests could be answered by anyone remotely familiar with using the modules).

So -1.

Right, the better solutions are here:
#10596: Make support requests more visible
#101292: Reorganize 'support' section of project page, make cleaner place to post support requests

#101292 is exactly what I've been thinking about, should check the project queue more often :)

Let’s go with the better solutions instead.