The W3C is one of the primary standards bodies that works on Web standards. Founded in 1994 along with the inventor of the Web Sir Tim Berners-Lee, it is a member based consortium originally modeled after the X-Consortium, with the stated aim of helping to "lead the Web to its full potential". Its 465 "member orgs" are various types of organizations, foundations, academia and companies. In late 2011 a movement in Web Standards began to take shape - seeking to help reform the things that many of us thought were broken. This meant creating a common/shared vision across several standards bodies, changing ideas about where successful and lasting standards come from and how they are made and really stressing the importance of Web developers (who weren't themselves members) to that equation. Lots and lots of positive change has happened at many levels, and lots more progress toward change has been set into motion but isn't yet complete and - if you'd like to see it continue, we could use your help.
Everything about how it works is based on a series of rules codified in a thing called "The Process Document." You can sort of think about them as "the laws" that govern the W3C. It's boring, I know, but it's crucially important if you want to really affect change to how the W3C works.
In the US, if you want to change or pass a law, it begins with a Bill. A bill is effectively, the text of the proposed change. If it can get a number of individuals in Congress to support it, it can eventually go to the Congress for a simple "yes" or "no" vote. Most countries (even localities and the United Nations) have similar concepts, but they use different terminology. So, incase the analogy/terminology is a little too culturally biased, here's a fun primer that a lot of US children saw when I was growing up that explains the ones I'm using:
In many ways, the W3C doesn't work dissimilarly: If you want to change the the way that the W3C really "works" you ultimately need to change the "laws" (the Process Document itself). Assembling a proposed "bill" begins with drafting a legitimate proposed change and building a number of co-supporters and taking it to the "congress" for consideration and a vote. In W3C terms, the "congress" are called the "Advisory Committee" - more specifically, the "Advisory Committee Representatives" - one per member organization. A large number of these members are assembled once per year at the W3C Technical Plenary And Committees meeting (TPAC).
An Advisory Committee Representative's job is to officially liason between W3C and individual member organizations. They are the one person empowered to "represent" their organization in an official capacity, including delegation to name people to working groups, sign off on IP policies, and... to cast their vote on things like a proposed change.
Within the W3C, the job of managing all of this - getting a "bill" together with a number of co-sponsors, building some support, bringing it to the "floor" at TPAC answering questions and so on so that it can come to a vote is placed upon a group called the "Advisory Board" (or AB). The AB also plays an important advisory role to the W3C staff itself on strategic issues.
In deep, and deeply nerdy ways, the AB is important if you want to affect fundamental changes.
The AB is itself is a (mostly) elected group of nine people. So, if you want to affect real, substantial and lasting "process" changes at the W3C, the first stop is the AB.
For most of the history of the W3C, all of this was "inside stuff" - that is, outside of the W3C, it was unknown. But then, around 2012, we began appealing to Web developers to help make our desires known under the pretense that, like Congress, membership to some extent must represent you. Without your support and adoption, they have very little - and it's worked. In nearly every election, "reform" has progressed and the opposition has slowly diminished. Groups like the AB have increasingly come to better represent us - they've also gotten more diverse and slowly, but surely things we have made substantial progress. The W3C is more interested in developers, in outreach, in how to include our voices. Incubation of ideas that includes developers is one thing that our AB have successfully advocated. Because of our efforts, even the quality of candidates who run has improved. But we're not there yet. As you can imagine, getting substantial change through is a long, dull and arduous process.
Currently, there is an election underway for the Advisory Board. 4 of the 9 seats are up for grabs and it once again falls to developers to show up and advocate if we want things to continue.
Each of the seats that are up for election have incumbent candidates, but we have 7 candidates for only 4 seats. You can have a look at all 7 official candidate statements made to the ACs asking for their votes.
For the most part, I believe that most of the new candidates will be less successful toward the aims we've been supporting - worse: Progress is much more easily lost than gained.
Except for one: Natasha Rooney. Natasha has been involved in numerous standards bodies and for quite a while she has stood out to me as someone who would be a great asset to the AB. I've personally encouraged her to run in the past, but the timing just wasn't right. But now, she is. To the best of my knowledge, she was the first (and I believe currently still the only) new candidate to publicly post a statement which I believe speaks for itself.
That's why I believe that the strongest slate of 4 is both largely stable and includes Natasha. After a lot of consideration, I most strongly support these folks for AB:
- Mike Champion
- Chris Wilson
- Natasha Rooney
- Judy Zhu
It may surprise some that this list doesn't include Charles McCathie Nevile as I have actively campaigned for him in the past. I'm thankful for his contributions and efforts and I'd actually largely happy for all of them to be re-elected. He's a good friend and I greatly respect all that he does. I'm not specifically opposing him, but the reality is that there are only 4 seats and, as he says in his statement: He's been there longer than anyone else and he does a crazy lot of other important stuff for the W3C. Given all this, this might be a great time to introduce some new energy and give him some space to focus on those other roles for a time. At least, that's what I think would be the best receipe for most success right now. This W3C election will also include a form of preferential voting, which is an effort he championed for a long time and is now in place, so ACs can be quite expressive with their own votes.
It's this simple: Share your support of whomever on social media. If you know anyone who works for any of the 465 W3C Member orgianizations and want to reach out to them directly, that'd be helpful too - especially if you know an AC rep (the list of AC reps is private, but some list it in their profiles). Share your thoughts, be part of the conversation. If Web developers speak up, history shows that people will hear you.