it'd be really slick to be able to define most project settings/variables on a per-type basis -- the "project type" taxonomy (e.g. on d.o: module, theme, tranlsation, etc). we already have this (in a hard-coded, manual way) for "Enabled sorting options" for browsing projects. it's be great to extend this to releases (and eventually issues), and to make it general so you could define a type-specific default that would override the general site-wide default. some other examples where this would be very useful:
- default version format string (e.g. so there could be a different one for translations: http://drupal.org/node/89969)
- default if releases should be enabled (e.g. so distribution projects could have releases disabled by default (there's a thread on the infrastructure mailing list about this)
- the "Browse projects by release versions" checkbox
ideas for the UI:
- A: sub-tabs on each project settings page for each project type (could get totally unwieldy on sites with lots of types)
- B: nested collapsed fieldsets under each setting where a type-specific override is implemented. e.g. a collapsed fieldset that says "type-specific [setting name] values", which if you click it, expands to a set of collapsed fieldsets for each type.
other bright ideas, mock-ups, or patches, anyone? ;)
Comments
Comment #1
gábor hojtsyWhat about exploiting that (most of) these use different node types, so we can tie settings to node types? In this case, adding different taxonomy vocabularies to dfferent project types would be very easily done, if different project types would actually be different node types. That "only" requires cloning of the project node type in many instances, and then allows cleaner node form altering and such.
Comment #2
dwwWas searching for something and this came up. Wow, stroll down memory lane! ;)
This is indeed how things work in Project* D7 now, both on d.o and for stand-alone Project* installs.