Re: Fwd: validator logo problem (camino)

Amy van der Hiel wrote:

> the link on <mailing list> was to:
> http://validator.w3.org/feedback.html#mailinglist (which didn't lead
> anywhere).

For me, that link leads to this text :

> Discuss and participate
>
> If you are interested in helping to improve this service, by writing code or just providing ideas, you should feel free to join or send a message to our mailing-list.
>
> The public mailing-list to discuss the Markup Validator, Link checker and other tools is www-validator.

which expands to http://lists.w3.org/Archives/Public/www-validator/

> You can subscribe to the list (and unsubscribe), or if you just have a small patch or idea and don't want to join the list, feel free to send it directly to the list. But whatever you do, always use the mail search engine first to check for existing messages on a given topic.
>
> If you just want to have an informal discussion with developers and users of the Validator, you may also join the IRC channel #validator on the freenode network (irc.freenode.net). However, please keep in mind that this is not a support channel.
> Bug reports
>
> The W3C maintains a public bug tracking database known as Bugzilla where developers and other technical users can log bug reports and feature suggestions directly. If you are not familiar with issue tracking systems in general or the Bugzilla bug tracker, send your feedback to the mailing list and someone on the W3C Validator Team will take care of logging your issue as appropriate.
>
> Before you enter a new bug in this database, we strongly encourage you to check that it is not yet in the list of opened issues. Here are a few links that you can use:
>
>     W3C issue tracking system homepage
>     All open Markup Validator issues
>     All Markup Validator issues
>     Search Markup Validator issues
>     New Markup Validator issue
>
> You may also search the bug database directly:
>
> If you encounter an HTML 5 related issue in the W3C validator, before reporting it in the W3C Bugzilla, see if you can reproduce it also with Validator.nu. If you can, report it according to the Validator.nu bug reporting instructions instead. This inconvenience is because the W3C validator uses the Validator.nu engine which is developed and maintained by a different team than the W3C validator to validate HTML 5 documents, and addressing bug reports directly to the team working on the system in question is likely to result in better and more timely responses.

Philip Taylor (not a Validator, just a human being).

Received on Tuesday, 2 October 2012 22:00:07 UTC