Our base system CSS is a thing, but it has no component maintainer.

JohnAlbin indicated he was willing to take on this role.

CommentFileSizeAuthor
#1 mutant-hybrid.patch422 bytesxjm

Comments

xjm’s picture

xjm
she/her
Primary language English
commented
StatusFileSize
new mutant-hybrid.patch422 bytes
johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Status: Needs review » Reviewed & tested by the community

I'd be shocked if the testbot came back with a failure.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Status: Reviewed & tested by the community » Needs review

What's the difference between this and Markup (that sun currently maintains according to maintainers.txt)?

xjm’s picture

xjm
she/her
Primary language English
commented

CSS is not markup?

Edit: It's enough not-markup to have a separate dropdown item in our component field.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Status: Needs review » Reviewed & tested by the community

Yep was a bit tired my I wrote that... what I was trying to express was that we should be wary of adding new singly maintained components to MAINTAINERS.txt. And I think we might get a better result if we group logically related things together, for example, CSS and markup. By better result I mean more ownership of parts of core.

However @xjm rightly points out we already have a CSS component so I guess let's move on here :)

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Status: Reviewed & tested by the community » Fixed

Committed 812318d and pushed to 8.x. Thanks!

xjm’s picture

xjm
she/her
Primary language English
commented
Issue tags: +Component maintainers

Automatically closed -- issue fixed for 2 weeks with no activity.