[META] Drupal.org ideation tool
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #2261945. -->
Reported by: [tvn](https://www.drupal.org/user/999848)
>>>
<p>As of January 30, 2016, and until any changes are made (like what is discussed below), <strong>the place to suggest ideas or request features for Drupal.org itself is in the appropriate issues list, e.g. the "<a href="https://www.drupal.org/project/issues/drupalorg?text=&status=All&priorities=All&categories=3&version=All&component=All">Issues for Drupal.org customizations</a>" list for ideas about the Drupal.org user interface.</strong> (This direction is based on <a href="https://groups.drupal.org/node/508566">a corresponding question and answer</a>.)</p>
<p><strong>Work on this "Drupal.org ideation tool" issue was postponed as of May 21, 2014</strong></p>
<p><strong>IMPORTANT: Our goal is to have initial version of this tool ready by DrupalCon Austin. Therefore, this specification is open for community feedback UNTIL 18TH OF MAY, 2014. After that we'll start active work on the implementation.</strong></p>
<p>Something to say about voting? Go here: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/drupalorg/issues/2263057" title="Status: Closed (won't fix)">#2263057: Voting on Drupal.org ideas (ideation tool nodes)</a></span></p>
<p>Something to say about implementation? Go here: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/drupalorg/issues/2263117" title="Status: Closed (won't fix)">#2263117: Drupal.org ideation tool implementation</a></span><br>
</p>
<h2>Description</h2>
<h3>Motivation</h3>
<ul>
<li>People have good ideas for Drupal.org</li>
<li>Having over 15 issue queues is confusing for opening issues about their ideas, or finding if the idea has already been suggested.</li>
<li>Community members need a way to see what ideas are approved and what stage of implementation the idea is in.</li>
<li>Community members need a way to suggest ideas that is not "open an issue" since the issue queue can be intimidating.</li>
<li>Members of the <a href="https://drupal.org/governance/drupalorg-working-groups/software/teams">Drupal.org Leadership teams</a> need a way to see what new features community wants to see.</li>
<li>Ideas need early feedback from D.o Leadership teams. </li>
<li>We need a custom tool (instead of g.d.o posts or d.o issues) because we need it to support custom workflow for ideation. We need to sort and filter by various fields, which isn't possible on groups. We need it to have custom fields, different from the issue queue. As well as additional functionality, such as (possibly) voting. We also want this tool to be closely tied and match the changes tool, where we'll track progress of ideas to being deployed.</li>
</ul>
<h3>History</h3>
<ul>
<li>Drupal.org needs to serve a wide variety of target audiences. Highly technical and non-technical people, people who live and breathe Drupal versus people just discovering it for the first time, both individual contributors and organizations that depend on it for their livelihood and to make Drupal actually happen, etc.</li>
<li>It is therefore extremely difficult for anyone (or group of someones) to have a firm grasp on what the biggest pain points are for all of Drupal.org's target audience. While <a href="https://drupal.org/governance/drupalorg-working-groups">Drupal.org Working Groups</a> are helping to set strategy in this area, there is still plenty of room for "bottom up" ideas on how to improve Drupal.org, especially from people who want to work on them.</li>
<li>In 2012, webchick ran an ideation process through an external service called IdeaScale at <a href="http://drupal-association.ideascale.com/">http://drupal-association.ideascale.com/</a> to try and get a general pulse on what people were thinking. 130 ideas were posted, 524 comments, 4114 votes from 408 users.
</li><li>This general process was repeated in a much shorter timeframe in 2013 by the Drupal.org Software Working group at <a href="https://groups.drupal.org/drupal-org-2014-roadmap-brainstorming">https://groups.drupal.org/drupal-org-2014-roadmap-brainstorming</a>. This resulted in 53 ideas submitted, 596 comments, 759 votes from 258 participants. (down about 50%).</li>
<li>Obviously, both of these represents only a small fraction of the overall Drupal community (and mostly "community insiders", largely technical / developers / contributors). We need to do better in engaging a wider pool of our target audience.</li>
</ul>
<h3>Proposed Resolution</h3>
<p>Build a custom Drupal.org ideation tool, in order to improve Drupal.org development process (<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/2141127" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/2141127</a></span>).</p>
<p>Have a single place for all ideas, suggestions and feature requests for Drupal.org. </p>
<p>This ideation tool will be closely connected to the Drupal.org changes tool (<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/2141131" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/2141131</a></span>), just for the ideation part. Once the idea has a proper description and is "approved" by the relevant Leadership team, it can move into the Drupal.org changes tool, for the actual implementation. As it goes through the changes tool workflow, issues will be created as appropriate, and linked back to the change request.</p>
<h3>Remaining tasks</h3>
<ul>
<li>Now, (potential users of ideation tool) Give feedback. *Before May 18 2014*</li>
<li>Now, (Drupal Software Working Group members) Respond to feedback, before May 18, and after. </li>
<li>Postponed on May 18, 2014, (DA staff) Implement tool/create sub issues (between May 18 and May 30)</li>
<li>Postponed until ... July 2014?, Suggest voting mechanism details. Voting to be added later. Initially, google analytics used to gauge interest. <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/drupalorg/issues/2263057" title="Status: Closed (won't fix)">#2263057: Voting on Drupal.org ideas (ideation tool nodes)</a></span></li>
<li>Postponed until specifications are more finalized here in this meta, Implementation discussion. <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/drupalorg/issues/2263117" title="Status: Closed (won't fix)">#2263117: Drupal.org ideation tool implementation</a></span></li>
</ul>
<h2>Specification</h2>
<p><strong>Content type:</strong> idea</p>
<p><strong>Fields:</strong></p>
<ul>
<li>Title</li>
<li>Summary (description of the idea)<br><br>
summary template: benefits, risks, how to measure impact (...)
<pre><h2>What are the benefits?</h2><br><h2>What are the risks?</h2><br><h2>How can we measure the impact of this idea? (metrics)</h2><br><h2>Are additional resources available for discovery/implementation? (volunteer effort, financial backing, etc.)</h2></pre></li>
<li>Status: Proposal (default), In Review, Approved (needs resources), Approved (In Progress: with change request status), Postponed, Duplicate, Rejected, Completed</li>
<li>Link to change request node (filled out after idea has been approved)</li>
<li>Impact: Small, Medium, Large (optional)</li>
<li>Target audience: Developers, Evaluators, Themers, Site builders, etc.</li>
<li>Component: matches those of the changes tool and the structure of Leadership teams (e.g. Developer tools: Project, Developer Tools: Testbot, Community Tools: Planet, Documentation tools, etc.)</li>
<li>Related ideas</li>
<li>Tags (taxonomy) </li>
<li>Share buttons: Tweet this idea, Share on FB, Share on G+, Email to a friend</li>
</ul>
<p><strong>Settings:</strong></p>
<ul>
<li>Comments enabled</li>
<li>Publishing options: Create new revision</li>
</ul>
<p><strong>Permissions:</strong><br>
Authenticated users can create ideas, comment on ideas, edit any idea</p>
<p><strong>How to gauge interest:</strong></p>
<ul>
<li>Google Analytics</li>
</ul>
<h2>Notifications</h2>
<p><strong>RSS feeds</strong></p>
<ul>
<li>Recent ideas</li>
<li>Ideas by status</li>
<li>Ideas by component</li>
</ul>
<p><strong>Automated tweets:</strong><br>
Create twitter account and auto tweet all new ideas</p>
<h2>Email notifications</h2>
<ul>
<li>Subscribe to all new ideas</li>
<li>Subscribe to new ideas per component</li>
<li>Subscribe to comments on all ideas</li>
<li>Subscribe to comments on ideas per component</li>
<li>Subscribe to comments on individual idea</li>
</ul>
<h2>Drupal.org integration:</h2>
<ul>
<li>Dashboard block “Your ideas”</li>
<li>Dashboard block “Ideas for [Component]”</li>
</ul>
<h2>Workflow:</h2>
<ul>
<li>Community member creates new idea in the tool (Status: proposal)</li>
<li>Component maintainer (Member of the relevant Leadership team) can give initial feedback, e.g.
<ul>
<li>this might be a good idea but we need more info (Status: postponed)</li>
<li>this is a bad idea for this and that reason, not going to happen (Status: rejected)</li>
</ul>
</li>
<li>Community member (same or different one) works on more detailed description of the idea, pros and cons, audience, reasons why it is important (Status: In review)</li>
<li>Component maintainer gives feedback:
<ul>
<li>this looks like a duplicate of X (Status: Duplicate)</li>
<li>this is a good idea, should be implemented (Status: Approved (needs resources))</li>
</ul>
</li>
<li>When someone (volunteer, DA staff, DSWG via contractor) decides to actually work on implementing this idea - change request node is created. Status of the idea node is changed to: Approved (In Progress). Status from the relevant change request node will be displayed on the idea node.</li>
</ul>
<p>A couple of mocks of the tool:</p>
<p><img src="https://drupal.org/files/issues/ideas-v4.png" alt=""></p>
<p><img src="https://drupal.org/files/issues/ideas-v3.png" alt=""></p>
> Related issue: [Issue #2141127](https://www.drupal.org/node/2141127)
issue