About the project
The Open SVG Test Suite is a project that aims to produce, through collaboration, a comprehensive test suite for SVG renderer and browser implementations. The intention is for implementors to share their tests to promote interoperability, however anyone is welcome to contribute tests. All contributions to the Open SVG Test Suite must be licensed under the Creative Commons Attribution-ShareAlike Licence.
Any problems, e-mail me at cam (at) mcc.id.au.
Trac site
The Trac site has a wiki that has more information about how to access the tests and the structure of the test suite, a browser of the subversion repository and a bug tracker for filing bugs against the tests.
Mailing list
For discussion about all aspects of the test suite, please use the discussion (at) svgtest.org mailing list (subscribe, archives).
News
Wiki and repository up
January 31, 2006: I've set up a Subversion repository for the test suite and also a wiki for documenting it. Though decisions haven't been made about formats and so on, I'd like people to start adding tests to the repository anyway. At this early stage it won't be problematic to modify the tests when some more concrete ideas about the structure are formulated.
If you want commit access to the repository, create a Trac account and mail me your username.
Project launched
January 18, 2006: The web site for the Open SVG Test Suite has now gone live. Functionality for editing the tests has not yet been added, however you can browse a couple of example tests. At this early stage, everything is open for debate. But specifically, I'd like to hear people's opinions about:
- the structure of the test suite,
- editing the tests with a wiki-style interface (which is what I plan to add) & whether SVN access to the tests should also be given, and
- licensing issues & whether requiring contributions to be CC-BY-SA will impede collaboration.
Please join the mailing list and discuss these issues.
There is not much point getting an account just yet since there isn't much functionality for editing the tests available yet. I'll hold off making any choices regarding the test suite structure until there's been some discussion about it, and I won't create the editing interface until some consensus has been found.
