Add field on projects to specify Drupal 9 plan summary and instructions how to help

+1 to all this.

A text area seems good, instead of forcing a link to a separate page. Might not be too much to say, so let folks say as little or as much as they need.

I'd be happy for a very short doc page that includes the list of example topics from the summary here, and we link to in the help text on the field.

Thanks,
-Derek

Discussing this with @Mixologic, he had concerns that we're exposing a lot of data here, and data that contains a lot of conditional logic (plural vs. signular, etc.). The bulk of the people visiting this page are not contributors to Drupal, but end users looking for easily digestable project info.

Would be perhaps better/simpler to do something more like:

[Yellow warning] Drupal 9 is planned to be released June 3, 2020. This project has detected compatibility issues with Drupal 9. [Read for more info]

[Blue box] Drupal 9 is planned to be released June 3, 2020. This project has no detected compatibility issues with Drupal 9.

And then "More info" outlines the specific issues, probably in a style akin to what Upgrade Status us doing @ #3040307: Design a "readiness report" for Drupal 8 => 9 migrations along with the text from the maintainer at the top of that page, if present. (In lieu of that, a link to general "how to port a module to Drupal 9" instructions.)

Adding credit where credit is due! :)

The next step on this issue looks like adding the field for maintainers. I’ll need

• The field title, maybe made generic in hopes that this plan works for D10 and later, too.
• The field description, potentially linking to a page with templates and more explanation.

And does this mean we are removing the contrib_tracker messages?

make the default value a display dynamic default value rather than a field default value, because otherwise we'll end up with any edited project get this and very hard to fix the link, etc. later.

I believe editing existing projects will ignore the field’s default value. They will be blank, unless we back-fill data (which we won’t), or form alter it in for projects last updated before the time this launches.

Updating Data model changes in the issue summary.

Projects are actually 7 content types. The ones I didn’t put in the issue summary to get the new field are:

• project_core - gets a pass
• project_drupalorg - community projects, not code for computers
• project_theme_engine - maybe we do want this?
• project_translation - deprecated

Adding the field_create_field()/field_create_instance() calls to make the field. This is the least-performance-degrading way to deploy new fields to Drupal.org.

Putting drafts of the relevant field configuration under User interface changes in the issue summary.

For maintainers, this currently looks like

Also updating Remaining tasks in the issue summary to add deployment notes.

Pushed a branch with the additions to the project page, which looks like:

Splitting off #3054064: Run weekly deprecation testing on Drupal 8 compatible drupal.org projects and add report on project page for adding the deprecation counts later.

And setting this to needs work since this could use a bit of review, and the field description needs copy.

Ok, Gábor and I met at #drupalcampby, and here's what we came up with:

• Help port this project at [#issue number]
• Identified issues are not yet actionable. See [link]
• Read more about this project’s readiness at [link]
• Fund the port of this project at [link]
• Use this project instead: [link]

Changes:

• Reorder according to estimated frequency that they come up
• Move links to the end so people don't need to futz with HTML
• Specifically call out "not yet actionable" ones, since with core support policy that will come up a lot.
• Tweaked the wording some

This should be good to go live! Thanks @drumm!

Another aspect we discussed was whether to put the D9 notice on all project pages, regardless of the content of the field.

Originally, I thought we should do that, linking to https://www.drupal.org/node/3032484 for more info on how people can get involved fixing things they see. However, @Gábor Hojtsy noted that until we get #3054064: Run weekly deprecation testing on Drupal 8 compatible drupal.org projects and add report on project page done, there's very little value in just blasting people in the face with this field unless there's actual info in there from the maintainer. I agree! ~50% of projects are already Drupal 9 ready and don't need any action. And there are better places to raise awareness about Drupal 9 coming (like the Drupal project page, maybe the download pages, etc.) than individual project pages.

Copying #26 into the issue summary for the full field description:

The Drupal 9 porting status of your project. For example:
<ul>
<li>Help port this project at [#issue number]</li>
<li>Identified issues are not yet actionable. See [link]</li>
<li>Read more about this project’s readiness at [link]</li>
<li>Fund the port of this project at [link]</li>
<li>Use this project instead: [link]</li>
</ul>

Final set of fields for field creation.

This has been deployed.

Not the best example, I put a value in for this project https://www.drupal.org/project/drupalorg

very good plan :)

This looks great, very clean and to the point, big +1 from me :)