Contrib.social

[meta] [upstream] Prioritized CKEditor 5 upstream blockers

Open on Drupal.org →
Created on 9 February 2023, almost 2 years ago

This issue centralizes the coordination and prioritization for all issues tagged or — i.e. issues that require coordination with the CKEditor 5 team upstream.

@lauriii and @Wim Leers did the prioritization in a Google Spreadsheet. For each issue, we specified:

  • Reach (% of sites affected
  • Impact (1–10, with: data loss = 10, semantics loss = 9, inconvenience = 1)
  • ⇒ multiply these to get a "Drupal priority" → color coded based on this: red = very high impact, orange = high, yellow = medium, gray = low
  • Effort to fix on Drupal side to determine if we should work around the problem on the Drupal side instead (0–1 — impossible/unmaintainable = 1, feasible = 0.5, easy = 0.25)
  • ⇒ multiply the effort with the Drupal priority to get a "CKEditor 5 priority" → sorted based on this

This gives us an ordered list of issues, to clearly indicate which CKEditor 5 issues are most important for the Drupal ecosystem/community to get fixed.

Prioritized list

⚠️ The top 5 have a significantly higher priority than the bottom 9!

🌱 Plan
Status

Active

Version

10.1 ✨

Component
CKEditor 5  →

Last updated about 24 hours ago

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities