Contributing to the CSS2.1 Test Suite

The CSS2.1 Test Suite still needs a lot of work, and the CSS Working Group can't finish it all by itself. Anyone can contribute: here are the guidelines.

How to License Your Contribution

Send a message to public-css-testsuite@w3.org stating the following:

I agree to license under the BSD 3-clause license [1] all my
contributions to the W3C CSS Test Suites.

[1] http://www.opensource.org/licenses/bsd-license.php

I also hereby grant to the W3C, a perpetual, non-exclusive,
royalty-free, world-wide right and license under my copyrights
in these contributions to copy, publish, use, modify, and to
distribute my contributions under the W3C Document License [2],
as well as a right and license of the same scope to any
derivative works that are prepared by the W3C or contributors
working on its behalf and that are based on or incorporating
all or part of my contributions.

[2] http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231

This way we have a record that you gave us permission to distribute your contribution under these two licenses.

How to Submit a New Test

You can submit a new test by

  1. Sending us permission to use the test as described above.
  2. Sending the test to public-css-testsuite@w3.org either as a link or an attachment.

Please make sure submissions follow the CSS2.1 Test Suite Guidelines. New tests are subject to the review process. We may ask you to fix problems in your test and resubmit it before adding it to the test suite.

How to Report a Problem in the Test Suite

  1. First check the Known Problems list to see if your problem has already been reported. If it hasn't, then
  2. Send an email to public-css-testsuite@w3.org describing the problem
  3. Ideally, also add it to the Known Problems list once your post shows up in the public-css-testsuite mail archives

How to Contribute a Fix to an Existing Test

To contribute a fix to an existing test, send an email to public-css-testsuite@w3.org with both

  • an explanation of the problem or a reference to a previous message explaining the problem
  • the precise changes necessary to fix the problem (preferably as a diff either against the CVS source copy or against the XHTML1.1 version)

Fixes to existing tests are also subject to the review process.

Other Ways to Contribute

What to Do If You Receive No Response

If you've waited at least a week and your contribution seems to be going nowhere, please complain to the test suite owner (currently fantasai). No, really, please do complain if this is the case; I'm probably just having some trouble staying on top of things and need a reminder or three.

 
test/css2.1/contribute.txt · Last modified: 2008/04/13 13:41 by fantasai
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki