Add field on projects to specify Drupal 9 plan summary and instructions how to help
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3046058. -->
Reported by: [gábor hojtsy](https://www.drupal.org/user/4166)
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>With the Drupal 7 to 8 transition, we had the Contrib porting tracker at <a href="https://www.drupal.org/project/contrib_tracker">https://www.drupal.org/project/contrib_tracker</a>. That was in many ways a hack. It would be great to give control to project maintainers about their plans. We can automate checking if we found any compatibility issues so we can display the state, however the plans of the maintainer we don't know.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Add a textarea on project nodes where project maintainers can specify their plans for Drupal 9 or a textfield where they can link to a page/issue with their Drupal 9 plans to learn more. Some possible things people could explain here are:</p>
<p>1. Leave this project alone now, I don't have bandwidth for this, will start thinking about it later in 2020.<br>
2. For Drupal 9 there is a better project at X, see that.<br>
3. I need funding to work on the Drupal 9 port, here is my funding mechanism (hire me, donate to this open collective, patreon, etc)<br>
4. I prefer working in a big megapatch or split patches like this. Also see the existing porting issues at [link]<br>
5. Get involved in the Z initiative to help port this project.</p>
<p>We'd love to display a pointer to these instructions in the Drupal in-site Upgrade Status D8 module so people using that to asses site readiness can directly be informed about plans of maintainers and maintainers can get the most value. Eg. no random patches when they are not necessary, too early or too distracting. Possible funding when maintainers need it, etc.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<p>Finish drafting and reviewing.</p>
<h4>Deployment</h4>
<ul>
<li>Bluecheese deployment for <a href="https://git.drupalcode.org/project/bluecheese/commit/88f8f7e018cd124d7f045f4e45d8b98df42d8280">https://git.drupalcode.org/project/bluecheese/commit/88f8f7e018cd124d7f045f4e45d8b98df42d8280</a></li>
<li>Add fields in production and export</li>
<li>Deploy other drupalorg changes</li>
</ul>
<h3 id="summary-ui-changes">User interface changes</h3>
<p>Projects would have a new field. The content of this field would be displayed in a new "Drupal 9" section of project pages (where the project maintainer filled it in).</p>
<p><strong>For project maintainers:</strong><br>
Label: <code>Drupal 9 porting info</code><br>
Description: </p>
<pre>The Drupal 9 porting status of your project. For example:<br><ul><br><li>Help port this project at [#issue number]</li><br><li>Identified issues are not yet actionable. See [link]</li><br><li>Read more about this project’s readiness at [link]</li><br><li>Fund the port of this project at [link]</li><br><li>Use this project instead: [link]</li><br></ul></pre><p><strong>For people viewing the project page:</strong><br>
<img src="https://www.drupal.org/files/issues/2019-05-10/Screen%20Shot%202019-05-10%20at%204.23.44%20PM.png" alt="Screenshot"></p>
<h3 id="summary-api-changes">API changes</h3>
<p>None.</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>New field on project_module, project_theme, project_distribution nodes.</p>
issue