Difference between revisions of "Webizen"

From W3C Wiki
Jump to: navigation, search
(Name: Added suggestions from Twitter)
m (Suggestions from AC meeting: Changed list to alphabetical order)
Line 72: Line 72:
=== Suggestions from AC meeting ===
=== Suggestions from AC meeting ===
* Webzealot
* Zombie
* Weeble
* Webbro
* Webbro
* Webelo
* Webchamp
* Webchamp
* Webelo
* Webzealot
* Weeble
* Zombie
While we strive to find a name that most like, it would also be helpful to select (or create!) a name that has some "sparkle" -- a name that will stand out and be distinctive. See, for example, the brainstorming below, seeking to imagine clever marketing phrases.
While we strive to find a name that most like, it would also be helpful to select (or create!) a name that has some "sparkle" -- a name that will stand out and be distinctive. See, for example, the brainstorming below, seeking to imagine clever marketing phrases.

Revision as of 13:26, 10 June 2014

< Headlights 2014

DRAFT - DRAFT - Help us! - DRAFT - Help us! - DRAFT - DRAFT

"Not just a Websumer, I'm a W3C Webizen!"

We are looking to explore a "Webizen" program. For a nominal small fee, an individual would get some benefits. This task force will explore whether such a program is viable and what the benefits should be (e.g. user groups, user conferences, T-shirts, ID-cards, a path to provide user input to Working Groups, recognition as a Webizen for participants in W3C Working Groups and Community Groups.)

To join, subscribe to public-webizen@w3.org, add your name to the #Participants list.


  • Open and public: This task force is open to the public and will operate until June 2014. Come and build the Webizen program!
  • e-mail: We welcome feedback on the public-webizen@w3.org mailing list archive and may even use your feedback in our work.
  • IRC: There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([1] Pre-filled Web interface to IRC]).
  • Twitter: W3C_Webizen


At TPAC 2013, in response to a question from the floor (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.

The current proposal, for a "Webizen" mode of participation, is not a Membership program. But it does provide certain privileges - for example participation (via representation) in the Advisory Committee (AC).

W3C Management explored the concept of “Individual Membership” – which would (for a fee) give individuals rights as Members; notably the ability to participate in W3C Working Groups. However, this key desire – to have appropriate individuals participate in W3C Working Groups – is already possible (without a fee) via Invited Experts (IE). Thus, individual membership is not necessary to participate in a Working Group. Further, we do not want to deprecate existing IEs, nor possibly ask them to suddenly pay a fee. Patent rights also add a complexity to the concept of individual membership -- which is already handled with the Invited Expert process; hence another reason to stick with that status for selected individuals participation in Working Groups.

Another type of status is 'W3C Supporters'. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.

Concept of the Webizen program

The idea of the program is to allow individuals to affiliate with the Web standards community by establishing a new designation of Webizen. This is not a Membership benefit and does not confer W3C Membership rights. Instead, we seek to make available a new means to congregate as a community.

As it is not a Membership benefit, 'Webizen' is an affiliation that may be chosen not only by current outsiders of the W3C community, but even individuals working for Member organizations or the W3C Team.

To make it a meaningful gesture, a token fee of e.g. $100 US per annum (or equivalent in another currency) is suggested. To make this a fair request, a key design goal is to create a package of benefits which arguably are worth $100. We intend to establish a sliding-scale fee to enable greater global participation. At the same time, the program must not lose money, so we must design the benefits accordingly.


Some people like the name "Webizen", others don't. It would be useful to have a collection of potential names so that we can shop them around and get community feedback. This is a collection place for candidate names. So far, the candidates are:

  • Webizen
  • W3bizen
  • W3Connector
  • Constituents
  • Constituent of the Web
  • Citizens
  • Citizen of the Web
  • Friend of the Consortium

Suggestions from this Twitter thread

  • Agent
  • Collaborator
  • Community Member
  • Comrade
  • Contributor
  • Delegate
  • Friend of the Web (FoW)
  • Homo webus
  • Individual Member
  • Spider (building the Web)
  • w3c.node
  • W3mber
  • Webbee
  • Webdoer
  • Webelong
  • Webholder
  • Webien

Suggestions from AC meeting

  • Webbro
  • Webchamp
  • Webelo
  • Webzealot
  • Weeble
  • Zombie

While we strive to find a name that most like, it would also be helpful to select (or create!) a name that has some "sparkle" -- a name that will stand out and be distinctive. See, for example, the brainstorming below, seeking to imagine clever marketing phrases.

In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.


  • Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers
  • Increase affiliation with W3C for this set of stakeholders
  • Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations
  • Increase general public review of web technology in general and W3C Reports
  • Provide a means for the general public to influence W3C agenda and priorities

Package of benefits

The key question for the Webizen task force is to design a package of benefits that would be meaningful for some number of Webizens, but not overly costly for W3C. Some suggestions to date include:

  • Webizen Electoral College
    • for every N individual members (where N x the cost of individual membership is > affiliate membership) one "Webizen" seat opens up on the AC. And every year or two, all Webizens votes to elect their representatives.
  • Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.
  • Webizen ID number.
    • This number could be used as a virtual identity and services could leverage this over time. There could be a physical ID card if anyone wants one.
  • Public profile on the W3C website.
  • A "flourish" next to where name appears in Community Group and Working Group list of participants.
  • Name listed on our Supporters page (with # years).
  • Annual Webizen T-shirt. (tentative design example)
    • Participate in annual T-shirt design competition
    • Many will not want another T-shirt or are happy to pick it up at a conference. For now we are calling this an optional benefit with a possibility of asking the Webizen to cover shipping, unless (s)he has a way to pick it up.
  • Stickers, mug, other 'goodies'.
  • Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.
  • Voice in a Webizen Blog (moderated by Webizens Reps) linked from W3C blog. Since the Webizen Reps have write access to the W3C blog (see below), there is also a means for the views of Webizens to be advanced to the AC blog.
    • -1 from chaals: "I would consider offering people the chance to publish stuff on the official W3C blog. And warn them that this means it has to be good enough."
  • A two hours welcoming session via conference call to explain how W3C work, and what are webizen rights, and raise questions (conducted on a semester basis, in the 3 timeslot regions)

Intermediate or Longer-term benefits

  • Creating user groups. W3C is vendor-dominated and we imagine that many Webizens might want to influence Web technologies in core issues of APIs, as well as UI design.
  • Best practice discussions, webinars, luncheons
  • User conferences
  • Providing @w3.org email addresses as vanity addresses and emails for those that want them.
    • In that case, IDs should use handles / short names (nicks) instead of long ID numbers.

Note: If W3C is putting together a local event, it should not be limited to Webizen participation. But there might be a fee for general public and either free or discounted entry for Webizens. We want to remain open to as many people as possible (and mixing Webizens and potential Webizens sounds useful).

Participation Benefits and Non Benefits

Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).

It is already possible (without a fee) to have appropriate individuals participate in W3C Working Groups as Invited Experts (IEs). Hence for WGs, extending participation to Webizens is not necessary. It would deprecate existing IEs, and possibly ask them to suddenly pay a fee. Further, there are potential patent issues.

Advisory Committee Membership is more valuable than the $100 fee that Webizens pay. However, Webizens will be able to elect Webizen representatives (reps) to the AC.

The design is to choose a number of reps which gives Webizens a real voice in the AC. On the other hand, given that the reps don't have an ongoing business relationship with their electorate (unlike AC reps for Member companies), and may not be able to represent whether there is commitment to implementations (unlike AC reps for Members) we will limit the number of reps - at least initially. We reserve the right to expand the limit over time.

The Webizen AC reps would have some, but not all, rights of an AC Member. They may review Charters and REC track deliverables, participate in ac-forum discussions, may attend AC meetings, may nominate for the TAG and AB, and vote in TAG and AB elections. They may accept Member-confidential information, but may not distribute Member-confidential information within their companies (since their companies are not Members) or among Webizens (because re-distribution to all Webizens means it is no longer in Member space). They cannot nominate themselves or anyone else to participate in Working Groups.

The Webizen AC reps would also have write-access to the official W3C blog.

The number of reps for the Webizen community is N/200 with a cap of 25, where N is the number of Webizens that have signed up. If the number is smaller than 10, they would be elected on an at-large basis. If larger than 10, we might devise a regional representation scheme.

No single company may have more than 1 AC representative. Thus, employees of Member companies cannot be Webizen reps, and if more than one rep is elected from a company, the one with fewer votes would need to step down.

Webizen voting for the AC

There are many different mechanisms for voting and it will no doubt be controversial what voting technique should be used by Webizens to select AC reps.

In W3C TAG and Advisory Board elections each voter can vote n times if there are n different seats. This has the desirable effect that the n "best" candidates need not compete with each other - they can all be named on every ballot. It has the undesirable effect that if a significant minority of voters prefer one slate of candidates and a majority prefer a different slate, that the minority gets no voice while the majority can take all of the slots.

For the Webizen vote, this undesirable effect is a significant issue. Voters could be distributed around the world and may not know people in other regions of the world. The W3C approach to voting could disenfranchise significant numbers of Webizens in the election.

This is not to say that geographical representation should be the major issue for Webizen voting. But it is at least one consideration where AC style voting is likely to lead to frustrated groups.

There are several approaches to addressing this.

A popular approach is Single Transferable Vote (STV) [2]. This removes the problem of shutting out the minority. But it introduces other problems. If balloting is for 25 candidates, it might be hard for voters to list all of their preferences - but there is no requirement to do so. And in general, STV is harder to count - but far from impossible.

Other organizations (e.g. IEEE [3]) have a regional component to their voting. Over a longer period of time, we need to explore the best voting mechanism for Webizens which may have a regional component.

Initially, there would be value to keep the voting mechanism simple and we should avoid the possibility that a "majority" region gets all of the seats.

In this space, we accumulate various proposals to voting mechanism. In the early years, we anticipate that the voting mechanism will be modified regularly (every year or two), until Webizens are comfortable with the mechanism.

Proposal #1

  1. Any Webizen can run for an AC position
  2. Every Webizen gets one vote
  3. If there are n seats available, they go to the top n vote-getters.

(In the view of this proposal writer, until n>9, we do not make the vote more complicated).

Under this proposal, if multiple candidates run in a certain region of the world or to represent an identifiable community, they will compete and result in fewer or no representatives from that part of the world than the voters from that region or community.

Proposal #2

  1. Any webizen can run for AC.
  2. Any webizen votes for as many candidates as they want, ranking them in preference order.

The winners are determined by "Schulze STV" voting.

To count the votes we could use the Open Source code available.

We could also run the entire election through the online implementation. it takes minutes to set up.


  1. Proposals for voting mechanisms are due by January 1, 2015
  2. Webizens will select their preferred voting mechanisms for the first year by April 1, 2015
  3. Nominations for 2016 are due on July 1, 2015.
  4. Nominee statements are due on August 1, 2015.
  5. Election period is September 1 - October 1, 2015.
  6. Position is help for one year, from 1/1/16 until 1/1/17

[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes [2] http://en.wikipedia.org/wiki/Single_transferable_vote [3] https://www.ieee.org/about/corporate/election/election_index.html

Drafting a Webizen network structure

In order to favor local *and* international community development, in addition to belong to a global community, W3C Offices should also track Webizens in their geography. Existing W3C offices are available http://www.w3.org/Consortium/Offices/staff. When joining a webizen would choose an office (the one he or she wants) and thus would be associated with that local life. This would help them be knowledgeable of local symposia, workshops, discussions, etc. about web technology. The local offices structure could be used later for a regional based organization and voting fragmenting reference.

Question: What does it mean in practice for a Webizen to be associated with an Office?

Marketing and Communications

No one really knows if this is a good idea. If we choose to launch it, we would do so without much broad advertising. We would start with modest targets for participation and a modest package of benefits. If the idea gets traction with the community and gets many participants, we can expand the activities later.

A comm plan would be some percentage of the Webizen program income, e.g. 8%

Webizen Messaging

Community Development

  • Find 25 people who will be the initial Webizens and promote the launch through their channels
  • Early adopter benefits (for first 200 Webizens)
    • Discount? [not supported at 2014-05-12 meeting]
    • Special early adopter T-shirt
    • Urge them to promote their participation
  • An alternative to providing discounts for early adopters, we discussed the possibility of giving an even better benefit - better than money - ownership of the low-order Webizen ID numbers. As soon as this was proposed, we had bids.
    • Jeff Jaffe: A very low number, but willing to defer if it helps attracts others
    • David Larlet: a very low number
    • Sébastien Desbenoit: 000000000000017
    • Ralph Swick: 27
    • Coralie Mercier: 000000000000042
    • Jean-Charles Verdié: 000000000000051
    • Karl Dubost: 000000000000069
    • Andrei Sambra: 000000000000007

Visual identity

  • Overall program, the essence of being a webizen
  • Badges (for Webizens and Webizen representatives)
  • Badge usage policy (e.g., licenses, derivative works, etc.)

Web site

  • Leverages visual identity
  • Content
    • What the program is about
    • List of benefits
    • How to become a Webizen
    • List of Webizens, highlighting representatives
    • How representatives are elected, and schedule for election
    • List of communications channels (e.g., for news and events)
    • FAQ (e.g., relation to Membership)

Estimated cost with visual design: $15-$20K

w3.org updates

  • W3C homepage
  • Participate page
  • Add link to footer of new site
  • Add link to left column of home page in dev section
  • Add link from validator home page, unicorn home page

W3C Notification

  • Home page news story announcing program
  • Initial blog post (Jeff?)
  • Announcement to Membership
  • W3C twitter, Facebook, LinkedIn channels
    • LinkedIn showcase page?
  • We do not anticipate a press release since we think social media channels will be more effective for this news

Notification via partners

  • All initial Webizens
  • A List Apart
  • Web Directions
  • ParisWeb
  • Web Visions
  • Webby Awards
  • @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell
  • W3C alums
  • W3C Members
  • Others?

Concept & pitch

Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.

Ideas of pitch:

  • "Take your place at the W3C table."
  • "Help ensure Web standards meet your needs."
  • "Not just a Websumer, I'm a Webizen."

Operational questions

  • The Webizen task force must look at operational costs: fee processing, database recording, mailing lists, costs of benefits, etc. to ensure that this low-revenue operation does not cost too much.
  • International and global issues
  • Accessibility
  • Who on the team would actually do the necessary tasks

Past discussion notes:


  • Organise design competition for annual t-shirt.
  • Can it be managed by a third party (budget needs to take that into account)?

Funds usage - internal to W3C

Revenue from the Webizen program will be used to offset the costs of the Webizen program. Any excess revenues will be made available for general W3C funds, rather than earmarked to a particular function or location.

ISSUES: June discussion at the W3C Advisory Committee Meeting

Announced at the 2014-05-05 Webizen TF meeting, the Webizen topic is on the AC Meeting agenda (June 2014). The presentation is less a presentation and more a discussion of the key issues:

  1. should we have a webizen program?
  2. what should we name it?
  3. collection of benefits, right sets, what to add or substract?
  4. is it acceptable for webizens to select representatives that participate in certain AC activities?
  5. should voting mechanism be decided by the Webizens?

If you want to raise additional issues and will not attend this meeting, please send your issue to the public-webizen@w3.org mail list before June 8.


How do I participate in a working group

Q: As a Webizen, how do I participate in a W3C Working Group?

A1: If you are an employee of a member company, ask your AC representative to add you to the working group.

A2: If you are an individual not employed by a member company:

Most working groups work publicly with a public mailing list that anybody can join.

In practice nearly all working groups are resource constrained for their work. Thus working groups are incentivized to recognize capable public individual participants and offer them invited expert status in the group to help with working group tasks.

In particular, take the following steps:

  1. Join the IRC channel and public mailing list of the working group (WG)
  2. Participate in good faith in IRC and the mailing list, and help out e.g. by:
    • documenting specific real world use-cases they think the WG should solve
    • pointing out errors/issues/improvements in specs
    • contributing test cases for WG technologies
    • provide helpful answers and responses to various questions raised

In practice, individuals that have shown up and consistently positively participated in this manner have been invited to become invited experts in many working groups, e.g. CSS. Often this invitation occurs by a WG chair or other member getting to know the individual, advocating for them inside the working group, and then reaching a consensus decision to invite the individual.

Administrative section

Task Force led by: Jeff Jaffe <jeff@w3.org>


  • Jeff Jaffe
  • Coralie Mercier
  • Veronica Thom
  • Alexandre Bertails
  • Amy van der Hiel
  • Ann Bassetti
  • Andrei Sambra
  • chaals
  • JC Verdie
  • Robin Berjon
  • Virginie Galindo
  • Sébastien Desbenoit
  • Mark Sadecki


  • October 2013 - January 2014: Proposals from W3C Members and Staff added to this page
  • Jan 2014: W3C management prioritization of headlights ideas
  • Feb 2014: Announcement of topics selected for further development and start of task forces
  • 7 March: People are encouraged to join the task forces by this date.
  • 10 March - June: Task forces develop ideas
  • 8-10 June 2014: AC meeting discussion
  • June-July 2014: Further development
  • July 2014: W3M evaluation of proposals and assignment of resources

Meeting records and actions

[no actions, edits welcome in existing sections of the wiki]

  • 2014-05-05
    • [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki
    • [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"
    • (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.
  • 2014-04-10
    • [done] koalie to align pitch phrases with goals as stated in section created today
    • [done] koalie to get W3C Offices to identify likely candidates and seek their reaction
    • (Carried from past meeting) Veronica to update wiki (discounts proposal)
  • 2014-03-27 11:00 am (ET)
    • [done] Jeff to elaborate on how elections should be done (college)
    • [done] Veronica to socialise her proposal further and update wiki (discounts)
  • 2014-03-20
    • [recurrent] Coralie to bring to Ted's attention any new proposed benefit that involves systeam and seek his opinion on feasability (1) and cost (2)
    • [done] Jeff to write a proposal to write up what an electoral college would look like.
    • [done]Veronica to figure what sort of discounts level to devcampus, VS etc. are high-enough to attract people, but not high-enough that they give the services away.
  • 2014-03-10
    • [done] Coralie to come up with comm plan for low-key start of webizen program.
    • [done] Coralie to create a wiki.
    • [done] Coralie to nudge Ted about systeam aspects of Webizen. (Minutes, key points)
    • [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.