[ignore] policy related issue collection

This is just to help me see them all at once.

🌱 [policy, no patch] Define usage heuristics for browser support Active
🌱 [Policy] How to select the minimum required database versions Active
🌱 [policy] Default to requiring the latest stable PHP release available when a new major version reaches beta Active
🌱 [policy, no patch] Drop support for Windows in production in Drupal 11 Active
🌱 [policy, no patch] Target any 11.x API/disruptive deprecations for removal in 13.x Active
🌱 MySQL should no longer be "Recommended" Active
📌 [policy no-patch] Discuss LTS options Active
📌 Defer disruptive 11.3 deprecations for removal until 13.0 Active
📌 [policy, no patch] Update allowed changes to current practice for backport of Test API changes Active

AU

• #3228628: [policy, no patch] Decide on the most optimal process for development, core review, and alpha-level testing of Package Manager (Automatic Updates) →
• 📌 [Policy, no patch] Projects depending on composer plugins will have to update the additional_trusted_composer_plugins setting in package_manager.settings Active
• 🌱 [PP-*] [policy] Allow package manager to work without openssl and/or a valid certificate bundle Active
• 🌱 [policy, no patch] Decide if and when automatic updates should rely only on packagist data to determine installability of modules Active
• 📌 [policy, no patch] Decide if a production level TUF is a requirement for beta-levelcommit of Package Manager Postponed

BC

• #2813311: API versioning: decide & document a backwards-compatibility policy for REST resources →
• 📌 Better define the backwards compatibility/API policy for JavaScript Active
• 📌 [policy, documentation] Clarify Constructor BC policy and document best practices for subclassing other classes Active
• 🌱 [Policy, no patch] Determine and document best practices for providing backwards compatibility code paths expected to be removed in the next major version. Active
• 🌱 [policy, no patch] Determine a best practice for providing BC for internal paths that change between minor releases Active
• 🌱 [Policy] SDC backwards compatibility policy Active
• 📌 CKEditor 5 backwards-compatibility policy needed Active

Composer

• 🌱 [policy, no patch] set miminum composer.json version constraints based on first minor release Active
• #3188544: [policy discussion] Address Composer namespacing issues when extensions move between core and contrib →

CSS

• 📌 [policy, no patch] Discuss how to update 3rd party CSS libraries while still proving BC for stable themes Active
• 🌱 [Policy] Do not use dev-master as a dependency for composer packages Needs work
• 📌 [Policy] Dependency evaluation critera Active
• 🌱 [policy, no patch] Automatic Updates & Project Browser, should NOT handle dependency management for projects not known to Composer Needs review

Deprecate

• #2713545: [policy, no patch] Are changes to ContentEntityBase base field definitions API breaking →
• 📌 [policy no patch] Make it possible to mark plugins as deprecated Needs work
• #2927251: [policy, no patch] Decide how to deal with methods needing to be moved down an interface hierarchy →
• 🌱 [policy, no patch] How to deprecate unused dependencies Needs review
• #3135100: [policy and meta] Provide a proper mechanism for deprecating modules and themes →
• #3168266: [policy & patch] Policy to deprecate a field setting →
• 🌱 [policy, no patch] Maintenance of JS in core Postponed: needs info
• 🌱 [policy, no patch] Updating core JavaScript APIs gracefully. Postponed
• #3228433: [policy, no patch] Add a more integrated process for adding rector rules for deprecations →

Extension

• ✨ [policy, no patch] Change experimental module policy, require update scripts for all experimental modules Active
• #3027053: [Policy, no patch] Allow experimental modules to use final to limit public API during development phase →
• 🌱 By default deprecate non-experimental modules that are used by less 5% of sites before the next major version Active
• 🌱 [Policy] Move Shortcut module to contrib Needs review
• 🌱 [Policy] Move Search module to contrib Active
• 🌱 Should we deprecate Stable9? Active
• 🌱 [Policy] Remove pgsql module from core and move it to contrib Active

Form

• 📌 [policy] Determine design for forms that have multiple actions Active

Gate

• #3229101: [policy, no patch] Image optimization performance core gate →

Issues

• 🌱 [policy, no patch] Establish a system for dealing with feature requests Active
• 🌱 [Policy, no patch] closing older issues Active
• 📌 [policy, no patch] Decide policy related to use of novice tag Active

Security

• 🌱 [policy] Treat username enumerations as security bugs that require Security Advisories Active
• 🌱 [policy, no patch] Should core use gpg-signed git annotated tags Active
• ✨ Strengthening Drupal: Protecting Content from AI Scrapers and Bots Active

Testing

• 📌 [policy, no patch] Discuss usage of @codeCoverageIgnore Postponed: needs info
• 🌱 [policy, no patch] Require functional test coverage for keyboard accessibility Active
• 🌱 [Policy] Mock external APIs/resources instead of depending on them directly in tests Active
• 🌱 [policy, no patch] Improving the test suite Active
• 🌱 Document when update tests are needed Active
• 📌 Consider dropping Nightwatch in favor of Functional Javascript tests Active

UI

• ✨ [policy, no patch] Revise the Druplicon logo Needs work
• 🌱 [policy] Rephrase input device-specific language (remove e.g. "click") Active

Other

1. 🌱 [policy, no patch] Decide and document guidelines for using string context Needs review
2. #1462472: [policy] Define standard for merging in branches from core sandboxes →
3. 📌 [policy no patch] config save format and default yml file format and coding standards Active
4. 📌 [policy] Inclusion criteria for CLDR territories in CountryManager::getStandardList() Active
5. 📌 [policy, then patch] Standardize service names Postponed: needs info
6. 📌 [policy, no patch] Trait strategy Postponed: needs info
7. 📌 [policy] Document Libricon semantics, including examples Postponed: needs info
8. 🌱 [policy, no patch] Require Node.js for a future Drupal major version and rewrite some of Drupal's UI code from PHP to JS Postponed: needs info
9. #2727011: [policy, no patch] Private vs protected, and the role of inheritance →
10. 🌱 [policy, no patch] Runtime Assertions Policy Postponed: needs info
11. ✨ [policy] Add a privacy policy to Drupal core Postponed: needs info
12. ✨ Add $entity->toUrl() and $entity->toLink() methods to allowed methods list in Twig sandbox policy Needs work
13. 🌱 [policy, no patch] Use "prefers-reduced-motion" media query to disable animations Active
14. 🌱 [policy, no patch] Distinct methods with and without exception? Postponed: needs info
15. #2956549: [policy, no patch]: Atomic behavior objects →
16. ✨ [policy, no patch] Reduce code reuse in dependency injection Postponed: needs info
17. 🌱 [policy, no patch] Publishing / Maintaining JS libraries produced by Drupal that do not have a dependency on Drupal Needs review
18. 🌱 [policy, no patch] Use declare(strict_types=1) in new code Active
19. 📌 [policy] Service autowiring - decide approach for multiple service implementations based on the same class and different arguments Needs work
20. 📌 [policy, no patch] Decide on policy regarding use of Events class with string constants for event names or class names instead Active
21. 📌 [policy, no patch] relax patch size policies Active
22. 🌱 [policy, no patch] Allow docblock to be removed when modifying constructor params Active
23. 🌱 Promote Drupal API Client Packages to Drupal NPM Namespace Active
24. 🌱 [policy, no patch] Explicitly cast all uses of database returned values Active
25. 🌱 [policy] Service names should use class names and use autowiring Active
26. 📌 [policy, no patch] Hook classes should not be marked final Active
27. 📌 [policy, no patch] Encourage hooks over event subscribers Active
28. ✨ [PP-1] Add $entity->uuid() methods to allowed methods list in Twig sandbox policy Postponed
29. 📌 Drupal should have a publiccode.yml file Active

Closed in 2024,

2. 🌱 [Policy, no patch] Normalize on usage of is_callable() instead of function_exists() Needs review
3. 📌 [Policy, no patch] Never require descriptions if a title/label is already required Postponed: needs info
4. 📌 [policy,meta] Automated xhprof based profiling for Drupal core to enhance performance core gate Postponed: needs info
5. 📌 [policy] Document when we should use each CSS unit Postponed: needs info
6. 📌 [policy, no patch] Standardize on src/Plugin/$vendor/$pluginType for plugin directories Closed: outdated
7. 📌 [policy, no patch] Are CSS changes change record worthy? Active
8. 🌱 [policy, no patch] Convert all entities that extend ContentEntityBase to be revisionable Closed: outdated
9. 🌱 [policy, no patch] Update patch backporting workflow to be compatible with semantic versioning Postponed: needs info
10. 🌱 [policy, no patch] Branch labels for core Postponed: needs info
11. 🌱 [policy, maybe patch] Clarify backport policy for testing framework changes, including new BTB tests Closed: outdated
12. 📌 [META] Enable layout builder for form displays, and deprecate field_layout Postponed
13. 📌 [policy] Document development dependencies Needs review
14. 🌱 [policy, no patch] All new Drupal 10 code should use appropriate type hints wherever possible Needs review
15. #3159972: [policy, no patch] Require Composer 2 for Automatic Updates while still supporting Composer 1 for Drupal 9 generally →
16. 📌 [policy, no patch] Secondary subdomain for viewing oEmbed content is confusing and pointless Active
17. #3218119: [policy, no patch] To enable or use Automatic Updates, require "proc_open" to not be disabled →
18. 📌 [policy, no patch] Backport policy for Starterkit theme changes Needs review
19. 📌 [policy, no patch] Decide how to handle parameter renaming now that PHP 8 allows it to be used as an API Active
20. 📌 Add php-tuf/php-tuf to core governance — for experimental Automatic Updates & Project Browser modules Needs work
21. 🌱 [policy] [PP-1] Branching strategy for post-11.0.x 10.x branches Active
22. 📌 Subsystem maintainer permissions on GitLab Needs work
23. 🌱 [policy] Decide on format of commit message Active
24. 📌 [policy review 2024-10] Testing core gate, heuristics section Active
25. 📌 [policy] Core module machine name and UI labeling for Automatic Updates Active
26. 📌 [policy, no patch] Clarify deprecation policy 3.2 Active
27. 📌 [Policy] Define explicit Drupal 10 end of life date of 2026 December regardless of Drupal 12 release Active