>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #322626. --> Reported by: [it-cru](https://www.drupal.org/user/324945) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>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 <a href="https://www.drupal.org/project/drush">drush</a> 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).</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Create a new project type on drupal.org (just via the taxonomy UI) called "Other" (or something)</li> <li>Give all projects using this type a different version string format. The current proposal is:<br> <pre>[major].[patch].(-[extra])?</pre><p> (e.g. "1.0", "2.0-beta1", etc).</p></li> <li>Teach Project* and Git about these new version strings (see below for details)</li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/project/issues/1434476" title="Status: Closed (won't fix)">#1434476: Add project-type-specific settings for default version_format strings</a></span></li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/versioncontrol_project/issues/1434500" title="Status: Active">#1434500: Add project-type-specific settings for label_version_mapper plugin</a></span></li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupalorg/issues/1434502" title="Status: Active">#1434502: Add another versioncontrol_project plugin for mapping release tags and branches for "generic" projects</a></span></li> <li>Testing (which will be hard since we don't have a working Git staging environment yet)</li> <li>Deployment</li> <li>Updating documentation</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>- There will be a new project type, so we'll need a new listing page for those at the downloads section.<br> - New project type radio button on project add/edit pages<br> - Possible new admin setting UIs for #1434476 and #1434500</p> <h3 id="summary-api-changes">API changes</h3> <p>Nothing user-facing. There will probably be some changes internal to project_release and versioncontrol_release modules.</p> <h3 id="summary-original-report">Original report by IT-Cru</h3> <p>// Text of original report here.<br> (for legacy issues whose initial post was not the issue summary)</p> <p>Hello,</p> <p>is it possible to create projects for scripts?</p> <p>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 ;)</p> <p>thx Gos77</p>