https://www.w3.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=DdavisW3C Wiki - User contributions [en]2024-03-29T14:49:01ZUser contributionsMediaWiki 1.41.0https://www.w3.org/wiki/index.php?title=TPAC/2015/SessionIdeas&diff=85659TPAC/2015/SessionIdeas2015-09-17T04:22:48Z<p>Ddavis: /* W3C Web API */ Removed own name</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2015]] Wednesday session ideas in advance of the meeting. <br />
<br />
See the [http://www.w3.org/wiki/TPAC2015/FAQ TPAC 2015 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
* '''Please place new proposal at the bottom of this document'''<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
== Proposed sessions ==<br />
<br />
=== Web Platform Incubator CG, HTML plan forward ===<br />
* '''status: TO BE CONFIRMED'''<br />
* Proposer: Philippe Le Hégaret<br />
* Summary: New ideas for the incubator CG, HTML plan going forward<br />
* Type: presentation + open discussion<br />
* Background materials:<br />
** [http://www.w3.org/blog/2015/07/wicg/ WICG: Evolving the Web from the ground up]<br />
** [https://www.w3.org/2015/05/07-ac-minutes.html#item02 Minutes of May 2015 AC Meeting "HTML"] (member-only link)<br />
* '''Note''': The new "HTML" plan is sufficiently core to the consortium to make this a Plenary topic<br />
<br />
=== Generic Sensor API ===<br />
* Proposer: Tobie Langel<br />
* Summary: Status update of spec and implementation, discussions around new use cases and future plans<br />
* Type: short presentation followed by an open discussion<br />
* Background materials:<br />
** [https://w3c.github.io/sensors/ Generic Sensor API spec]<br />
** [https://github.com/w3c/sensors/issues Generic Sensor Issue Tracker]<br />
<br />
=== Getting your hands dirty with the automatic publication system (and later celebrating how that little investment of time pays off in the end, by saving you time and headaches), or the convenience or writing succinct titles ===<br />
* '''Proposer''': [[User:Antonio | Antonio]], on behalf of [http://www.w3.org/People/domain/systeam Systeam].<br />
* '''Summary''': demo, workshop, Q&A about the [https://github.com/w3c/echidna/wiki/FAQ automatic publication system] and related tools.<br />
* '''Type''': moderately geeky discussion.<br />
* '''Background materials''': none, but some familiarity with [https://github.com/w3c/echidna Echidna] & [https://github.com/w3c/specberus Specberus] is desirable.<br />
* '''Constraint''': ideally, at at a time when any systeamers and other interested parties (''Philippe'', ''Dom'', ''Robin'') can attend.<br />
<br />
=== W3C Web API ===<br />
* '''Proposer''': Ted Guild, on behalf of [http://www.w3.org/People/domain/comm MarComm] and [http://www.w3.org/People/domain/systeam Systeam].<br />
* '''Summary''': demo, prototypes of dashboard and groups home page templates backed by the W3C Web API and available on gh so our collaborators can contribute.<br />
* '''Type''': presentations, discussion<br />
* '''Background materials''': TBD during September<br />
* '''Constraint''':<br />
<br />
=== Business side of Verticals ===<br />
* '''Proposer''': Alan Bird, W3C Global Business Development Lead<br />
* '''Summary''': What is the business side of Verticals (aka Industry Engagement Meetings)? We need global voices in our detailed work as well as our Strategic Industry discussions.<br />
* '''Type''': discussion<br />
* '''Background materials''': TBD<br />
* '''Constraint''': 30 minute session<br />
<br />
=== Project FoxEye ===<br />
* Proposer: [[User:Glaxy | Chiahung Tai]] and [[User:kakukogou | Tzuhao Kuo]] from Mozilla.<br />
* Summary: demo, prototypes of FoxEye project.<br />
* Type: presentations, discussion<br />
* More detail: [https://wiki.mozilla.org/Project_FoxEye FoxEye]<br />
* goals of session: The goal of this project is bringing the power of computer vision and image processing to the Web.<br />
<br />
=== CJK Web Leadership Forum ===<br />
* Proposer: CJK AB (Soohong Daniel Park, Judy Zhu and Jay Kishigami)<br />
* Summary: strategic thoughts and plan<br />
* Type: open discussion based on AB material(Industry Group) with plh<br />
* More detail: TBD<br />
* goals of session: aiming to dig out any ideas to share W3C strategic information with various industries leaders in CJK, listen and learn about their requirements in specific.</div>Ddavishttps://www.w3.org/wiki/index.php?title=TPAC/2015/SessionIdeas&diff=85304TPAC/2015/SessionIdeas2015-08-05T22:50:50Z<p>Ddavis: </p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2015]] Wednesday session ideas in advance of the meeting. <br />
<br />
See the [http://www.w3.org/wiki/TPAC2015/FAQ TPAC 2015 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
* '''Please place new proposal at the bottom of this document'''<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
== Proposed sessions ==<br />
<br />
=== Web Platform Incubator CG, HTML plan forward ===<br />
* '''status: TO BE CONFIRMED'''<br />
* Proposer: Philippe Le Hégaret<br />
* Summary: New ideas for the incubator CG, HTML plan going forward<br />
* Type: presentation + open discussion<br />
* Background materials:<br />
** [http://www.w3.org/blog/2015/07/wicg/ WICG: Evolving the Web from the ground up]<br />
** [https://www.w3.org/2015/05/07-ac-minutes.html#item02 Minutes of May<br />
2015 AC Meeting "HTML"] (member-only link)<br />
* '''Note''': The new "HTML" plan is sufficiently core to the consortium to make this a Plenary topic<br />
<br />
=== Generic Sensor API ===<br />
* Proposer: Tobie Langel<br />
* Summary: Status update of spec and implementation, discussions around new use cases and future plans<br />
* Type: short presentation followed by an open discussion<br />
* Background materials:<br />
** [https://w3c.github.io/sensors/ Generic Sensor API spec]<br />
** [https://github.com/w3c/sensors/issues Generic Sensor Issue Tracker]<br />
<br />
=== Getting your hands dirty with the automatic publication system (and later celebrating how that little investment of time pays off in the end, by saving you time and headaches), or the convenience or writing succinct titles ===<br />
* '''Proposer''': [[User:Antonio | Antonio]], on behalf of [http://www.w3.org/People/domain/systeam Systeam].<br />
* '''Summary''': demo, workshop, Q&A about the [https://github.com/w3c/echidna/wiki/FAQ automatic publication system] and related tools.<br />
* '''Type''': moderately geeky discussion.<br />
* '''Background materials''': none, but some familiarity with [https://github.com/w3c/echidna Echidna] & [https://github.com/w3c/specberus Specberus] is desirable.<br />
* '''Constraint''': ideally, at at a time when any systeamers and other interested parties (''Philippe'', ''Dom'', ''Robin'') can attend.<br />
<br />
=== W3C Web API ===<br />
* '''Proposer''': [[User:DDavis | Daniel Davis]] and Ted Guild, on behalf of [http://www.w3.org/People/domain/comm MarComm] and [http://www.w3.org/People/domain/systeam Systeam].<br />
* '''Summary''': demo, prototypes of dashboard and groups home page templates backed by the W3C Web API and available on gh so our collaborators can contribute.<br />
* '''Type''': presentations, discussion<br />
* '''Background materials''': TBD during September<br />
* '''Constraint''':</div>Ddavishttps://www.w3.org/wiki/index.php?title=HTML/Media_Task_Force/MSE_Ad_Insertion_Use_Cases&diff=84098HTML/Media Task Force/MSE Ad Insertion Use Cases2015-05-13T08:31:28Z<p>Ddavis: /* Comments */</p>
<hr />
<div>==Use Cases==<br />
<br />
This section outlines ad insertion use cases that are not adequately addressed by the current MSE APIs.<br />
<br />
Each of the use cases is comprised of a situation where the user wishes to perform a seamless switch from main content to ad content or vice versa. In each use case, one piece of content is identified as content A, and the other is identified as content B. A may be ads and B may be main content, or vice versa. The user wishes to play content A (or a portion of A) then perform a seamless switch to content B (or a portion of B) at a specific time or frame.<br />
<br />
For each of the use cases, assume that:<br />
<br />
:Assumption 1) A seamless switch is defined as continuous playback where no visible/audible pause during the transition from A to B occurs whether due to late buffering, late codec initialization, or other causes.<br />
<br />
:Assumption 2) User agent is given enough advance notice that a seamless switch is theoretically possible.<br />
<br />
::''Example: User would like to perform a switch from content A to content B in 15 seconds. Assuming decent network conditions, this should be enough time to fetch the content, buffer it, and schedule a seamless switch.''<br />
<br />
:Assumption 3) A and B may have been encoded with different encoders or with different settings that cannot be synchronized. This may occur for reasons such as:<br />
<br />
::a) A and B originate from different sources.<br />
<br />
::''Example: A is primary content that originates from an MVPD. B is ad content that originates one of many vendors outside the MVPD. The encoder models and settings used to encode A and B may differ since it is impractical for the MVPD to synchronize encoder settings and models across all ad vendors.''<br />
<br />
::b) A and B were encoded at different times.<br />
<br />
::''Example: An MVPD encodes A using encoder model M1. At a later time, the MVPD decides to begin using encoder model M2 across their organization. The MVPD encoders content B using M2. Details such as track IDs may differ between M1 and M2. Due to the size of the MVPD's content library, it is impractical to re-encode all legacy content.''<br />
<br />
===Use case 1) Seamless switch between ads and main content that contain different number of tracks===<br />
<br />
'''Priority:''' HIGH<br />
<br />
User wishes to play content A (or a portion of A) then perform a seamless switch to content B (or a portion of B) at a specific time or frame. <br />
<br />
A is multiplexed content and contains x tracks of type T. B is multiplexed content and contains y tracks also of type T, but x != y. All other factors (codec, etc) are consistent between A and B.<br />
<br />
''Example: A is main content with English/Spanish audio, B is an ad with only English. Ad content often contains a smaller number of language tracks than main content.''<br />
<br />
===Use case 2) Seamless switch between ads and primary content that use different codecs===<br />
<br />
'''Priority:''' HIGH<br />
<br />
A uses codec C1. B uses codec C2. All other factors (track IDs, etc) are consistent between A and B.<br />
<br />
''Examples:''<br />
<br />
* ''A is main content with H264 video and Dolby audio. B is an ad with H264 video and AAC audio. Dolby support is common among set-top boxes. Primary content is often encoded with Doby audio. Dolby audio is not as common among ad content.''<br />
* ''A is main content with HEVC video and AAC audio. B is an ad with H264 video and AAC audio. As HEVC gains adoption, ad and primary content will often be a mixture of HEVC and H264.''<br />
<br />
The use case of switching across profiles and levels does not typically cause issues since "higher" profiles/level are generally supersets of lower profiles/levels.<br />
<br />
===Use case 3) Seamless switch between ads and primary content that use different byte stream formats===<br />
<br />
'''Priority:''' HIGH<br />
<br />
A is of a different byte stream format from B.<br />
<br />
''Example: A is main content formatted as m2ts. B is ad content formatted as mp4. This is common when dealing with legacy VoD content.''<br />
<br />
===Use case 4) Seamless switch between ads and primary content with different track IDs===<br />
<br />
'''Priority:''' LOW<br />
<br />
A is multiplexed content with x tracks of type T. B is also multiplexed content with x tracks of type T. The track IDs of A differ from those of B. x > 1. All other factors (codec, etc) are consistent between A and B.<br />
<br />
''Example: A is main content with English/Spanish audio with track IDs 1 and 2. B is an ad with English/Spanish audio with track IDs 1 and 3. Since ad content is typically encoded independently from primary content and track IDs are not standardized, there is no guarantee they will use consistent schemes for designating track IDs.''<br />
<br />
===Use case 5) Seamless switch between ads and primary content, where one is multiplexed and the other is demultiplexed===<br />
<br />
'''Priority:''' LOW<br />
<br />
A consists of demultiplexed tracks. B consists of multiplexed tracks.<br />
<br />
==Specification Gaps==<br />
<br />
This section outlines gaps in the current specification in addressing the above use cases.<br />
<br />
The use cases encounter difficulty due to step #3 of the initialization segment received algorithm (Section 3.5.8). Step #3 reads:<br />
<br />
::''3. If the first initialization segment received flag is true, then run the following steps:''<br />
:::''1. Verify the following properties.'' '''''If any of the checks fail then run the end of stream algorithm with the error parameter set to "decode" and abort these steps.'''''<br />
::::'''''* The number of audio, video, and text tracks match what was in the first initialization segment.'''''<br />
::::'''''* The codecs for each track, match what was specified in the first initialization segment.'''''<br />
::::'''''* If more than one track for a single type are present (ie 2 audio tracks), then the Track IDs match the ones in the first initialization segment.'''''<br />
<br />
A possible workaround (Workaround A) might be to utilize multiple MediaSource objects, but this approach has multiple issues:<br />
# Initiating the switch using TextTrackCue is not guaranteed to be frame accurate. Testing suggests that current implementations are not frame accurate.<br />
# The user agent is unaware of the switch until the time of the switch and therefore cannot perform buffering or decoder initialization ahead of time.<br />
# User Agent implementations may not support multiple MediaSource objects. Section 2.2 specifies this as a "quality of implementation issue."<br />
<br />
A second workaround (Workaround B) might be to intiialize SourceBuffers of all possible audio and video codecs. This approach has multiple issues:<br />
# Issues #1 and #2 of Workaround A still apply.<br />
# User Agent implementations may not support enough SourceBuffers. Section 2.2 specifies this as a "quality of implementation issue."<br />
# The number of required SourceBuffers may be unmanageably large, especially when considering use cases that involve a combination of multiplexed/demultiplexed content and multiple possible codecs.<br />
# The complexity required for a user to implement this solution is high.<br />
<br />
A third workaround (Workaround C) might be to add a JavaScript container format parser to Workaround B. This approach has multiple issues:<br />
# The complexity required for a user to implement this solution is very high. The Javascript code must parse the container format, demultiplex tracks, and remap track IDs in order to work around model limitations.<br />
# For the multi-codec use case, issues #1-4 of Workaround B still apply. This approach reduces the number of necessary SourceBuffers, but potentially requires more SourceBuffers than may be supported. Switches are not guranteed be frame accurate.<br />
<br />
==Comments==<br />
<br />
Some feedback from members of the [https://www.w3.org/community/webtiming/ Multi-Device Timing Community Group]:<br />
* https://lists.w3.org/Archives/Public/public-web-and-tv/2015May/0002.html<br />
* https://lists.w3.org/Archives/Public/public-web-and-tv/2015May/0004.html</div>Ddavishttps://www.w3.org/wiki/index.php?title=HTML/Media_Task_Force/MSE_Ad_Insertion_Use_Cases&diff=84097HTML/Media Task Force/MSE Ad Insertion Use Cases2015-05-13T08:30:53Z<p>Ddavis: Added comments section</p>
<hr />
<div>==Use Cases==<br />
<br />
This section outlines ad insertion use cases that are not adequately addressed by the current MSE APIs.<br />
<br />
Each of the use cases is comprised of a situation where the user wishes to perform a seamless switch from main content to ad content or vice versa. In each use case, one piece of content is identified as content A, and the other is identified as content B. A may be ads and B may be main content, or vice versa. The user wishes to play content A (or a portion of A) then perform a seamless switch to content B (or a portion of B) at a specific time or frame.<br />
<br />
For each of the use cases, assume that:<br />
<br />
:Assumption 1) A seamless switch is defined as continuous playback where no visible/audible pause during the transition from A to B occurs whether due to late buffering, late codec initialization, or other causes.<br />
<br />
:Assumption 2) User agent is given enough advance notice that a seamless switch is theoretically possible.<br />
<br />
::''Example: User would like to perform a switch from content A to content B in 15 seconds. Assuming decent network conditions, this should be enough time to fetch the content, buffer it, and schedule a seamless switch.''<br />
<br />
:Assumption 3) A and B may have been encoded with different encoders or with different settings that cannot be synchronized. This may occur for reasons such as:<br />
<br />
::a) A and B originate from different sources.<br />
<br />
::''Example: A is primary content that originates from an MVPD. B is ad content that originates one of many vendors outside the MVPD. The encoder models and settings used to encode A and B may differ since it is impractical for the MVPD to synchronize encoder settings and models across all ad vendors.''<br />
<br />
::b) A and B were encoded at different times.<br />
<br />
::''Example: An MVPD encodes A using encoder model M1. At a later time, the MVPD decides to begin using encoder model M2 across their organization. The MVPD encoders content B using M2. Details such as track IDs may differ between M1 and M2. Due to the size of the MVPD's content library, it is impractical to re-encode all legacy content.''<br />
<br />
===Use case 1) Seamless switch between ads and main content that contain different number of tracks===<br />
<br />
'''Priority:''' HIGH<br />
<br />
User wishes to play content A (or a portion of A) then perform a seamless switch to content B (or a portion of B) at a specific time or frame. <br />
<br />
A is multiplexed content and contains x tracks of type T. B is multiplexed content and contains y tracks also of type T, but x != y. All other factors (codec, etc) are consistent between A and B.<br />
<br />
''Example: A is main content with English/Spanish audio, B is an ad with only English. Ad content often contains a smaller number of language tracks than main content.''<br />
<br />
===Use case 2) Seamless switch between ads and primary content that use different codecs===<br />
<br />
'''Priority:''' HIGH<br />
<br />
A uses codec C1. B uses codec C2. All other factors (track IDs, etc) are consistent between A and B.<br />
<br />
''Examples:''<br />
<br />
* ''A is main content with H264 video and Dolby audio. B is an ad with H264 video and AAC audio. Dolby support is common among set-top boxes. Primary content is often encoded with Doby audio. Dolby audio is not as common among ad content.''<br />
* ''A is main content with HEVC video and AAC audio. B is an ad with H264 video and AAC audio. As HEVC gains adoption, ad and primary content will often be a mixture of HEVC and H264.''<br />
<br />
The use case of switching across profiles and levels does not typically cause issues since "higher" profiles/level are generally supersets of lower profiles/levels.<br />
<br />
===Use case 3) Seamless switch between ads and primary content that use different byte stream formats===<br />
<br />
'''Priority:''' HIGH<br />
<br />
A is of a different byte stream format from B.<br />
<br />
''Example: A is main content formatted as m2ts. B is ad content formatted as mp4. This is common when dealing with legacy VoD content.''<br />
<br />
===Use case 4) Seamless switch between ads and primary content with different track IDs===<br />
<br />
'''Priority:''' LOW<br />
<br />
A is multiplexed content with x tracks of type T. B is also multiplexed content with x tracks of type T. The track IDs of A differ from those of B. x > 1. All other factors (codec, etc) are consistent between A and B.<br />
<br />
''Example: A is main content with English/Spanish audio with track IDs 1 and 2. B is an ad with English/Spanish audio with track IDs 1 and 3. Since ad content is typically encoded independently from primary content and track IDs are not standardized, there is no guarantee they will use consistent schemes for designating track IDs.''<br />
<br />
===Use case 5) Seamless switch between ads and primary content, where one is multiplexed and the other is demultiplexed===<br />
<br />
'''Priority:''' LOW<br />
<br />
A consists of demultiplexed tracks. B consists of multiplexed tracks.<br />
<br />
==Specification Gaps==<br />
<br />
This section outlines gaps in the current specification in addressing the above use cases.<br />
<br />
The use cases encounter difficulty due to step #3 of the initialization segment received algorithm (Section 3.5.8). Step #3 reads:<br />
<br />
::''3. If the first initialization segment received flag is true, then run the following steps:''<br />
:::''1. Verify the following properties.'' '''''If any of the checks fail then run the end of stream algorithm with the error parameter set to "decode" and abort these steps.'''''<br />
::::'''''* The number of audio, video, and text tracks match what was in the first initialization segment.'''''<br />
::::'''''* The codecs for each track, match what was specified in the first initialization segment.'''''<br />
::::'''''* If more than one track for a single type are present (ie 2 audio tracks), then the Track IDs match the ones in the first initialization segment.'''''<br />
<br />
A possible workaround (Workaround A) might be to utilize multiple MediaSource objects, but this approach has multiple issues:<br />
# Initiating the switch using TextTrackCue is not guaranteed to be frame accurate. Testing suggests that current implementations are not frame accurate.<br />
# The user agent is unaware of the switch until the time of the switch and therefore cannot perform buffering or decoder initialization ahead of time.<br />
# User Agent implementations may not support multiple MediaSource objects. Section 2.2 specifies this as a "quality of implementation issue."<br />
<br />
A second workaround (Workaround B) might be to intiialize SourceBuffers of all possible audio and video codecs. This approach has multiple issues:<br />
# Issues #1 and #2 of Workaround A still apply.<br />
# User Agent implementations may not support enough SourceBuffers. Section 2.2 specifies this as a "quality of implementation issue."<br />
# The number of required SourceBuffers may be unmanageably large, especially when considering use cases that involve a combination of multiplexed/demultiplexed content and multiple possible codecs.<br />
# The complexity required for a user to implement this solution is high.<br />
<br />
A third workaround (Workaround C) might be to add a JavaScript container format parser to Workaround B. This approach has multiple issues:<br />
# The complexity required for a user to implement this solution is very high. The Javascript code must parse the container format, demultiplex tracks, and remap track IDs in order to work around model limitations.<br />
# For the multi-codec use case, issues #1-4 of Workaround B still apply. This approach reduces the number of necessary SourceBuffers, but potentially requires more SourceBuffers than may be supported. Switches are not guranteed be frame accurate.<br />
<br />
==Comments==<br />
<br />
Some thoughts from members of the [https://www.w3.org/community/webtiming/ Multi-Device Timing Community Group]:<br />
* https://lists.w3.org/Archives/Public/public-web-and-tv/2015May/0002.html<br />
* https://lists.w3.org/Archives/Public/public-web-and-tv/2015May/0004.html</div>Ddavishttps://www.w3.org/wiki/index.php?title=HTML/wg/2015-04-Agenda&diff=83636HTML/wg/2015-04-Agenda2015-04-15T02:22:47Z<p>Ddavis: /* Logistics and meeting location */ Fixed broken map link</p>
<hr />
<div>= Media Task Force April 15-16 2015 F2F Meeting =<br />
<br />
This page is for the [[HTML/wg|HTML WG]] Media Task Force F2F on Wed and Thu April 15-16 2015. The meeting host is [mailto:pcotton@microsoft.com Paul Cotton].<br />
<br />
== Logistics and meeting location ==<br />
<br />
The F2F meeting will be held on the Microsoft campus in Redmond, WA in the Shasta conference room of Building 43.<br />
<br />
[http://binged.it/1OcqmoF Microsoft Building 43 (East Campus)]<br />
15580 NE 31st St.<br />
Redmond, WA<br />
98052, United States<br />
Note: If you have difficulty using the link please do a search for the street address.<br />
<br />
There is an underground parking garage between buildings 42 and 43 that you can use. Please register your vehicle at the Building 43 reception.<br />
<br />
The meeting will start at 9:30am PT on Wed Apr 15. Please arrive at the Building 43 reception between 9am and 9:15am on Wed Apr 15 to register and to be accompanied to the meeting room.<br />
<br />
== IRC and Teleconference facilities ==<br />
<br />
Zakim teleconference bridge:<br />
+1.617.761.6200, conference 63342 ("media")<br />
https://www.w3.org/Guide/1998/08/teleconference-calendar#s_5366<br />
<br />
Supplementary IRC chat (logged):<br />
#html-media on irc.w3.org port 6665 or port 80 <br />
<br />
== Specifications, Documents and References: ==<br />
<br />
Media Task Force specifications<br />
<br />
* [https://w3c.github.io/media-source/ Media Source Extensions Editor's Draft]<br />
* [https://w3c.github.io/encrypted-media/ Encrypted Media Extensions Editor's Draft] <br />
<br />
EME bugs and issues<br />
<br />
* [http://tinyurl.com/7tfambo Encrypted Media Extensions bugs] <br />
* [https://github.com/w3c/encrypted-media/issues EME GitHub issues]<br />
<br />
MSE bugs<br />
<br />
* [http://tinyurl.com/kfeptqy Media Source Extensions bugs] <br />
<br />
See also:<br />
<br />
* [http://www.w3.org/html/wg/ HTML WG homepage]<br />
* [http://www.w3.org/wiki/HTML/Publications HTML WG and TF Publications]<br />
<br />
== Potential Topics ==<br />
<br />
=== MSE ===<br />
# Plan for getting MSE out of CR (i.e. [http://lists.w3.org/Archives/Public/public-html-media/2014Dec/0012.html MSE test suite status]) - Wed 5pm time slot requested to permit Mike Smith to join from Japan<br />
# Selected MSE bugs<br />
## [https://www.w3.org/Bugs/Public/show_bug.cgi?id=28465 MSE does not work with Mixed Content, unlike video/audio.src=]<br />
## [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27242 Clarify how track buffer ranges are updated.]<br />
# [Rus K] [https://www.w3.org/wiki/HTML/Media_Task_Force/MSE_Ad_Insertion_Use_Cases Use cases] driving additional content insertion requirements.<br />
<br />
=== EME ===<br />
# [ddorwin] Interoperability<br />
# [markw, ddorwin] Secure origin requirement.<br />
## [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26332 Bug 26332]<br />
## [https://lists.w3.org/Archives/Public/public-html-media/2015Mar/0006.html David's email on enabling Mixed Content]<br />
# [ddorwin] <tt>persistent-release-message</tt> session type<br />
## [https://github.com/w3c/encrypted-media/issues/45 ISSUE-45 Remove "persistent-release-message" MediaKeySessionType]<br />
# [markw] Persistent secure release messages (Issues 45,16)<br />
## [https://github.com/w3c/encrypted-media/issues/45 ISSUE-45 Remove "persistent-release-message" MediaKeySessionType]<br />
## [https://github.com/w3c/encrypted-media/issues/16 ISSUE-16 Review close() and remove() logic and behavior for persistent-* sessions]<br />
# [skip if no owner] Review the disposition of the session/key persistence issues 18,20,26<br />
## [https://github.com/w3c/encrypted-media/issues/18 ISSUE-18 MediaKeySession.remove() and close() should mark session's keys as "unknown" ]<br />
## [https://github.com/w3c/encrypted-media/issues/20 ISSUE-20 Ensure session type is correct for loaded sessions]<br />
## [https://github.com/w3c/encrypted-media/issues/26 ISSUE-26 Require that the license match the session type]<br />
# [steele] Resolve [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27093 Bug 27093] about allowing keys in initData<br />
## The discussion is really in https://github.com/w3c/encrypted-media/issues/41.<br />
# [steele] Discuss appetite for common license request/response format?<br />
## [https://lists.w3.org/Archives/Public/public-html-media/2015Apr/0018.html Joe's email]<br />
## https://github.com/steelejoe/eme-generic-protocol<br />
## Related: [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27053 Bug 27053] - Platform Segmentation<br />
## Related: [https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944 Bug 20944] - EME should do more to encourage/ensure CDM-level interop<br />
# [steele] Revisit the [https://www.w3.org/wiki/HTML/Media_Task_Force/EME_Use_Cases EME use cases wiki]?<br />
# [ddorwin] Automatically publishing to TR/<br />
## W3C now has a self-serve/automatable [https://github.com/w3c/echidna/wiki/How-to-use-Echidna tool] for publishing to www.w3.org/TR/xyz.<br />
## Eliminates W3C Team involvement/dependency and reduces/eliminates the lag of the TR/ URL.<br />
## [https://lists.w3.org/Archives/Public/public-html/2015Mar/0058.html HTML 5.1 is now automatically published] soon after a commit.<br />
## Note: Not an option for MSE because it only supports WDs.<br />
<br />
==== Moving the EME spec forward ====<br />
# Plan for [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26573 Bug 26573 Getting EME to last call]<br />
## Permanent home for EME registry.<br />
# Plan for addressing interop/segmentation bugs:<br />
## [https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944 Bug 20944] - EME should do more to encourage/ensure CDM-level interop<br />
## [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27053 Bug 27053] - Platform Segmentation<br />
# [ddorwin] What is the definition of [http://www.w3.org/2014/Process-20140801/#implementation-experience independent interoperable implementations] for EME?<br />
# [ddorwin] Tests - Should we use MSE rather than .src= for spec tests?<br />
<br />
=== Other ===<br />
# [ddorwin] Telecon frequency, agenda, etc.<br />
# [A11Y TF] Discussion of [https://www.w3.org/WAI/PF/HTML/wiki/Full_Transcript transcript accessibility] and [https://www.w3.org/html/wg/tracker/issues/194 HTML ISSUE-194] (Requested to be at 4pm on Wed)<br />
<br />
== EME open bugs and issues ==<br />
<br />
* [http://tinyurl.com/7tfambo Encrypted Media Extensions Bugzilla bugs] <br />
<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944 Bug 20944 - EME should do more to encourage/ensure CDM-level interop] depends on:<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27053 Bug 27053 - Platform Segmentation]<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27093 Bug 27093 - Support for proprietary/system-specific formats in initData should be discouraged/deprecated]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=23827 Bug 23827 - Need to add features at risk prior to entry into Candidate Recommendation]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26838 Bug 26838 - Normatively address vulnerabilities related to initData contained in media data] depends on:<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26332 Bug 26332 - Applications should only use EME APIs on secure origins (e.g. HTTPS)]<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27093 Bug 27093 - Support for proprietary/system-specific formats in initData should be discouraged/deprecated]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26573 Bug 26573 - Prepare for Last Call] depends on:<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26811 Bug 26811 - Separate definitions of Initialization Data Types from Stream Format parsing]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26738 Bug 26738 - Add entry for MPEG-2 TS CENC to the Stream Format Registry ] depends on:<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26811 Bug 26811 - Separate definitions of Initialization Data Types from Stream Format parsing]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26776 Bug 26776 - Diagnosing and resolving CDM errors needs a numeric systemCode (deleted with MediaKeyError)]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=26887 Bug 26887 - Allowing license servers and CDMs to control data persistence and secure release] <br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27054 Bug 27054 - Accessibility Concerns]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27055 Bug 27055 - Surfacing license to the user]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27067 Bug 27067 - Define what to do when CDM becomes unavailable]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27168 Bug 27168 - Individualization text regarding device identifiers is overbroad and should be more specific] <br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27269 Bug 27269 - Normatively require distinctive identifiers to be different by top-level and EME-using origin] depends on:<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27268 Bug 27268 - Add a definition of a distinctive identifier] <br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27271 Bug 27271 - Normatively require https for all ancestor origins when requiring https at all] depends on:<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27190 WHATWG Bug 27190 - Add TLS state to environment settings objects. This is needed for Fetch and Mixed Content ...]<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27302 WebAppSec Bug 27302 - Define an elaboration of #may-document-use-powerful-features that checks ancestor browsing contexts]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27283 Bug 27283 - InvalidAccessError usage is questionable; use TypeError instead?] depends on:<br />
** [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27284 WebApps Bug 27284 - Should InvalidAccessError be discouraged?]<br />
* [https://github.com/w3c/encrypted-media/issues EME GitHub issues]<br />
* [https://github.com/w3c/encrypted-media/issues/14 ISSUE-14 Consider changing how the MediaKeySession method algorithms run other algorithms to more accurately reflect implementations] depends on:<br />
** [https://github.com/w3c/encrypted-media/issues/19 ISSUE-19 Ensure promises returned by methods are fulfilled before event handlers are executed]<br />
* [https://github.com/w3c/encrypted-media/issues/22 ISSUE-22 Request: Require CDMs to support and enforce resolution restrictions (and expose the status of those restrictions to the application)]<br />
* [https://github.com/w3c/encrypted-media/issues/23 ISSUE-23 CDM implementations must support multiple keys per session]<br />
* [https://github.com/w3c/encrypted-media/issues/31 ISSUE-31 generateRequest() should allow the first message to not be a license request based on initData] depends on:<br />
** [https://github.com/w3c/encrypted-media/issues/19 ISSUE-19 Ensure promises returned by methods are fulfilled before event handlers are executed]<br />
* [https://github.com/w3c/encrypted-media/issues/41 ISSUE-41 generateRequest may result in keys being usable when no key request needs to be sent]<br />
* [https://github.com/w3c/encrypted-media/issues/42 ISSUE-42 Notification when playback is resumed from waitingForKey]<br />
* [https://github.com/w3c/encrypted-media/issues/45 ISSUE-45 Remove "persistent-release-message" MediaKeySessionType]<br />
* [https://github.com/w3c/encrypted-media/issues/47 ISSUE-47 MediaKeySystemConfiguration.sessionTypes should be sequence<DOMString> for forwards compatibility]<br />
* [https://github.com/w3c/encrypted-media/issues/48 ISSUE-48 Clear Key should not use "A128KW" as the JWK "alg"]<br />
<br />
== EME open bugs - pending implemention ==<br />
<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27725 Bug 27725 - Missing acknowledgments section]<br />
* [https://github.com/w3c/encrypted-media/issues/2 ISSUE-2 stack_overview.svg needs to be updated to match the latest spec]<br />
* [https://github.com/w3c/encrypted-media/issues/8 ISSUE-8 Define behavior for implementations that delay playback until setMediaKeys() is called]<br />
* [https://github.com/w3c/encrypted-media/issues/9 ISSUE-9 Remove note that MediaKeySession events may not be fired until the MediaKeys object is associated with a media element]<br />
* [https://github.com/w3c/encrypted-media/issues/10 ISSUE-10 Include real initData and Clear Key license in the Clear Key example]<br />
* [https://github.com/w3c/encrypted-media/issues/12 ISSUE-12 MediaKeySystemConfiguration returned from MediaKeySystemAccess::getConfiguration() should contain the exact strings from requestMediaKeySystemAccess()]<br />
* [https://github.com/w3c/encrypted-media/issues/15 ISSUE-15 MediaKeySystemAccess::getConfiguration() should return a read-only object (copy)]<br />
* [https://github.com/w3c/encrypted-media/issues/17 ISSUE-17 Replace "fire a simple event" with "fire an event" for non-simple Events ]<br />
* [https://github.com/w3c/encrypted-media/issues/20 ISSUE-20 Ensure session type is correct for loaded sessions]<br />
* [https://github.com/w3c/encrypted-media/issues/30 ISSUE-30 Switch terminology from "asynchronously" to "in parallel"]<br />
* [https://github.com/w3c/encrypted-media/issues/32 ISSUE-32 Consider providing guidance for implementations on platforms that do not expose key IDs]<br />
* [https://github.com/w3c/encrypted-media/issues/34 ISSUE-34 Replace base64url values in examples with realistic values that use base64url-specific characters]<br />
* [https://github.com/w3c/encrypted-media/issues/36 ISSUE-36 Explicitly state that MediaKeySystemMediaCapability's contentType attribute MUST be a valid MIME type]<br />
* [https://github.com/w3c/encrypted-media/issues/39 ISSUE-39 MediaKeyStatusMap: Replace maplike with explicit methods]<br />
* [https://github.com/w3c/encrypted-media/issues/43 ISSUE-43 Provide guidance on object and CDM lifetime]<br />
* [https://github.com/w3c/encrypted-media/issues/44 ISSUE-44 Idea: Add opaque "label" DOMString member to MediaKeySystemConfiguration]<br />
<br />
== MSE open bugs ==<br />
<br />
* [http://tinyurl.com/kfeptqy Media Source Extensions Bugzilla bugs] <br />
<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27239 Bug 27239 - Update SourceBuffer.appendStream() and related algorithms to use ReadableByteStream] <br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27242 Bug 27242 - Clarify how track buffer ranges are updated]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27790 Bug 27790 - Some of the attributes returning TimeRanges objects seem to return a new object each time the getter is invoked]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27843 Bug 27843 - Should the media element load algorithm trigger detaching from a media element?]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27854 Bug 27854 - Should fetch algorithm failure trigger detaching from a media element?]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27980 Bug 27980 - Ambiguous behaviour when running sourcebuffer.abort()]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=27982 Bug 27982 - Clarify asynchronicity in duration change algorithm when reducing duration ]<br />
<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=28379 Bug 28379 - should buffering model be an option?]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=28465 Bug 28465 - MSE does not work with Mixed Content, unlike video/audio.src=]<br />
<br />
Recently fixed bugs:<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=28209 Bug 28209 - Confusing text, might be better off without it]<br />
* [https://www.w3.org/Bugs/Public/show_bug.cgi?id=28234 Bug 28234 - "highest presentation timestamp" is ambiguous/misleading]<br />
<br />
== Agenda April 15 ==<br />
<br />
* 09:30 - 10:00 Tweak agenda à la an [http://en.wikipedia.org/wiki/Unconference unconference style meeting]<br />
* 10:00 - 11:00 Agenda item A<br />
* 11:00 - 12:00 Agenda item B<br />
* 12:00 - 13:00 Lunch break<br />
* 13:00 - 15:00 Agenda item C<br />
* 15:00 - 16:00 Agenda item D<br />
* 16:00 - 17:00 [A11Y TF] Discussion of [https://www.w3.org/WAI/PF/HTML/wiki/Full_Transcript transcript accessibility] and [https://www.w3.org/html/wg/tracker/issues/194 HTML ISSUE-194]<br />
* 17:00 - 18:00 Plan for getting MSE out of CR (i.e. [http://lists.w3.org/Archives/Public/public-html-media/2014Dec/0012.html MSE test suite status]) - Wed 5pm time slot requested to permit Mike Smith to join from Japan<br />
<br />
== Agenda April 16 ==<br />
<br />
* 09:00 - 09:15 Tweak agenda à la an [http://en.wikipedia.org/wiki/Unconference unconference style meeting]</div>Ddavishttps://www.w3.org/wiki/index.php?title=AB/2014-2015_Priorities/multilingual_W3C&diff=81360AB/2014-2015 Priorities/multilingual W3C2015-02-13T13:23:31Z<p>Ddavis: /* Suggestions (based on members discussion) */ Added link to TPAC 2013 breakout session</p>
<hr />
<div><br />
==== Raison d'être ====<br />
<br />
The limits of your language means the limits of your world. However only one language as English is workable for W3C works such as f2f discussion, email discussion, documentation and even minutes officially. That situation makes non-English natives hesitant for W3C participation and sometimes not fully productive within the W3C. <br />
<br />
The new project as the best practice for multilingual W3C has been formed during the last AB meeting in November TPAC and chartered to work on the brainstorming and researching ways of wider collaboration in W3C from non-English native speakers than before, and come up with the solutions.<br />
<br />
==== Basics of the project ====<br />
<br />
* The project does not intend non-English speakers to learn any languages and level up their communications skill. It is clearly out of scope of the project.<br />
<br />
* The project aims to look into the current W3C multilingual issues and come up with the best practice for multilingual participation and discussions in W3C from non-English speakers.<br />
<br />
==== Suggestions (based on members discussion) ====<br />
* Non-English participation<br />
** Call for question/comment to multilingual participants and collect their requirements prior to the meeting (in particular AC/TPAC) and post them on the meeting website to be shared with all participants. Anyone can answer them freely on the website or in the meeting in person.<br />
** Detail descriptions on all agenda items to be clearly understood to multilingual participants prior to the meeting (in particular AC/TPAC). Don't say like "HTML5 what is next ?". This could be a local meeting or call and could include IRC advice and "some tricks for offline communication like corridor conversation and bar talk" (Angel's comment). <br />
* Translation method<br />
** no preference at this stage.<br />
* Technical<br />
** First step is to have a Simple-English summary of any important topics after the meeting. For instance, policy discussions, process changes and specific decisions. That should take place less than one week from the meeting end.<br />
* Application<br />
* Communication barrier between multi-culture background'''<br />
** Several breakout sessions for each multilingual participants coordinated with W3C teams where major language is not English, and each breakout session can have its own preferred language. To recognize these sessions, we are tagging the mark to these sessions on the agenda page or dashboard in meeting place. For instance, A Session (Korean), B Session (Japanese), C Session (Chinese), and so on.<br />
* General<br />
** Set up an anonymous question page (Members only) where AC reps can post questions they may be embarrassed to ask in person (e.g. What is WHATWG? What are the main points in the @@@ discussion?). Answers or clarification could be sent either to the w3c-ac-forum list or a new w3c-answers list. <br />
** Extend the buddy program beyond AC/TPAC meetings only so that new AC reps have someone specific to ask for help during their first year. (Originally suggested by Ann I believe.)<br />
** See also the minutes from the [http://www.w3.org/2013/11/13-participate-minutes.html "Better Participation" breakout session] at TPAC 2013 (Shenzhen).<br />
<br />
==== Milestones ====<br />
<br />
* [~'14.4Q] Researching and surveying on the current practices and experiences in the international communities.<br />
<br />
* [~'14.4Q] Gathering the comments and suggestions from W3C members regarding the current limitations and obstacles. <br />
<br />
* [~'15.1Q] Analyzing and brainstorming on the collected suggestions, limitations and ideas to come up with the preferable approaches to multilingual participations. In conjunction with AB meeting on February, 2015.<br />
<br />
* [~'15.2Q] Summarizing the AB suggestions to AC and having their feedbacks for further evaluations. In conjunction with AC meeting on May, 2015.<br />
<br />
* [~'15.4Q] Evaluating the suggested practices and expanding the research and survey continuously.<br />
<br />
==== Task Force members ====<br />
<br />
* Soohong Daniel Park [Lead]<br />
* Jay Kishigami [Lead]<br />
* Natasha Rooney (I live in Japan and have to deal with the late conference calls, also, I can relay any issues being expressed to me from the native Japanese speakers who may have little English ability)<br />
* Daniel Davis (I also live in Japan - same comment/offer as Natasha)<br />
* Kerry Taylor (I live in Australia and I want time zone and hemisphere and distance to be addressed too! And I think the task force should be called "global W3C")<br />
* Ann Bassetti (I live in Seattle. I have long been interested in, concerned about, and fascinated by how to better enable communications across language, culture, time zones, etc.)<br />
* Angel Li (Interesting self-introduction pattern :-) I live in Beijing, not a native English speaker. Also have to deal with late night calls, interpret/translate the information from W3C to local community in an easier way, and try to set up or sometimes work as the bridge between W3C community and the local members. Not easy. This TF seems to be a good place to work on this puzzle. Happy to be on board.)</div>Ddavishttps://www.w3.org/wiki/index.php?title=AB/2014-2015_Priorities/multilingual_W3C&diff=81353AB/2014-2015 Priorities/multilingual W3C2015-02-13T08:15:55Z<p>Ddavis: /* Suggestions (based on members discussion) */</p>
<hr />
<div><br />
==== Raison d'être ====<br />
<br />
The limits of your language means the limits of your world. However only one language as English is workable for W3C works such as f2f discussion, email discussion, documentation and even minutes officially. That situation makes non-English natives hesitant for W3C participation and sometimes not fully productive within the W3C. <br />
<br />
The new project as the best practice for multilingual W3C has been formed during the last AB meeting in November TPAC and chartered to work on the brainstorming and researching ways of wider collaboration in W3C from non-English native speakers than before, and come up with the solutions.<br />
<br />
==== Basics of the project ====<br />
<br />
* The project does not intend non-English speakers to learn any languages and level up their communications skill. It is clearly out of scope of the project.<br />
<br />
* The project aims to look into the current W3C multilingual issues and come up with the best practice for multilingual participation and discussions in W3C from non-English speakers.<br />
<br />
==== Suggestions (based on members discussion) ====<br />
* Non-English participation<br />
** Call for question/comment to multilingual participants and collect their requirements prior to the meeting (in particular AC/TPAC) and post them on the meeting website to be shared with all participants. Anyone can answer them freely on the website or in the meeting in person.<br />
** Detail descriptions on all agenda items to be clearly understood to multilingual participants prior to the meeting (in particular AC/TPAC). Don't say like "HTML5 what is next ?". This could be a local meeting or call and could include IRC advice and "some tricks for offline communication like corridor conversation and bar talk" (Angel's comment). <br />
* Translation method<br />
** no preference at this stage.<br />
* Technical<br />
** First step is to have a Simple-English summary of any important topics after the meeting. For instance, policy discussions, process changes and specific decisions. That should take place less than one week from the meeting end.<br />
* Application<br />
* Communication barrier between multi-culture background'''<br />
** Several breakout sessions for each multilingual participants coordinated with W3C teams where major language is not English, and each breakout session can have its own preferred language. To recognize these sessions, we are tagging the mark to these sessions on the agenda page or dashboard in meeting place. For instance, A Session (Korean), B Session (Japanese), C Session (Chinese), and so on.<br />
* General<br />
** Set up an anonymous question page (Members only) where AC reps can post questions they may be embarrassed to ask in person (e.g. What is WHATWG? What are the main points in the @@@ discussion?). Answers or clarification could be sent either to the w3c-ac-forum list or a new w3c-answers list. <br />
** Extend the buddy program beyond AC/TPAC meetings only so that new AC reps have someone specific to ask for help during their first year. (Originally suggested by Ann I believe.)<br />
<br />
==== Milestones ====<br />
<br />
* [~'14.4Q] Researching and surveying on the current practices and experiences in the international communities.<br />
<br />
* [~'14.4Q] Gathering the comments and suggestions from W3C members regarding the current limitations and obstacles. <br />
<br />
* [~'15.1Q] Analyzing and brainstorming on the collected suggestions, limitations and ideas to come up with the preferable approaches to multilingual participations. In conjunction with AB meeting on February, 2015.<br />
<br />
* [~'15.2Q] Summarizing the AB suggestions to AC and having their feedbacks for further evaluations. In conjunction with AC meeting on May, 2015.<br />
<br />
* [~'15.4Q] Evaluating the suggested practices and expanding the research and survey continuously.<br />
<br />
==== Task Force members ====<br />
<br />
* Soohong Daniel Park [Lead]<br />
* Jay Kishigami [Lead]<br />
* Natasha Rooney (I live in Japan and have to deal with the late conference calls, also, I can relay any issues being expressed to me from the native Japanese speakers who may have little English ability)<br />
* Daniel Davis (I also live in Japan - same comment/offer as Natasha)<br />
* Kerry Taylor (I live in Australia and I want time zone and hemisphere and distance to be addressed too! And I think the task force should be called "global W3C")<br />
* Ann Bassetti (I live in Seattle. I have long been interested in, concerned about, and fascinated by how to better enable communications across language, culture, time zones, etc.)<br />
* Angel Li (Interesting self-introduction pattern :-) I live in Beijing, not a native English speaker. Also have to deal with late night calls, interpret/translate the information from W3C to local community in an easier way, and try to set up or sometimes work as the bridge between W3C community and the local members. Not easy. This TF seems to be a good place to work on this puzzle. Happy to be on board.)</div>Ddavishttps://www.w3.org/wiki/index.php?title=AB/2014-2015_Priorities/multilingual_W3C&diff=81352AB/2014-2015 Priorities/multilingual W3C2015-02-13T08:12:03Z<p>Ddavis: /* Suggestions (based on members discussion) */ Added extra explanation to pre-AC agenda call.</p>
<hr />
<div><br />
==== Raison d'être ====<br />
<br />
The limits of your language means the limits of your world. However only one language as English is workable for W3C works such as f2f discussion, email discussion, documentation and even minutes officially. That situation makes non-English natives hesitant for W3C participation and sometimes not fully productive within the W3C. <br />
<br />
The new project as the best practice for multilingual W3C has been formed during the last AB meeting in November TPAC and chartered to work on the brainstorming and researching ways of wider collaboration in W3C from non-English native speakers than before, and come up with the solutions.<br />
<br />
==== Basics of the project ====<br />
<br />
* The project does not intend non-English speakers to learn any languages and level up their communications skill. It is clearly out of scope of the project.<br />
<br />
* The project aims to look into the current W3C multilingual issues and come up with the best practice for multilingual participation and discussions in W3C from non-English speakers.<br />
<br />
==== Suggestions (based on members discussion) ====<br />
* Non-English participation<br />
** Call for question/comment to multilingual participants and collect their requirements prior to the meeting (in particular AC/TPAC) and post them on the meeting website to be shared with all participants. Anyone can answer them freely on the website or in the meeting in person.<br />
** Detail descriptions on all agenda items to be clearly understood to multilingual participants prior to the meeting (in particular AC/TPAC). Don't say like "HTML5 what is next ?". This could be a local meeting or call and could include "some tricks for offline communication like corridor conversation and bar talk" (Angel's comment). <br />
* Translation method<br />
** no preference at this stage.<br />
* Technical<br />
** First step is to have a Simple-English summary of any important topics after the meeting. For instance, policy discussions, process changes and specific decisions. That should take place less than one week from the meeting end.<br />
* Application<br />
* Communication barrier between multi-culture background'''<br />
** Several breakout sessions for each multilingual participants coordinated with W3C teams where major language is not English, and each breakout session can have its own preferred language. To recognize these sessions, we are tagging the mark to these sessions on the agenda page or dashboard in meeting place. For instance, A Session (Korean), B Session (Japanese), C Session (Chinese), and so on.<br />
* General<br />
** Set up an anonymous question page (Members only) where AC reps can post questions they may be embarrassed to ask in person (e.g. What is WHATWG? What are the main points in the @@@ discussion?). Answers or clarification could be sent either to the w3c-ac-forum list or a new w3c-answers list. <br />
** Extend the buddy program beyond AC/TPAC meetings only so that new AC reps have someone specific to ask for help during their first year. (Originally suggested by Ann I believe.)<br />
<br />
==== Milestones ====<br />
<br />
* [~'14.4Q] Researching and surveying on the current practices and experiences in the international communities.<br />
<br />
* [~'14.4Q] Gathering the comments and suggestions from W3C members regarding the current limitations and obstacles. <br />
<br />
* [~'15.1Q] Analyzing and brainstorming on the collected suggestions, limitations and ideas to come up with the preferable approaches to multilingual participations. In conjunction with AB meeting on February, 2015.<br />
<br />
* [~'15.2Q] Summarizing the AB suggestions to AC and having their feedbacks for further evaluations. In conjunction with AC meeting on May, 2015.<br />
<br />
* [~'15.4Q] Evaluating the suggested practices and expanding the research and survey continuously.<br />
<br />
==== Task Force members ====<br />
<br />
* Soohong Daniel Park [Lead]<br />
* Jay Kishigami [Lead]<br />
* Natasha Rooney (I live in Japan and have to deal with the late conference calls, also, I can relay any issues being expressed to me from the native Japanese speakers who may have little English ability)<br />
* Daniel Davis (I also live in Japan - same comment/offer as Natasha)<br />
* Kerry Taylor (I live in Australia and I want time zone and hemisphere and distance to be addressed too! And I think the task force should be called "global W3C")<br />
* Ann Bassetti (I live in Seattle. I have long been interested in, concerned about, and fascinated by how to better enable communications across language, culture, time zones, etc.)<br />
* Angel Li (Interesting self-introduction pattern :-) I live in Beijing, not a native English speaker. Also have to deal with late night calls, interpret/translate the information from W3C to local community in an easier way, and try to set up or sometimes work as the bridge between W3C community and the local members. Not easy. This TF seems to be a good place to work on this puzzle. Happy to be on board.)</div>Ddavishttps://www.w3.org/wiki/index.php?title=AB/2014-2015_Priorities/multilingual_W3C&diff=81350AB/2014-2015 Priorities/multilingual W3C2015-02-13T07:00:09Z<p>Ddavis: /* Suggestions (based on members discussion) */ Added two more suggestions</p>
<hr />
<div><br />
==== Raison d'être ====<br />
<br />
The limits of your language means the limits of your world. However only one language as English is workable for W3C works such as f2f discussion, email discussion, documentation and even minutes officially. That situation makes non-English natives hesitant for W3C participation and sometimes not fully productive within the W3C. <br />
<br />
The new project as the best practice for multilingual W3C has been formed during the last AB meeting in November TPAC and chartered to work on the brainstorming and researching ways of wider collaboration in W3C from non-English native speakers than before, and come up with the solutions.<br />
<br />
==== Basics of the project ====<br />
<br />
* The project does not intend non-English speakers to learn any languages and level up their communications skill. It is clearly out of scope of the project.<br />
<br />
* The project aims to look into the current W3C multilingual issues and come up with the best practice for multilingual participation and discussions in W3C from non-English speakers.<br />
<br />
==== Suggestions (based on members discussion) ====<br />
* Non-English participation<br />
** Call for question/comment to multilingual participants and collect their requirements prior to the meeting (in particular AC/TPAC) and post them on the meeting website to be shared with all participants. Anyone can answer them freely on the website or in the meeting in person.<br />
** Detail descriptions on all agenda items to be clearly understood to multilingual participants prior to the meeting (in particular AC/TPAC). Don't say like "HTML5 what is next ?". <br />
* Translation method<br />
** no preference at this stage.<br />
* Technical<br />
** First step is to have a Simple-English summary of any important topics after the meeting. For instance, policy discussions, process changes and specific decisions. That should take place less than one week from the meeting end.<br />
* Application<br />
* Communication barrier between multi-culture background'''<br />
** Several breakout sessions for each multilingual participants coordinated with W3C teams where major language is not English, and each breakout session can have its own preferred language. To recognize these sessions, we are tagging the mark to these sessions on the agenda page or dashboard in meeting place. For instance, A Session (Korean), B Session (Japanese), C Session (Chinese), and so on.<br />
* General<br />
** Set up an anonymous question page (Members only) where AC reps can post questions they may be embarrassed to ask in person (e.g. What is WHATWG? What are the main points in the @@@ discussion?). Answers or clarification could be sent either to the w3c-ac-forum list or a new w3c-answers list. <br />
** Extend the buddy program beyond AC/TPAC meetings only so that new AC reps have someone specific to ask for help during their first year. (Originally suggested by Ann I believe.)<br />
<br />
==== Milestones ====<br />
<br />
* [~'14.4Q] Researching and surveying on the current practices and experiences in the international communities.<br />
<br />
* [~'14.4Q] Gathering the comments and suggestions from W3C members regarding the current limitations and obstacles. <br />
<br />
* [~'15.1Q] Analyzing and brainstorming on the collected suggestions, limitations and ideas to come up with the preferable approaches to multilingual participations. In conjunction with AB meeting on February, 2015.<br />
<br />
* [~'15.2Q] Summarizing the AB suggestions to AC and having their feedbacks for further evaluations. In conjunction with AC meeting on May, 2015.<br />
<br />
* [~'15.4Q] Evaluating the suggested practices and expanding the research and survey continuously.<br />
<br />
==== Task Force members ====<br />
<br />
* Soohong Daniel Park [Lead]<br />
* Jay Kishigami [Lead]<br />
* Natasha Rooney (I live in Japan and have to deal with the late conference calls, also, I can relay any issues being expressed to me from the native Japanese speakers who may have little English ability)<br />
* Daniel Davis (I also live in Japan - same comment/offer as Natasha)<br />
* Kerry Taylor (I live in Australia and I want time zone and hemisphere and distance to be addressed too! And I think the task force should be called "global W3C")<br />
* Ann Bassetti (I live in Seattle. I have long been interested in, concerned about, and fascinated by how to better enable communications across language, culture, time zones, etc.)<br />
* Angel Li (Interesting self-introduction pattern :-) I live in Beijing, not a native English speaker. Also have to deal with late night calls, interpret/translate the information from W3C to local community in an easier way, and try to set up or sometimes work as the bridge between W3C community and the local members. Not easy. This TF seems to be a good place to work on this puzzle. Happy to be on board.)</div>Ddavishttps://www.w3.org/wiki/index.php?title=HTML/Media_Task_Force&diff=80960HTML/Media Task Force2015-02-04T05:47:26Z<p>Ddavis: Added link to mailing list archives</p>
<hr />
<div>= HTML Media Task Force =<br />
<br />
This is the HTML Media Task Force wiki. We can collect use cases, useful references, etc. <br />
<br />
* [http://lists.w3.org/Archives/Public/public-html-media/ Mailing list archives]<br />
<br />
== Encrypted Media Extensions ==<br />
<br />
[https://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/encrypted-media.html Current Editor's Draft]<br />
<br />
[[HTML/Media_Task_Force/EME_Use_Cases|Use Cases]]<br />
<br />
[[HTML/Media_Task_Force/CDM_Use_Cases|CDM Use Cases]]<br />
<br />
=== External References ===<br />
<br />
* [http://www.uvvuwiki.com/specs Public Ultraviolet specifications]<br />
* [https://docs.google.com/drawings/d/128iTMqVgI3gCPo7q1mB2RIq-iCV3og0FMfVlY0mRWOg/edit?usp=sharing Generic Key Model]<br />
<br />
== Media Source Extensions ==<br />
<br />
[https://w3c.github.io/media-source/ Current Editor's Draft]</div>Ddavishttps://www.w3.org/wiki/index.php?title=HTML/Media_Task_Force&diff=80959HTML/Media Task Force2015-02-04T05:44:31Z<p>Ddavis: Added MSE section</p>
<hr />
<div>= HTML Media Task Force =<br />
<br />
This is the HTML Media Task Force wiki. We can collect use cases, useful references, etc. <br />
<br />
== Encrypted Media Extensions ==<br />
<br />
[https://dvcs.w3.org/hg/html-media/raw-file/default/encrypted-media/encrypted-media.html Current Editor's Draft]<br />
<br />
[[HTML/Media_Task_Force/EME_Use_Cases|Use Cases]]<br />
<br />
[[HTML/Media_Task_Force/CDM_Use_Cases|CDM Use Cases]]<br />
<br />
=== External References ===<br />
<br />
* [http://www.uvvuwiki.com/specs Public Ultraviolet specifications]<br />
* [https://docs.google.com/drawings/d/128iTMqVgI3gCPo7q1mB2RIq-iCV3og0FMfVlY0mRWOg/edit?usp=sharing Generic Key Model]<br />
<br />
== Media Source Extensions ==<br />
<br />
[https://w3c.github.io/media-source/ Current Editor's Draft]</div>Ddavishttps://www.w3.org/wiki/index.php?title=IRC&diff=80389IRC2015-01-14T02:14:56Z<p>Ddavis: /* See Also */ Added link to other IRC page with client details</p>
<hr />
<div>This public wiki was started in November 2013 as part of an [[AB]] objective to [[Encouraging-Participation|Encourage meeting participation]]. <br />
<br />
This wiki complements the [http://www.w3.org/Project/IRC/ Guidebook section on IRC], and serves as a beginner's introduction to IRC for W3C Meetings.<br />
<br />
__TOC__ <br />
<br />
==Brief overview for using IRC at W3C ==<br />
<br />
Internet Relay Chat (IRC) is perhaps the most important tool used at W3C. Typically, everyone in a meeting is logged into the IRC channel for that meeting -- whether they are in a face-to-face meeting or virtual. <br />
<br />
These pages seek to give participants a basic understanding of how to use IRC at W3C.<br />
<br />
=== Introduction === <br />
* IRC = "Internet Relay Chat", a form of group chat<br />
* Each participant chooses when he or she enters and leaves the chat room (also known as a "channel")<br />
* Everyone sees, and can respond to, what anyone in the room types<br />
* Minutes of almost all W3C meetings are written ('scribed') in IRC during the meeting<br />
* Meeting participants can watch the notes being written during the meeting, adding to them, or clarifying statements. (One can also help be the scribe!)<br />
<br />
=== How to log in ===<br />
* This image shows how to access IRC via a browser connecting to the W3C IRC server.<br />
* There is also IRC software available for most platforms and other IRC servers.<br />
[[File:Irc-w3-org.png|frameless|500px]]<br />
* Start by going to http://irc.w3.org<br />
* Which takes you to this login screen...<br />
[[File:W3c_irc_login.png|frameless|500px]]<br />
<br />
# Put your name (might be your full name, or a nickname such as 'AnnB', as shown). If more than one word, you must use a hyphen or underline instead of space (example: Ann_Bean).<br />
#* Consider adding your IRC nickname to [[irc-people]]<br />
# Put the chat channel (or 'room') you want to enter (in this example = #ac). Channel names start with # character.<br />
# Put a space, then the password, if there is one (in this example 'mita' is the password). If there is no password, you only type the channel name, with nothing following.<br />
# Click "Connect"<br />
[[File:W3c_ac_channel.png|frameless|500px]]<br />
* You should now be 'in the room'. (See the arrow indicating where IRC says AnnB joined the room.) The list of names on the right shows all the people in the room. (Also see the arrow indicating AnnB among the list of people 'in the room', on the right.)<br />
* When a participant says or does something, his or her name appears in brackets, followed by what was said or done. In this example, 'ivan' and 'olivier' have said things. 'AnnB', 'manyoung' and 'kazu' have entered the room.<br />
<br />
If that doesn't work, leave the channel field empty, and use "/join #ac mita" in the input field of the window after connecting.<br />
<br />
=== How to say something ===<br />
[[File:How_to_say_something_in_IRC.png|frameless|500px]]<br />
* To post a comment in the chat room, put your cursor in the blank area at the bottom of the screen, and type. In this example, I am about to say "... the goal is to give a succinct overview to a situation and proposal". <br />
* When you push the 'Enter' button, your comment will be posted into the chat room. You can edit or delete your comment before you 'Enter'. <br />
* You may also enter a URL, which will show up as a link in the chat room.<br />
<br />
=== How to change something you said, after it has been posted ===<br />
[[File:Change text after posted 1of3.png|frameless|500px]]<br />
* For example, AnnB posted "this is a demo posting"<br />
[[File:Change text after posted 2of3.png|frameless|500px]]<br />
* Then she decided it was more accurate to say, "this is a test post"<br />
* The format of the command to change the entry is ''''' s/<old text>/<new text>/'''''<br />
* Note: one does not see the change in the chat room, in the 'raw' chat log. The text will be corrected in the "cleaned-up" web version of the minutes.<br />
[[File:Change text after posted 3of3.png|frameless|500px]]<br />
* Next, because this was only an example posting, AnnB wanted to delete the text totally<br />
* The format of the command to delete an entry is '''''s/<text to be deleted>//''''' <br />
* Again, the change does not appear in the 'raw' chat log, but will be corrected in the "cleaned-up" web version of the minutes.<br />
<br />
=== How to join more than one room ===<br />
* You can be in more than one chat room at a time. See the next example...<br />
[[File:Join new room.png|frameless|500px]]<br />
* At the bottom of the chat window you are in, type the command: ''''' /join #name-of-new-room''''' <br />
* In this example, I am in the room #ac, and am asking to join the additional room called "ac-chat".<br />
[[File:More than one room.png|frameless|500px]]<br />
* Using the W3C tool in a browser, each room shows up as a different 'tab', as indicated. <br />
* Click the tabs to move back and forth between rooms. In this example, I am in both the #ac and #ac-chat rooms, and I am reading what's going on in #ac.<br />
* TIP: in many W3C meetings, there is one room for the meeting minutes and discussion, and a separate room for 'social' chatter. In this case, the name of the social room is "#ac-chat". This is where people make jokes, side comments and ask questions that are unrelated to the formal discussion going on in the meeting. The names of the rooms are announced during each meeting.<br />
<br />
=== Putting yourself in the speaking queue ===<br />
The W3C IRC system uses its own software robot, named 'Zakim', to manage the speakers' queue. This is very helpful during a meeting, to know whose turn it is to speak. ([http://www.w3.org/2001/12/zakim-irc-bot Zakim has other capabilities] as well.)<br />
[[File:Put yourself in queue.png|frameless|500px]]<br />
# To put yourself in the speakers' queue, type: '''q+''' (In the #1 example shown, the user named 'jerenkrantz' has just put himself into the queue. ) Zakim responds by listing out the current queue. (In this example, 'jerenkrantz' is the only person in the queue.)<br />
# When you put yourself in the queue, you can also type a reminder to yourself about what you want to say, by typing: '''q+ to say <what you want to say>''' In the #2 example shown, 'MikeSmith' puts himself in the queue, reminding himself he wants to ask about the logistics of the group.<br />
# One can check to see who is in the queue by typing: '''q?''' In the third example, 'dom' checks the queue and Zakim responds that 'jerenkrantz' and 'MikeSmith' are in the queue, in that sequence.<br />
<br />
=== Removing yourself from the speaking queue ===<br />
[[File:Remove yourself from queue.png|frameless|500px]]<br />
Occasionally one decides that he or she wants to drop off the speaking queue. <br />
# In this example, "AnnB" is in the queue, as is "chaals" <br />
# She decides she no longer wants to speak, thus types: '''q-''' which removes her from the queue.<br />
# Zakim (the IRC software robot) responds, showing that the only person remaining in the queue is now 'chaals'. <br />
<br />
=== Out of band or off the record comments ===<br />
W3C house style is to use "action" messages to denote out-of-band or off-the-record comments. Most IRC clients have a command called '''/me''' that generates this type of message. Clients generally display these messages in a different style from normal messages. For example, the irc command "/me waves" might result in the discussion window showing the text "* AnnB waves". The RRSAgent logging tool excludes these messages from the Web log and minutes.<br />
<br />
When IRC is used to keep meeting minutes it is important to distinguish what was actually said in the meeting from side conversations that were not heard by all (i.e., on a teleconference). We encourage the use of square brackets around messages that are intended to be side comments for the log; e.g. "[AnnB agrees]".<br />
<br />
=== Conclusion ===<br />
IRC is a very important tool for participating in W3C meetings, as well as in the social community. Please join in!<br />
<br />
== See Also ==<br />
* [[irc-people]]<br />
* [[InternetRelayChat]]</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=79521Webizen2014-11-26T07:41:10Z<p>Ddavis: /* Participants */ Added myself</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
This wiki is the home page for the ''Webizen Task Force''. <br />
<br />
[See the [https://www.w3.org/wiki/Webizen-historic historic content] that the task force developed between March and June 2014.]<br />
<br />
The essence of the '''proposed''' ''Webizen'' program is to provide a way for individuals to obtain some benefits, possibly in exchange for a nominal fee. This task force will explore whether such a program is viable and, if so, the set of benefits.<br />
<br />
'''This document is a DRAFT, i.e. it is a Work In Progress (WIP). Feedback is welcome, preferably by directly editing this document or by sending email to <code>[mailto:public-webizen@w3.org public-webizen@w3.org]</code> ([http://lists.w3.org/Archives/Public/public-webizen/ archive]). We are also interested in input from non-Members i.e. ''The Public''.'''<br />
<br />
----<br />
<br />
To join the task force, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org] and add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until @TBD. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive]<br />
* '''teleconference''': +1.617.761.6200, Code: 93249 (“WEBIZ"). <br />
* '''IRC''': irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
* '''Facebook''': [https://www.facebook.com/Webizen Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (search for “individual membership“), the W3C Director requested exploration of individual participation in W3C. The current proposal, for a "Webizen" mode of participation, addresses this request. Note, the ''Webizen'' program is '''not''' a Membership program, although it should provide certain benefits and privileges. 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.<br />
<br />
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.<br />
<br />
== Goals ==<br />
We can make a distinction between the goals of the W3C and those of the future Webizens.<br />
<br />
=== for the W3C ===<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
* Become a forum for discussing issues around W3C specifications, sharing solutions, providing feedback to W3C, and for W3C to share information out.<br />
* Enhance W3C's stewardship of the Web<br />
* Build appreciation for W3C among front-end developers<br />
<br />
=== for the subscribers ===<br />
<br />
* Add a line on the CV that shows commitment to the advances of Web standards and W3C's recognition for the help individually provided<br />
* Get a discount for conferences<br />
* Influence the design of standards<br />
* [tbc] Meet (online and irl) the community of web standard makers<br />
<br />
== Mission ==<br />
<br />
We need to have a longer discussion about mission. The focus to date has been around increased affiliation or inclusion in the W3C community. But other laudable mission statements have also been proposed. The working set of missions under discussion are:<br />
<br />
* Allow greater affiliation with W3C making W3C a more inclusive organization.<br />
* Increase the professionalism of the web community<br />
* Enhance education and training<br />
* Increase creativity of the web community<br />
<br />
While the last three are truly worthwhile, the current set of proposed elements of the program do not address these candidate mission statements. So we need to decide: accept the broader mission and design a program to match, or start with the narrower mission.<br />
<br />
== Success criteria ==<br />
It is important to verify that the values mentioned implied by "Goals" above (especially for W3C) are actually materialized. A worst-case scenario could be that the criteria mentioned below are achieved, but it also creates a lot of friction and problems for W3C's normal business (e.g., WGs).<br />
* Achieve aforementioned goals<br />
* Don't lose money<br />
* Attract a significant number of Webizens<br />
** Should be supremely confident about the first 100<br />
** Should have some idea where the next 900 will come from<br />
* Most Invited Experts should be persuaded to also become Webizens<br />
* [tbc] Don't affect the current membership<br />
<br />
== Representation ==<br />
<br />
For Webizens to appreciate that the program gives them access to the work of W3C requires building some mechanisms that makes their input effective. By comparison there are two major methods in which Members have input into W3C, by assigning staff to Working Groups and in advising W3C on governance related issues through the Advisory Committee (AC). A significant part of the latter is AC Charter review for new work.<br />
<br />
It has been an item of controversy to determine what mechanism we should use for Webizens. On the one hand, W3C already takes public input quite seriously. So even without a Webizen program there are already mechanisms for the general public to have input to W3C. Moreover, for actual participation in Working Groups, we already have a successful Invited Expert program (which has no cost for the IE). On the other hand, an earlier proposal - to essentially give a seat on the AC to some number of Webizens - received considerable pushback from the AC. Members point out that they receive AC review rights by investing a great deal in the consortium (through Membership dues, assigning staff to Working Groups, and IPR commitments) and so these rights should not be deprecated by giving similar rights to Webizens.<br />
<br />
With no consensus on this key topic, we summarize in this wiki the closest we have come to consensus. The idea would be to get further feedback through the market survey below. Here is the proposal:<br />
<br />
* Webizens have no additional means to participate in Working Groups (i.e. the existing IE mechanism suffices).<br />
* Webizens do not participate in the W3C Advisory Committee.<br />
* Webizens are able to review W3C Charters. In truth, proposed Charters are public and can be reviewed today by the public. However, this rarely happens, and individual Members of the public might feel that their individual inputs might be ignored. However, Webizens will band together to form "Developer Groups" who provide aggregate input from classes of developers. Accordingly, the W3C Director would take this input very seriously; even if it is not a part of the formal W3C process. Sample developer groups could be of the form:<br />
** Front end developers<br />
** Developers who worry about accessibility<br />
** Developers who worry about privacy<br />
** App developers<br />
** FOSS developers<br />
<br />
== Target market and marketing study ==<br />
<br />
The task force decided to reach out to W3C community with a questionnaire to be our marketing study, promoting it via Twitter and other means.<br />
<br />
Julian will also reach out to additional resources to determine if we can professionalize the study.<br />
<br />
The study will ask people if they would be willing to become Webizens. It will offer several candidate benefits and see which ones are of interest; which ones would make it worthwhile to become Webizens.<br />
<br />
We will send the same poll to the AC to get their input as well.<br />
<br />
=== Workspace for Survey ===<br />
<br />
The plan is to tweet to W3C's followers that we are having this survey and provide the link to the survey. As encouragement responders could get some validator coupons. We ended up not leveraging coupons.<br />
<br />
Survey: <br />
* [https://www.w3.org/2002/09/wbs/1/webizen-survey/ https://www.w3.org/2002/09/wbs/1/webizen-survey/]<br />
* [https://koalie.typeform.com/to/znIPxi https://koalie.typeform.com/to/znIPxi]<br />
<br />
Results:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Oct/0000.html Quick overview of public survey]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Oct/0002.html Consolidated results of the public Webizen survey]<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
* Daniel Glazman<br />
* Georg Rehm<br />
* Mark Crawford<br />
* Vagner Diniz<br />
* Julian Harriott<br />
* Yosuke Funahashi<br />
* Léonie Watson<br />
* Armin Haller<br />
* Olle Olsson<br />
* David Ezell<br />
* Christophe Guéret<br />
* Michiel Leenaars<br />
* Timothy Holborn<br />
* Daniel Davis<br />
<br />
=== Schedule ===<br />
<br />
<br />
=== Meeting records and actions===<br />
* [https://www.w3.org/2014/10/03-webizen-minutes.html 2014-10-03]<br />
* [https://www.w3.org/2014/09/05-webizen-minutes.html 2014-09-05]<br />
** ACTION: Coralie to get survey, once final, translated in W3C Offices languages<br />
** ... Subsequently [http://lists.w3.org/Archives/Public/public-webizen/2014Sep/0040.html cancelled]<br />
* [http://www.w3.org/2014/08/20-webizen-minutes.html 2014-08-20]<br />
** ACTION: Jeff to, based on this call, propose further questions to the survey.<br />
* [http://www.w3.org/2014/08/01-webizen-minutes.html 2014-08-01]<br />
** ACTION: Julian will determine whether colleagues from market research firms could help with the market research study.</div>Ddavishttps://www.w3.org/wiki/index.php?title=AB&diff=78995AB2014-11-05T23:44:05Z<p>Ddavis: /* AB Priorities for 2014/2015 */ Tiny typo fix</p>
<hr />
<div><div style="float:right;padding:0 0 1em 1em">[[File:20140917_AB-london.jpg|400px]]</div><br />
The <dfn>'''[http://www.w3.org/2002/ab/ W3C Advisory Board]'''</dfn> (AB) provides ongoing guidance to the W3C Team on issues of strategy, management, legal matters, process, and conflict resolution. this page gathres the diffrent project AB is currently handling, and is open to any suggestion from members and non-members. <br />
<div style="float:right;clear:right">__TOC__</div><br />
<br />
== AB Priorities for 2014/2015 ==<br />
AB identified some projects gathering enough support by AB members to be rolled out in 2014/2015. Here is a short description of each identified project. <br />
<br />
# '''Identify work not destined for success.''' Lead: Mike Champion [''this is project #1 from "Prioritizing the current investments of W3C"''] See [https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_work_success plan]<br />
# '''Identify the most important priorities for the Web and W3C.''' Lead: Jeff Jaffe [''this is a merge of projects #3 and #4 from "Prioritizing..."'' ] See [https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_most_important plan]<br />
# '''Improve agility of W3C.''' Lead: Chris Wilson [''this is a merge of projects #1, #2, #6, and #7 from "Improving the W3C Process broadly, or best practices to implement the process"''] See [https://www.w3.org/wiki/Agility plan]<br />
# '''W3C Process Revision 2015.''' Lead: Steve Zilles, Editor: Chaals McCathie Nevile [''this also includes working on Process Revision 2016. This is project #3 from "Improving..."'']<br />
# '''Trademark Policy and Licensing.''' Lead: Mike Champion and Tantek Çelik [''this is project #5 from "Improving..."''] See [https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_work_trademark plan]<br />
# '''Provenance of spec text.''' Lead: Mike Champion [''this is project #8 from "Improving..."''] See [https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_spec_provenance plan]<br />
# '''Voting experiment.''' Lead: Chaals McCathie Nevile [''this is project #3 from "Voting"'']<br />
# '''W3C synchronization and consistency.''' Lead: Virginie Galindo [''this is project #3 from "New demands"''] See [https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_synchro_consistency_plan plan]<br />
# '''Improving how AB represents the AC.''' Lead: Virginie Galindo [''this is project #2 from "AB role"''] See [https://www.w3.org/wiki/AB/2014-2015_Priorities/w3C_AB_representing_AC_plan plan]<br />
# '''Best practices to support multilingual W3C''' Lead: Daniel Park and Jay Kishigami See [https://www.w3.org/wiki/AB/2014-2015_Priorities/multilingual_W3C plan]<br />
<br />
<br />
See how AB members have been selecting priority topics [https://www.w3.org/wiki/AB/2014-2015_Priorities 2014-2015 AB Priorities wiki page]<br />
<br />
== New project to suggest to the AB ? ==<br />
Suggestions for the AB can be done directly by editing this wiki, here, anytime. <br />
<br />
== AB F2F Meetings and conference calls ==<br />
=== Upcoming meetings ===<br />
* [[AB/2014-11-SCL|2014-10-30..31 Santa Clara, California]] (during [[TPAC2014]])<br />
* 2014-11-17 teleconference<br />
* 2014-12-15 teleconference<br />
* [[AB/2015-02-TKY|2015-02-11..12 Tokyo, Japan]]<br />
* 2015-05-04..05 Paris, France (next to AC Meeting)<br />
<br />
<br />
Taxi sharing for f2f meetings is organized on the wiki: [[MeetingTaxis]]<br />
<br />
More: https://www.w3.org/Member/Board/ (W3C Member Only Link)<br />
<br />
=== Past ===<br />
Past f2f meetings:<br />
* [[AB/2014-03-SF|2014-03-04..05 San Francisco]]<br />
* [[AB/2014-06-MA|2014-06-11..12 Cambridge, MA]] (after Cambridge, MA AC Meeting)<br />
* [[AB/2014-09-LON|2014-09-16..17 London, England]]<br />
<br />
=== Editing and Publishing the minutes of AB Meetings (related to W3C members minutes)===<br />
Quote from the [https://lists.w3.org/Archives/Member/w3c-ac-members/2011OctDec/0056.html summary of 3-4 November 2011 AB face-to-face meeting] (W3C Member only link):<br />
<blockquote>The Advisory Board, recognizing that the IRC minutes are not a verbatim transcription, adopted a protocol by which each speaker can have their recorded statements edited when he or she feels that what is recorded is either incorrect or needs clarification.</blockquote><br />
<br />
<blockquote>Other AB participants can ask a participant to clarify his or her remarks, but cannot insist on a change. </blockquote><br />
<br />
<blockquote>The protocol is to send requests in e-mail to the AB list, as the only mechanism to change the minutes generated from the IRC record. The goal is to increase both transparency and coherence.</blockquote><br />
<br />
== W3C Process, Governance and IP related projects ==<br />
<br />
=== W3C Process maintenance ===<br />
W3C [[process]] improvements are discussed in the community group:<br />
* http://www.w3.org/community/w3process/<br />
<br />
See [[process]] for more details.<br />
<br />
<br />
<br />
=== Cultural conventions for attribution ===<br />
The new [[HTMLWG]] charter allows for working group members to contribute HTML5 Extension specifications using CC-by, and then places attribution requirements on any derivative works.<br />
<br />
These attribution requirements are a good start for growing cultural conventions for attribution both inside W3C, and beyond W3C, towards a goal of making attribution founded in cultural norms rather than legal (copyright) requirements, potentially allowing for use of CC0 for contributions to W3C in the future.<br />
<br />
=== Trademark License ===<br />
{{main|AB/trademark-license}}<br />
<br />
The AB has created a Trademark License task force (Tantek Çelik and Michael Champion) to build broad consensus on a combination trademark / license policy to potentially permit more permissive copyright licenses on W3C drafts and specifications.<br />
<br />
=== Open AB ===<br />
The AB is working on (as is evident by this wiki page) doing more and more of its work in the open.<br />
<br />
Currently Open AB work is occurring in two places:<br />
* http://www.w3.org/wiki/AB (all projects on this wiki page)<br />
** see "Suggestions" section below to contribute<br />
* https://twitter.com/w3cab<br />
<br />
=== Twitter Account ===<br />
The Advisory Board has a Twitter account: [https://twitter.com/w3cab @W3CAB]<br />
<br />
Nearly the entire AB has access and can post anything regarding AB-related matters. The methodology is to empower individual responsibility and trust by default, especially in such a small group. This method has worked well with the [[CSSWG]] (any CSSWG member may "have the keys" to [https://twitter.com/csswg @CSSWG]) and it's been hugely successful in engaging the broader developer community. <br />
<br />
If you are a [http://www.w3.org/2002/ab/ member of the AB], contact [[User:Tantekelik|Tantek Çelik]] on a secure communications channel and he'll gladly share access to @W3CAB.<br />
<br />
* 2013-09-18 access broadly shared with AB members in person W3C AB meeting at MIT.<br />
* 2013-06-04 @W3CAB Twitter created.<br />
<br />
=== Making sure the ABs get members opinion ===<br />
* AB are elected by W3C members and need to make sure that they are collecting their ideas, suggestion... That wiki is great, the recent minutes members-only minutes issued by Coralie were great, but regular open debriefing communication to members/interested parties is key. It could be interesting to have an every-6-months call scheduled in advance to 'meet the AB'. This would be the opportunity to ask direct question to the AB, based on a collaborative agenda.<br />
Virginie Galindo (gemalto AC rep)<br />
<nowiki>~~~~</nowiki><br />
<br />
=== AB and TAG election : voting experiment ===<br />
AB has been conducting work in order to audit voting and representativity. An experiment will be conducted in 2014/2015. See FAQ and explanation for that first experiment [https://www.w3.org/wiki/AB/STV_experiment page]<br />
<br />
== W3C Community and Tools ==<br />
=== W3C Chairs Training ===<br />
The Advisory Board has established Chair Training as a priority for 2014. At TPAC2013, Chairs had a breakfast meeting and expressed what additional information and skills they required to improve their effectiveness. The W3C Team developed a list of areas which have now evolved into a quarterly Chair Training program.<br />
* 1. [http://www.w3.org/2014/01/23-chairing-minutes.html W3C, Process, and the W3C Team], Philippe Le Hegaret, 23 January 2014<br />
** [http://lists.w3.org/Archives/Public/www-archive/2014Apr/0026.html Anchor sections] by Art Barstow<br />
* 2. [http://www.w3.org/2014/04/24-chairing-minutes Tools], Ralph Swick, 24 April 2014<br />
* 3. [http://www.w3.org/2014/06/17-chairing-minutes.html The Human Dimension], Charles McCathie Nevile, 17 June 2014<br />
* 4. [http://www.w3.org/2014/10/23-chairing-minutes.html Focus and Productivity], Arnaud Le Hors, 23 October 2014<br />
* 5. New W3C process, its philosophy, and how to use it for agility, Steve Zilles, January 2015<br />
* 6. TBC: Making rapid progress in developing specs in W3C despite the W3C process<br />
<br />
=== Creating a web community ===<br />
Not official AB projects per say, but projects that various AB members are participating in that may have W3C-wide scope.<br />
* [[Webizen]]<br />
<br />
=== Use of GitHub at W3C ===<br />
* See <span id="Use_of_Github_at_W3C">[[GitHub]]</span>.<br />
<br />
=== Remote Participation ===<br />
The AB is looking at issues related to remote participation in W3C meetings.<br />
* See [[Remote participation]]<br />
* Including Ann Bassetti's [https://www.w3.org/wiki/IRC Introduction to IRC]<br />
<br />
=== OpenWeb Tools at W3C (was dogfooding) === <br />
Many (most?) presentations at W3C workshops (e.g. the [http://indiewebcamp.com/2013/osfw3c Workshop on Social Standards: The Future of Business]) used non-open-web technologies/formats. W3C may work on good practices. <br />
* See [[open web tool]]<br />
<br />
=== Headlights presented to W3C members for 2014 === <br />
* See: [[Headlights2014]]<br />
<br />
<br />
== AB Wiki Editing Itself ==<br />
Things to work on wiki-editing workflow for (Tantek, Virgine)<br />
* long lived projects having their own undated URLs<br />
* using redirects for per year priorities<br />
* incorporate stuff in [[W3C AB 2013 2014 OLD PAGE]] into specific subpages for more navigable archival.<br />
<br />
== Historical Documents ==<br />
* [[W3C AB 2013 2014 OLD PAGE]]</div>Ddavishttps://www.w3.org/wiki/index.php?title=AB/2014-2015_Priorities/multilingual_W3C&diff=78937AB/2014-2015 Priorities/multilingual W3C2014-11-04T02:14:45Z<p>Ddavis: /* Task Force members */ Added Daniel Davis</p>
<hr />
<div><br />
==== Raison d'être ====<br />
<br />
==== Basics of the project ====<br />
<br />
==== Methodology ====<br />
<br />
==== Milestones ====<br />
<br />
==== Task Force members ====<br />
* Jay Kishigami<br />
* Soohong Daniel Park<br />
* Natasha Rooney (I live in Japan and have to deal with the late conference calls, also, I can relay any issues being expressed to me from the native Japanese speakers who may have little English ability)<br />
* Daniel Davis (I also live in Japan - same comment/offer as Natasha)</div>Ddavishttps://www.w3.org/wiki/index.php?title=AB&diff=73704AB2014-06-10T20:23:05Z<p>Ddavis: /* Dogfooding at W3C */</p>
<hr />
<div><div style="float:right;padding:0 0 1em 1em">[[File:W3C_AB.jpg|400px]]</div><br />
The <dfn>'''[http://www.w3.org/2002/ab/ W3C Advisory Board]'''</dfn> (AB) provides ongoing guidance to the W3C Team on issues of strategy, management, legal matters, process, and conflict resolution.<br />
<div style="float:right;clear:right">__TOC__</div><br />
== Projects ==<br />
=== W3C Process ===<br />
W3C [[process]] improvements are discussed in the community group:<br />
* http://www.w3.org/community/w3process/<br />
<br />
See [[process]] for more details.<br />
<br />
=== W3C Chairs Training ===<br />
The Advisory Board has established Chair Training as a priority for 2014. At TPAC2013, Chairs had a breakfast meeting and expressed what additional information and skills they required to improve their effectiveness. The W3C Team developed a list of areas which have now evolved into a quarterly Chair Training program.<br />
* 1. [http://www.w3.org/2014/01/23-chairing-minutes.html W3C, Process, and the W3C Team, Philippe Le Hegaret, 23 January 2014]<br />
** [http://lists.w3.org/Archives/Public/www-archive/2014Apr/0026.html Anchor sections] by Art Barstow<br />
* 2. [http://www.w3.org/2014/04/24-chairing-minutes Tools], Ralph Swick, 24 April 2014.<br />
* 3. The Human Dimension, Charles McCathie Nevile, 17 June 2014.<br />
* 4. Focus and Productivity, Arnaud Le Hors, October.<br />
<br />
=== Use of GitHub at W3C ===<br />
* See <span id="Use_of_Github_at_W3C">[[GitHub]]</span>.<br />
<br />
=== Cultural conventions for attribution ===<br />
The new [[HTMLWG]] charter allows for working group members to contribute HTML5 Extension specifications using CC-by, and then places attribution requirements on any derivative works.<br />
<br />
These attribution requirements are a good start for growing cultural conventions for attribution both inside W3C, and beyond W3C, towards a goal of making attribution founded in cultural norms rather than legal (copyright) requirements, potentially allowing for use of CC0 for contributions to W3C in the future.<br />
<br />
=== Dogfooding at W3C ===<br />
Many (most?) presentations at W3C workshops (e.g. the [http://indiewebcamp.com/2013/osfw3c Workshop on Social Standards: The Future of Business]) used non-open-web technologies/formats.<br />
<br />
A challenge was made to the participants to use HTML for their presentations proposing additions/technologies for the web platform[http://tantek.com/2013/219/t7/new-rule-learn-html-before-innovate-osfw3c][http://tantek.com/2013/219/t11/osfw3c-w3c-teach-html-slides-instead-powerpoint-pdf] (and criticism for using non-open-web technologies to do so [http://tantek.com/2013/219/t5/publishing-web-docs-specs-pdf-wrong-osfw3c][http://tantek.com/2013/219/t10/not-know-html-publish-know-not-innovate-osfw3c])<br />
<br />
The broader challenge is to use openweb technologies in our day to day interactions at and with W3C, with such use-cases as:<br />
* Presentations (slide formats / online slides)<br />
* Remote collaboration (e.g. use of WebRTC / webcasting instead of phones)<br />
<br />
There is a spectrum of W3C members that can be more/less expected to adopt and use open web technologies:<br />
# Highly technical contributors who are actively designing and specifying advancement of the web platform<br />
# Semi-technical contributors who have some understanding (can write HTML), but have challenges<br />
# General contributors who are discussing customer needs, use-cases<br />
We should be dogfooding and improving tools from top to bottom in this spectrum.<br />
<br />
Education:<br />
* We need to document existing openweb tools to make it easier for knowledgable and motivated individuals to use openweb tools more often. e.g. open source HTML presentation frameworks out there:<br />
** [http://shwr.me/ Shower Presentation Engine]<br />
*** Used by [[Tantek Çelik]] (e.g.[http://tantek.com/presentations/2014/05/indieweb/]), [[Jeff Jaffe]](e.g.[https://www.w3.org/2014/Talks/AC-meeting-Jeff/reportcard])<br />
** [http://lab.hakim.se/reveal-js Reveal.js]<br />
** [http://www.w3.org/Talks/Tools/Slidy2/ Slidy]<br />
** ...<br />
<br />
Workshop communication:<br />
* We should request that W3C workshop participants use openweb platform tools<br />
* HTML-based presentations, posted on the web at a permalink, with varying emphasis per the spectrum:<br />
** MUST: Technical contributors advocating specific technical advancements to the platform must use HTML and other openweb platform technologies.<br />
** SHOULD: Contributors who consider themselves technical should try using HTML for their presentations, and at least report back what difficulties they experience.<br />
** ENCOURAGED: All other workshop participants should be encouraged to learn HTML, and attempt creating HTML content, or saving their non-open-web presentations in HTML form.<br />
* Blog posts criticising of workshop structure/defaults:<br />
** http://infrequently.org/2013/06/that-old-skool-smell/<br />
** http://infrequently.org/2013/06/that-old-skool-smell-part-2/<br />
<br />
Tool Requests:<br />
* We should document where openweb tools fall down, where they are difficult etc. as compared to non-open-web technologies/formats, and what we need from openweb tools. E.g.<br />
* Web-based graphical user interface to create and edit presentations and slides<br />
** Even just simple styled text<br />
** Maybe with one image embedded on a slide<br />
<br />
=== Open AB ===<br />
The AB is working on (as is evident by this wiki page) doing more and more of its work in the open.<br />
<br />
Currently Open AB work is occurring in two places:<br />
* http://www.w3.org/wiki/AB (all projects on this wiki page)<br />
** see "Suggestions" section below to contribute<br />
* https://twitter.com/w3cab<br />
<br />
=== Remote Participation ===<br />
The AB is looking at issues related to remote participation in W3C meetings.<br />
* See [[Remote participation]]<br />
<br />
=== Headlights ===<br />
* See: [[Headlights2014]]<br />
<br />
=== Trademark License ===<br />
{{main|AB/trademark-license}}<br />
<br />
The AB has created a Trademark License task force (Tantek Çelik and Michael Champion) to build broad consensus on a combination trademark / license policy to potentially permit more permissive copyright licenses on W3C drafts and specifications.<br />
<br />
== Related Projects ==<br />
Not official AB projects per say, but projects that various AB members are participating in that may have W3C-wide scope.<br />
* [[Webizen]]<br />
<br />
== Twitter Account ==<br />
The Advisory Board has a Twitter account: [https://twitter.com/w3cab @W3CAB]<br />
<br />
Nearly the entire AB has access and can post anything regarding AB-related matters. The methodology is to empower individual responsibility and trust by default, especially in such a small group. This method has worked well with the [[CSSWG]] (any CSSWG member may "have the keys" to [https://twitter.com/csswg @CSSWG]) and it's been hugely successful in engaging the broader developer community. <br />
<br />
If you are a [http://www.w3.org/2002/ab/ member of the AB], contact [[User:Tantekelik|Tantek Çelik]] on a secure communications channel and he'll gladly share access to @W3CAB.<br />
<br />
* 2013-09-18 access broadly shared with AB members in person W3C AB meeting at MIT.<br />
* 2013-06-04 @W3CAB Twitter created.<br />
<br />
== Suggestions ==<br />
Suggestions for the AB.<br />
<br />
=== Minor Process Tweaks ===<br />
The Process document hasn't really been maintained in many years. There's talk of overhauling the Process, but meanwhile, how about making some simple changes that address particularly frustrating points in the Process?<br />
<br />
* Allowing REC to refer to CR (treating PR as a transitional phase, like LC). [[User:Fantasai|fantasai]] 04:52, 7 June 2013 (UTC)<br />
** Agreed. I'll see what I can do to help this along. - [[User:Tantekelik|Tantek Çelik]] 14:30, 8 July 2013 (UTC)<br />
** Inter-W3C-spec normative referencing policy is apparently not an explicit part of the Process Document. See [http://www.w3.org/community/w3process/track/issues/33 CG W3Process issue 33] for more info/updates on this. - [[User:Tantekelik|Tantek Çelik]] 14:54, 8 July 2013 (UTC)<br />
* Creating a "Proposed Edited Candidate Recommendation" stage (or pick a better name) to allow CRs to be updated without going back to Working Draft. This would be identical to LC--just a renaming of an existing process--so qualifies as a Dead Simple Change. [[User:Fantasai|fantasai]] 04:52, 7 June 2013 (UTC)<br />
** What about simply combining LC and CR, and allowing a document in that phase to be updated and stay at that phase? - [[User:Tantekelik|Tantek Çelik]] 14:30, 8 July 2013 (UTC)<br />
<br />
=== Making sure the ABs get members opinion ===<br />
* AB are elected by W3C members and need to make sure that they are collecting their ideas, suggestion... That wiki is great, the recent minutes members-only minutes issued by Coralie were great, but regular open debriefing communication to members/interested parties is key. It could be interesting to have an every-6-months call scheduled in advance to 'meet the AB'. This would be the opportunity to ask direct question to the AB, based on a collaborative agenda.<br />
Virginie Galindo (gemalto AC rep)<br />
<nowiki>~~~~</nowiki><br />
<br />
=== Add Your Suggestion Here ... ===<br />
* ...<br />
and sign it with <nowiki>~~~~</nowiki> (four tildas)<br />
<br />
== Meetings ==<br />
Upcoming meetings:<br />
* [[AB/2014-03-SF|2014-03-04..05 San Francisco]]<br />
* [[AB/2014-06-MA|2014-06-11..12 Cambridge, MA]] (after Cambridge, MA AC Meeting)<br />
<br />
Taxi sharing for meetings is organized on the wiki: [[MeetingTaxis]]<br />
<br />
== Background ==<br />
Background about this page.<br />
<br />
I ([[User:Tantekelik|Tantek Çelik]]) ran for the AB on a [http://tantek.com/2013/128/b1/reforming-w3c-advisory-board platform of greater openness] in how we do things. As part of that, feel free to add your suggestions for improving the AB and W3C Process as a whole here and I'll see what I can about them. I'm going to encourage other AB members to similarly consider using input from the wiki as another source. Thanks, - [[User:Tantekelik|Tantek Çelik]] 04:44, 7 June 2013 (UTC)<br />
<br />
== Resources ==<br />
* [https://www.w3.org/2012/03/cepc.html Code of Ethics and Professional Conduct]<br />
<br />
== See Also ==<br />
* [http://www.w3.org/2002/ab/ Official W3C Advisory Board home page]<br />
* [https://twitter.com/w3cab W3C Advisory Board Twitter]</div>Ddavishttps://www.w3.org/wiki/index.php?title=AB&diff=73703AB2014-06-10T20:22:38Z<p>Ddavis: /* Dogfooding at W3C */ Added link to Slidy</p>
<hr />
<div><div style="float:right;padding:0 0 1em 1em">[[File:W3C_AB.jpg|400px]]</div><br />
The <dfn>'''[http://www.w3.org/2002/ab/ W3C Advisory Board]'''</dfn> (AB) provides ongoing guidance to the W3C Team on issues of strategy, management, legal matters, process, and conflict resolution.<br />
<div style="float:right;clear:right">__TOC__</div><br />
== Projects ==<br />
=== W3C Process ===<br />
W3C [[process]] improvements are discussed in the community group:<br />
* http://www.w3.org/community/w3process/<br />
<br />
See [[process]] for more details.<br />
<br />
=== W3C Chairs Training ===<br />
The Advisory Board has established Chair Training as a priority for 2014. At TPAC2013, Chairs had a breakfast meeting and expressed what additional information and skills they required to improve their effectiveness. The W3C Team developed a list of areas which have now evolved into a quarterly Chair Training program.<br />
* 1. [http://www.w3.org/2014/01/23-chairing-minutes.html W3C, Process, and the W3C Team, Philippe Le Hegaret, 23 January 2014]<br />
** [http://lists.w3.org/Archives/Public/www-archive/2014Apr/0026.html Anchor sections] by Art Barstow<br />
* 2. [http://www.w3.org/2014/04/24-chairing-minutes Tools], Ralph Swick, 24 April 2014.<br />
* 3. The Human Dimension, Charles McCathie Nevile, 17 June 2014.<br />
* 4. Focus and Productivity, Arnaud Le Hors, October.<br />
<br />
=== Use of GitHub at W3C ===<br />
* See <span id="Use_of_Github_at_W3C">[[GitHub]]</span>.<br />
<br />
=== Cultural conventions for attribution ===<br />
The new [[HTMLWG]] charter allows for working group members to contribute HTML5 Extension specifications using CC-by, and then places attribution requirements on any derivative works.<br />
<br />
These attribution requirements are a good start for growing cultural conventions for attribution both inside W3C, and beyond W3C, towards a goal of making attribution founded in cultural norms rather than legal (copyright) requirements, potentially allowing for use of CC0 for contributions to W3C in the future.<br />
<br />
=== Dogfooding at W3C ===<br />
Many (most?) presentations at W3C workshops (e.g. the [http://indiewebcamp.com/2013/osfw3c Workshop on Social Standards: The Future of Business]) used non-open-web technologies/formats.<br />
<br />
A challenge was made to the participants to use HTML for their presentations proposing additions/technologies for the web platform[http://tantek.com/2013/219/t7/new-rule-learn-html-before-innovate-osfw3c][http://tantek.com/2013/219/t11/osfw3c-w3c-teach-html-slides-instead-powerpoint-pdf] (and criticism for using non-open-web technologies to do so [http://tantek.com/2013/219/t5/publishing-web-docs-specs-pdf-wrong-osfw3c][http://tantek.com/2013/219/t10/not-know-html-publish-know-not-innovate-osfw3c])<br />
<br />
The broader challenge is to use openweb technologies in our day to day interactions at and with W3C, with such use-cases as:<br />
* Presentations (slide formats / online slides)<br />
* Remote collaboration (e.g. use of WebRTC / webcasting instead of phones)<br />
<br />
There is a spectrum of W3C members that can be more/less expected to adopt and use open web technologies:<br />
# Highly technical contributors who are actively designing and specifying advancement of the web platform<br />
# Semi-technical contributors who have some understanding (can write HTML), but have challenges<br />
# General contributors who are discussing customer needs, use-cases<br />
We should be dogfooding and improving tools from top to bottom in this spectrum.<br />
<br />
Education:<br />
* We need to document existing openweb tools to make it easier for knowledgable and motivated individuals to use openweb tools more often. e.g. open source HTML presentation frameworks out there:<br />
** [http://shwr.me/ Shower Presentation Engine]<br />
*** Used by [[Tantek Çelik]] (e.g.[http://tantek.com/presentations/2014/05/indieweb/]), [[Jeff Jaffe]](e.g.[https://www.w3.org/2014/Talks/AC-meeting-Jeff/reportcard])<br />
** [http://lab.hakim.se/reveal-js Reveal.js]<br />
** [www.w3.org/Talks/Tools/Slidy2/ Slidy]<br />
** ...<br />
<br />
Workshop communication:<br />
* We should request that W3C workshop participants use openweb platform tools<br />
* HTML-based presentations, posted on the web at a permalink, with varying emphasis per the spectrum:<br />
** MUST: Technical contributors advocating specific technical advancements to the platform must use HTML and other openweb platform technologies.<br />
** SHOULD: Contributors who consider themselves technical should try using HTML for their presentations, and at least report back what difficulties they experience.<br />
** ENCOURAGED: All other workshop participants should be encouraged to learn HTML, and attempt creating HTML content, or saving their non-open-web presentations in HTML form.<br />
* Blog posts criticising of workshop structure/defaults:<br />
** http://infrequently.org/2013/06/that-old-skool-smell/<br />
** http://infrequently.org/2013/06/that-old-skool-smell-part-2/<br />
<br />
Tool Requests:<br />
* We should document where openweb tools fall down, where they are difficult etc. as compared to non-open-web technologies/formats, and what we need from openweb tools. E.g.<br />
* Web-based graphical user interface to create and edit presentations and slides<br />
** Even just simple styled text<br />
** Maybe with one image embedded on a slide<br />
<br />
=== Open AB ===<br />
The AB is working on (as is evident by this wiki page) doing more and more of its work in the open.<br />
<br />
Currently Open AB work is occurring in two places:<br />
* http://www.w3.org/wiki/AB (all projects on this wiki page)<br />
** see "Suggestions" section below to contribute<br />
* https://twitter.com/w3cab<br />
<br />
=== Remote Participation ===<br />
The AB is looking at issues related to remote participation in W3C meetings.<br />
* See [[Remote participation]]<br />
<br />
=== Headlights ===<br />
* See: [[Headlights2014]]<br />
<br />
=== Trademark License ===<br />
{{main|AB/trademark-license}}<br />
<br />
The AB has created a Trademark License task force (Tantek Çelik and Michael Champion) to build broad consensus on a combination trademark / license policy to potentially permit more permissive copyright licenses on W3C drafts and specifications.<br />
<br />
== Related Projects ==<br />
Not official AB projects per say, but projects that various AB members are participating in that may have W3C-wide scope.<br />
* [[Webizen]]<br />
<br />
== Twitter Account ==<br />
The Advisory Board has a Twitter account: [https://twitter.com/w3cab @W3CAB]<br />
<br />
Nearly the entire AB has access and can post anything regarding AB-related matters. The methodology is to empower individual responsibility and trust by default, especially in such a small group. This method has worked well with the [[CSSWG]] (any CSSWG member may "have the keys" to [https://twitter.com/csswg @CSSWG]) and it's been hugely successful in engaging the broader developer community. <br />
<br />
If you are a [http://www.w3.org/2002/ab/ member of the AB], contact [[User:Tantekelik|Tantek Çelik]] on a secure communications channel and he'll gladly share access to @W3CAB.<br />
<br />
* 2013-09-18 access broadly shared with AB members in person W3C AB meeting at MIT.<br />
* 2013-06-04 @W3CAB Twitter created.<br />
<br />
== Suggestions ==<br />
Suggestions for the AB.<br />
<br />
=== Minor Process Tweaks ===<br />
The Process document hasn't really been maintained in many years. There's talk of overhauling the Process, but meanwhile, how about making some simple changes that address particularly frustrating points in the Process?<br />
<br />
* Allowing REC to refer to CR (treating PR as a transitional phase, like LC). [[User:Fantasai|fantasai]] 04:52, 7 June 2013 (UTC)<br />
** Agreed. I'll see what I can do to help this along. - [[User:Tantekelik|Tantek Çelik]] 14:30, 8 July 2013 (UTC)<br />
** Inter-W3C-spec normative referencing policy is apparently not an explicit part of the Process Document. See [http://www.w3.org/community/w3process/track/issues/33 CG W3Process issue 33] for more info/updates on this. - [[User:Tantekelik|Tantek Çelik]] 14:54, 8 July 2013 (UTC)<br />
* Creating a "Proposed Edited Candidate Recommendation" stage (or pick a better name) to allow CRs to be updated without going back to Working Draft. This would be identical to LC--just a renaming of an existing process--so qualifies as a Dead Simple Change. [[User:Fantasai|fantasai]] 04:52, 7 June 2013 (UTC)<br />
** What about simply combining LC and CR, and allowing a document in that phase to be updated and stay at that phase? - [[User:Tantekelik|Tantek Çelik]] 14:30, 8 July 2013 (UTC)<br />
<br />
=== Making sure the ABs get members opinion ===<br />
* AB are elected by W3C members and need to make sure that they are collecting their ideas, suggestion... That wiki is great, the recent minutes members-only minutes issued by Coralie were great, but regular open debriefing communication to members/interested parties is key. It could be interesting to have an every-6-months call scheduled in advance to 'meet the AB'. This would be the opportunity to ask direct question to the AB, based on a collaborative agenda.<br />
Virginie Galindo (gemalto AC rep)<br />
<nowiki>~~~~</nowiki><br />
<br />
=== Add Your Suggestion Here ... ===<br />
* ...<br />
and sign it with <nowiki>~~~~</nowiki> (four tildas)<br />
<br />
== Meetings ==<br />
Upcoming meetings:<br />
* [[AB/2014-03-SF|2014-03-04..05 San Francisco]]<br />
* [[AB/2014-06-MA|2014-06-11..12 Cambridge, MA]] (after Cambridge, MA AC Meeting)<br />
<br />
Taxi sharing for meetings is organized on the wiki: [[MeetingTaxis]]<br />
<br />
== Background ==<br />
Background about this page.<br />
<br />
I ([[User:Tantekelik|Tantek Çelik]]) ran for the AB on a [http://tantek.com/2013/128/b1/reforming-w3c-advisory-board platform of greater openness] in how we do things. As part of that, feel free to add your suggestions for improving the AB and W3C Process as a whole here and I'll see what I can about them. I'm going to encourage other AB members to similarly consider using input from the wiki as another source. Thanks, - [[User:Tantekelik|Tantek Çelik]] 04:44, 7 June 2013 (UTC)<br />
<br />
== Resources ==<br />
* [https://www.w3.org/2012/03/cepc.html Code of Ethics and Professional Conduct]<br />
<br />
== See Also ==<br />
* [http://www.w3.org/2002/ab/ Official W3C Advisory Board home page]<br />
* [https://twitter.com/w3cab W3C Advisory Board Twitter]</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73701Webizen2014-06-10T13:42:41Z<p>Ddavis: /* Suggestions from AC meeting */</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Citizens<br />
* Citizen of the Web<br />
* Constituents<br />
* Constituent of the Web<br />
* Friend of the Consortium<br />
* W3bizen<br />
* W3Connector<br />
* Webizen<br />
<br />
=== Suggestions from [https://twitter.com/robinberjon/status/461062248623251456 this Twitter thread] ===<br />
* Agent<br />
* Collaborator<br />
* Community Member<br />
* Comrade<br />
* Contributor<br />
* Delegate<br />
* Friend of the Web (FoW)<br />
* Homo webus<br />
* Individual Member<br />
* Spider (building the Web)<br />
* w3c.node<br />
* W3mber<br />
* Webbee<br />
* Webdoer<br />
* Webelong<br />
* Webholder<br />
* Webien<br />
<br />
=== Suggestions from AC meeting ===<br />
* Friend of the W3C<br />
* Tim's Army<br />
* W3C Affiliated Professional<br />
* W3C Esteemed Buddy<br />
* W3c Esteemed International Respected Developer or Operator<br />
* W3C Individual Member Program (WIMP)<br />
* W3C Professional<br />
* Webbro<br />
* Webchamp<br />
* Webelo<br />
* Webzealot<br />
* Weeble<br />
* Zombie<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73700Webizen2014-06-10T13:41:26Z<p>Ddavis: /* Suggestions from AC meeting */ Added more suggestions from IRC chat</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Citizens<br />
* Citizen of the Web<br />
* Constituents<br />
* Constituent of the Web<br />
* Friend of the Consortium<br />
* W3bizen<br />
* W3Connector<br />
* Webizen<br />
<br />
=== Suggestions from [https://twitter.com/robinberjon/status/461062248623251456 this Twitter thread] ===<br />
* Agent<br />
* Collaborator<br />
* Community Member<br />
* Comrade<br />
* Contributor<br />
* Delegate<br />
* Friend of the Web (FoW)<br />
* Homo webus<br />
* Individual Member<br />
* Spider (building the Web)<br />
* w3c.node<br />
* W3mber<br />
* Webbee<br />
* Webdoer<br />
* Webelong<br />
* Webholder<br />
* Webien<br />
<br />
=== Suggestions from AC meeting ===<br />
* Friend of the W3C<br />
* W3C Affiliated Professional<br />
* W3C Esteemed Buddy<br />
* W3c Esteemed International Respected Developer or Operator<br />
* W3C Individual Member Program (WIMP)<br />
* W3C Professional<br />
* Webbro<br />
* Webchamp<br />
* Webelo<br />
* Webzealot<br />
* Weeble<br />
* Zombie<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73699Webizen2014-06-10T13:35:29Z<p>Ddavis: /* Suggestions from AC meeting */</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Citizens<br />
* Citizen of the Web<br />
* Constituents<br />
* Constituent of the Web<br />
* Friend of the Consortium<br />
* W3bizen<br />
* W3Connector<br />
* Webizen<br />
<br />
=== Suggestions from [https://twitter.com/robinberjon/status/461062248623251456 this Twitter thread] ===<br />
* Agent<br />
* Collaborator<br />
* Community Member<br />
* Comrade<br />
* Contributor<br />
* Delegate<br />
* Friend of the Web (FoW)<br />
* Homo webus<br />
* Individual Member<br />
* Spider (building the Web)<br />
* w3c.node<br />
* W3mber<br />
* Webbee<br />
* Webdoer<br />
* Webelong<br />
* Webholder<br />
* Webien<br />
<br />
=== Suggestions from AC meeting ===<br />
* Friend of the W3C<br />
* W3C Individual Member Program (WIMP)<br />
* W3C Professional<br />
* Webbro<br />
* Webchamp<br />
* Webelo<br />
* Webzealot<br />
* Weeble<br />
* Zombie<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73698Webizen2014-06-10T13:33:52Z<p>Ddavis: /* Suggestions from AC meeting */</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Citizens<br />
* Citizen of the Web<br />
* Constituents<br />
* Constituent of the Web<br />
* Friend of the Consortium<br />
* W3bizen<br />
* W3Connector<br />
* Webizen<br />
<br />
=== Suggestions from [https://twitter.com/robinberjon/status/461062248623251456 this Twitter thread] ===<br />
* Agent<br />
* Collaborator<br />
* Community Member<br />
* Comrade<br />
* Contributor<br />
* Delegate<br />
* Friend of the Web (FoW)<br />
* Homo webus<br />
* Individual Member<br />
* Spider (building the Web)<br />
* w3c.node<br />
* W3mber<br />
* Webbee<br />
* Webdoer<br />
* Webelong<br />
* Webholder<br />
* Webien<br />
<br />
=== Suggestions from AC meeting ===<br />
* Friend of the W3C<br />
* W3C Individual Member Program (WIMP)<br />
* Webbro<br />
* Webchamp<br />
* Webelo<br />
* Webzealot<br />
* Weeble<br />
* Zombie<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73697Webizen2014-06-10T13:29:37Z<p>Ddavis: /* Suggestions from AC meeting */</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Citizens<br />
* Citizen of the Web<br />
* Constituents<br />
* Constituent of the Web<br />
* Friend of the Consortium<br />
* W3bizen<br />
* W3Connector<br />
* Webizen<br />
<br />
=== Suggestions from [https://twitter.com/robinberjon/status/461062248623251456 this Twitter thread] ===<br />
* Agent<br />
* Collaborator<br />
* Community Member<br />
* Comrade<br />
* Contributor<br />
* Delegate<br />
* Friend of the Web (FoW)<br />
* Homo webus<br />
* Individual Member<br />
* Spider (building the Web)<br />
* w3c.node<br />
* W3mber<br />
* Webbee<br />
* Webdoer<br />
* Webelong<br />
* Webholder<br />
* Webien<br />
<br />
=== Suggestions from AC meeting ===<br />
* Friend of the W3C<br />
* Webbro<br />
* Webchamp<br />
* Webelo<br />
* Webzealot<br />
* Weeble<br />
* Zombie<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73696Webizen2014-06-10T13:27:33Z<p>Ddavis: /* Name */ Changed to alphabetic order</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Citizens<br />
* Citizen of the Web<br />
* Constituents<br />
* Constituent of the Web<br />
* Friend of the Consortium<br />
* W3bizen<br />
* W3Connector<br />
* Webizen<br />
<br />
=== Suggestions from [https://twitter.com/robinberjon/status/461062248623251456 this Twitter thread] ===<br />
* Agent<br />
* Collaborator<br />
* Community Member<br />
* Comrade<br />
* Contributor<br />
* Delegate<br />
* Friend of the Web (FoW)<br />
* Homo webus<br />
* Individual Member<br />
* Spider (building the Web)<br />
* w3c.node<br />
* W3mber<br />
* Webbee<br />
* Webdoer<br />
* Webelong<br />
* Webholder<br />
* Webien<br />
<br />
=== Suggestions from AC meeting ===<br />
* Webbro<br />
* Webchamp<br />
* Webelo<br />
* Webzealot<br />
* Weeble<br />
* Zombie<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73695Webizen2014-06-10T13:26:54Z<p>Ddavis: /* Suggestions from AC meeting */ Changed list to alphabetical order</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Webizen<br />
* W3bizen<br />
* W3Connector<br />
* Constituents<br />
* Constituent of the Web<br />
* Citizens<br />
* Citizen of the Web<br />
* Friend of the Consortium<br />
<br />
=== Suggestions from [https://twitter.com/robinberjon/status/461062248623251456 this Twitter thread] ===<br />
* Agent<br />
* Collaborator<br />
* Community Member<br />
* Comrade<br />
* Contributor<br />
* Delegate<br />
* Friend of the Web (FoW)<br />
* Homo webus<br />
* Individual Member<br />
* Spider (building the Web)<br />
* w3c.node<br />
* W3mber<br />
* Webbee<br />
* Webdoer<br />
* Webelong<br />
* Webholder<br />
* Webien<br />
<br />
=== Suggestions from AC meeting ===<br />
* Webbro<br />
* Webchamp<br />
* Webelo<br />
* Webzealot<br />
* Weeble<br />
* Zombie<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73694Webizen2014-06-10T13:26:07Z<p>Ddavis: /* Name */ Added suggestions from Twitter</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Webizen<br />
* W3bizen<br />
* W3Connector<br />
* Constituents<br />
* Constituent of the Web<br />
* Citizens<br />
* Citizen of the Web<br />
* Friend of the Consortium<br />
<br />
=== Suggestions from [https://twitter.com/robinberjon/status/461062248623251456 this Twitter thread] ===<br />
* Agent<br />
* Collaborator<br />
* Community Member<br />
* Comrade<br />
* Contributor<br />
* Delegate<br />
* Friend of the Web (FoW)<br />
* Homo webus<br />
* Individual Member<br />
* Spider (building the Web)<br />
* w3c.node<br />
* W3mber<br />
* Webbee<br />
* Webdoer<br />
* Webelong<br />
* Webholder<br />
* Webien<br />
<br />
=== Suggestions from AC meeting ===<br />
* Webzealot<br />
* Zombie<br />
* Weeble<br />
* Webbro<br />
* Webelo<br />
* Webchamp<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=Webizen&diff=73693Webizen2014-06-10T13:22:26Z<p>Ddavis: /* Name */ Added suggestions from AC meeting</p>
<hr />
<div>< [https://www.w3.org/wiki/Headlights2014 Headlights 2014]<br />
<br />
'''DRAFT''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''Help us!''' - '''DRAFT''' - '''DRAFT'''<br />
<br />
'''"Not just a Websumer, I'm a W3C Webizen!"'''<br />
<br />
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.)<br />
<br />
----<br />
<br />
To join, [mailto:public-webizen-request&#64;w3.org?subject=subscribe subscribe to public-webizen@w3.org], add your name to the [[#Participants]] list.<br />
<br />
'''Participation:'''<br />
* '''Open and public''': This task force is open to the public and will operate until June 2014. '''Come and build the Webizen program!''' <br />
* '''e-mail''': We welcome feedback on the public-webizen@w3.org mailing list [http://lists.w3.org/Archives/Public/public-webizen/ archive] and may even use your feedback in our work.<br />
* '''IRC''': There is an IRC channel you can join too: irc.w3.org, port 6665, channel #webizen ([http://irc.w3.org/?channels=webizen] Pre-filled Web interface to IRC]).<br />
* '''Twitter''': [https://twitter.com/W3C_Webizen W3C_Webizen]<br />
<br />
----<br />
<br />
__TOC__ <br />
<br />
== Background ==<br />
<br />
At TPAC 2013, in response to a [http://www.w3.org/2013/11/13-tpac-minutes.html question from the floor] (Look for “individual membership“), the W3C Director requested exploration of individual participation in W3C.<br />
<br />
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). <br />
<br />
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 [http://www.w3.org/2004/08/invexp.html 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.<br />
<br />
Another type of status is [http://www.w3.org/Consortium/sup 'W3C Supporters']. This provides no real benefits to the supporters, but allows them to charitably give donations to W3C.<br />
<br />
== Concept of the Webizen program ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Name ==<br />
<br />
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:<br />
<br />
* Webizen<br />
* W3bizen<br />
* W3Connector<br />
* Constituents<br />
* Constituent of the Web<br />
* Citizens<br />
* Citizen of the Web<br />
* Friend of the Consortium<br />
* [https://twitter.com/robinberjon/status/461062248623251456 Twitter thread]<br />
=== From AC meeting ===<br />
* Webzealot<br />
* Zombie<br />
* Weeble<br />
* Webbro<br />
* Webelo<br />
* Webchamp<br />
<br />
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.<br />
<br />
In finding a name, we must consider it may have a meaning and connotations in other languages/cultures.<br />
<br />
== Goals ==<br />
<br />
* Attract more stakeholders to the W3C community, including those who care greatly about the Web even if they may not be spec writers<br />
* Increase affiliation with W3C for this set of stakeholders<br />
* Get closer linkages between W3C spec writers, and the vast ecosystem that relies on W3C Recommendations<br />
* Increase general public review of web technology in general and W3C Reports<br />
* Provide a means for the general public to influence W3C agenda and priorities<br />
<br />
== Package of benefits ==<br />
<br />
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:<br />
<br />
* Webizen Electoral College<br />
** 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.<br />
* Invitation to teleconference organized once annually by the CEO for a discussion of W3C's activities and plans.<br />
* Webizen ID number. <br />
** 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.<br />
* Public profile on the W3C website.<br />
* A "flourish" next to where name appears in Community Group and Working Group list of participants. <br />
* Name listed on our Supporters page (with # years).<br />
* Annual Webizen T-shirt. (tentative design [https://i.imgur.com/Sdbz8HY.png example])<br />
** Participate in annual T-shirt design competition<br />
** 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.<br />
* Stickers, mug, other 'goodies'.<br />
* Discounts of W3C services of interest to individuals; such as W3C Validator Suite and certain conference fees.<br />
* 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.<br />
** -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."<br />
* 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)<br />
<br />
* [https://www.w3.org/wiki/images/c/c8/W3C_Member_Benefits.xlsx Table of Member benefits ]<br />
<br />
=== Intermediate or Longer-term benefits ===<br />
<br />
* 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.<br />
* Best practice discussions, webinars, luncheons<br />
* User conferences<br />
* Providing @w3.org email addresses as vanity addresses and emails for those that want them.<br />
** In that case, IDs should use handles / short names (nicks) instead of long ID numbers.<br />
<br />
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).<br />
<br />
== Participation Benefits and Non Benefits ==<br />
<br />
Two key Member benefits are not available to At Large Webizens: participation in Working Groups (WG) and the Advisory Committee (AC).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
The Webizen AC reps would also have write-access to the official W3C blog.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Webizen voting for the AC ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are several approaches to addressing this.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
'''Proposal #1'''<br />
<br />
#Any Webizen can run for an AC position<br />
#Every Webizen gets one vote<br />
#If there are n seats available, they go to the top n vote-getters.<br />
<br />
(In the view of this proposal writer, until n>9, we do not make the vote more complicated).<br />
<br />
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.<br />
<br />
'''Proposal #2'''<br />
# Any webizen can run for AC.<br />
# Any webizen votes for as many candidates as they want, ranking them in preference order.<br />
<br />
The winners are determined by "[http://en.wikipedia.org/wiki/Schulze_STV Schulze STV" voting].<br />
<br />
To count the votes we could use the [https://github.com/bradbeattie/python-vote-core/blob/master/pyvotecore/schulze_stv.py Open Source code available].<br />
<br />
We could also run the entire election through [https://modernballots.com/ the online implementation]. it takes minutes to set up.<br />
<br />
'''Schedule'''<br />
<br />
#Proposals for voting mechanisms are due by January 1, 2015<br />
#Webizens will select their preferred voting mechanisms for the first year by April 1, 2015<br />
#Nominations for 2016 are due on July 1, 2015.<br />
#Nominee statements are due on August 1, 2015.<br />
#Election period is September 1 - October 1, 2015.<br />
#Position is help for one year, from 1/1/16 until 1/1/17<br />
<br />
[1] http://www.w3.org/2005/10/Process-20051014/acreview.html#ACVotes<br />
[2] http://en.wikipedia.org/wiki/Single_transferable_vote<br />
[3] https://www.ieee.org/about/corporate/election/election_index.html<br />
<br />
== Drafting a Webizen network structure ==<br />
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.<br />
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.<br />
The local offices structure could be used later for a regional based organization and voting fragmenting reference.<br />
<br />
Question: What does it mean in practice for a Webizen to be associated with an Office?<br />
<br />
== Marketing and Communications ==<br />
<br />
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.<br />
<br />
A comm plan would be some percentage of the Webizen program income, e.g. 8%<br />
<br />
=== Webizen Messaging ===<br />
<br />
=== Community Development ===<br />
* Find 25 people who will be the initial Webizens and promote the launch through their channels<br />
* Early adopter benefits (for first 200 Webizens)<br />
** Discount? [not supported at [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12 meeting]]<br />
** Special early adopter T-shirt<br />
** Urge them to promote their participation<br />
* 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.<br />
** Jeff Jaffe: A very low number, but willing to defer if it helps attracts others<br />
** David Larlet: a very low number<br />
** Sébastien Desbenoit: 000000000000017<br />
** Ralph Swick: 27<br />
** Coralie Mercier: 000000000000042<br />
** Jean-Charles Verdié: 000000000000051<br />
** Karl Dubost: 000000000000069<br />
** Andrei Sambra: 000000000000007<br />
<br />
=== Visual identity ===<br />
* Overall program, the essence of being a webizen<br />
* Badges (for Webizens and Webizen representatives)<br />
* Badge usage policy (e.g., licenses, derivative works, etc.)<br />
<br />
=== Web site ===<br />
* Leverages visual identity<br />
* Content<br />
** What the program is about<br />
** List of benefits<br />
** How to become a Webizen<br />
** List of Webizens, highlighting representatives<br />
** How representatives are elected, and schedule for election<br />
** List of communications channels (e.g., for news and events)<br />
** FAQ (e.g., relation to Membership)<br />
<br />
Estimated cost with visual design: $15-$20K<br />
<br />
=== w3.org updates ===<br />
<br />
* W3C homepage<br />
* [http://www.w3.org/participate Participate page]<br />
* Add link to footer of new site<br />
* Add link to left column of home page in dev section<br />
* Add link from validator home page, unicorn home page<br />
<br />
=== W3C Notification ===<br />
* Home page news story announcing program<br />
* Initial blog post (Jeff?)<br />
* Announcement to Membership<br />
* W3C twitter, Facebook, LinkedIn channels<br />
** LinkedIn showcase page?<br />
* We do '''not''' anticipate a press release since we think social media channels will be more effective for this news<br />
<br />
=== Notification via partners ===<br />
<br />
* All initial Webizens<br />
* A List Apart<br />
* Web Directions<br />
* ParisWeb<br />
* Web Visions<br />
* Webby Awards<br />
* @timberners_lee, @webplatform, @w3cmemes, @slightlylate (Alex Russell, who asked about indiv. membership at TPAC 2013), @parisweb, @openwebgroup, @stshank, @whiteafrican, Lea Verou, Brian Kardell<br />
* W3C alums<br />
* W3C Members<br />
* Others?<br />
<br />
=== Concept & pitch ===<br />
<br />
Note: Start work on a manifesto (credo) before working on pitch; synergies might arise.<br />
<br />
Ideas of pitch:<br />
* "Take your place at the W3C table."<br />
* "Help ensure Web standards meet your needs."<br />
* "Not just a Websumer, I'm a Webizen."<br />
<br />
== Operational questions ==<br />
<br />
* 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.<br />
* International and global issues<br />
* Accessibility<br />
* Who on the team would actually do the necessary tasks<br />
<br />
Past discussion notes:<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014May/0058.html Notes from 2014-05-16 Webizen Operations Team-Discussion]<br />
* [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html Notes from 2014-03-19 W3C Systems team perspective for Webizen TF]<br />
<br />
=== Operations ===<br />
* Organise design competition for annual t-shirt.<br />
* Can it be managed by a third party (budget needs to take that into account)?<br />
<br />
=== Funds usage - internal to W3C ===<br />
<br />
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.<br />
<br />
== ISSUES: June discussion at the W3C Advisory Committee Meeting ==<br />
<br />
Announced at the [http://www.w3.org/2014/05/05-webizen-minutes.html#item07 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''':<br />
# should we have a webizen program?<br />
# what should we name it?<br />
# collection of benefits, right sets, what to add or substract?<br />
# is it acceptable for webizens to select representatives that participate in certain AC activities?<br />
# should voting mechanism be decided by the Webizens?<br />
<br />
'''If you want to raise additional issues and will not attend this meeting, please send your issue to the <code>[http://lists.w3.org/Archives/Public/public-webizen/ public-webizen@w3.org]</code> mail list before June 8.'''<br />
<br />
== FAQ ==<br />
=== How do I participate in a working group ===<br />
Q: As a Webizen, how do I participate in a W3C Working Group?<br />
<br />
A1: If you are an employee of a member company, ask your AC representative to add you to the working group.<br />
<br />
A2: If you are an individual not employed by a member company:<br />
<br />
Most working groups work publicly with a public mailing list that anybody can join.<br />
<br />
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.<br />
<br />
In particular, take the following steps:<br />
# Join the IRC channel and public mailing list of the working group (WG)<br />
# Participate in good faith in IRC and the mailing list, and help out e.g. by:<br />
#* documenting specific real world use-cases they think the WG should solve<br />
#* pointing out errors/issues/improvements in specs<br />
#* contributing test cases for WG technologies<br />
#* provide helpful answers and responses to various questions raised<br />
<br />
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.<br />
<br />
== Administrative section ==<br />
<br />
Task Force led by: Jeff Jaffe <jeff@w3.org><br />
<br />
=== Participants ===<br />
* Jeff Jaffe<br />
* Coralie Mercier<br />
* Veronica Thom<br />
* Alexandre Bertails<br />
* Amy van der Hiel<br />
* Ann Bassetti<br />
* Andrei Sambra<br />
* chaals<br />
* JC Verdie<br />
* Robin Berjon<br />
* Virginie Galindo<br />
* Sébastien Desbenoit<br />
* Mark Sadecki<br />
<br />
=== Schedule ===<br />
<br />
* October 2013 - January 2014: Proposals from W3C Members and Staff added to this page<br />
* Jan 2014: W3C management prioritization of headlights ideas<br />
* Feb 2014: Announcement of topics selected for further development and start of task forces<br />
* 7 March: People are encouraged to join the task forces by this date.<br />
* 10 March - June: Task forces develop ideas<br />
* 8-10 June 2014: AC meeting discussion<br />
* June-July 2014: Further development<br />
* July 2014: W3M evaluation of proposals and assignment of resources<br />
<br />
=== Meeting records and actions===<br />
<br />
* [https://www.w3.org/2014/06/02-webizen-minutes.html 2014-06-02]<br />
<br />
* [http://www.w3.org/2014/05/12-webizen-minutes.html 2014-05-12]<br />
[no actions, edits welcome in existing sections of the wiki]<br />
<br />
* [http://www.w3.org/2014/05/05-webizen-minutes.html 2014-05-05]<br />
** [done] Coralie to work with Sébastien on commenting in wiki on "zen" connotation in "Name" section of the wiki<br />
** [done] Ann to update the "Name" section in the wiki, to add a note on "sparkle"<br />
** (Jeff?) We should let the constituents of the Web decide, rather than imposing a voting mechanism.<br />
<br />
* [http://www.w3.org/2014/04/10-webizen-minutes.html 2014-04-10]<br />
** [done] koalie to align pitch phrases with goals as stated in section created today<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0039.html done]] koalie to get W3C Offices to identify likely candidates and seek their reaction<br />
** (Carried from past meeting) Veronica to update wiki (discounts proposal)<br />
<br />
* [http://www.w3.org/2014/03/27-webizen-minutes.html 2014-03-27] 11:00 am (ET)<br />
** [done] Jeff to elaborate on how elections should be done (college)<br />
** [done] Veronica to socialise her proposal further and update wiki (discounts)<br />
<br />
* [http://www.w3.org/2014/03/20-webizen-minutes.html 2014-03-20]<br />
** [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)<br />
** [done] Jeff to write a proposal to write up what an electoral college would look like. <br />
** [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.<br />
<br />
* [http://www.w3.org/2014/03/10-webizen-minutes.html 2014-03-10]<br />
** [[http://lists.w3.org/Archives/Public/public-webizen/2014May/0021.html done]] Coralie to come up with comm plan for low-key start of webizen program.<br />
** [done] Coralie to create a wiki.<br />
** [done] Coralie to nudge Ted about systeam aspects of Webizen. ([https://www.w3.org/2014/03/18-webizen-minutes.html Minutes], [http://lists.w3.org/Archives/Public/public-webizen/2014Mar/0006.html key points])<br />
** [done] Veronica to draft a proposal of what kind of discounts a Webizen program would confer.</div>Ddavishttps://www.w3.org/wiki/index.php?title=AdvisoryCommittee/AC2014&diff=73691AdvisoryCommittee/AC20142014-06-10T13:08:45Z<p>Ddavis: Fixed heading for Tools</p>
<hr />
<div>People attending [https://www.w3.org/Member/Meeting/2014ac/June/ AC 2014] are invited to note topics for discussion at the AC meeting. In particular, we welcome seed topics for the unconference breakout sessions on 10 June; see the [https://www.w3.org/Member/Meeting/2014ac/June/ agenda] for more information.<br />
<br />
== Suggested unconferenced sessions ==<br />
<br />
<br />
<br />
=== Security landscape in W3C and what's coming next === <br />
<ul class="show_items"><br />
* session proposer Viginie Galindo (gemalto)<br />
* W3C Web Security IG has been collected some secuirty needs from different sources (workshops, members, other organizations) and would like to trigger members vision on priority to allocate on those features<br />
* presentation and open discussion<br />
* get a priority from members to address the security features, get volunteers to execute the plan<br />
* wendy from W3C, (please add you name if you wanna speak)<br />
</ul><br />
<br />
=== Review of Proposed Changes to Technical Reports Process (Room 4-153)=== <br />
<ul class="show_items"><br />
* Session proposer: David Singer<br />
* Likely Chairs (not yet confirmed): Charles, SteveZ, Jeff<br />
* Purpose: Walk through all the changes of the [http://www.w3.org/2014/05/Process-20140506/ Proposed New Process]<br />
* Potential topics:<br />
** What are the key differences from the [http://www.w3.org/2005/10/Process-20051014/tr.html#Reports 2005 Technical Reports Process]; where is the ''problem statement'' and ''key use cases'' this proposal addresses; what are the motivations for the changes?<br />
** How does the proposal affect various constituencies?<br />
*** Chairs<br />
*** Editors<br />
*** WG members<br />
*** Other members of the consortium<br />
*** The public at large (e.g. ‘public review steps’)<br />
*** IPR review and policy<br />
** Are the various constituencies empowered or disadvantaged by this process? What unintended consequences might there be for each of these communities?<br />
** Does changing LCWD from being an explicit part of the workflow to being implicit really result in less work?<br />
** Rather than eliminating an explicit review step, why can't the same results be achieved by providing more education, best practices, guidelines and such? <br />
** Which WG is going to be the `guinea pig(s)?<br />
** What is the plan to get wide review of the proposed process by other SSOs that use W3C standards?<br />
</ul><br />
<br />
SeeAlso:<br />
<br />
* [https://lists.w3.org/Archives/Member/w3c-ac-forum/2014AprJun/0152.html ''Please extend the Call for Review: Proposed World Wide Web Consortium Process Document'' thread on w3c-ac-forum list]<br />
=== W3C tools===<br />
<ul class="show_items"><br />
* Proposed by Jeff Jaffe<br />
* Led by Ted Guild<br />
* How should infrastructure for W3C groups evolve<br />
* Discussion<br />
* What do we need for groups? Relation to tool ecosystem?<br />
</ul><br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top.</div>Ddavishttps://www.w3.org/wiki/index.php?title=TPAC/2013/SiteRedesign&diff=70521TPAC/2013/SiteRedesign2013-11-13T09:52:36Z<p>Ddavis: Added "notes and todos"</p>
<hr />
<div>* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on wireframes for part of the site redesign, and to discuss other parts of the project.<br />
* Minutes: http://www.w3.org/2013/11/13-site-design-minutes.html<br />
<br />
== Notes & Todos ==<br />
<br />
* Add a point of contact to the industry landing pages<br />
* Look into the grouping of specs, maybe using tags, for example for Internationalization<br />
* A tool for distributed editing of metadata (of TRs)</div>Ddavishttps://www.w3.org/wiki/index.php?title=TPAC/2013/SiteRedesign&diff=70515TPAC/2013/SiteRedesign2013-11-13T09:48:37Z<p>Ddavis: Added minutes</p>
<hr />
<div>* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on wireframes for part of the site redesign, and to discuss other parts of the project.<br />
* Minutes: http://www.w3.org/2013/11/13-site-design-minutes.html</div>Ddavishttps://www.w3.org/wiki/index.php?title=TPAC/2013/SessionIdeas&diff=70360TPAC/2013/SessionIdeas2013-11-13T01:41:27Z<p>Ddavis: /* Second Screen for the Web */</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2013]] session ideas in advance of the meeting. <br />
<br />
See the [http://www.w3.org/wiki/TPAC2013/FAQ TPAC 2013 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top. See [[#Site Redesign|site redesign below]] as a template for new entries.<br />
<br />
== Suggestions for Tuesday Morning AC Meeting ==<br />
<br />
The Tuesday morning of the AC Meeting is optional. It is intended for informal discussion among Chairs, AC, TAG, AB, Offices, and Team.<br />
<br />
=== [Breakout session] How to Effectively "listen" to activity ===<br />
<br />
* Proposed by: Al Villarica (Smart Communications) & Alan Bird (W3C and Smart's MRM)<br />
* Summary: W3C has a lot of different activities going on at any given point in time. For a member with a smaller amount of resource it's a challenge to find out what's going on that isn't on our current "radar". We're assuming that members that have been with W3C for a longer period of time may have some "best practices" they could share to help newer, smaller members. <br />
* Type: Discussion<br />
* Goals: Open discussion to provide members with ideas they can implement to gain more value from their W3C Membership by being aware of areas that might be in their organizations longer term objectives. <br />
* Interested: Rebecca Hauck, Masataka Yakura<br />
<br />
=== [Breakout session] New W3C Services ===<br />
* Proposed by: Marie-Claire Forgue and Bernard Gidon<br />
* Summary: W3C is introducing new services ([http://www.w3devcampus.com/courses/ training] and [https://validator-suite.w3.org/ validator suite])<br />
* Type: Presentation and discussion<br />
* Goals: The "new services team" would like to provide an update on these existing services. We will be happy to answer your questions and also introcuce the related W3C Members benefits. We are also interested in finding new ways to promote these new services through the members' networks of developers and customers.<br />
* Interested: AlanB, JérômeC<br />
<br />
=== Notes from the Team ===<br />
<br />
* Introduction to W3C's IPR Policies<br />
* New W3C Services activity<br />
<br />
=== Notes from the Program committee ===<br />
<br />
* EME<br />
* Schema.org<br />
* Boundaries of W3C work in technology/policy areas<br />
* Improving remote participation in W3C meetings<br />
* Focus AC agenda on TPWG progress; use breakout for broader discussion of Web privacy.<br />
<br />
=== Notes on breakout rooms ===<br />
<br />
* We will seek three breakout rooms + the main room.<br />
* However groups will be meeting in many of the available rooms.<br />
* Therefore, if we can't arrange for 3 distinct rooms, we'll grab corners of the main room.<br />
<br />
== Suggestions for Wednesday Breakouts ==<br />
<br />
Note: For 2013 we invite the Advisory Committee to use the Wednesday breakouts for AC-type topics as well.<br />
<br />
We encourage attendees to start brainstorming [[TPAC2013]] session ideas in advance of the meeting. <br />
<br />
See the [http://www.w3.org/wiki/TPAC2013/FAQ TPAC 2013 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top. See [[#Site Redesign|site redesign below]] as a template for new entries.<br />
<br />
== Suggestions for Tuesday Morning AC Meeting ==<br />
<br />
The Tuesday morning of the AC Meeting is optional. It is intended for informal discussion among Chairs, AC, TAG, AB, Offices, and Team.<br />
<br />
=== [Breakout session] How to Effectively "listen" to activity ===<br />
<br />
* Proposed by: Al Villarica (Smart Communications) & Alan Bird (W3C and Smart's MRM)<br />
* Summary: W3C has a lot of different activities going on at any given point in time. For a member with a smaller amount of resource it's a challenge to find out what's going on that isn't on our current "radar". We're assuming that members that have been with W3C for a longer period of time may have some "best practices" they could share to help newer, smaller members. <br />
* Type: Discussion<br />
* Goals: Open discussion to provide members with ideas they can implement to gain more value from their W3C Membership by being aware of areas that might be in their organizations longer term objectives. <br />
* Interested: Rebecca Hauck, Masataka Yakura<br />
<br />
=== [Breakout session] New W3C Services ===<br />
* Proposed by: Marie-Claire Forgue and Bernard Gidon<br />
* Summary: W3C is introducing new services ([http://www.w3devcampus.com/courses/ training] and [https://validator-suite.w3.org/ validator suite])<br />
* Type: Presentation and discussion<br />
* Goals: The "new services team" would like to provide an update on these existing services. We will be happy to answer your questions and also introcuce the related W3C Members benefits. We are also interested in finding new ways to promote these new services through the members' networks of developers and customers.<br />
* Interested: AlanB, JérômeC<br />
<br />
=== Notes from the Team ===<br />
<br />
* Introduction to W3C's IPR Policies<br />
* New W3C Services activity<br />
<br />
=== Notes from the Program committee ===<br />
<br />
* EME<br />
* Schema.org<br />
* Boundaries of W3C work in technology/policy areas<br />
* Improving remote participation in W3C meetings<br />
* Focus AC agenda on TPWG progress; use breakout for broader discussion of Web privacy.<br />
<br />
=== Notes on breakout rooms ===<br />
<br />
* We will seek three breakout rooms + the main room.<br />
* However groups will be meeting in many of the available rooms.<br />
* Therefore, if we can't arrange for 3 distinct rooms, we'll grab corners of the main room.<br />
<br />
== Suggestions for Wednesday Breakouts ==<br />
<br />
Note: For 2013 we invite the Advisory Committee to use the Wednesday breakouts for AC-type topics as well.<br />
<br />
=== Ruby ===<br />
<br />
* Proposed by: Robin Berjon<br />
* Summary: Discuss the work on ruby going on in both CSS and HTML<br />
* Session: Get up to speed on where we are and figure out where to go next.<br />
* Goal: improve the state of ruby on the Web<br />
* Interested: <br />
<br />
<br />
=== Web Payments ===<br />
<br />
* Proposed by: Manu Sporny<br />
* Summary: Discuss the role of W3C in the creation of a set of value-exchange (payment / crowdfunding / P2P finance) standards for the Web, consider PaySwarm, Bitcoin, Ripple and other emerging technologies.<br />
* Session: Short 15 minute intro on the topic followed by open discussion<br />
* Link to Session Page: http://www.w3.org/wiki/TPAC2013/session-web-payments<br />
* Goals<br />
** See if a Web Payments Workshop or Working Group is needed<br />
** Educate and organize people around the Web Payments work<br />
** Determine the path forward<br />
** Establish E-Commerce Interoperability standard<br />
* Interested : Mountie Lee, Mete Balci, Dave Raggett, Virginie Galindo, Takahiro Sakai, Keiji Yanagiuchi, Kazuhiro Hoya, Hayato Ozawa, Art Barstow, Karen Myers, Christian Fuhrhop, Bryan Sullivan, Hirotaka Nakajima, Wonsuk Lee<br />
<br />
=== Site Redesign ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on wireframes for part of the site redesign, and to discuss other parts of the project.<br />
* Interested: ddavis, Rebecca Hauck, Yosuke Funahashi, Masataka Yakura<br />
<br />
=== Headlights 2014 ===<br />
<br />
<br />
* Proposed by: Jeff Jaffe<br />
* Summary: W3C management reviews W3C priorities and resources on an ongoing basis, and annually (typically mid-year) explores major re-allocations of resources to align with important trends. W3C Members and W3C Staff participate in [http://www.w3.org/wiki/Headlights2014 Headlights 2014] to identify some potential directions for W3C (technical, organizational, etc.). <br />
* Type: Discussion<br />
* Goals: Gather Headlights 2014 ideas<br />
* Interested: <br />
<br />
=== W3C Data ===<br />
<br />
* Proposed by: Ian Jacobs (Need to get Ted Guild on board!)<br />
* Summary: Data needs <br />
* Goals: Share information about what plans are for exposing and documenting W3C Data<br />
* Interested: <br />
<br />
=== How we can be better Chairs ===<br />
Summary: Chairs are one of the key components in a Working Group, and they can make a big positive or negative difference to the effectiveness of their group. This session is intended for active chairs and people who expect to be or would like to be chairs<br />
<br />
* Proposed by: Chaals<br />
* Type: Open Discussion<br />
* Goals: Share experience and learn from each other. Look at the resources available in the chairs' [http://www.w3.org/guide Guide] and propose necessary changes.<br />
* Interested: Natasha Rooney, Virgnie Galindo, Nigel Megitt, Yosuke Funahashi, Manu Sporny, Olivier Thereaux, Wonsuk Lee<br />
<br />
Some potential topics:<br />
* dealing with trolls<br />
* Tools: github, tracker, bugzilla, lc-track, ...<br />
* Meetings - when to have them, how to plan them, how to get the best out of them<br />
* Editors, authors, and one-man bands<br />
<br />
=== Rec track process ===<br />
Summary: Looking at how to make the Recommendation track meet the needs of our stakeholders<br />
<br />
* Proposed by: Chaals<br />
* Type: Discussion and presentation<br />
* Goals: Work out who are our stakeholders, and what do they need from our specs. Explain the AB's proposed changes for the Process document<br />
* Interested: Masataka Yakura, Alan Stearns<br />
<br />
=== Security roadmap ===<br />
<br />
* Proposed by: Virginie GALINDO<br />
* Summary: Discuss the security roadmap of W3C by presenting the existing work done in WebAppSec and Web Crypto Working Group, reminding the existence of the Web Security Interest Group and collecting the current security challenges that the members are facing to create the security roadmap of W3C. <br />
* Session: Short 10 minute intro on the topic followed by open discussion<br />
* Goals<br />
** Educate people on the security feature under development in W3C<br />
** Collect the wish list in terms of security of the attendees<br />
** Build the priority topics that should be discussed in Web Security Interest Group<br />
*** JS sandboxing / integrity checking / encryption / signature verification / obfuscation<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow, Natasha Rooney, Mountie Lee, Hirotaka Nakajima, Mete Balci, Dom Hazael-Massieux, Mark Nottingham, Wendy Seltzer, Dave Raggett, Manu Sporny, Dirk Schulze<br />
<br />
=== Update on Offline ===<br />
<br />
* Wiki: [http://www.w3.org/wiki/TPAC2013/session-offline TPAC Wiki Session Page]<br />
* Proposed by: Natasha Rooney<br />
* Summary: We had a great Offline Breakout at last year's TPAC and a lot has happened since then. We have seen work in App Cache, Manifest files and now ServiceWorker. This session will give an overview of what is going on and give everyone a good opportunity to ask the experts questions and have some useful discussions on the topic which might bring about some issues which can be considered for future work. <br />
* Type: Presentation and discussion<br />
* Goals: Bring everyone up to a similar level of understanding, raise important issues to all W3C members, and to help those working on solutions.<br />
* Interested: Art Barstow, Dom Hazael-Massieux, Mark Nottingham, Masataka Yakura, Manu Sporny, Alan Stearns, Bryan Sullivan, Wonsuk Lee<br />
<br />
=== Moving Forward on Geolocation API ===<br />
<br />
* Proposed by: Giri Mandyam<br />
* Summary: Discuss a next version of the Geolocation API. This will include enhancements to the existing API (e.g. indoor location, geofencing, etc.), testing and conformance, and the status of the existing specifications from the Geolocation Working Group (e.g. DeviceOrientation).<br />
* Session: 15 minute intro followed by open discussion<br />
* Wiki: [http://www.w3.org/wiki/TPAC2013/session-geolocation TPAC 2013 Wiki Session Page for Geolocation]<br />
* Goals<br />
** Determine interest in reopening the Geolocation Working Group<br />
** Itemize desired enhancements from member companies for existing geolocation specifications<br />
* Interested: '''People will put names here if interested in attending this session:''' Dom Hazael-Massieux, Lars Erik Bolstad<br />
<br />
=== Make better tele-conf system ===<br />
<br />
* Proposed by: Kensaku Komatsu (NTT Communications)<br />
* Summary: Discuss how we can build better tele-conf system. With brand-new web specs, lots of issues about telephone conference will be addressed. For instance, easy to connect, voice recognition, automatic translation. (This session is related to Web on Zakim Community Group)<br />
* Type: Presentation and discussion<br />
* Goals: Obtain nice idea for better tele-conf system.<br />
* Interested: '''People will put names here if interested in attending this session:''' Yusuke Naka, Satoru Takagi, Tomoyuki Shimizu, Koichi Takagi, Ryoya Kawai, Natasha Rooney, Hayato Ozawa, Hirotaka Nakajima<br />
<br />
=== Web of Things ===<br />
<br />
* Proposed by: Rich Tibbett, Jacques Bourhis, Dave Raggett<br />
* Summary: How do we advertise, discover and connect the next billion internet-enabled devices to web pages? What is the current state-of-the-art, immediate priorities and outstanding issues for such an initiative to succeed? We will start with a short summary of some of the proposals currently being worked on at the W3C (things like the [https://dvcs.w3.org/hg/dap/raw-file/tip/discovery-api/Overview.html Network Service Discovery API], [http://www.w3.org/2012/nfc/web-api/ NFC API], current plans for Bluetooth connectivity, indoor location sensing, beacons, the role of Cloud computing for scalable solutions for open markets of services, and other initiatives). Then we can open the floor for other attendees to share their own thoughts and ideas.<br />
* Type: A short presentation (~5 mins) on the current status of related W3C work followed by open discussion and demos<br />
* Goals: Are W3C working on the right things? Are there other connected-devices topics the W3C should be working on? Roadmaps and next steps.<br />
* Heads up on the [http://www.w3.org/community/wot/ W3C Web of Things Community Group] and plans for a Web of Things Workshop in mid 2014 -- [http://www.w3.org/2013/Talks/wot-break-out/ slides]<br />
* Interested: Jonathan Jeon, Kensaku Komatsu, Tomoyuki Shimizu, Art Barstow, Dom Hazael-Massieux, Takayuki Nishikawa, Yosuke Funahashi, Hayato Ozawa, Kunio Numabe, Kinji Matsumura, Yusuke Doi, Karen Myers, Mark Crawford, Manu Sporny, Michael Cooper, Bryan Sullivan<br />
<br />
=== Publishing Management ===<br />
<br />
* Proposed by: Robin Berjon (well, really Ian Jacobs but he wants me to pretend that I did it)<br />
* Summary: It is absurd to enforce the Heartbeat requirement in an age in which editors' drafts are public anyway. We should just have them on TR. I have outlined a proposal in that direction, which seems to benefit from some support: http://lists.w3.org/Archives/Public/spec-prod/2013OctDec/0029.html<br />
* Type: Presentation and discussion<br />
* Goals: Try to set things up so that within the following year we can transition to the new system (yay ambition!)<br />
* Interested: Alan Stearns, Michael Cooper, Dom Hazael-Massieux, Olivier Thereaux<br />
<br />
=== Pervasive Monitoring and the IETF ===<br />
<br />
* Proposed by: Mark Nottingham (requested by PLH)<br />
* Summary: The IETF is going to be meeting for a week before TPAC, where the theme will be "Pervasive Monitoring," an unusual step prompted by recent news. <br />
* Type: Presentation and discussion<br />
* Goals: Inform W3C participants about what's happening in the IETF regarding pervasive monitoring, and spur discussion about what impact this might have on W3C work.<br />
* Interested: Hirotaka Nakajima, Wendy Seltzer, Virginie Galindo, Dom Hazael-Massieux, Jonathan Jeon, Manu Sporny, Bryan Sullivan<br />
<br />
=== HTTP/2.0 Update ===<br />
<br />
* Proposed by: Mark Nottingham (requested by PLH)<br />
* Summary: Work is well underway on a new version of the web's protocol, HTTP/2.0.<br />
* Type: Presentation and discussion<br />
* Goals: Inform W3C participants about what HTTP/2.0 is, what it's status is, and how it impacts W3C work.<br />
* Interested: Hirotaka Nakajima, Yosuke Funahashi, Hayato Ozawa, Natasha Rooney, Bo Hu, Silvia Pfeiffer, Manu Sporny, Wonsuk Lee<br />
<br />
=== Second Screen for the Web ===<br />
<br />
* Proposed by: Dominik Röttsches, Hongbo Min, Anssi Kostiainen<br />
* Summary: Native apps are able to use secondary displays to share the viewing experience across screens. Typical use cases include sharing a video or presentation with a larger audience. To bridge this gap with native, we’ve been experimenting with a Web API that allows web pages to programmatically display web content on secondary displays. In this session we will introduce our [http://webscreens.github.io/presentation-api/ API proposal], show a live demo of our experimental Chromium implementation, and open the discussion on how to evolve this proposal [http://www.w3.org/community/webscreens/ together with the community].<br />
* Type: A short presentation, a live demo, and discussion<br />
* Goals: Bootstrap the W3C Community Group, get interested people on board<br />
* [[TPAC2013/session-second-screen-web|Break-Out Session Wiki Page]]<br />
* Interested: Mozilla, Tomoyuki Shimizu, Natasha Rooney, Dom Hazael-Massieux, Takahiro Sakai, Keiji Yanagiuchi, Kazuhiro Hoya, Yuka Ozawa, Hayato Ozawa, Kunio Numabe, Noriya Sakamoto, Kinji Matsumura, Karen Myers, Jonathan Jeon, Silvia Pfeiffer, Christian Fuhrhop, Olivier Thereaux, Rich Tibbett, Wonsuk Lee, Daniel Davis<br />
<br />
=== Test the Web Foward - What's Next? ===<br />
<br />
* Proposed by: Rebecca Hauck, Larry Mclister, Israel Noto Garcia<br />
* Summary: <br />
** Progress on goals<br />
** What we think is next<br />
** Carry the torch<br />
* Type: Presentation and discussion<br />
* Goals: <br />
** Enlist more w3c members to help drive the movement<br />
** Brainstorm ideas for how to extend the movement beyond just events<br />
* Interested: Masataka Yakura, Alan Stearns, Michael Cooper, Bryan Sullivan, Wonsuk Lee<br />
<br />
=== Entertain Web with Musical Instruments - Web MIDI API ===<br />
<br />
* Proposed by: Ryoya Kawai (AMEI: Association of Musical Electronics Industory, Yamaha)<br />
* Summary: To share what developers build when they get the power of music(focused on MIDI), what else we can control by Web MIDI API to create entertainment web?<br />
* Type: Presentation and discussion<br />
* Goals: Obtain greate ideas for creating entertainment web. <br />
* Interested: Kazuhiro Hoya, Hayato Ozawa, Chris Lilley, Olivier Thereaux, Michael Cooper<br />
<br />
=== Testing - Status and Future Plans ===<br />
<br />
* Proposed by: jgraham<br />
* Summary: The effort to improve the testing of the web platform has been gaining momentum for some time. The goal of this session is to look at what we have achieved so far, and discuss what problems remain to be solved.<br />
* Type: Presentation and discussion<br />
* Goals: Inform participants about the current state of the testsuite and get ideas for overcoming the problems we currently face.<br />
* Interested: ArtB, Yosuke Funahashi, Hayato Ozawa, Masataka Yakura, Alan Stearns, Michael Cooper, Bryan Sullivan<br />
<br />
=== How does Telecom involve in W3C?===<br />
<br />
* Proposed by: Qiuling Pan, Ruinan Sun, Gang Liang<br />
* Summary: Currently internet economy extends to the real economy.Telecom also is affected by web technologies. For example, many OTT provide voice and message services by web page. Mobile Internet usage will be the future. How to converge Telecom technologies with WEB technologies to meet the mobile internet development?<br />
* Type: Presentation and discussion<br />
* Goals: Inform participants about the current state of the mobile internet and get ideas for invoking telecom in W3C.<br />
* Interested: <br />
<br />
=== How to attract Chinese involving in the W3C activity?===<br />
<br />
* Proposed by: Qiuling Pan, Ruinan Sun, Gang Liang<br />
* Summary: Discussion about current situation of Chinese participation in W3C. Summarize the main problems and opportunities, and find a way of improving the activities of Chinese in W3C future work.<br />
* Type: Survey and discussion<br />
* Goals: Inform participants about the current state of Chinese participation and get ideas for improvement.<br />
* Interested: Kang-Hao (Kenny) Lu<br />
<br />
=== Media Resources In-band Tracks ===<br />
<br />
* Proposed by: Cyril Concolato<br />
* Summary: The Media Resources In-band Track Community Group was recently started. This session is meant to kick-off this activity, discuss the first steps.<br />
* Type: Discussion<br />
* Goals: Reviewing the initial documents and agree on future steps. <br />
* Interested: Silvia Pfeiffer, Olivier Thereaux<br />
<br />
=== Towards paginated layouts for (e-)books using Web technologies ===<br />
<br />
* Proposed by: Dave Cramer & Bert Bos<br />
* Summary: The DPug IG and the CSS WG started listing features that are not yet available from CSS (or other Web technologies), but the list is not complete, and, moreover, only few features so far have a home in some Working Draft.<br />
* Type: open discussion<br />
* Goals: (1) What are the (most important) missing features of the Web Platform for the layout of (e-)books? (2) Where in CSS (or elsewhere in W3C) should they be defined? (3) Who can work on them?<br />
* Interested: Alan Stearns, Michael Cooper, Brady Duga, Wonsuk Lee<br />
<br />
=== WebPlatform Docs: Where we are, what our plans are, how it can help your spec===<br />
<br />
* Proposed by: Eliot Graff<br />
* Summary: WebPlatform Docs is the documentation site for the open web platform. We'll present a status report of the state of the site and the how it's relevant to you, and how you and your organization can benefit from participation.<br />
* Session: 20 minute talk about Webplatform.org followed by open discussion<br />
* Goals<br />
** Provide information on the status of WPD.<br />
** Show benefits to spec editors, WG members, and others for getting involved.<br />
** Discuss opportunities for localizing and translating content for web developers.<br />
* Additional speakers: Doug Schepers<br />
* Interested: Masataka Yakura</div>Ddavishttps://www.w3.org/wiki/index.php?title=MeetingTaxis&diff=69783MeetingTaxis2013-11-02T03:32:18Z<p>Ddavis: /* If you want a shuttle bus from HKG to a Hotel in Shenzhen */</p>
<hr />
<div>[[Category:EswMeetings]]<br />
<br />
Use this page to help coordinate taxis and shuttles between Hong Kong Airport (HKG) and Shenzhen hotels.<br />
<br />
* For taxis, people are on their own to coordinate rides.<br />
* For shuttle buses, Tencent and W3C are working together to provide shuttle rides where there are enough people who need rides. <br />
**Private buses are being reserved based on minimum passenger requirements. <br />
<br />
*Deadline to submit bus requests: <b>Friday, 1 November 2013 by 21:00 eastern daylight time</b> local Boston time.<br />
<br />
*A Bus Schedule will be posted by Monday, 4 November 2013.<br />
<br />
<br />
The one-way shuttle fee is estimated to be around 50 USD. Payable (note: change will be in RMB):<br />
** By credit card (see [http://www.w3.org/2013/11/TPAC/#Cash info on payment by credit cards])<br />
** 50 USD<br />
** 300 RMB<br />
** 390 HKD<br />
<br />
The event staff will meet TPAC attendees holding signage outside exit of luggage pick-up, and will check the names.<br\> <br />
Attendees will get on the dedicated bus and will pay the fee. Then, the attendees will have to get off the the bus with all the lugggage (immigration clearance).<br />
The bus will stop at:<br />
* Wuzhou Guest House<br />
* Futian Shangri-La<br />
* Pavillion Hotel<br />
<br />
It takes around 2.5h for the whole trip from HK airport bus port to <br />
Shenzhen hotels. Whole journey will be escorted by event staff.<br />
<br />
* There may be other ways to travel including ferry from HKG to Shenzhen; feel free to use this page to coordinate travel.<br />
<br />
Please, note that this page is '''public'''.<br />
<br />
= TPAC 2013 =<br />
<br />
==If you want a taxi from HKG to a Hotel in Shenzhen== <br />
''REMINDER:''' Please, put entries in chronological order.<br />
<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Time <br />
! Airport Info <br />
! Flight Info <br />
! Hotel <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
==If you want a taxi from Shenzhen Airport to a Hotel in Shenzhen== <br />
''REMINDER:''' Please, put entries in chronological order.<br />
<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Time <br />
! Airport Info <br />
! Flight Info <br />
! Hotel <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
|10 Nov<br />
|11:25 AM<br />
|Shenzhen Terminal D<br />
|Korean Air 827<br />
|Wuzhou<br />
|Jeanne Spellman<br />
|jeanne@w3.org<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
==If you want a taxi from a Shenzhen Hotel to HKG == <br />
''REMINDER:''' Please, put entries in chronological order.<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Meeting <br> Departure <br> Time <br />
! Flight Time <br />
! Airport Info <br />
! Flight Info <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<br />
==If you want a shuttle bus from HKG to a Hotel in Shenzhen== <br />
''REMINDER:''' Please, put entries in chronological order.<br />
<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Time <br />
! Airport Info <br />
! Flight Info <br />
! Hotel <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
|Nov 08<br />
|09:00<br />
|HKG<br />
|Regal<br />
|Wuzhou Guest House<br />
|Alan Stearns<br />
|[mailto:stearns@adobe.com stearns@adobe.com]<br />
|(arriving the night before, staying at the Regal Airport Hotel)<br />
|-<br />
|Nov 08<br />
|09:00<br />
|HKG<br />
|Regal<br />
|Wuzhou Guest House<br />
|Rik Cabanier<br />
|[mailto:cabanier@adobe.com cabanier@adobe.com]<br />
|(arriving the night before, staying at the Regal Airport Hotel)<br />
|-<br />
|Nov 08<br />
|10:35<br />
|MRU -> HKG<br />
|MK 640<br />
|Wuzhou Guest House<br />
|Denis Ah-Kang<br />
|[mailto:denis@w3.org denis@w3.org]<br />
|<br />
|-<br />
|Nov 8<br />
|12:55<br />
|HND -> HKG<br />
|NH 1171<br />
|Wuzhou Guest House<br />
|Sam Sugimoto<br />
|[mailto:sam@w3.org sam@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|12:55<br />
|HND -> HKG<br />
|NH 1171<br />
|The Pavilion Century Tower<br />
|Takeshi Kurosawa<br />
|[mailto:kurosawa-takeshi@mitsue.co.jp kurosawa-takeshi@mitsue.co.jp]<br />
|<br />
|-<br />
|Nov 08<br />
|12:55<br />
|HND -> HKG<br />
|NH 1171<br />
|Wuzhou Guest House<br />
|Sangwhan Moon<br />
|[mailto:smoon@opera.com smoon@opera.com]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|Chris Lilley<br />
|[mailto:chris@w3.org chris@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|David Burns<br />
|[mailto:dburns@mozilla.com dburns@mozilla.com]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|James Graham<br />
|[mailto:jgraham@mozilla.com jgraham@mozilla.com]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Futian Shangri-La<br />
|Simon Sapin<br />
|[mailto:simon.sapin@exyr.org simon.sapin@exyr.org]<br />
|<br />
|-<br />
|Nov&#160;08<br />
|14:10<br />
|HND&#160;»&#160;HKG<br />
|JL 29<br />
|Wuzhou<br />
|Michael[tm]&#160;Smith<br />
|[mailto:mike@w3.org mike@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Futian Shangri-La, Shenzhen<br />
|Masahito KAWAMORI<br />
|[mailto:kawamori@w3.org kawamori@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou<br />
|Ryoichi Kawada<br />
|[mailto:ry-kawada@kddi.com ry-kawada@kddi.com]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou<br />
|Daniel Davis<br />
|[mailto:ddavis@w3.org ddavis@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|14:30<br />
|YYZ -> HKG<br />
|AC 15<br />
|Wuzhou Guest House<br />
|Michael Cooper<br />
|[mailto:cooper@w3.org cooper@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|16:05<br />
|MUE -> HKG<br />
|LH 730<br />
|Wuzhou Guest House<br />
|Dirk Schulze<br />
|[mailto:dschulze@adobe.com dschulze@adobe.com]<br />
|<br />
|-<br />
|Nov 08<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Bert Bos<br />
|[mailto:bert@w3.org bert]<br />
|<br />
|-<br />
|Nov 08<br />
|16:45<br />
|LHR -> HKG<br />
|BA 27<br />
|The Pavilion Century Tower<br />
|Anne van Kesteren<br />
|[mailto:annevk@annevk.nl annevk]<br />
|<br />
|-<br />
|Nov 08<br />
|17:40<br />
|LHR -> HKG<br />
|VS 200<br />
|Wuzhou Guest House<br />
|Richard Ishida<br />
|[mailto:ishida@w3.org ishida@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|18:05<br />
|CDG -> HKG<br />
|AF 188<br />
|Wuzhou Guest House<br />
|Robin Berjon<br />
|[mailto:robin@w3.org robin@w3.org]<br />
|-<br />
|Nov 08<br />
|20:35<br />
|EWR -> HKG<br />
|UA 117<br />
|Wuzhou Guest House<br />
|Mark Sadecki<br />
|[mailto:mark@w3.org mark@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|20:35<br />
|EWR -> HKG<br />
|UA 117<br />
|Wuzhou Guest House<br />
|Andrew Kirkpatrick<br />
|[mailto:akirkpat@adobe.com akirkpat@adobe.com]<br />
|<br />
|-<br />
|Nov 08<br />
|20:35<br />
|EWR -> HKG<br />
|UA 117<br />
|Wuzhou Guest House<br />
|Janina Sajka<br />
|[mailto:janina@rednote.net janina@rednote.net]<br />
|<br />
|-<br />
|Nov 09<br />
|7:40<br />
|LAX -> HKG<br />
|AA6119 / CX88<br />
|Wuzhou Guest House<br />
|Joshua Peek<br />
|[mailto:jp@github.com jp@github.com]<br />
|<br />
|-<br />
|Nov 09<br />
|9:10<br />
|TPE -> HKG<br />
|CI601<br />
|Wuzhou Guest House<br />
|Frode Kileng<br />
|[mailto:frode.kileng@telenor.com frode.kileng@telenor.com]<br />
|<br />
|-<br />
|Nov 09<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Yosuke Funahashi<br />
|[mailto:yfuna@tomo-digi.co.jp yfuna@tomo-digi.co.jp]<br />
|<br />
|-<br />
|Nov 09<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Kazutaka Yamamoto<br />
|[mailto:yamamoto.kazutaka@po.ntts.co.jp yamamoto.kazutaka@po.ntts.co.jp]<br />
|<br />
|-<br />
|Nov 09<br />
|13:30<br />
|KIX -> HKG<br />
|NH 175<br />
|Wuzhou Guest House<br />
|Yoshiaki Ohsumi<br />
|[mailto:ohsumi.yoshiaki@jp.panasonic.com ohsumi.yoshiaki@jp.panasonic.com]<br />
|<br />
|-<br />
|Nov 09<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Futian Shangri-La, Shenzhen.<br />
|Taichi Kawabata<br />
|[mailto:kawabata.taichi@gmail.com kawabata.taichi@gmail.com]<br />
|<br />
|-<br />
|Nov 09<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Futian Shangri-La, Shenzhen.<br />
|Nobuo Saito<br />
|[mailto:ns@slab.sfc.keio.ac.jp ns@slab.sfc.keio.ac.jp]<br />
|<br />
|-<br />
|Nov 09<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|Alexandra Lavirotte<br />
|[mailto:alex@w3.org alex@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|Vivien Lacourba<br />
|[mailto:vivien@w3.org vivien@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|14:30<br />
|YYZ -> HKG<br />
|AC 0015<br />
|Wuzhou Guest House<br />
|Liam Quin<br />
|[mailto:liam&#64;w3.org liam@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|14:55<br />
|SYD -> HKG<br />
|CX 110<br />
|Wuzhou Guest House<br />
|Silvia Pfeiffer<br />
|[mailto:silvia.pfeiffer@nicta.com.au silvia.pfeiffer@nicta.com.au]<br />
|<br />
|-<br />
|Nov 09<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Bernard Gidon<br />
|[mailto:bgidon@w3.org bgidon@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|16:40<br />
|IST -> HKG<br />
|TK 070<br />
|Wuzhou Guest House<br />
|Mete Balci<br />
|[mailto:mete.balci@pozitron.com mete.balci@pozitron.com]<br />
|<br />
|-<br />
|Nov 09<br />
|17:25<br />
|SYD -> HKG<br />
|QF 127<br />
|Wuzhou Guest House<br />
|Cameron McCormack<br />
|[mailto:cam@mcc.id.au cam@mcc.id.au]<br />
|<br />
|-<br />
|Nov 09<br />
|17:35<br />
|YVR -> HKG<br />
|AC 007<br />
|Pavilion Century Tower<br />
|Yusuke Doi<br />
|[mailto:yusuke.doi@toshiba.co.jp yusuke.doi@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 09<br />
|19:00<br />
|ORD -> HKG<br />
|UA 895<br />
|Wuzhou Guest House<br />
|Art Barstow<br />
|[mailto:art.barstow@nokia.com art.barstow@nokia.com]<br />
|<br />
|-<br />
|Nov 09<br />
|19:00<br />
|ORD -> HKG<br />
|UA 895<br />
|Wuzhou Guest House<br />
|Ian Jacobs, Marilyn Siderwicz<br />
|[mailto:ij@w3.org ij@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|19:05<br />
|LAX -> HKG<br />
|CPA 885<br />
|Wuzhou Guest House<br />
|Brady Duga<br />
|[mailto:duga@google.com duga@google.com]<br />
|Also willing to try a ferry or other mode of transit if anyone wants to join me<br />
|-<br />
|Nov 09<br />
|19:10<br />
|YVR -> HKG<br />
|CX 837<br />
|Futian Shangri-La<br />
|Mark Nottingham<br />
|[mailto:mnot@mnot.net mnot@mnot.net]<br />
|Happy to take the ferry as well, if someone wants to come with / fate-share.<br />
|-<br />
|Nov 09<br />
|20:05<br />
|SFO -> HKG<br />
|UA 869<br />
|Pavilion Century Tower<br />
|Jonas Sicking<br />
|[mailto:jonas@sicking.cc jonas@sicking.cc]<br />
|Happy to take the ferry if it still runs and if someone wants to join<br />
|-<br />
|Nov 09<br />
|20:15<br />
|DMK -> HKG<br />
|FD 2502<br />
|Wuzhou Guest House<br />
|Thierry Michel<br />
|[mailto:tmichel@w3.org tmichel@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|20:35<br />
|EWR -> HKG<br />
|UA117<br />
|Wuzhou Guest House<br />
|Ted Guild<br />
|[mailto:ted@w3.org ted@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|21:25<br />
|YVR -> HKG<br />
|CX 888<br />
|Futian Shangri-La, Shenzhen<br />
|Hirotaka Nakajima<br />
|[mailto:hiro@w3.org hiro@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|06:00<br />
|LAX -> HKG<br />
|CX 883<br />
|Futian Shangri-La, Shenzhen<br />
|Giri Mandyam<br />
|[mailto:mandyam@quicinc.com mandyam@quicinc.com]<br />
|<br />
|-<br />
|Nov 10<br />
|06:00<br />
|SFO -> HKG<br />
|CX 873<br />
|Wuzhou Guest House<br />
|Pierre Lemieux<br />
|[mailto:pal@sandflow.com pal@sandflow.com]<br />
|<br />
|-<br />
|Nov 10<br />
|07:00<br />
|MEL -> HKG<br />
|CX 178<br />
|Wuzhou Guest House<br />
|Jason White<br />
|[mailto:jason@jasonjgw.net jason@jasonjgw.net]<br />
|<br />
|-<br />
|Nov 10<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Wuzhou Guest House<br />
|Dominique Hazaël-Massieux<br />
|[mailto:dom@w3.org dom@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Futian Shangri-La<br />
|Philipp Hoschka<br />
|[mailto:ph@w3.org ph@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Wuzhou Guest House<br />
|Marie-Claire Forgue<br />
|[mailto:mcf@w3.org mcf@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Wuzhou Guest House<br />
|Coralie Mercier<br />
|[mailto:coralie@w3.org coralie@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|AM<br />
|HKG<br />
|<br />
|Wuzhou Guest House<br />
|Glenn Adams<br />
|[mailto:glenn@skynav.com glenn@skynav.com]<br />
|<br />
|-<br />
|Nov 10<br />
|12:50<br />
|LHR -> HKG<br />
|CX238<br />
|Wuzhou Guest House<br />
|Dave Raggett<br />
|[mailto:dsr@w3.org dsr@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Masao Isshiki<br />
|[mailto:masao@w3.org masao@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Masahiro Isobe<br />
|[mailto:ma-isobe@kddi.com ma-isobe@kddi.com]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Hiroyuki Aizu<br />
|[mailto:hiroyuki.aizu@toshiba.co.jp hiroyuki.aizu@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Narumichi Sakai<br />
|[mailto:narumichi.sakai@toshiba.co.jp narumichi.sakai@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Keisuke Minami<br />
|[mailto:keisuke.minami@toshiba.co.jp keisuke.minami@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Kinji Matsumura<br />
|[mailto:matsumura.k-ke@nhk.or.jp matsumura.k-ke@nhk.or.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Hisayuki Ohmata<br />
|[mailto:oomata.h-ik@nhk.or.jp oomata.h-ik@nhk.or.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Noriya Sakamoto<br />
|[mailto:noriya.sakamoto@toshiba.co.jp noriya.sakamoto@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Shoko Okuma<br />
|[mailto:okuma@tomo-digi.co.jp okuma@tomo-digi.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|13:25<br />
|NRT -> HKG<br />
|CX 509<br />
|The Pavilion Century Tower<br />
|Tomoyuki Shimizu<br />
|[mailto:tomoyuki.labs@gmail.com tomoyuki.labs@gmail.com]<br />
|<br />
|-<br />
|Nov 10<br />
|13:30<br />
|KIX -> HKG<br />
|NH 175<br />
|Wuzhou Guest House<br />
|Takuki Kamiya<br />
|[mailto:tkamiya@us.fujitsu.com tkamiya@us.fujitsu.com]<br />
|<br />
|-<br />
|Nov 10<br />
|13:30<br />
|KIX -> HKG<br />
|NH 175<br />
|Wuzhou Guest House<br />
|Yuka Ozawa<br />
|[mailto:ozawa.yuka@jp.panasonic.com ozawa.yuka@jp.panasonic.com]<br />
|<br />
|-<br />
|Nov 10<br />
|13:50<br />
|LHR -> HKG<br />
|CX 250<br />
|Futian Shangri-La, Shenzhen<br />
|Nigel Megitt<br />
|[mailto:nigel.megitt@bbc.co.uk nigel.megitt@bbc.co.uk]<br />
|Destination actually the Marco Polo, Futian Shangri-La looks closest.<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou Guest House<br />
|Hidenobu Ito<br />
|[mailto:itou.hidenobu@jp.fujitsu.com itou.hidenobu@jp.fujitsu.com]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Pavilion Century Tower<br />
|Tomohiro Yamada<br />
|[mailto:yamada.tomohiro@lab.ntt.co.jp yamada.tomohiro@lab.ntt.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Pavilion Century Tower<br />
|Kiyoshi Tanaka<br />
|[mailto:tanaka.kiyoshi@lab.ntt.co.jp tanaka.kiyoshi@lab.ntt.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou Guest House<br />
|Hiroshi Yoshida<br />
|[mailto:hiroshi.yoshida@hakuhodo.co.jp hiroshi.yoshida@hakuhodo.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou Guest House<br />
|Kosuke Ushiro<br />
|[mailto:kosuke.ushiro@hakuhodody-media.co.jp kosuke.ushiro@hakuhodody-media.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|Olivier Thereaux<br />
|[mailto:Olivier.Thereaux@bbc.co.uk Olivier.Thereaux@bbc.co.uk]<br />
|<br />
|-<br />
|Nov 10<br />
|14:15<br />
|JFK -> HKG<br />
|CX 841<br />
|Wuzhou Guest House<br />
|Debbie Dahl<br />
|[mailto:dahl@conversational-technologies.com dahl@conversational-technologies.com]<br />
|<br />
|-<br />
|Nov 10<br />
|15:35<br />
|BKK -> HKG<br />
|HX 772<br />
|Wuzhou Guest House<br />
|Gerald Oskoboiny<br />
|[mailto:gerald@w3.org gerald@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Jean-Guilhem Rouel<br />
|[mailto:jean-gui@w3.org jean-gui@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Laurent Carcone<br />
|[mailto:carcone@w3.org carcone@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Rigo Wenning<br />
|[mailto:rigo@w3.org rigo@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Jirka Kosek<br />
|[mailto:jirka@kosek.cz jirka@kosek.cz]<br />
|<br />
|-<br />
|Nov 10<br />
|20:05<br />
|SFO -> HKG<br />
|UA 869<br />
|Wuzhou Guest House<br />
|Sheau Ng<br />
|[mailto:sheau.ng@nbcuni.com sheau.ng@nbcuni.com]<br />
|<br />
|-<br />
|Nov 11<br />
|11:20<br />
|ICN -> HKG<br />
|KE 603<br />
|Wuzhou Guest House<br />
|Lars Erik Bolstad<br />
|[mailto:lbolstad@opera.com lbolstad@opera.com]<br />
|<br />
|-<br />
|Nov 11<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Wuzhou Guest House<br />
|Jerome Chailloux<br />
|[mailto:jerome@w3.org jerome@w3.org]<br />
|<br />
|-<br />
|Nov 11<br />
|14:10<br />
|HND -> HKG<br />
|JL 29<br />
|Wuzhou Guest House<br />
|Brian Birtles<br />
|[mailto:bbirtles@mozilla.com bbirtles@mozilla.com]<br />
|<br />
|-<br />
|Nov 12<br />
|07:00<br />
|LHR -> HKG<br />
|CX 252<br />
|Wuzhou Guest House<br />
|Phil Archer<br />
|[mailto:phila@w3.org phila@w3.org]<br />
|<br />
|-<br />
|Nov 12<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Caroline Baron<br />
|[mailto:cbaron@w3.org cbaron@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Takahiro Sakai<br />
|[mailto:t.sakai@wowow.co.jp t.sakai@wowow.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 29<br />
|Wuzhou Guest House<br />
|Koichi Takagi<br />
|[mailto:ko-takagi@kddi.com ko-takagi@kddi.com]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 29<br />
|Wuzhou Guest House<br />
|Satoru Takagi<br />
|[mailto:sa-takagi@kddi.com sa-takagi@kddi.com]<br />
|<br />
|-<br />
|}<br />
<br />
==If you want a shuttle bus from a Shenzhen Hotel to HKG == <br />
''REMINDER:''' Please, put entries in chronological order.<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Meeting <br> Departure <br> Time <br />
! Flight Time <br />
! Airport Info <br />
! Flight Info <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
|Nov 13<br />
|Wuzhou Guest House, Morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Hiroshi Yoshida<br />
|[mailto:hiroshi.yoshida@hakuhodo.co.jp hiroshi.yoshida@hakuhodo.co.jp]<br />
| <br />
|-<br />
|Nov 13<br />
|Wuzhou Guest House, Morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Kosuke Ushiro<br />
|[mailto:kosuke.ushiro@hakuhodody-media.co.jp kosuke.ushiro@hakuhodody-media.co.jp]<br />
| <br />
|-<br />
|Nov 14<br />
|The Pavilion Century Tower, Morning.<br />
|12:30<br />
|HKG -> SFO<br />
|UA 862<br />
|Jonas Sicking<br />
|[mailto:jonas@sicking.cc jonas@sicking.cc]<br />
| <br />
|-<br />
|Nov 14<br />
|The Pavilion Century Tower, Morning.<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Tomohiro Yamada<br />
|[mailto:yamada.tomohiro@lab.ntt.co.jp yamada.tomohiro@lab.ntt.co.jp]<br />
| <br />
|-<br />
|Nov 14<br />
|The Pavilion Century Tower, Morning.<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Kiyoshi Tanaka<br />
|[mailto:tanaka.kiyoshi@lab.ntt.co.jp tanaka.kiyoshi@lab.ntt.co.jp]<br />
| <br />
|-<br />
|Nov 14<br />
|Wuzhou Guest House, morning<br />
|16:35<br />
|HKG -> LAX<br />
|CPA 882<br />
|Brady Duga<br />
|[mailto:duga@google.com duga@google.com]<br />
|<br />
|-<br />
|Nov 14<br />
|Futian Shangri-La, Shenzhen. Morning<br />
| <br />
|HKG-NRT-SEA<br />
|DL156<br />
|Sylvain Galineau<br />
|[mailto:galineau@adobe.com galineau@adobe.com]<br />
|Flying out the next morning; staying at Regal Hotel in HKG<br />
|-<br />
|Nov 15<br />
|Wuzhou Guest House<br />
|11:10<br />
|HKG -> ORD<br />
|UA 896<br />
|Art Barstow<br />
|[mailto:art.barstow@nokia.com art.barstow@Nokia.com]<br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Masao Isshiki <br />
|[mailto:masao@w3.org masao@w3.org] <br />
| <br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|15:25<br />
|HKG -> KIX<br />
|NH 176<br />
|Yuka Ozawa<br />
|[mailto:ozawa.yuka@jp.panasonic.com ozawa.yuka@jp.panasonic.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 26<br />
|Brian Birtles <br />
|[mailto:bbirtles@mozilla.com bbirtles@mozilla.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Jun Fujisawa <br />
|[mailto:fujisawa.jun@canon.co.jp fujisawa.jun@canon.co.jp] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|17:35<br />
|HKG -> DOH<br />
|QR817<br />
|Frode Kileng <br />
|[mailto:frode.kileng@telenor.com frode.kileng@telenor.com] <br />
| <br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|<br />
|HKG -> SFO<br />
| AC 108<br />
|Rebecca Hauck <br />
|[mailto:rhauck@adobe.com rhauck@adobe.com] <br />
| Flying out in the morning, staying at Regal Hotel in HKG<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, Afternoon<br />
|23:55 <br />
|HKG -> LHR<br />
|CX 251 <br />
|Lars Erik Bolstad <br />
|[mailto:lbolstad@opera.com lbolstad@opera.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, Afternoon<br />
|23:45 <br />
|HKG -> LHR<br />
|BA 28<br />
|David Burns<br />
|[mailto:dburns@mozilla.com dburns@mozilla.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, Afternoon<br />
|23:45 <br />
|HKG -> LHR<br />
|BA 28 <br />
|James Graham<br />
|[mailto:jgraham@mozilla.com jgraham@mozilla.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, Afternoon<br />
|<br />
|HKG -> KIX<br />
|NH 176<br />
|Yoshiaki Ohsumi<br />
|[mailto:ohsumi.yoshiaki@jp.panasonic.com ohsumi.yoshiaki@jp.panasonic.com]<br />
|Move to HKG on public transport.Flying out the next day;<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, Afternoon of 15th<br />
|1:00am<br />
|HKG -> SFO<br />
|CX872<br />
|Silvia Pfeiffer<br />
|[mailto:silvia.pfeiffer@nicta.com.au silvia.pfeiffer@nicta.com.au]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, Afternoon of 15th<br />
|1:00am<br />
|HKG -> SFO<br />
|CX 872<br />
|Pierre Lemieux<br />
|[mailto:pal@sandflow.com pal@sandflow.com]<br />
|<br />
|-<br />
|Nov 16<br />
|The Pavilion Century Tower, Morning<br />
|10:20<br />
|HKG→NRT<br />
|CX520<br />
|Tomoyuki Shimizu<br />
|[mailto:tomoyuki.labs@gmail.com tomoyuki.labs@gmail.com]<br />
|<br />
|-<br />
|Nov 16<br />
|Grand Hyatt, Morning<br />
|1230<br />
|HKG→SFO<br />
|UA862<br />
|Edward O'Connor<br />
|[mailto:eoconnor@apple.com eoconnor@apple.com]<br />
|<br />
|-<br />
|Nov 16<br />
|Wouzou, Morning<br />
|12:30<br />
|HKG→SFO<br />
|UA862<br />
|Janina Sajka<br />
|[mailto:janina@rednote.net janina@rednote.net]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, 0915<br />
|1315 <br />
|HKG <br />
|PR319<br />
|Glenn Adams<br />
|[mailto:glenn@skynav.com glenn@skynav.com]<br />
| <br />
|-<br />
|Nov 16 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Hiroyuki Aizu <br />
|[mailto:hiroyuki.aizu@toshiba.co.jp hiroyuki.aizu@toshiba.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Narumichi Sakai<br />
|[mailto:narumichi.sakai@toshiba.co.jp narumichi.sakai@toshiba.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Keisuke Minami<br />
|[mailto:keisuke.minami@toshiba.co.jp keisuke.minami@toshiba.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Masahiro Isobe<br />
|[mailto:ma-isobe@kddi.com ma-isobe@kddi.com] <br />
| <br />
|-<br />
|Nov 16 <br />
|Futian Shangri-La, Shenzhen, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Noriya Sakamoto<br />
|[mailto:noriya.sakamoto@toshiba.co.jp noriya.sakamoto@toshiba.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Futian Shangri-La, Shenzhen, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Yosuke Funahashi<br />
|[mailto:yfuna@tomo-digi.co.jp yfuna@tomo-digi.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Futian Shangri-La, Shenzhen, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Shoko Okuma<br />
|[mailto:okuma@tomo-digi.co.jp okuma@tomo-digi.co.jp] <br />
|<br />
|-<br />
|Nov 16 <br />
|Futian Shangri-La, Shenzhen, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Kazutaka Yamamoto<br />
|[mailto:yamamoto.kazutaka@po.ntts.co.jp yamamoto.kazutaka@po.ntts.co.jp] <br />
|<br />
|-<br />
|Nov 16<br />
|Marco Polo, Shenzhen, morning<br />
|15:05<br />
|HKG -> LHR<br />
|CX253<br />
|Nigel Megitt<br />
|[mailto:nigel.megitt@bbc.co.uk nigel.megitt@bbc.co.uk]<br />
|Happy to take an early bus and have a look round part of Hong Kong before completing journey to airport on public transport.<br />
|-<br />
|Nov 16<br />
|The Pavilion Century Tower, morning<br />
|15:20<br />
|HKG -> NRT<br />
|NH910<br />
|Takeshi Kurosawa<br />
|[mailto:kurosawa-takeshi@mitsue.co.jp kurosawa-takeshi@mitsue.co.jp]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Hidenobu Ito<br />
|[mailto:itou.hidenobu@jp.fujitsu.com itou.hidenobu@jp.fujitsu.com]<br />
|<br />
|-<br />
|Nov 16<br />
|Futian Shangri-La, Shenzhen.<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Taichi Kawabata<br />
|[mailto:kawabata.taichi@gmail.com kawabata.taichi@gmail.com]<br />
| <br />
|-<br />
|Nov 16<br />
|Futian Shangri-La, Shenzhen.<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Nobuo Saito<br />
|[mailto:ns@slab.sfc.keio.ac.jp ns@slab.sfc.keio.ac.jp]<br />
| <br />
|-<br />
|Nov 16<br />
|Wuzhou<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Ryoichi Kawada<br />
|[mailto:ry-kawada@kddi.com ry-kawada@kddi.com]<br />
| <br />
|-<br />
|Nov 16<br />
|Futian Shangri-La, Shenzhen.<br />
|19:20<br />
|HKG -> AKL<br />
|NZ<br />
|Jet Villegas<br />
|[mailto:jet@mozilla.com jet@mozilla.com]<br />
| <br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, late morning<br />
|19:45<br />
|HKG -> JFK<br />
|CX846<br />
|Debbie Dahl<br />
|[mailto:dahl@conversational-technologies.com dahl@conversational-technologies.com]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House<br />
|20:15<br />
|HKG -> SYD<br />
|QF 128<br />
|Cameron McCormack<br />
|[mailto:cam@mcc.id.au cam@mcc.id.au]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, late morning<br />
|23:15<br />
|HKG -> IST<br />
|TK 071<br />
|Mete Balci<br />
|[mailto:mete.balci@pozitron.com mete.balci@pozitron.com]<br />
| <br />
|-<br />
|Nov 17<br />
|Wuzhou Guest House<br />
|14:25<br />
|HKG -> HND<br />
|NH 1172<br />
|Takuki Kamiya<br />
|[mailto:tkamiya@us.fujitsu.com tkamiya@us.fujitsu.com]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|10:30<br />
|HKG -> NRT -> YVR<br />
|JL 736 / 18<br />
|Gerald Oskoboiny<br />
|[mailto:gerald@w3.org gerald@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:25<br />
|HKG -> EWR -> BOS<br />
|UA 116 / 226<br />
|Philippe Le Hegaret<br />
|[mailto:plh@w3.org plh@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|16:20 flight<br />
|HKG -> YYZ<br />
|AC 0016<br />
|Liam Quin<br />
|[mailto:liam@w3.org liam@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|16:20<br />
|HKG -> YYZ<br />
|AC 16<br />
|Michael Cooper<br />
|[mailto:cooper@w3.org cooper@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:10 <br />
|HKG -> ORD<br />
|UA 896<br />
|Ian Jacobs<br />
|[mailto:ij@w3.org ij@w3.org]<br />
|<br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:10<br />
|HKG -> ORD<br />
|UA 896<br />
|Ted Guild<br />
|[mailto:ted@w3.org ted@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:10<br />
|HKG -> ORD<br />
|UA 896<br />
|Karen Myers<br />
|[mailto:karen@w3.org karen@w3.org]<br />
|<br />
|-<br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:10<br />
|HKG -> ORD<br />
|UA 896<br />
|Veronica Thom<br />
|[mailto:veronica@w3.org veronica@w3.org]<br />
|<br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|12:30<br />
|HKG -> SFO -> BOS<br />
|UA 862<br />
|Marilyn Siderwicz<br />
|[mailto:msiderwicz@w3.org msiderwicz@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|12:30<br />
|HKG -> SFO -> BOS<br />
|UA 862<br />
|Marilyn Siderwicz<br />
|[mailto:msiderwicz@w3.org msiderwicz@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|14:25<br />
|HKG -> HND<br />
|NH 1172<br />
|Sam Sugimoto<br />
|[mailto:sam@w3.org sam@w3.org]<br />
|<br />
|-<br />
|Nov 16<br />
|Futian Shangri-La, Shenzhen.<br />
|15:20<br />
|HKG -> NRT<br />
|NH910<br />
|Takahiro Sakai<br />
|[mailto:t.sakai@wowow.co.jp t.sakai@wowow.co.jp]<br />
|<br />
|-<br />
|Nov 16<br />
|The Pavilion Century Tower, Morning.<br />
|10:30<br />
|HKG -> NRT<br />
|JL 736<br />
|Satoru Takagi<br />
|[mailto:sa-takagi@kddi.com sa-takagi@kddi.com]<br />
| <br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, Morning.<br />
|10:30<br />
|HKG -> NRT<br />
|JL 736<br />
|Koichi Takagi<br />
|[mailto:ko-takagi@kddi.com ko-takagi@kddi.com]<br />
| <br />
|-</div>Ddavishttps://www.w3.org/wiki/index.php?title=MeetingTaxis&diff=69782MeetingTaxis2013-11-02T03:31:32Z<p>Ddavis: /* If you want a shuttle bus from HKG to a Hotel in Shenzhen */ Added ddavis</p>
<hr />
<div>[[Category:EswMeetings]]<br />
<br />
Use this page to help coordinate taxis and shuttles between Hong Kong Airport (HKG) and Shenzhen hotels.<br />
<br />
* For taxis, people are on their own to coordinate rides.<br />
* For shuttle buses, Tencent and W3C are working together to provide shuttle rides where there are enough people who need rides. <br />
**Private buses are being reserved based on minimum passenger requirements. <br />
<br />
*Deadline to submit bus requests: <b>Friday, 1 November 2013 by 21:00 eastern daylight time</b> local Boston time.<br />
<br />
*A Bus Schedule will be posted by Monday, 4 November 2013.<br />
<br />
<br />
The one-way shuttle fee is estimated to be around 50 USD. Payable (note: change will be in RMB):<br />
** By credit card (see [http://www.w3.org/2013/11/TPAC/#Cash info on payment by credit cards])<br />
** 50 USD<br />
** 300 RMB<br />
** 390 HKD<br />
<br />
The event staff will meet TPAC attendees holding signage outside exit of luggage pick-up, and will check the names.<br\> <br />
Attendees will get on the dedicated bus and will pay the fee. Then, the attendees will have to get off the the bus with all the lugggage (immigration clearance).<br />
The bus will stop at:<br />
* Wuzhou Guest House<br />
* Futian Shangri-La<br />
* Pavillion Hotel<br />
<br />
It takes around 2.5h for the whole trip from HK airport bus port to <br />
Shenzhen hotels. Whole journey will be escorted by event staff.<br />
<br />
* There may be other ways to travel including ferry from HKG to Shenzhen; feel free to use this page to coordinate travel.<br />
<br />
Please, note that this page is '''public'''.<br />
<br />
= TPAC 2013 =<br />
<br />
==If you want a taxi from HKG to a Hotel in Shenzhen== <br />
''REMINDER:''' Please, put entries in chronological order.<br />
<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Time <br />
! Airport Info <br />
! Flight Info <br />
! Hotel <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
==If you want a taxi from Shenzhen Airport to a Hotel in Shenzhen== <br />
''REMINDER:''' Please, put entries in chronological order.<br />
<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Time <br />
! Airport Info <br />
! Flight Info <br />
! Hotel <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
|10 Nov<br />
|11:25 AM<br />
|Shenzhen Terminal D<br />
|Korean Air 827<br />
|Wuzhou<br />
|Jeanne Spellman<br />
|jeanne@w3.org<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
==If you want a taxi from a Shenzhen Hotel to HKG == <br />
''REMINDER:''' Please, put entries in chronological order.<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Meeting <br> Departure <br> Time <br />
! Flight Time <br />
! Airport Info <br />
! Flight Info <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|}<br />
<br />
<br />
==If you want a shuttle bus from HKG to a Hotel in Shenzhen== <br />
''REMINDER:''' Please, put entries in chronological order.<br />
<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Time <br />
! Airport Info <br />
! Flight Info <br />
! Hotel <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
|Nov 08<br />
|09:00<br />
|HKG<br />
|Regal<br />
|Wuzhou Guest House<br />
|Alan Stearns<br />
|[mailto:stearns@adobe.com stearns@adobe.com]<br />
|(arriving the night before, staying at the Regal Airport Hotel)<br />
|-<br />
|Nov 08<br />
|09:00<br />
|HKG<br />
|Regal<br />
|Wuzhou Guest House<br />
|Rik Cabanier<br />
|[mailto:cabanier@adobe.com cabanier@adobe.com]<br />
|(arriving the night before, staying at the Regal Airport Hotel)<br />
|-<br />
|Nov 08<br />
|10:35<br />
|MRU -> HKG<br />
|MK 640<br />
|Wuzhou Guest House<br />
|Denis Ah-Kang<br />
|[mailto:denis@w3.org denis@w3.org]<br />
|<br />
|-<br />
|Nov 8<br />
|12:55<br />
|HND -> HKG<br />
|NH 1171<br />
|Wuzhou Guest House<br />
|Sam Sugimoto<br />
|[mailto:sam@w3.org sam@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|12:55<br />
|HND -> HKG<br />
|NH 1171<br />
|The Pavilion Century Tower<br />
|Takeshi Kurosawa<br />
|[mailto:kurosawa-takeshi@mitsue.co.jp kurosawa-takeshi@mitsue.co.jp]<br />
|<br />
|-<br />
|Nov 08<br />
|12:55<br />
|HND -> HKG<br />
|NH 1171<br />
|Wuzhou Guest House<br />
|Sangwhan Moon<br />
|[mailto:smoon@opera.com smoon@opera.com]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|Chris Lilley<br />
|[mailto:chris@w3.org chris@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|David Burns<br />
|[mailto:dburns@mozilla.com dburns@mozilla.com]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|James Graham<br />
|[mailto:jgraham@mozilla.com jgraham@mozilla.com]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Futian Shangri-La<br />
|Simon Sapin<br />
|[mailto:simon.sapin@exyr.org simon.sapin@exyr.org]<br />
|<br />
|-<br />
|Nov&#160;08<br />
|14:10<br />
|HND&#160;»&#160;HKG<br />
|JL 29<br />
|Wuzhou<br />
|Michael[tm]&#160;Smith<br />
|[mailto:mike@w3.org mike@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Futian Shangri-La, Shenzhen<br />
|Masahito KAWAMORI<br />
|[mailto:kawamori@w3.org kawamori@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou<br />
|Ryoichi Kawada<br />
|[mailto:ry-kawada@kddi.com ry-kawada@kddi.com]<br />
|<br />
|-<br />
|Nov 08<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou<br />
|Daniel Davis<br />
|[mailto:ddavis@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|14:30<br />
|YYZ -> HKG<br />
|AC 15<br />
|Wuzhou Guest House<br />
|Michael Cooper<br />
|[mailto:cooper@w3.org cooper@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|16:05<br />
|MUE -> HKG<br />
|LH 730<br />
|Wuzhou Guest House<br />
|Dirk Schulze<br />
|[mailto:dschulze@adobe.com dschulze@adobe.com]<br />
|<br />
|-<br />
|Nov 08<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Bert Bos<br />
|[mailto:bert@w3.org bert]<br />
|<br />
|-<br />
|Nov 08<br />
|16:45<br />
|LHR -> HKG<br />
|BA 27<br />
|The Pavilion Century Tower<br />
|Anne van Kesteren<br />
|[mailto:annevk@annevk.nl annevk]<br />
|<br />
|-<br />
|Nov 08<br />
|17:40<br />
|LHR -> HKG<br />
|VS 200<br />
|Wuzhou Guest House<br />
|Richard Ishida<br />
|[mailto:ishida@w3.org ishida@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|18:05<br />
|CDG -> HKG<br />
|AF 188<br />
|Wuzhou Guest House<br />
|Robin Berjon<br />
|[mailto:robin@w3.org robin@w3.org]<br />
|-<br />
|Nov 08<br />
|20:35<br />
|EWR -> HKG<br />
|UA 117<br />
|Wuzhou Guest House<br />
|Mark Sadecki<br />
|[mailto:mark@w3.org mark@w3.org]<br />
|<br />
|-<br />
|Nov 08<br />
|20:35<br />
|EWR -> HKG<br />
|UA 117<br />
|Wuzhou Guest House<br />
|Andrew Kirkpatrick<br />
|[mailto:akirkpat@adobe.com akirkpat@adobe.com]<br />
|<br />
|-<br />
|Nov 08<br />
|20:35<br />
|EWR -> HKG<br />
|UA 117<br />
|Wuzhou Guest House<br />
|Janina Sajka<br />
|[mailto:janina@rednote.net janina@rednote.net]<br />
|<br />
|-<br />
|Nov 09<br />
|7:40<br />
|LAX -> HKG<br />
|AA6119 / CX88<br />
|Wuzhou Guest House<br />
|Joshua Peek<br />
|[mailto:jp@github.com jp@github.com]<br />
|<br />
|-<br />
|Nov 09<br />
|9:10<br />
|TPE -> HKG<br />
|CI601<br />
|Wuzhou Guest House<br />
|Frode Kileng<br />
|[mailto:frode.kileng@telenor.com frode.kileng@telenor.com]<br />
|<br />
|-<br />
|Nov 09<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Yosuke Funahashi<br />
|[mailto:yfuna@tomo-digi.co.jp yfuna@tomo-digi.co.jp]<br />
|<br />
|-<br />
|Nov 09<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Kazutaka Yamamoto<br />
|[mailto:yamamoto.kazutaka@po.ntts.co.jp yamamoto.kazutaka@po.ntts.co.jp]<br />
|<br />
|-<br />
|Nov 09<br />
|13:30<br />
|KIX -> HKG<br />
|NH 175<br />
|Wuzhou Guest House<br />
|Yoshiaki Ohsumi<br />
|[mailto:ohsumi.yoshiaki@jp.panasonic.com ohsumi.yoshiaki@jp.panasonic.com]<br />
|<br />
|-<br />
|Nov 09<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Futian Shangri-La, Shenzhen.<br />
|Taichi Kawabata<br />
|[mailto:kawabata.taichi@gmail.com kawabata.taichi@gmail.com]<br />
|<br />
|-<br />
|Nov 09<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Futian Shangri-La, Shenzhen.<br />
|Nobuo Saito<br />
|[mailto:ns@slab.sfc.keio.ac.jp ns@slab.sfc.keio.ac.jp]<br />
|<br />
|-<br />
|Nov 09<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|Alexandra Lavirotte<br />
|[mailto:alex@w3.org alex@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|Vivien Lacourba<br />
|[mailto:vivien@w3.org vivien@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|14:30<br />
|YYZ -> HKG<br />
|AC 0015<br />
|Wuzhou Guest House<br />
|Liam Quin<br />
|[mailto:liam&#64;w3.org liam@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|14:55<br />
|SYD -> HKG<br />
|CX 110<br />
|Wuzhou Guest House<br />
|Silvia Pfeiffer<br />
|[mailto:silvia.pfeiffer@nicta.com.au silvia.pfeiffer@nicta.com.au]<br />
|<br />
|-<br />
|Nov 09<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Bernard Gidon<br />
|[mailto:bgidon@w3.org bgidon@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|16:40<br />
|IST -> HKG<br />
|TK 070<br />
|Wuzhou Guest House<br />
|Mete Balci<br />
|[mailto:mete.balci@pozitron.com mete.balci@pozitron.com]<br />
|<br />
|-<br />
|Nov 09<br />
|17:25<br />
|SYD -> HKG<br />
|QF 127<br />
|Wuzhou Guest House<br />
|Cameron McCormack<br />
|[mailto:cam@mcc.id.au cam@mcc.id.au]<br />
|<br />
|-<br />
|Nov 09<br />
|17:35<br />
|YVR -> HKG<br />
|AC 007<br />
|Pavilion Century Tower<br />
|Yusuke Doi<br />
|[mailto:yusuke.doi@toshiba.co.jp yusuke.doi@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 09<br />
|19:00<br />
|ORD -> HKG<br />
|UA 895<br />
|Wuzhou Guest House<br />
|Art Barstow<br />
|[mailto:art.barstow@nokia.com art.barstow@nokia.com]<br />
|<br />
|-<br />
|Nov 09<br />
|19:00<br />
|ORD -> HKG<br />
|UA 895<br />
|Wuzhou Guest House<br />
|Ian Jacobs, Marilyn Siderwicz<br />
|[mailto:ij@w3.org ij@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|19:05<br />
|LAX -> HKG<br />
|CPA 885<br />
|Wuzhou Guest House<br />
|Brady Duga<br />
|[mailto:duga@google.com duga@google.com]<br />
|Also willing to try a ferry or other mode of transit if anyone wants to join me<br />
|-<br />
|Nov 09<br />
|19:10<br />
|YVR -> HKG<br />
|CX 837<br />
|Futian Shangri-La<br />
|Mark Nottingham<br />
|[mailto:mnot@mnot.net mnot@mnot.net]<br />
|Happy to take the ferry as well, if someone wants to come with / fate-share.<br />
|-<br />
|Nov 09<br />
|20:05<br />
|SFO -> HKG<br />
|UA 869<br />
|Pavilion Century Tower<br />
|Jonas Sicking<br />
|[mailto:jonas@sicking.cc jonas@sicking.cc]<br />
|Happy to take the ferry if it still runs and if someone wants to join<br />
|-<br />
|Nov 09<br />
|20:15<br />
|DMK -> HKG<br />
|FD 2502<br />
|Wuzhou Guest House<br />
|Thierry Michel<br />
|[mailto:tmichel@w3.org tmichel@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|20:35<br />
|EWR -> HKG<br />
|UA117<br />
|Wuzhou Guest House<br />
|Ted Guild<br />
|[mailto:ted@w3.org ted@w3.org]<br />
|<br />
|-<br />
|Nov 09<br />
|21:25<br />
|YVR -> HKG<br />
|CX 888<br />
|Futian Shangri-La, Shenzhen<br />
|Hirotaka Nakajima<br />
|[mailto:hiro@w3.org hiro@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|06:00<br />
|LAX -> HKG<br />
|CX 883<br />
|Futian Shangri-La, Shenzhen<br />
|Giri Mandyam<br />
|[mailto:mandyam@quicinc.com mandyam@quicinc.com]<br />
|<br />
|-<br />
|Nov 10<br />
|06:00<br />
|SFO -> HKG<br />
|CX 873<br />
|Wuzhou Guest House<br />
|Pierre Lemieux<br />
|[mailto:pal@sandflow.com pal@sandflow.com]<br />
|<br />
|-<br />
|Nov 10<br />
|07:00<br />
|MEL -> HKG<br />
|CX 178<br />
|Wuzhou Guest House<br />
|Jason White<br />
|[mailto:jason@jasonjgw.net jason@jasonjgw.net]<br />
|<br />
|-<br />
|Nov 10<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Wuzhou Guest House<br />
|Dominique Hazaël-Massieux<br />
|[mailto:dom@w3.org dom@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Futian Shangri-La<br />
|Philipp Hoschka<br />
|[mailto:ph@w3.org ph@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Wuzhou Guest House<br />
|Marie-Claire Forgue<br />
|[mailto:mcf@w3.org mcf@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Wuzhou Guest House<br />
|Coralie Mercier<br />
|[mailto:coralie@w3.org coralie@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|AM<br />
|HKG<br />
|<br />
|Wuzhou Guest House<br />
|Glenn Adams<br />
|[mailto:glenn@skynav.com glenn@skynav.com]<br />
|<br />
|-<br />
|Nov 10<br />
|12:50<br />
|LHR -> HKG<br />
|CX238<br />
|Wuzhou Guest House<br />
|Dave Raggett<br />
|[mailto:dsr@w3.org dsr@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Masao Isshiki<br />
|[mailto:masao@w3.org masao@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Masahiro Isobe<br />
|[mailto:ma-isobe@kddi.com ma-isobe@kddi.com]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Hiroyuki Aizu<br />
|[mailto:hiroyuki.aizu@toshiba.co.jp hiroyuki.aizu@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Narumichi Sakai<br />
|[mailto:narumichi.sakai@toshiba.co.jp narumichi.sakai@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Keisuke Minami<br />
|[mailto:keisuke.minami@toshiba.co.jp keisuke.minami@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Kinji Matsumura<br />
|[mailto:matsumura.k-ke@nhk.or.jp matsumura.k-ke@nhk.or.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Wuzhou Guest House<br />
|Hisayuki Ohmata<br />
|[mailto:oomata.h-ik@nhk.or.jp oomata.h-ik@nhk.or.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Noriya Sakamoto<br />
|[mailto:noriya.sakamoto@toshiba.co.jp noriya.sakamoto@toshiba.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Shoko Okuma<br />
|[mailto:okuma@tomo-digi.co.jp okuma@tomo-digi.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|13:25<br />
|NRT -> HKG<br />
|CX 509<br />
|The Pavilion Century Tower<br />
|Tomoyuki Shimizu<br />
|[mailto:tomoyuki.labs@gmail.com tomoyuki.labs@gmail.com]<br />
|<br />
|-<br />
|Nov 10<br />
|13:30<br />
|KIX -> HKG<br />
|NH 175<br />
|Wuzhou Guest House<br />
|Takuki Kamiya<br />
|[mailto:tkamiya@us.fujitsu.com tkamiya@us.fujitsu.com]<br />
|<br />
|-<br />
|Nov 10<br />
|13:30<br />
|KIX -> HKG<br />
|NH 175<br />
|Wuzhou Guest House<br />
|Yuka Ozawa<br />
|[mailto:ozawa.yuka@jp.panasonic.com ozawa.yuka@jp.panasonic.com]<br />
|<br />
|-<br />
|Nov 10<br />
|13:50<br />
|LHR -> HKG<br />
|CX 250<br />
|Futian Shangri-La, Shenzhen<br />
|Nigel Megitt<br />
|[mailto:nigel.megitt@bbc.co.uk nigel.megitt@bbc.co.uk]<br />
|Destination actually the Marco Polo, Futian Shangri-La looks closest.<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou Guest House<br />
|Hidenobu Ito<br />
|[mailto:itou.hidenobu@jp.fujitsu.com itou.hidenobu@jp.fujitsu.com]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Pavilion Century Tower<br />
|Tomohiro Yamada<br />
|[mailto:yamada.tomohiro@lab.ntt.co.jp yamada.tomohiro@lab.ntt.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Pavilion Century Tower<br />
|Kiyoshi Tanaka<br />
|[mailto:tanaka.kiyoshi@lab.ntt.co.jp tanaka.kiyoshi@lab.ntt.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou Guest House<br />
|Hiroshi Yoshida<br />
|[mailto:hiroshi.yoshida@hakuhodo.co.jp hiroshi.yoshida@hakuhodo.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 029<br />
|Wuzhou Guest House<br />
|Kosuke Ushiro<br />
|[mailto:kosuke.ushiro@hakuhodody-media.co.jp kosuke.ushiro@hakuhodody-media.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|LHR -> HKG<br />
|BA 25<br />
|Wuzhou Guest House<br />
|Olivier Thereaux<br />
|[mailto:Olivier.Thereaux@bbc.co.uk Olivier.Thereaux@bbc.co.uk]<br />
|<br />
|-<br />
|Nov 10<br />
|14:15<br />
|JFK -> HKG<br />
|CX 841<br />
|Wuzhou Guest House<br />
|Debbie Dahl<br />
|[mailto:dahl@conversational-technologies.com dahl@conversational-technologies.com]<br />
|<br />
|-<br />
|Nov 10<br />
|15:35<br />
|BKK -> HKG<br />
|HX 772<br />
|Wuzhou Guest House<br />
|Gerald Oskoboiny<br />
|[mailto:gerald@w3.org gerald@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Jean-Guilhem Rouel<br />
|[mailto:jean-gui@w3.org jean-gui@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Laurent Carcone<br />
|[mailto:carcone@w3.org carcone@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Rigo Wenning<br />
|[mailto:rigo@w3.org rigo@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Jirka Kosek<br />
|[mailto:jirka@kosek.cz jirka@kosek.cz]<br />
|<br />
|-<br />
|Nov 10<br />
|20:05<br />
|SFO -> HKG<br />
|UA 869<br />
|Wuzhou Guest House<br />
|Sheau Ng<br />
|[mailto:sheau.ng@nbcuni.com sheau.ng@nbcuni.com]<br />
|<br />
|-<br />
|Nov 11<br />
|11:20<br />
|ICN -> HKG<br />
|KE 603<br />
|Wuzhou Guest House<br />
|Lars Erik Bolstad<br />
|[mailto:lbolstad@opera.com lbolstad@opera.com]<br />
|<br />
|-<br />
|Nov 11<br />
|11:50<br />
|AMS -> HKG<br />
|KL 887<br />
|Wuzhou Guest House<br />
|Jerome Chailloux<br />
|[mailto:jerome@w3.org jerome@w3.org]<br />
|<br />
|-<br />
|Nov 11<br />
|14:10<br />
|HND -> HKG<br />
|JL 29<br />
|Wuzhou Guest House<br />
|Brian Birtles<br />
|[mailto:bbirtles@mozilla.com bbirtles@mozilla.com]<br />
|<br />
|-<br />
|Nov 12<br />
|07:00<br />
|LHR -> HKG<br />
|CX 252<br />
|Wuzhou Guest House<br />
|Phil Archer<br />
|[mailto:phila@w3.org phila@w3.org]<br />
|<br />
|-<br />
|Nov 12<br />
|16:15<br />
|FRA -> HKG<br />
|LH 796<br />
|Wuzhou Guest House<br />
|Caroline Baron<br />
|[mailto:cbaron@w3.org cbaron@w3.org]<br />
|<br />
|-<br />
|Nov 10<br />
|12:55<br />
|HND -> HKG<br />
|NH1171<br />
|Futian Shangri-La, Shenzhen<br />
|Takahiro Sakai<br />
|[mailto:t.sakai@wowow.co.jp t.sakai@wowow.co.jp]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 29<br />
|Wuzhou Guest House<br />
|Koichi Takagi<br />
|[mailto:ko-takagi@kddi.com ko-takagi@kddi.com]<br />
|<br />
|-<br />
|Nov 10<br />
|14:10<br />
|HND -> HKG<br />
|JL 29<br />
|Wuzhou Guest House<br />
|Satoru Takagi<br />
|[mailto:sa-takagi@kddi.com sa-takagi@kddi.com]<br />
|<br />
|-<br />
|}<br />
<br />
==If you want a shuttle bus from a Shenzhen Hotel to HKG == <br />
''REMINDER:''' Please, put entries in chronological order.<br />
{| class="wikitable sortable" style="background-color:#E0F4FF;" border="1" cellpadding="10" cellspacing="0"<br />
! Date <br />
! Meeting <br> Departure <br> Time <br />
! Flight Time <br />
! Airport Info <br />
! Flight Info <br />
! Name <br />
! Email <br />
! Notes <br />
|-<br />
|Nov 13<br />
|Wuzhou Guest House, Morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Hiroshi Yoshida<br />
|[mailto:hiroshi.yoshida@hakuhodo.co.jp hiroshi.yoshida@hakuhodo.co.jp]<br />
| <br />
|-<br />
|Nov 13<br />
|Wuzhou Guest House, Morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Kosuke Ushiro<br />
|[mailto:kosuke.ushiro@hakuhodody-media.co.jp kosuke.ushiro@hakuhodody-media.co.jp]<br />
| <br />
|-<br />
|Nov 14<br />
|The Pavilion Century Tower, Morning.<br />
|12:30<br />
|HKG -> SFO<br />
|UA 862<br />
|Jonas Sicking<br />
|[mailto:jonas@sicking.cc jonas@sicking.cc]<br />
| <br />
|-<br />
|Nov 14<br />
|The Pavilion Century Tower, Morning.<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Tomohiro Yamada<br />
|[mailto:yamada.tomohiro@lab.ntt.co.jp yamada.tomohiro@lab.ntt.co.jp]<br />
| <br />
|-<br />
|Nov 14<br />
|The Pavilion Century Tower, Morning.<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Kiyoshi Tanaka<br />
|[mailto:tanaka.kiyoshi@lab.ntt.co.jp tanaka.kiyoshi@lab.ntt.co.jp]<br />
| <br />
|-<br />
|Nov 14<br />
|Wuzhou Guest House, morning<br />
|16:35<br />
|HKG -> LAX<br />
|CPA 882<br />
|Brady Duga<br />
|[mailto:duga@google.com duga@google.com]<br />
|<br />
|-<br />
|Nov 14<br />
|Futian Shangri-La, Shenzhen. Morning<br />
| <br />
|HKG-NRT-SEA<br />
|DL156<br />
|Sylvain Galineau<br />
|[mailto:galineau@adobe.com galineau@adobe.com]<br />
|Flying out the next morning; staying at Regal Hotel in HKG<br />
|-<br />
|Nov 15<br />
|Wuzhou Guest House<br />
|11:10<br />
|HKG -> ORD<br />
|UA 896<br />
|Art Barstow<br />
|[mailto:art.barstow@nokia.com art.barstow@Nokia.com]<br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Masao Isshiki <br />
|[mailto:masao@w3.org masao@w3.org] <br />
| <br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|15:25<br />
|HKG -> KIX<br />
|NH 176<br />
|Yuka Ozawa<br />
|[mailto:ozawa.yuka@jp.panasonic.com ozawa.yuka@jp.panasonic.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 26<br />
|Brian Birtles <br />
|[mailto:bbirtles@mozilla.com bbirtles@mozilla.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Jun Fujisawa <br />
|[mailto:fujisawa.jun@canon.co.jp fujisawa.jun@canon.co.jp] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|17:35<br />
|HKG -> DOH<br />
|QR817<br />
|Frode Kileng <br />
|[mailto:frode.kileng@telenor.com frode.kileng@telenor.com] <br />
| <br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, late morning<br />
|<br />
|HKG -> SFO<br />
| AC 108<br />
|Rebecca Hauck <br />
|[mailto:rhauck@adobe.com rhauck@adobe.com] <br />
| Flying out in the morning, staying at Regal Hotel in HKG<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, Afternoon<br />
|23:55 <br />
|HKG -> LHR<br />
|CX 251 <br />
|Lars Erik Bolstad <br />
|[mailto:lbolstad@opera.com lbolstad@opera.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, Afternoon<br />
|23:45 <br />
|HKG -> LHR<br />
|BA 28<br />
|David Burns<br />
|[mailto:dburns@mozilla.com dburns@mozilla.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, Afternoon<br />
|23:45 <br />
|HKG -> LHR<br />
|BA 28 <br />
|James Graham<br />
|[mailto:jgraham@mozilla.com jgraham@mozilla.com] <br />
|<br />
|-<br />
|Nov 15 <br />
|Wuzhou Guest House, Afternoon<br />
|<br />
|HKG -> KIX<br />
|NH 176<br />
|Yoshiaki Ohsumi<br />
|[mailto:ohsumi.yoshiaki@jp.panasonic.com ohsumi.yoshiaki@jp.panasonic.com]<br />
|Move to HKG on public transport.Flying out the next day;<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, Afternoon of 15th<br />
|1:00am<br />
|HKG -> SFO<br />
|CX872<br />
|Silvia Pfeiffer<br />
|[mailto:silvia.pfeiffer@nicta.com.au silvia.pfeiffer@nicta.com.au]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, Afternoon of 15th<br />
|1:00am<br />
|HKG -> SFO<br />
|CX 872<br />
|Pierre Lemieux<br />
|[mailto:pal@sandflow.com pal@sandflow.com]<br />
|<br />
|-<br />
|Nov 16<br />
|The Pavilion Century Tower, Morning<br />
|10:20<br />
|HKG→NRT<br />
|CX520<br />
|Tomoyuki Shimizu<br />
|[mailto:tomoyuki.labs@gmail.com tomoyuki.labs@gmail.com]<br />
|<br />
|-<br />
|Nov 16<br />
|Grand Hyatt, Morning<br />
|1230<br />
|HKG→SFO<br />
|UA862<br />
|Edward O'Connor<br />
|[mailto:eoconnor@apple.com eoconnor@apple.com]<br />
|<br />
|-<br />
|Nov 16<br />
|Wouzou, Morning<br />
|12:30<br />
|HKG→SFO<br />
|UA862<br />
|Janina Sajka<br />
|[mailto:janina@rednote.net janina@rednote.net]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, 0915<br />
|1315 <br />
|HKG <br />
|PR319<br />
|Glenn Adams<br />
|[mailto:glenn@skynav.com glenn@skynav.com]<br />
| <br />
|-<br />
|Nov 16 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Hiroyuki Aizu <br />
|[mailto:hiroyuki.aizu@toshiba.co.jp hiroyuki.aizu@toshiba.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Narumichi Sakai<br />
|[mailto:narumichi.sakai@toshiba.co.jp narumichi.sakai@toshiba.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Keisuke Minami<br />
|[mailto:keisuke.minami@toshiba.co.jp keisuke.minami@toshiba.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Wuzhou Guest House, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Masahiro Isobe<br />
|[mailto:ma-isobe@kddi.com ma-isobe@kddi.com] <br />
| <br />
|-<br />
|Nov 16 <br />
|Futian Shangri-La, Shenzhen, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Noriya Sakamoto<br />
|[mailto:noriya.sakamoto@toshiba.co.jp noriya.sakamoto@toshiba.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Futian Shangri-La, Shenzhen, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Yosuke Funahashi<br />
|[mailto:yfuna@tomo-digi.co.jp yfuna@tomo-digi.co.jp] <br />
| <br />
|-<br />
|Nov 16 <br />
|Futian Shangri-La, Shenzhen, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Shoko Okuma<br />
|[mailto:okuma@tomo-digi.co.jp okuma@tomo-digi.co.jp] <br />
|<br />
|-<br />
|Nov 16 <br />
|Futian Shangri-La, Shenzhen, morning<br />
|14:25<br />
|HKG -> HND<br />
|NH1172<br />
|Kazutaka Yamamoto<br />
|[mailto:yamamoto.kazutaka@po.ntts.co.jp yamamoto.kazutaka@po.ntts.co.jp] <br />
|<br />
|-<br />
|Nov 16<br />
|Marco Polo, Shenzhen, morning<br />
|15:05<br />
|HKG -> LHR<br />
|CX253<br />
|Nigel Megitt<br />
|[mailto:nigel.megitt@bbc.co.uk nigel.megitt@bbc.co.uk]<br />
|Happy to take an early bus and have a look round part of Hong Kong before completing journey to airport on public transport.<br />
|-<br />
|Nov 16<br />
|The Pavilion Century Tower, morning<br />
|15:20<br />
|HKG -> NRT<br />
|NH910<br />
|Takeshi Kurosawa<br />
|[mailto:kurosawa-takeshi@mitsue.co.jp kurosawa-takeshi@mitsue.co.jp]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, morning<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Hidenobu Ito<br />
|[mailto:itou.hidenobu@jp.fujitsu.com itou.hidenobu@jp.fujitsu.com]<br />
|<br />
|-<br />
|Nov 16<br />
|Futian Shangri-La, Shenzhen.<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Taichi Kawabata<br />
|[mailto:kawabata.taichi@gmail.com kawabata.taichi@gmail.com]<br />
| <br />
|-<br />
|Nov 16<br />
|Futian Shangri-La, Shenzhen.<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Nobuo Saito<br />
|[mailto:ns@slab.sfc.keio.ac.jp ns@slab.sfc.keio.ac.jp]<br />
| <br />
|-<br />
|Nov 16<br />
|Wuzhou<br />
|15:40<br />
|HKG -> HND<br />
|JL 026<br />
|Ryoichi Kawada<br />
|[mailto:ry-kawada@kddi.com ry-kawada@kddi.com]<br />
| <br />
|-<br />
|Nov 16<br />
|Futian Shangri-La, Shenzhen.<br />
|19:20<br />
|HKG -> AKL<br />
|NZ<br />
|Jet Villegas<br />
|[mailto:jet@mozilla.com jet@mozilla.com]<br />
| <br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, late morning<br />
|19:45<br />
|HKG -> JFK<br />
|CX846<br />
|Debbie Dahl<br />
|[mailto:dahl@conversational-technologies.com dahl@conversational-technologies.com]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House<br />
|20:15<br />
|HKG -> SYD<br />
|QF 128<br />
|Cameron McCormack<br />
|[mailto:cam@mcc.id.au cam@mcc.id.au]<br />
|<br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, late morning<br />
|23:15<br />
|HKG -> IST<br />
|TK 071<br />
|Mete Balci<br />
|[mailto:mete.balci@pozitron.com mete.balci@pozitron.com]<br />
| <br />
|-<br />
|Nov 17<br />
|Wuzhou Guest House<br />
|14:25<br />
|HKG -> HND<br />
|NH 1172<br />
|Takuki Kamiya<br />
|[mailto:tkamiya@us.fujitsu.com tkamiya@us.fujitsu.com]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|10:30<br />
|HKG -> NRT -> YVR<br />
|JL 736 / 18<br />
|Gerald Oskoboiny<br />
|[mailto:gerald@w3.org gerald@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:25<br />
|HKG -> EWR -> BOS<br />
|UA 116 / 226<br />
|Philippe Le Hegaret<br />
|[mailto:plh@w3.org plh@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|16:20 flight<br />
|HKG -> YYZ<br />
|AC 0016<br />
|Liam Quin<br />
|[mailto:liam@w3.org liam@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|16:20<br />
|HKG -> YYZ<br />
|AC 16<br />
|Michael Cooper<br />
|[mailto:cooper@w3.org cooper@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:10 <br />
|HKG -> ORD<br />
|UA 896<br />
|Ian Jacobs<br />
|[mailto:ij@w3.org ij@w3.org]<br />
|<br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:10<br />
|HKG -> ORD<br />
|UA 896<br />
|Ted Guild<br />
|[mailto:ted@w3.org ted@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:10<br />
|HKG -> ORD<br />
|UA 896<br />
|Karen Myers<br />
|[mailto:karen@w3.org karen@w3.org]<br />
|<br />
|-<br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|11:10<br />
|HKG -> ORD<br />
|UA 896<br />
|Veronica Thom<br />
|[mailto:veronica@w3.org veronica@w3.org]<br />
|<br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|12:30<br />
|HKG -> SFO -> BOS<br />
|UA 862<br />
|Marilyn Siderwicz<br />
|[mailto:msiderwicz@w3.org msiderwicz@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|12:30<br />
|HKG -> SFO -> BOS<br />
|UA 862<br />
|Marilyn Siderwicz<br />
|[mailto:msiderwicz@w3.org msiderwicz@w3.org]<br />
| <br />
|-<br />
|Nov 18<br />
|Sheraton Dameisha Resort<br />
|14:25<br />
|HKG -> HND<br />
|NH 1172<br />
|Sam Sugimoto<br />
|[mailto:sam@w3.org sam@w3.org]<br />
|<br />
|-<br />
|Nov 16<br />
|Futian Shangri-La, Shenzhen.<br />
|15:20<br />
|HKG -> NRT<br />
|NH910<br />
|Takahiro Sakai<br />
|[mailto:t.sakai@wowow.co.jp t.sakai@wowow.co.jp]<br />
|<br />
|-<br />
|Nov 16<br />
|The Pavilion Century Tower, Morning.<br />
|10:30<br />
|HKG -> NRT<br />
|JL 736<br />
|Satoru Takagi<br />
|[mailto:sa-takagi@kddi.com sa-takagi@kddi.com]<br />
| <br />
|-<br />
|Nov 16<br />
|Wuzhou Guest House, Morning.<br />
|10:30<br />
|HKG -> NRT<br />
|JL 736<br />
|Koichi Takagi<br />
|[mailto:ko-takagi@kddi.com ko-takagi@kddi.com]<br />
| <br />
|-</div>Ddavishttps://www.w3.org/wiki/index.php?title=Headlights2013/SiteRedesign/&diff=68833Headlights2013/SiteRedesign/2013-10-02T03:48:31Z<p>Ddavis: Added more links</p>
<hr />
<div>* [[Headlights2013/SiteRedesign | General notes]]<br />
* [[Headlights2013/SiteRedesign/Vision | Vision]]<br />
* [[Headlights2013/SiteRedesign/Survey_Analysis_Notes | Survey analysis notes]]<br />
* [[Headlights2013/SiteRedesign/ChairSurvey | Chair survey]]<br />
* [[Headlights2013/SiteRedesign/MemberSurvey | Member survey]]<br />
* [[Headlights2013/SiteRedesign/PublicSurvey | Public survey]]<br />
* [[Headlights2013/SiteRedesign/CombinedSurvey | Combined survey]]<br />
* [[Headlights2013/SiteRedesign/Calendar | Calendar]]<br />
* [[Headlights2013/SiteRedesign/Proposal | Proposal]]<br />
* [[Headlights2013/SiteRedesign/InfoArch | Information architecture]]</div>Ddavishttps://www.w3.org/wiki/index.php?title=Headlights2013/SiteRedesign/&diff=68832Headlights2013/SiteRedesign/2013-10-02T03:40:34Z<p>Ddavis: Added more links</p>
<hr />
<div>* [[Headlights2013/SiteRedesign | General notes]]<br />
* [[Headlights2013/SiteRedesign/Vision | Vision]]<br />
* [[Headlights2013/SiteRedesign/Survey_Analysis_Notes | Survey analysis notes]]<br />
* [[Headlights2013/SiteRedesign/Proposal | Proposal]]<br />
* [[Headlights2013/SiteRedesign/InfoArch | Information architecture]]</div>Ddavishttps://www.w3.org/wiki/index.php?title=Headlights2013/SiteRedesign/&diff=68831Headlights2013/SiteRedesign/2013-10-02T03:35:31Z<p>Ddavis: Added links to sub-pages</p>
<hr />
<div>* [[Headlights2013/SiteRedesign/Proposal | Proposal]]<br />
* [[Headlights2013/SiteRedesign/InfoArch | Information Architecture]]</div>Ddavishttps://www.w3.org/wiki/index.php?title=TPAC/2013/SessionIdeas&diff=67947TPAC/2013/SessionIdeas2013-08-21T07:39:15Z<p>Ddavis: /* Site Redesign */</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2013]] session ideas in advance of the meeting. See the [http://www.w3.org/wiki/TPAC2013/FAQ TPAC 2013 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top. See [[#Site Redesign|site redesign below]] as a template for new entries.<br />
<br />
== Suggestions for Tuesday Morning AC Meeting ==<br />
<br />
The Tuesday morning of the AC Meeting is optional. It is intended for informal discussion among Chairs, AC, TAG, AB, Offices, and Team.<br />
<br />
=== Notes from the Team ===<br />
<br />
* New Member Intros<br />
* Introduction to W3C's IPR Policies<br />
<br />
=== Notes on breakout rooms ===<br />
<br />
* We will seek three breakout rooms + the main room.<br />
* However groups will be meeting in many of the available rooms.<br />
* Therefore, if we can't arrange for 3 distinct rooms, we'll grab corners of the main room.<br />
<br />
== Suggestions for Wednesday Breakouts ==<br />
<br />
Note: For 2013 we invite the Advisory Committee to use the Wednesday breakouts for AC-type topics as well.<br />
<br />
=== Notes from the Team ===<br />
<br />
* Anniversary planning<br />
<br />
=== Site Redesign ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on a the site redesign, including the vision for the site, information architecture, and implementation plans. <br />
* Interested: ddavis<br />
<br />
=== How we can be better Chairs ===<br />
Summary: Chairs are one of the key components in a Working Group, and they can make a big positive or negative difference to the effectiveness of their group. This session is intended for active chairs and people who expect to be or would like to be chairs<br />
<br />
* Proposed by: Chaals<br />
* Type: Open Discussion<br />
* Goals: Share experience and learn from each other. Look at the resources available in the chairs' [http://www.w3.org/guide Guide] and propose necessary changes.<br />
* Interested: '''People will put names here if interested in attending this session'''<br />
<br />
Some potential topics:<br />
* dealing with trolls<br />
* Tools: github, tracker, bugzilla, lc-track, ...<br />
* Meetings - when to have them, how to plan them, how to get the best out of them<br />
* Editors, authors, and one-man bands<br />
<br />
=== Rec track process ===<br />
Summary: Looking at how to make the Recommendation track meet the needs of our stakeholders<br />
<br />
* Proposed by: Chaals<br />
* Type: Discussion and presentation<br />
* Goals: Work out who are our stakeholders, and what do they need from our specs. Explain the AB's proposed changes for the Process document<br />
* Interested: '''People will put names here if interested in attending this session'''</div>Ddavishttps://www.w3.org/wiki/index.php?title=TPAC/2013/SessionIdeas&diff=67946TPAC/2013/SessionIdeas2013-08-21T07:38:57Z<p>Ddavis: /* Site Redesign */ Added myself</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2013]] session ideas in advance of the meeting. See the [http://www.w3.org/wiki/TPAC2013/FAQ TPAC 2013 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top. See [[#Site Redesign|site redesign below]] as a template for new entries.<br />
<br />
== Suggestions for Tuesday Morning AC Meeting ==<br />
<br />
The Tuesday morning of the AC Meeting is optional. It is intended for informal discussion among Chairs, AC, TAG, AB, Offices, and Team.<br />
<br />
=== Notes from the Team ===<br />
<br />
* New Member Intros<br />
* Introduction to W3C's IPR Policies<br />
<br />
=== Notes on breakout rooms ===<br />
<br />
* We will seek three breakout rooms + the main room.<br />
* However groups will be meeting in many of the available rooms.<br />
* Therefore, if we can't arrange for 3 distinct rooms, we'll grab corners of the main room.<br />
<br />
== Suggestions for Wednesday Breakouts ==<br />
<br />
Note: For 2013 we invite the Advisory Committee to use the Wednesday breakouts for AC-type topics as well.<br />
<br />
=== Notes from the Team ===<br />
<br />
* Anniversary planning<br />
<br />
=== Site Redesign ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on a the site redesign, including the vision for the site, information architecture, and implementation plans. <br />
* Interested: '''People will put names here if interested in attending this session'''<br />
** ddavis<br />
<br />
=== How we can be better Chairs ===<br />
Summary: Chairs are one of the key components in a Working Group, and they can make a big positive or negative difference to the effectiveness of their group. This session is intended for active chairs and people who expect to be or would like to be chairs<br />
<br />
* Proposed by: Chaals<br />
* Type: Open Discussion<br />
* Goals: Share experience and learn from each other. Look at the resources available in the chairs' [http://www.w3.org/guide Guide] and propose necessary changes.<br />
* Interested: '''People will put names here if interested in attending this session'''<br />
<br />
Some potential topics:<br />
* dealing with trolls<br />
* Tools: github, tracker, bugzilla, lc-track, ...<br />
* Meetings - when to have them, how to plan them, how to get the best out of them<br />
* Editors, authors, and one-man bands<br />
<br />
=== Rec track process ===<br />
Summary: Looking at how to make the Recommendation track meet the needs of our stakeholders<br />
<br />
* Proposed by: Chaals<br />
* Type: Discussion and presentation<br />
* Goals: Work out who are our stakeholders, and what do they need from our specs. Explain the AB's proposed changes for the Process document<br />
* Interested: '''People will put names here if interested in attending this session'''</div>Ddavishttps://www.w3.org/wiki/index.php?title=User:Ddavis&diff=67529User:Ddavis2013-07-18T13:48:47Z<p>Ddavis: Created page with "[http://www.w3.org/People#ddavis Daniel Davis]"</p>
<hr />
<div>[http://www.w3.org/People#ddavis Daniel Davis]</div>Ddavis