Add JohnAlbin as a component maintainer for CSS [#2048925]

Comment	File	Size	Author
#1	mutant-hybrid.patch	422 bytes	xjm

File	Size
mutant-hybrid.patch	422 bytes

Comment #2

JohnAlbin

he/they/他

English

Taipei, Taiwan

CreditAttribution: JohnAlbin commented 24 July 2013 at 00:52

Status:

Needs review

» Reviewed & tested by the community

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

Log in or register to post comments

Comment #3

alexpott

he/they

English

🇪🇺🌍

CreditAttribution: alexpott commented 24 July 2013 at 07:31

Status:

Reviewed & tested by the community

» Needs review

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

Log in or register to post comments

Comment #4

xjm

she/her

English

CreditAttribution: xjm commented 24 July 2013 at 12:38

CSS is not markup?

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

Log in or register to post comments

Comment #5

alexpott

he/they

English

🇪🇺🌍

CreditAttribution: alexpott commented 24 July 2013 at 14:55

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 :)