Form_alter the theme vocabularies so that they only show up for theme node editing

http://drupal.org/node/372062 is dependend on this.

Themes will have their own vocabularies #371957: Add new taxonomy vocabularies for themes. Since we can only limit vocabularies to content types, this issue still stands. We either need to hack away to limit the showing and entering of the theme vocabularies to theme projects, or we need to complete this issue to make multiple content types be projects.

This is a fairly large can of worms at this point (for example, see #239485: attach an issue queue to any node type. and #75565: make a hook to get version options for a given project). Given the "we must have a working D6 version ready 6 months ago" mentality of the upgrade efforts, I've spent no time on cleanups like this in the code, beyond porting things to using views. If the goal is to have this done soon, I would suggest drupalorg_form_alter() to modify which vocabularies are present when editing different kinds of project nodes. There's already code related to this in project module itself, to conditionally hide/show the multi-select for the project categories depending on the radio for the top-level term.

Plus, I have no intention of working on anything like this before the D6 upgrade is live on d.o, and there are still known bugs and issues to work out there. However, there's a (easy) work-around for the immediate redesign efforts, so this shouldn't block anything else. Therefore, I'm marking this postponed for now.

Well, this all sounds more like stuff we should do in a custom drupal.org module, right?

Yes, that's what I said: "drupalorg_form_alter()". I'm just pointing out there's already code that does something similar so you can start from there instead of starting from scratch.

Meanwhile, this is still a valid request for project itself, so we can leave it here. But the way to implement #372062: Add special fields to theme content type and #371957: Add new taxonomy vocabularies for themes is via hook_form_alter in drupalorg.module.

Once #371957: Add new taxonomy vocabularies for themes is solved, we should have the form_altering based on "project subtype" done.

BTW should be done in the drupalorg.module. Should be both implemented in HEAD and DRUPAL-6--1, and we should deploy the DRUPAL-6--1 version on drupal.org if the vocabularies are live to not confuse people who are going to edit projects before the redesign is live. I can do the deployment once the changes are in.