CSS current work & how to participate (original) (raw)
If you want to help
The preferred way is to raise issues via GitHub. (You will need to create an account on GitHub first.) Github contains copies of the editors' drafts of the CSS specifications and ‘Houdini’ APIs.
The contributor guidelines explain in more detail what role GitHub issues play in the development of CSS specifications.
There is also the archived mailing list www-style@w3.org. You can subscribe yourself. On the mailing list you will find also the agenda and the minutes of the meetings of the working group. Please, don't use this list for questions of the type How do I… Use comp. infosystems. www. authoring. stylesheets ("ciwas") or see ‘Learning CSS’.
On the mailing list, you will be talking to many people, many very busy people. Before you post, please, search the archive to see if your great idea has maybe already been discussed. Follow the usual netiquette and W3C's policies on spam, attachments, etc.
If you are sending comments on a specific CSS module, please prefix the subject of your message with the appropriate spec code (given in the ‘Status of this document’ section) in brackets, e.g. ‘[css3-flexbox] error in margin calculations’. This will help the editors find and track your comments.
Laurens Holst (a.k.a. ‘Grauw’) maintains an FAQ for www-style. (For additions, please, contact Laurens directly. Laurens is not associated with W3C.)
If you work for a W3C member organization, you can also join the CSS working group and come to its meetings. To participate, you need to commit to (on average) 1 day per week. Contact me (Bert Bos) or your organization's W3C contact person. The group's minutes are public and posted on the CSS WG blog.
There are many ways to keep up to date with new publications by the CSS WG. The ‘What's new?’ section above shows the most recent drafts and it also has an Atom feed. Publications are announced on the CSS WG's blog and its
Atom feed, and the group's
Mastodon account. First drafts from all W3C working groups appear on the public-review-announce mailing list and its RSS feed. The latest publications from all W3C working groups are at the top of the Technical Reports page, which also has an
RSS feed.
About the test suites
The CSS working group intends to spend a lot of time on developing the CSS test suites along with the CSS specifications. By providing a test suite for each module as soon as the module is published, we hope not only that CSS implementations will conform to the specification much earlier, but also that people will have an easier time understanding the formal text of the spec.
The test suites have their own archived mailing list public-css-testsuite@w3.org. Please send error reports, test case submissions, and any other questions and comments about the CSS test suites there. Elika Etemad maintains the CSS Testing Wiki with more info for contributors.
Raising issues via GitHub is also possible: see the Web-platform tests repository.
Mark-up conventions
The source mark-up of the specifications follows certain conventions (which is useful for automatic processing).