Difference between revisions of "Webizen"

From W3C Wiki
Jump to: navigation, search
(next meeting)
(Package of benefits)
Line 65: Line 65:
* Best practice discussions, webinars, luncheons
* Best practice discussions, webinars, luncheons
* User conferences.
* User conferences.
=== Developing countries ===
We need to have a lower entry cost for individuals who live in developing countries, possibly with fewer benefits.
== Non Benefits ==
== Non Benefits ==

Revision as of 18:27, 21 March 2014

< Headlights 2014

"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]).


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.

W3C Management (W3M) explored the concept of “Individual Membership” – which would (for a fee) confer on individuals rights as Members; notably the ability to participate in W3C Working Groups. For a variety of reasons W3M concluded that this would be unwieldy. Many W3C processes are organized around Member rights (participation in WGs, voting for AB and TAG, AC reviews of documents) that creating a new membership category would be extremely complicated and not worth the considerable effort.

Moreover, a key desire – to have appropriate individuals participate in W3C Working Groups – is already possible (without a fee) via Invited Experts (IE). Hence for this key request, Individual Membership is not necessary. It would deprecate existing IEs; possibly ask them to suddenly pay a fee.

An additional piece of background 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 community by getting a new designation of Webizen. This is not a Membership benefit and does not confer Membership rights. But we make available a new means to congregate as a community.

As it is not a Membership benefit, it 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.

Concept & pitch

Ideas of pitch:

  • "A simple donation is all it takes to show that you want to give back to the Web for all you have gained - knowledge, ease of shopping, social networking, and the continued equality and connection of humans. You can say: the free, interoperable, international Web has given me so much, I want to give back. I'm a W3C Webizen."
  • "The Web has given me so much, I want to give back. I'm a W3C Webizen."
  • "Not just a Websumer, I'm a Webizen."

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 – since we anticipate a low-key launch. Some suggestions to date include:

  • Webizen ID card.
  • Public profile on the W3C website.
  • 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.
  • Stickers, mug, other schwag.
  • Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.
  • Voice in a Webizen Blog linked from W3C blog.
  • Invitation to teleconference organized once annually by the CEO to provide an update on W3C's activities and plans.
  • Webizen Electoral College
    • for every N individual members (where N x the 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.

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.

Developing countries

We need to have a lower entry cost for individuals who live in developing countries, possibly with fewer benefits.

Non Benefits


Low-key launch

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%

Low-key launch Comm plan

A low-key comm plan could be:

  • posting on our Website,
  • a mailing to all individuals in work groups

Target audience

List of who we would approach first to become Webizens:

  • Individuals in our work groups;
  • 5.6K Premium Validator suite users, Unicorn users;
  • W3C alumni;

Preferred approach to reach them (without spamming them):

Intermediate or Longer-term Comm plan


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


  • Organise design competition for annual t-shirt.

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


  • 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

  • 2014-03-27 11:00 am (ET)
  • 2014-03-20
    • Coralie to bring to Ted's attention any new proposed benefit that involves systeam and seek his opinion on feasability (1) and cost (2)
    • Jeff to write a proposal to write up what an electoral college would look like.
    • 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
    • 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)
    • Veronica to draft a proposal of what kind of discounts a Webizen program would confer.