The Core Leadership team is working towards doing a regular review of the core extensions once per major cycle. The team already has a process to discuss extensions as a whole, in regard to removing, and this issue is to allow the same for all contributors.
When thinking whether and extension should stay in core or not one must take into account how the extension fits with the Drupal Strategy. Also to think about are the capability the extension provides to a CMS, the strategic value of the extension, and the maintainability of the extension. And then be aware of what contributed projects exist that provided that same functionality.
Proposed resolution
Contributors who think an extension should be removed should comment here as the first step.
When the Core Leadership team completes their review the results will be added here. That and contributor discussion will be used to decide which extensions should have a policy issue where the decision to remove or not is made. That policy issue is the one that needs sign-off before the extension can be deprecated and removed.
Close this issue by the time Drupal 12.1.0 is released.
Note that the Core Leadership team has not yet schedule when their review will be done.
Candidate extension
Remaining tasks
Un-postpone the following when the Core Team completes their extension review.
Comments
Comment #2
quietone commentedComment #3
quietone commentedComment #4
larowlanI think it's time for comment module
Comment #5
nicxvan commentedWith canvas, I wonder if layout builder and layout builder discovery should be reviewed?
Comment #6
larowlanI don't think canvas belongs in core but I agree that layout builder makes sense outside core as it's a product feature
Comment #7
nicxvan commentedI agree with 6, I didn't mean to imply canvas belongs in core.
Comment #8
catchThere's some discussion about removing block UI, I don't think we have an issue for that yet but adding a couple of pre-requisites as related issues.