W3C home > Mailing lists > Public > public-qa-dev@w3.org > November 2005

Re: How to write code for W3C

From: olivier Thereaux <ot@w3.org>
Date: Wed, 9 Nov 2005 09:44:44 +0900
Message-Id: <52345801-8B1E-49CB-8562-14A11823EADB@w3.org>
Cc: QA Dev <public-qa-dev@w3.org>
To: Karl Dubost <karl@w3.org>

On 9 Nov 2005, at 05:55, Karl Dubost wrote:
> The first two links are How to write code and how to get involved.  
> The /QA Page will be changed soon once the QA IG rechartering is  
> done and if it's accepted. :) I think we will have a lot to learn  
> from Mozilla.
> The Getting Involved was there, but I would push it in its own page
>     http://www.w3.org/QA/Overview.html#involved

I agree we've made mistakes in this regard.
One goes to /QA/, find "getting involved", then goes to the QAIG  
page, and then the qa-dev page (which does not really give  
instructions to participate). First mistake probably was to separate  
getting involved in QA vs QAIG. Second issue is that there is not one  
process to contribute to software. Each project has its mailing-list  
(or not), its IRc channel (or not), is maintainer (...or not).

It would probably make (more) sense to have a "how to contribute to  
W3C open-source software" in http://www.w3.org/Status
and have other locations (one "writing code" and a "help build better  
software" in the QA home, as well as the qa-dev description page)  
more consistently link to /Status.

> In changing the /QA Home page, I think we could improve
>     * The real estate for information
>     * The design
>     * The labels for accessing the different parts of the site
>         "How to write code" is certainly clearer than "Tools -> Qa  
> Dev".

Yes. The key here I think, as hinted by my comment above, will be to  
not repeat the usual mistake of thinking in terms of W3C internal  

Received on Wednesday, 9 November 2005 00:44:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:26 UTC