Decide on Starshot's product name
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3452281. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>I never thought I'd have to file a critical <em>marketing</em> issue, but here we are.</p> <p>As @catch pointed out in <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/starshot/issues/3452233" title="Status: Closed (fixed)">#3452233: [PP-1] Establish the repository layout</a></span>, if we're going to provide Starshot's component recipes to people for use in their own projects, we're going to need to expose them to Project Browser. If we're going to expose them to Project Browser, we need them to be projects on drupal.org. And if we're going to do <em>that</em>, we need to decide on the permanent name of the Starshot product suite, because projects and releases are written in stone on drupal.org.</p> <p>Okay, sure -- projects could be migrated from one namespace to another. But, because each individual recipe needs to be its own project, we anticipate that Starshot will generate <em>many</em> sub-projects. Therefore, it'll be better for everyone if we decide on this now, so as to minimize the amount of debris we create.</p> <p>So, let's fling open this biggest of all bikesheds. I don't think we have a <em>ton</em> of time to decide this, but maybe @Dries would be willing to accept some sort of deadline, since I'm guessing the final decision lies with him.</p> <p>Last I heard, "Drupal CMS" was the option that seems to be floating around. I don't have a problem with that. But if you have some other/better idea, go ahead and share your $0.02.</p> <h2>Proposed resolutiom <blockquote><p> Suzanne (I think) mentioned in Drupal Slack that it's been narrowed down to:</p> <p>Drupal CMS<br> Drupal Spark<br> Drupal Plus</p> <p>and the team is going to move forward with user testing these against user personas who are not part of the Drupal community. </p></blockquote> </h2> > Related issue: [Issue #3424410](https://www.drupal.org/node/3424410)
issue