Voting starts in March for the Drupal Association Board election.
Some things packaged on drupal.org aren't Drupal modules or themes. For them, the [core_version]-[major].[patch]-[extra] version strings don't make sense, since they're not bound to a specific version of core. The prime example is drush although lots of other scripts, add-ons, drush plugins, etc, are forced to either live elsewhere, or be subject to the core-compatible version strings which aren't appropriate for them (often leading to confusion for end users who think they need a specific version of core to use them).
- Create a new project type on drupal.org (just via the taxonomy UI) called "Other" (or something)
- Give all projects using this type a different version string format. The current proposal is:
(e.g. "1.0", "2.0-beta1", etc).
- Teach Project* and Git about these new version strings (see below for details)
- Testing (which will be hard since we don't have a working Git staging environment yet)
- Updating documentation
User interface changes
- There will be a new project type, so we'll need a new listing page for those at the downloads section.
- New project type radio button on project add/edit pages
- Possible new admin setting UIs for #1434476 and #1434500
Nothing user-facing. There will probably be some changes internal to project_release and versioncontrol_release modules.
Original report by IT-Cru
// Text of original report here.
(for legacy issues whose initial post was not the issue summary)
is it possible to create projects for scripts?
I'm currently working on a little automated drupal update bash-script, but this doesn't match with modules, themes, translation or so. A categorie script for new projects would be nice ;)