PUBLIC MARKS with search standards

an interesting conclusion about how to turn new and casual contributors into long-time community members: the key is to distribute ownership.

To wrap up, there were several things that motivated me to stay active in the Mozilla community: * A belief in the mission of the project — to create a web browser that supports and promotes the use of open standards * An interest in the technology — initially with the Gecko logo as my hook * The feeling of belonging in a community of people with similar interests * The desire to give something back to a project that gave (and still gives) me the best browser in the world for free * The experiences gained by managing a website — HTML, CSS, server configurations, and perhaps most importantly, the English language * The recognition and respect from Mozilla project members for my contributions * The pride of being responsible for an important piece of the project

So, in a nutshell, here is a tick-list for an architecture for participation:

* Open Source Implementations

* Test Suites

* Continuous Integration

* Wiki Driven Documentation

* Small, Lightweight Specifications

* Free and Open Licensing

I've published a manifesto for this approach in the form of a gnomic sampler on http://standeace.com, a contraction of "Standards" and "Peace":

The W3C does not, and never will, publish real standards because it is not a standards organization: It's a CONSORTIUM (you know, that "C" in W3C is there for a reason - look it up!). Standards and Standards Bodies must be endorsed by governments and legally enforceable. W3C recommendations are simply "recommendations". There is no legal consequence to not following or fully conforming to a "recommendation"...

C'est étrange cette manie des participants à la WTF à mélanger tout et n'importe au nom du pragmatisme (plus loin dans son commentaire, Marcos Caceres explique en quoi un "vrai standard" n'est pas pragmatique pour le web). Pour rappel, selon lui l'ISO ne produit pas de standards, pas plus que l'IETF, etc... Sur sa page publique, il indique "I work as a software architect/standards engineer for Opera Software." Selon sa définition, Opera ne supporte aucun standard, donc il est au mieux architecte logiciel. Et en même temps, c'est un hsivoniste, donc il reconnaît qu'il n'y a que les développeurs de moteurs CSS qui savent gérer les mutations d'une structure en arbre, ceux travaillant sur le DOM n'en ayant pas les compétences. Marcos Caceres ne travaillant pas sur le moteur CSS chez Opera, on en déduit qu'il ne sait pas très bien manipuler les structures arborescentes. Donc en fait, selon lui, il est au mieux développeur junior chez Opera.

I did notice however several mentions of the "HTML5 standard" that led me to write this post to remind the community of the current status of the specification, both in practice and on the standards track.. HTML5 isn't a W3C standard. We certainly look forward to the day when it is, but it isn't yet. In fact, the specification, co-authored by Ian Hickson from Google, is still very much a work in progress.

Rappelons que HTML5 est le format "sérialisé à la SGML" du document, pour le standard on devrait écrire HTML 5 (mais Google a plus de mal à le trouver dans ce cas). Et Hickson nous rappelle dans les commentaires comment il peut être pragmatique (cf. hier).

We're done with the tired old fontstacks of yesteryear. Enough with the limitations of the web, we won't have it. It's time to raise our standards. Here, you'll find only the most well-made, free & open-source, @font-face ready fonts. Like any revolution, we aim to make progress, and we need help. If you want to be a part of this free, open-source type movement, you should join us and contribute.

3. The Linked Open Data movement uses open royalty-free standards from W3C.

These do not bind the federal government to any specific supplier.

Starting on or about the third week of April, users still running IE6 or IE7 on Windows XP, Windows Vista, Windows Server 2003, or Windows Server 2008 will get will get a notification through Automatic Update about IE8. This rollout will start with a narrow audience and expand over time to the entire user base. On Windows XP and Server 2003, the update will be High-Priority. On Windows Vista and Server 2008 it will be Important. IE8 will not automatically install on machines. Users must opt-in to install IE8. Users will see a Welcome screen that offers choices: Ask later, install now, or don’t install.