Skip to content

Add Sebastian as CSS 2024 co-editor #11157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
svgeesus opened this issue Nov 5, 2024 · 1 comment
Closed

Add Sebastian as CSS 2024 co-editor #11157

svgeesus opened this issue Nov 5, 2024 · 1 comment
Labels
Closed as Question Answered Used when the issue is more of a question than a problem, and it's been answered. css-2024 The 2024 snapshot

Comments

@svgeesus
Copy link
Contributor

svgeesus commented Nov 5, 2024

@SebastianZ has already been doing a lot of work for this spec, we just need a CSSWG resolution to make it official

@astearns I imagine this can be done async?
@svgeesus svgeesus added Async Resolution: Proposed Candidate for auto-resolve with stated time limit css-2024 The 2024 snapshot labels Nov 5, 2024
@astearns
Copy link
Member

astearns commented Nov 5, 2024

Huh, I thought we had already done this. But I can’t find where, so my apologies @SebastianZ!

As far as I understand, a resolution is not required: chairs can just appoint editors. So I appoint Sebastian Zartner as editor of the CSS Snapshot.

@astearns astearns closed this as completed Nov 5, 2024
@astearns astearns removed the Async Resolution: Proposed Candidate for auto-resolve with stated time limit label Nov 5, 2024
@svgeesus svgeesus added the Closed as Question Answered Used when the issue is more of a question than a problem, and it's been answered. label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Closed as Question Answered Used when the issue is more of a question than a problem, and it's been answered. css-2024 The 2024 snapshot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@astearns @svgeesus