[META] Remove deprecated modules and themes from the Drupal 10 branch

What's the relationship of this issue to #3118154: [meta] Deprecate dependencies, libraries, modules, and themes that will be removed from Drupal 10 core by 9.4.0-beta1? How can #3227033: Remove Quick Edit from core fit into this since it can't have multiple parents / ancestry?

Adding both as related for now.

Thanks,
-Derek

10.0.x is under development and we are starting to remove things, so this can be active now, but I also don't quite understand the relationship with the other meta.

Updating the IS to list only things that are actually already deprecated

I have the same type of question as #4 and #5, that is, is this issue needed?

With this issue we are tracking the removal of module in two places. Here and the Meta issues tracking the 'deprecation to removal' process for each module, according to the Modules and themes policy, have a step and issue specifically for the 'removal'. That meta also includes the steps to be done post the actual removal, like composer and documentation.

I do see that the new policy for the module deprecation process needs work to identify the version an issue is filed against and will try to get to that this weekend.

Updated the IS to be more clear. Once a module is deprecated, removing it from 10.0.x is a beta blocker for D10. Otherwise, there is no beta blocker.

With the exception of Aggregator and QuickEdit, all module deprecations are 100% optional. This is part of why mixing 9.4.x work and 10.0.x work in the 9.4.x deprecation meta is not correct.

This issue is to track the must-have followups to the deprecations that are already complete.

Add all module removals to the Issue Summary.

Discussed with catch and xjm, the order of removal for Color and Bartik because of the test dependency discussed in the IS of #3301713: Update migration Color tests to not use Bartik. Color will be first followed closely by Bartik.

Fix formatting

Add Farbastic

update link to CKEditor

Is the Book module still planned to be removed from core?
[Policy] Deprecate book module and move it to contrib in Drupal 10

@Chris Matthews, the policy issue you refer to would have to be RTBC before the process of deprecation and removal began.

Moved the following to Drupal 11

Too optimistic, still need some documentation moving.

CKEditor 4 removal is complete!

The remaining work on the themes is to triage the respective issue queues.

Celebrating that removing Bartik is done.

Update IS, Bartik and Stable are complete.

This can be closed now.