[policy, no patch] Deprecate Stable9 and move to contrib

If deprecated is the intention to move it to a contributed project or just delete?

@quietone we'd need to move it to a contributed project as we did for stable.

@catch, thanks.

Adding tags. Since @markconroy is the Stable9 maintainer, this already has subsystem maintainer approval.

I don't know that markconroy is in favor, I think he created this to track catch's discussion, but I don't want to speak for him.

Adding tag back in that case.

I am in the same boat and have been subtheming stable9 for the past few years.
The "create the bare minimum and just overrides the templates that you want" reasoning is what I liked about doing it this way.
Just me chiming in incase it's relevant.

Per #3158669-49: [Policy] By default deprecate non-experimental modules that are used by less 5% of sites before the next major version stable9 is used on approximately 2.8% of Drupal 11 sites.

Tagging for 11.4.0 release target because if we get this done, we can remove it in 12.0, otherwise it will need to wait until Drupal 13.

Reminded of this because every time we move some CSS around, stable9 tests fail unless you also move the CSS around in stable9, e.g. #3565297: Move 'display link' CSS to its own views library.

Removing the RM review tag, this will make theme improvements easier to work on in core without having to keep track of a relatively complex bc layer and duplicate files.

+1 to remove, we have starterkit and we don't want to have to maintain this in core.

All the arguments point to it being the most logical step to remove it, so signing off as a Drupal core product manager too.

All the sign-off have been given here.

The work to deprecate this is being done in #3560200: [meta] Tasks to deprecate Stable 9

I am sad about this move and I hate the Starterkit method.

I like (like #3) creating a theme based on Stable or any other existing theme, so that I don't need to start from scratch.

I appreciate Classy and Stable in the contrib form, but once in contrib, development and enhancements drops to almost zero.

Well, moving stable9 to contrib will make it very stable.

stable9 doesn't include any CSS or templates that core doesn't ship with itself, so it is really the same as starting from scratch, the difference is in stable9 the CSS and templates don't get updated for core improvements (except when it does sometimes to fix bugs etc.)

Starterkit has stable9 set as its base theme?!

name: Starterkit theme
type: theme
'base theme': stable9

We might deprecate Starterkit as well.

#3560200: [meta] Tasks to deprecate Stable 9 is open so I think we can mark this one fixed.