Dear all,
(with apologies for the cross-posting, let's try and keep replies on
only one of the lists)
I now and then get to talk with some of you, often heavy users of the
validators, and who'd like to get involved and "give back" to the
validators, but don't feel that they have the time/skills to actually
code.
Some of you choose to subscribe to the mailing-lists and do a great
job at supporting other users. That's one excellent way to help, many
thanks to you.
Another thing that can be done, and is perhaps less well-known, is to
monitor the www-validator-cvs mailing-list:
http://lists.w3.org/Archives/Public/www-validator-cvs/
This medium-traffic list is not a discussion forum, instead, it gets
copied whenever the code of our validators is modified in CVS, or
when there is activity in bugzilla regarding one of the validators.
Reading/subscribing to that list means that you can:
* keep an eye for obvious mistakes in code changes (if you are
knowledgeable in perl or java)
* help respond to bug reports sent to bugzilla directly, not through
the mailing-list
The only "rule" to know is that the discussion generally doesn't take
place on the www-validator-cvs mailing-list. If you want to reply to
a bug report, there will be a link to bugzilla in the mails. If you
want to comment on a code commit, better quote the piece of code and
send mail to the relevant validator's discussion list, or to the
smaller developers' mailing-list:
http://lists.w3.org/Archives/Public/public-qa-dev/
www-validator-cvs (and public-qa-dev) is open to subscriptions - no
barrier for entry. If you feel you can make even a small difference
by helping there, either through code review or keeping an eye on bug
reports, feel free to join in.
Thank you.
olivier
--
olivier Thereaux - W3C - http://www.w3.org/People/olivier/
W3C Open Source Software: http://www.w3.org/Status