https://www.w3.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=AmyW3C Wiki - User contributions [en]2024-03-19T06:11:26ZUser contributionsMediaWiki 1.41.0https://www.w3.org/wiki/index.php?title=AB/VisionTF&diff=116539AB/VisionTF2023-10-27T13:12:51Z<p>Amy: /* Meeting Schedule and Agenda */</p>
<hr />
<div>On 6 April 2023, the AB resolved to open a temporary Task Force (TF) to [https://github.com/w3c/AB-public/tree/main/Vision work on the Vision]:<br />
* with the ultimate goal of creating a W3C-endorsed, W3C-wide Vision statement for the organization<br />
* with the initial task of publishing an AB-consensus [https://www.w3.org/2021/Process-20211102/#WGNote NOTE] developed with the community as a first step towards that goal<br />
* with the explicit intention of working with the community in a manner yet to be determined to subsequently revise and elevate this NOTE to a [https://www.w3.org/2021/Process-20211102/#memo W3C Statement] representing a consensus Vision for W3C<br />
* with Task Force participation open to W3C Members, Invited Experts, and Team, actively seeking consensus of all Task Force participants, but taking formal decisions by consensus of the AB<br />
* meeting bi-weekly during the AB slot on weeks the AB does not meet from now until the end of the upcoming AB membership transition<br />
* conducting meetings and publishing minutes in Member-only space to allow participants to speak more freely; but maintaining editors' drafts and issue discussion in public, [https://github.com/w3c/AB-public/issues in the AB-public GitHub repo], to allow broader input<br />
<br />
== Drafts, Repository, Issue-tracking ==<br />
* [https://www.w3.org/TR/w3c-vision/ Official Draft]<br />
* [https://github.com/w3c/AB-public/tree/main/Vision Editor’s Draft]<br />
* [https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3AVision Open Issues]<br />
<br />
== Meeting Schedule and Agenda ==<br />
<br />
* Meeting Time: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230427T14 14:00 UTC]<br />
* Meeting Coordinates: [https://www.w3.org/groups/tf/vision/calendar/ W3C Calendar], | [https://lists.w3.org/Archives/Member/chairs/2023AprJun/0028.html Member Visible] | [https://lists.w3.org/Archives/Group/group-invited-experts/2023Apr/0003.html Invited-Expert Visible]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date !! Agenda !! Minutes<br />
|-<br />
| 2023-10-26 || [[AB/VisionTF/2023-10-26|Agenda]] || [https://www.w3.org/2023/10/26-vision-minutes.html Minutes 2023-10-26]<br />
|-<br />
|-<br />
| 2023-10-12 || CANCELED || CANCELED<br />
|-<br />
| 2023-09-28 || [[AB/VisionTF/2023-09-28|Agenda]] || [https://www.w3.org/2023/09/28-vision-minutes.html Minutes 2023-09-28]<br />
|-<br />
| 2023-09-12 || [[AB/VisionTF/2023-09-12|Agenda]] || [https://www.w3.org/2023/09/12-vision-minutes.html Minutes 2023-09-12]<br />
|-<br />
| 2023-08-24|| [[AB/VisionTF/2023-08-24|Agenda]] || [https://www.w3.org/2023/08/24-vision-minutes.html Minutes 2023-08-24]<br />
|-<br />
| 2023-08-10|| [[AB/VisionTF/2023-08-10|Agenda]] || [https://www.w3.org/2023/08/10-vision-minutes.html Minutes 2023-08-10]<br />
|-<br />
| 2023-07-13 || [[AB/VisionTF/2023-07-13|Agenda]] || [https://www.w3.org/2023/07/13-vision-minutes.html Minutes 2023-07-13]<br />
|-<br />
| 2023-06-22 || [[AB/VisionTF/2023-06-22|Agenda]] || [https://www.w3.org/2023/06/22-vision-minutes.html Minutes 2023-06-22]<br />
|-<br />
| 2023-06-08 || [[AB/VisionTF/2023-06-08|Agenda]] || [https://www.w3.org/2023/06/08-vision-minutes.html Minutes 2023-06-08]<br />
|-<br />
| 2023-05-25 || [[AB/VisionTF/2023-05-25|Agenda]] || [https://www.w3.org/2023/05/25-vision-minutes.html Minutes 2023-05-25]<br />
|-<br />
| 2023-05-11 || CANCELED || CANCELED<br />
|-<br />
| 2023-04-27 || [[AB/VisionTF/2023-04-27|Agenda]] || [https://www.w3.org/2023/04/27-vision-minutes.html Minutes 2023-04-27]<br />
|-<br />
<br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=AB/VisionTF&diff=116538AB/VisionTF2023-10-27T13:12:22Z<p>Amy: /* Meeting Schedule and Agenda */</p>
<hr />
<div>On 6 April 2023, the AB resolved to open a temporary Task Force (TF) to [https://github.com/w3c/AB-public/tree/main/Vision work on the Vision]:<br />
* with the ultimate goal of creating a W3C-endorsed, W3C-wide Vision statement for the organization<br />
* with the initial task of publishing an AB-consensus [https://www.w3.org/2021/Process-20211102/#WGNote NOTE] developed with the community as a first step towards that goal<br />
* with the explicit intention of working with the community in a manner yet to be determined to subsequently revise and elevate this NOTE to a [https://www.w3.org/2021/Process-20211102/#memo W3C Statement] representing a consensus Vision for W3C<br />
* with Task Force participation open to W3C Members, Invited Experts, and Team, actively seeking consensus of all Task Force participants, but taking formal decisions by consensus of the AB<br />
* meeting bi-weekly during the AB slot on weeks the AB does not meet from now until the end of the upcoming AB membership transition<br />
* conducting meetings and publishing minutes in Member-only space to allow participants to speak more freely; but maintaining editors' drafts and issue discussion in public, [https://github.com/w3c/AB-public/issues in the AB-public GitHub repo], to allow broader input<br />
<br />
== Drafts, Repository, Issue-tracking ==<br />
* [https://www.w3.org/TR/w3c-vision/ Official Draft]<br />
* [https://github.com/w3c/AB-public/tree/main/Vision Editor’s Draft]<br />
* [https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3AVision Open Issues]<br />
<br />
== Meeting Schedule and Agenda ==<br />
<br />
* Meeting Time: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230427T14 14:00 UTC]<br />
* Meeting Coordinates: [https://www.w3.org/groups/tf/vision/calendar/ W3C Calendar], | [https://lists.w3.org/Archives/Member/chairs/2023AprJun/0028.html Member Visible] | [https://lists.w3.org/Archives/Group/group-invited-experts/2023Apr/0003.html Invited-Expert Visible]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date !! Agenda !! Minutes<br />
|-<br />
| 2023-10-26 || [[AB/VisionTF/2023-10-26|Agenda]] || [ https://www.w3.org/2023/10/26-vision-minutes.html Minutes]<br />
|-<br />
|-<br />
| 2023-10-12 || CANCELED || CANCELED<br />
|-<br />
| 2023-09-28 || [[AB/VisionTF/2023-09-28|Agenda]] || [https://www.w3.org/2023/09/28-vision-minutes.html Minutes 2023-09-28]<br />
|-<br />
| 2023-09-12 || [[AB/VisionTF/2023-09-12|Agenda]] || [https://www.w3.org/2023/09/12-vision-minutes.html Minutes 2023-09-12]<br />
|-<br />
| 2023-08-24|| [[AB/VisionTF/2023-08-24|Agenda]] || [https://www.w3.org/2023/08/24-vision-minutes.html Minutes 2023-08-24]<br />
|-<br />
| 2023-08-10|| [[AB/VisionTF/2023-08-10|Agenda]] || [https://www.w3.org/2023/08/10-vision-minutes.html Minutes 2023-08-10]<br />
|-<br />
| 2023-07-13 || [[AB/VisionTF/2023-07-13|Agenda]] || [https://www.w3.org/2023/07/13-vision-minutes.html Minutes 2023-07-13]<br />
|-<br />
| 2023-06-22 || [[AB/VisionTF/2023-06-22|Agenda]] || [https://www.w3.org/2023/06/22-vision-minutes.html Minutes 2023-06-22]<br />
|-<br />
| 2023-06-08 || [[AB/VisionTF/2023-06-08|Agenda]] || [https://www.w3.org/2023/06/08-vision-minutes.html Minutes 2023-06-08]<br />
|-<br />
| 2023-05-25 || [[AB/VisionTF/2023-05-25|Agenda]] || [https://www.w3.org/2023/05/25-vision-minutes.html Minutes 2023-05-25]<br />
|-<br />
| 2023-05-11 || CANCELED || CANCELED<br />
|-<br />
| 2023-04-27 || [[AB/VisionTF/2023-04-27|Agenda]] || [https://www.w3.org/2023/04/27-vision-minutes.html Minutes 2023-04-27]<br />
|-<br />
<br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=AB/VisionTF&diff=116507AB/VisionTF2023-10-23T19:10:09Z<p>Amy: /* Meeting Schedule and Agenda */</p>
<hr />
<div>On 6 April 2023, the AB resolved to open a temporary Task Force (TF) to [https://github.com/w3c/AB-public/tree/main/Vision work on the Vision]:<br />
* with the ultimate goal of creating a W3C-endorsed, W3C-wide Vision statement for the organization<br />
* with the initial task of publishing an AB-consensus [https://www.w3.org/2021/Process-20211102/#WGNote NOTE] developed with the community as a first step towards that goal<br />
* with the explicit intention of working with the community in a manner yet to be determined to subsequently revise and elevate this NOTE to a [https://www.w3.org/2021/Process-20211102/#memo W3C Statement] representing a consensus Vision for W3C<br />
* with Task Force participation open to W3C Members, Invited Experts, and Team, actively seeking consensus of all Task Force participants, but taking formal decisions by consensus of the AB<br />
* meeting bi-weekly during the AB slot on weeks the AB does not meet from now until the end of the upcoming AB membership transition<br />
* conducting meetings and publishing minutes in Member-only space to allow participants to speak more freely; but maintaining editors' drafts and issue discussion in public, [https://github.com/w3c/AB-public/issues in the AB-public GitHub repo], to allow broader input<br />
<br />
== Drafts, Repository, Issue-tracking ==<br />
* [https://www.w3.org/TR/w3c-vision/ Official Draft]<br />
* [https://github.com/w3c/AB-public/tree/main/Vision Editor’s Draft]<br />
* [https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3AVision Open Issues]<br />
<br />
== Meeting Schedule and Agenda ==<br />
<br />
* Meeting Time: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230427T14 14:00 UTC]<br />
* Meeting Coordinates: [https://www.w3.org/groups/tf/vision/calendar/ W3C Calendar], | [https://lists.w3.org/Archives/Member/chairs/2023AprJun/0028.html Member Visible] | [https://lists.w3.org/Archives/Group/group-invited-experts/2023Apr/0003.html Invited-Expert Visible]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date !! Agenda !! Minutes<br />
|-<br />
| 2023-10-25 || [Agenda] || [Minutes]<br />
|-<br />
|-<br />
| 2023-10-12 || CANCELED || CANCELED<br />
|-<br />
| 2023-09-28 || [[AB/VisionTF/2023-09-28|Agenda]] || [https://www.w3.org/2023/09/28-vision-minutes.html Minutes 2023-09-28]<br />
|-<br />
| 2023-09-12 || [[AB/VisionTF/2023-09-12|Agenda]] || [https://www.w3.org/2023/09/12-vision-minutes.html Minutes 2023-09-12]<br />
|-<br />
| 2023-08-24|| [[AB/VisionTF/2023-08-24|Agenda]] || [https://www.w3.org/2023/08/24-vision-minutes.html Minutes 2023-08-24]<br />
|-<br />
| 2023-08-10|| [[AB/VisionTF/2023-08-10|Agenda]] || [https://www.w3.org/2023/08/10-vision-minutes.html Minutes 2023-08-10]<br />
|-<br />
| 2023-07-13 || [[AB/VisionTF/2023-07-13|Agenda]] || [https://www.w3.org/2023/07/13-vision-minutes.html Minutes 2023-07-13]<br />
|-<br />
| 2023-06-22 || [[AB/VisionTF/2023-06-22|Agenda]] || [https://www.w3.org/2023/06/22-vision-minutes.html Minutes 2023-06-22]<br />
|-<br />
| 2023-06-08 || [[AB/VisionTF/2023-06-08|Agenda]] || [https://www.w3.org/2023/06/08-vision-minutes.html Minutes 2023-06-08]<br />
|-<br />
| 2023-05-25 || [[AB/VisionTF/2023-05-25|Agenda]] || [https://www.w3.org/2023/05/25-vision-minutes.html Minutes 2023-05-25]<br />
|-<br />
| 2023-05-11 || CANCELED || CANCELED<br />
|-<br />
| 2023-04-27 || [[AB/VisionTF/2023-04-27|Agenda]] || [https://www.w3.org/2023/04/27-vision-minutes.html Minutes 2023-04-27]<br />
|-<br />
<br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=AB/VisionTF&diff=116129AB/VisionTF2023-07-28T18:35:03Z<p>Amy: /* Meeting Schedule and Agenda */</p>
<hr />
<div>On 6 April 2023, the AB resolved to open a temporary Task Force (TF) to [https://github.com/w3c/AB-public/tree/main/Vision work on the Vision]:<br />
* with the ultimate goal of creating a W3C-endorsed, W3C-wide Vision statement for the organization<br />
* with the initial task of publishing an AB-consensus [https://www.w3.org/2021/Process-20211102/#WGNote NOTE] developed with the community as a first step towards that goal<br />
* with the explicit intention of working with the community in a manner yet to be determined to subsequently revise and elevate this NOTE to a [https://www.w3.org/2021/Process-20211102/#memo W3C Statement] representing a consensus Vision for W3C<br />
* with Task Force participation open to W3C Members, Invited Experts, and Team, actively seeking consensus of all Task Force participants, but taking formal decisions by consensus of the AB<br />
* meeting bi-weekly during the AB slot on weeks the AB does not meet from now until the end of the upcoming AB membership transition<br />
* conducting meetings and publishing minutes in Member-only space to allow participants to speak more freely; but maintaining editors' drafts and issue discussion in public, [https://github.com/w3c/AB-public/issues in the AB-public GitHub repo], to allow broader input<br />
<br />
== Drafts, Repository, Issue-tracking ==<br />
<br />
* [https://github.com/w3c/AB-public/tree/main/Vision Editor’s Draft]<br />
* [https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3AVision Open Issues]<br />
<br />
== Meeting Schedule and Agenda ==<br />
<br />
* Meeting Time: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230427T14 14:00 UTC]<br />
* Meeting Coordinates: [https://www.w3.org/groups/tf/vision/calendar/ W3C Calendar], | [https://lists.w3.org/Archives/Member/chairs/2023AprJun/0028.html Member Visible] | [https://lists.w3.org/Archives/Group/group-invited-experts/2023Apr/0003.html Invited-Expert Visible]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date !! Agenda !! Minutes<br />
|-<br />
| 2023-04-27 || [[AB/VisionTF/2023-04-27|Agenda]] || [https://www.w3.org/2023/04/27-vision-minutes.html Minutes 2023-04-27]<br />
|-<br />
| 2023-05-11 || CANCELED || CANCELED<br />
|-<br />
| 2023-05-25 || [[AB/VisionTF/2023-05-25|Agenda]] || [https://www.w3.org/2023/05/25-vision-minutes.html Minutes 2023-05-25]<br />
|-<br />
| 2023-06-08 || [[AB/VisionTF/2023-06-08|Agenda]] || [https://www.w3.org/2023/06/08-vision-minutes.html Minutes 2023-06-08]<br />
|-<br />
| 2023-06-22 || [[AB/VisionTF/2023-06-22|Agenda]] || [https://www.w3.org/2023/06/22-vision-minutes.html Minutes 2023-06-22]<br />
|-<br />
| 2023-07-13 || [[AB/VisionTF/2023-07-13|Agenda]] || [https://www.w3.org/2023/07/13-vision-minutes.html Minutes 2023-07-13]<br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=AB/VisionTF&diff=116128AB/VisionTF2023-07-28T18:34:43Z<p>Amy: /* Meeting Schedule and Agenda */</p>
<hr />
<div>On 6 April 2023, the AB resolved to open a temporary Task Force (TF) to [https://github.com/w3c/AB-public/tree/main/Vision work on the Vision]:<br />
* with the ultimate goal of creating a W3C-endorsed, W3C-wide Vision statement for the organization<br />
* with the initial task of publishing an AB-consensus [https://www.w3.org/2021/Process-20211102/#WGNote NOTE] developed with the community as a first step towards that goal<br />
* with the explicit intention of working with the community in a manner yet to be determined to subsequently revise and elevate this NOTE to a [https://www.w3.org/2021/Process-20211102/#memo W3C Statement] representing a consensus Vision for W3C<br />
* with Task Force participation open to W3C Members, Invited Experts, and Team, actively seeking consensus of all Task Force participants, but taking formal decisions by consensus of the AB<br />
* meeting bi-weekly during the AB slot on weeks the AB does not meet from now until the end of the upcoming AB membership transition<br />
* conducting meetings and publishing minutes in Member-only space to allow participants to speak more freely; but maintaining editors' drafts and issue discussion in public, [https://github.com/w3c/AB-public/issues in the AB-public GitHub repo], to allow broader input<br />
<br />
== Drafts, Repository, Issue-tracking ==<br />
<br />
* [https://github.com/w3c/AB-public/tree/main/Vision Editor’s Draft]<br />
* [https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3AVision Open Issues]<br />
<br />
== Meeting Schedule and Agenda ==<br />
<br />
* Meeting Time: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230427T14 14:00 UTC]<br />
* Meeting Coordinates: [https://www.w3.org/groups/tf/vision/calendar/ W3C Calendar], | [https://lists.w3.org/Archives/Member/chairs/2023AprJun/0028.html Member Visible] | [https://lists.w3.org/Archives/Group/group-invited-experts/2023Apr/0003.html Invited-Expert Visible]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date !! Agenda !! Minutes<br />
|-<br />
| 2023-04-27 || [[AB/VisionTF/2023-04-27|Agenda]] || [https://www.w3.org/2023/04/27-vision-minutes.html Minutes 2023-04-27]<br />
|-<br />
| 2023-05-11 || CANCELED || CANCELED<br />
|-<br />
| 2023-05-25 || [[AB/VisionTF/2023-05-25|Agenda]] || [https://www.w3.org/2023/05/25-vision-minutes.html Minutes 2023-05-25]<br />
|-<br />
| 2023-06-08 || [[AB/VisionTF/2023-06-08|Agenda]] || [https://www.w3.org/2023/06/08-vision-minutes.html Minutes 2023-06-08]<br />
|-<br />
| 2023-06-22 || [[AB/VisionTF/2023-06-22|Agenda]] || [https://www.w3.org/2023/06/22-vision-minutes.html Minutes 2023-06-22]<br />
|-<br />
| 2023-07-13 || [[AB/VisionTF/2023-07-13|Agenda]] || [https://www.w3.org/2023/07/13-vision-minutes.html Minutes]<br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=AB/VisionTF&diff=116032AB/VisionTF2023-06-26T18:54:48Z<p>Amy: /* Meeting Schedule and Agenda */</p>
<hr />
<div>On 6 April 2023, the AB resolved to open a temporary Task Force (TF) to [https://github.com/w3c/AB-public/tree/main/Vision work on the Vision]:<br />
* with the ultimate goal of creating a W3C-endorsed, W3C-wide Vision statement for the organization<br />
* with the initial task of publishing an AB-consensus [https://www.w3.org/2021/Process-20211102/#WGNote NOTE] developed with the community as a first step towards that goal<br />
* with the explicit intention of working with the community in a manner yet to be determined to subsequently revise and elevate this NOTE to a [https://www.w3.org/2021/Process-20211102/#memo W3C Statement] representing a consensus Vision for W3C<br />
* with Task Force participation open to W3C Members, Invited Experts, and Team, actively seeking consensus of all Task Force participants, but taking formal decisions by consensus of the AB<br />
* meeting bi-weekly during the AB slot on weeks the AB does not meet from now until the end of the upcoming AB membership transition<br />
* conducting meetings and publishing minutes in Member-only space to allow participants to speak more freely; but maintaining editors' drafts and issue discussion in public, [https://github.com/w3c/AB-public/issues in the AB-public GitHub repo], to allow broader input<br />
<br />
== Drafts, Repository, Issue-tracking ==<br />
<br />
* [https://github.com/w3c/AB-public/tree/main/Vision Editor’s Draft]<br />
* [https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3AVision Open Issues]<br />
<br />
== Meeting Schedule and Agenda ==<br />
<br />
* Meeting Time: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230427T14 14:00 UTC]<br />
* Meeting Coordinates: [https://www.w3.org/groups/tf/vision/calendar/ W3C Calendar], | [https://lists.w3.org/Archives/Member/chairs/2023AprJun/0028.html Member Visible] | [https://lists.w3.org/Archives/Group/group-invited-experts/2023Apr/0003.html Invited-Expert Visible]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date !! Agenda !! Minutes<br />
|-<br />
| 2023-04-27 || [[AB/VisionTF/2023-04-27|Agenda]] || [https://www.w3.org/2023/04/27-vision-minutes.html Minutes 2023-04-27]<br />
|-<br />
| 2023-05-11 || CANCELED || CANCELED<br />
|-<br />
| 2023-05-25 || [[AB/VisionTF/2023-05-25|Agenda]] || [https://www.w3.org/2023/05/25-vision-minutes.html Minutes 2023-05-25]<br />
|-<br />
| 2023-06-08 || [[AB/VisionTF/2023-06-08|Agenda]] || [https://www.w3.org/2023/06/08-vision-minutes.html Minutes 2023-06-08]<br />
|-<br />
| 2023-06-22 || [[AB/VisionTF/2023-06-22|Agenda]] || Minutes<br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=AB/VisionTF&diff=115980AB/VisionTF2023-06-09T14:19:55Z<p>Amy: /* Meeting Schedule and Agenda */</p>
<hr />
<div>On 6 April 2023, the AB resolved to open a temporary Task Force (TF) to [https://github.com/w3c/AB-public/tree/main/Vision work on the Vision]:<br />
* with the ultimate goal of creating a W3C-endorsed, W3C-wide Vision statement for the organization<br />
* with the initial task of publishing an AB-consensus [https://www.w3.org/2021/Process-20211102/#WGNote NOTE] developed with the community as a first step towards that goal<br />
* with the explicit intention of working with the community in a manner yet to be determined to subsequently revise and elevate this NOTE to a [https://www.w3.org/2021/Process-20211102/#memo W3C Statement] representing a consensus Vision for W3C<br />
* with Task Force participation open to W3C Members, Invited Experts, and Team, actively seeking consensus of all Task Force participants, but taking formal decisions by consensus of the AB<br />
* meeting bi-weekly during the AB slot on weeks the AB does not meet from now until the end of the upcoming AB membership transition<br />
* conducting meetings and publishing minutes in Member-only space to allow participants to speak more freely; but maintaining editors' drafts and issue discussion in public, [https://github.com/w3c/AB-public/issues in the AB-public GitHub repo], to allow broader input<br />
<br />
== Drafts, Repository, Issue-tracking ==<br />
<br />
* [https://github.com/w3c/AB-public/tree/main/Vision Editor’s Draft]<br />
* [https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3AVision Open Issues]<br />
<br />
== Meeting Schedule and Agenda ==<br />
<br />
* Meeting Time: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230427T14 14:00 UTC]<br />
* Meeting Coordinates: [https://www.w3.org/events/meetings/bc8714a0-1ade-4a5c-b4cd-c7fa3a1fe80c/20230427T100000 W3C Calendar Event] | [https://lists.w3.org/Archives/Member/chairs/2023AprJun/0028.html Member Visible] | [https://lists.w3.org/Archives/Group/group-invited-experts/2023Apr/0003.html Invited-Expert Visible]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date !! Agenda !! Minutes<br />
|-<br />
| 2023-04-27 || [[AB/VisionTF/2023-04-27|Agenda]] || [https://www.w3.org/2023/04/27-vision-minutes.html Minutes 2023-04-27]<br />
|-<br />
| 2023-05-11 || CANCELED || CANCELED<br />
|-<br />
| 2023-05-25 || [[AB/VisionTF/2023-05-25|Agenda]] || [https://www.w3.org/2023/05/25-vision-minutes.html Minutes 2023-05-25]<br />
|-<br />
| 2023-06-08 || [[AB/VisionTF/2023-06-08|Agenda]] || Minutes<br />
|-<br />
| 2023-06-22 || [[AB/VisionTF/2023-06-22|Agenda]] || Minutes<br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=AB/VisionTF&diff=115979AB/VisionTF2023-06-09T14:19:39Z<p>Amy: /* Meeting Schedule and Agenda */</p>
<hr />
<div>On 6 April 2023, the AB resolved to open a temporary Task Force (TF) to [https://github.com/w3c/AB-public/tree/main/Vision work on the Vision]:<br />
* with the ultimate goal of creating a W3C-endorsed, W3C-wide Vision statement for the organization<br />
* with the initial task of publishing an AB-consensus [https://www.w3.org/2021/Process-20211102/#WGNote NOTE] developed with the community as a first step towards that goal<br />
* with the explicit intention of working with the community in a manner yet to be determined to subsequently revise and elevate this NOTE to a [https://www.w3.org/2021/Process-20211102/#memo W3C Statement] representing a consensus Vision for W3C<br />
* with Task Force participation open to W3C Members, Invited Experts, and Team, actively seeking consensus of all Task Force participants, but taking formal decisions by consensus of the AB<br />
* meeting bi-weekly during the AB slot on weeks the AB does not meet from now until the end of the upcoming AB membership transition<br />
* conducting meetings and publishing minutes in Member-only space to allow participants to speak more freely; but maintaining editors' drafts and issue discussion in public, [https://github.com/w3c/AB-public/issues in the AB-public GitHub repo], to allow broader input<br />
<br />
== Drafts, Repository, Issue-tracking ==<br />
<br />
* [https://github.com/w3c/AB-public/tree/main/Vision Editor’s Draft]<br />
* [https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3AVision Open Issues]<br />
<br />
== Meeting Schedule and Agenda ==<br />
<br />
* Meeting Time: [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230427T14 14:00 UTC]<br />
* Meeting Coordinates: [https://www.w3.org/events/meetings/bc8714a0-1ade-4a5c-b4cd-c7fa3a1fe80c/20230427T100000 W3C Calendar Event] | [https://lists.w3.org/Archives/Member/chairs/2023AprJun/0028.html Member Visible] | [https://lists.w3.org/Archives/Group/group-invited-experts/2023Apr/0003.html Invited-Expert Visible]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date !! Agenda !! Minutes<br />
|-<br />
| 2023-04-27 || [[AB/VisionTF/2023-04-27|Agenda]] || [https://www.w3.org/2023/04/27-vision-minutes.html Minutes 2023-04-27]<br />
|-<br />
| 2023-05-11 || CANCELED || CANCELED<br />
|-<br />
| 2023-05-25 || [[AB/VisionTF/2023-05-25|Agenda]] || https://www.w3.org/2023/05/25-vision-minutes.html Minutes 2023-05-25]<br />
|-<br />
| 2023-06-08 || [[AB/VisionTF/2023-06-08|Agenda]] || Minutes<br />
|-<br />
| 2023-06-22 || [[AB/VisionTF/2023-06-22|Agenda]] || Minutes<br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105853WG Best Practices2018-02-15T13:25:18Z<p>Amy: /* Charing and attending Group Meetings */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== Disciplinary actions ==<br />
Where a group member is considered to have failed to meet the requirements of the Code of Ethics and Professional Conduct (CEPC), Chairs and Team, may @@under consultation with W3M or an Ombudsperson@@ give warnings and/or institute temporary or more permanent bans. See: [https://www.w3.org/2002/09/discipline Disciplinary Actions]. <br />
<br />
See also the [https://www.w3.org/Consortium/pwe/#Procedures Procedures section] of the CoC. There is a list of Ombudspersons with whom issues can be raised if talking with the Chair or Team contact is not possible or preferred. <br />
<br />
Finally, under the [https://www.w3.org/2017/11/Process-20171102-diff#ParticipationCriteria W3C Process Document, (3.1 Individual Participation Criteria)] It is now required that participants in any W3C activity must abide by the terms and spirit of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct] [ PUB38 ]. “The Director may suspend or remove for cause a participant in any group (including the AB and TAG), where cause includes failure to meet the requirements of this process, the membership agreement, or applicable laws.<br />
<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C [https://www.w3.org/Consortium/cepc/Code of Ethics and Professional Conduct]. Under the CoC members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br/><br />
• Never harass or bully anyone verbally, physically or sexually.<br/><br />
• Never discriminate on the basis of personal characteristics or group membership.<br/><br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br/><br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br/><br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br/><br />
• Respect the privacy of others and the confidentiality of data you access.<br/><br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br/><br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105852WG Best Practices2018-02-15T13:25:01Z<p>Amy: /* Charing and attending Group Meetings */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== Disciplinary actions ==<br />
Where a group member is considered to have failed to meet the requirements of the Code of Ethics and Professional Conduct (CEPC), Chairs and Team, may @@under consultation with W3M or an Ombudsperson@@ give warnings and/or institute temporary or more permanent bans. See: [https://www.w3.org/2002/09/discipline Disciplinary Actions]. <br />
<br />
See also the [https://www.w3.org/Consortium/pwe/#Procedures Procedures section] of the CoC. There is a list of Ombudspersons with whom issues can be raised if talking with the Chair or Team contact is not possible or preferred. <br />
<br />
Finally, under the [https://www.w3.org/2017/11/Process-20171102-diff#ParticipationCriteria W3C Process Document, (3.1 Individual Participation Criteria)] It is now required that participants in any W3C activity must abide by the terms and spirit of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct] [ PUB38 ]. “The Director may suspend or remove for cause a participant in any group (including the AB and TAG), where cause includes failure to meet the requirements of this process, the membership agreement, or applicable laws.<br />
<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C [https://www.w3.org/Consortium/cepc/Code of Ethics and Professional Conduct]. Under the CoC members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br/><br />
• Never harass or bully anyone verbally, physically or sexually.<br/><br />
• Never discriminate on the basis of personal characteristics or group membership.<br/><br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br/><br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br/><br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br/><br />
• Respect the privacy of others and the confidentiality of data you access.<br/><br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br/><br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105378WG Best Practices2017-12-11T20:07:15Z<p>Amy: /* Code of Conduct: */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct. Under the CoC members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br/><br />
• Never harass or bully anyone verbally, physically or sexually.<br/><br />
• Never discriminate on the basis of personal characteristics or group membership.<br/><br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br/><br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br/><br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br/><br />
• Respect the privacy of others and the confidentiality of data you access.<br/><br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br/><br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== Disciplinary actions ==<br />
Where a group member is considered to have failed to meet the requirements of the Code of Ethics and Professional Conduct (CEPC), Chairs and Team, may @@under consultation with W3M or an Ombudsperson@@ give warnings and/or institute temporary or more permanent bans. See: [https://www.w3.org/2002/09/discipline Disciplinary Actions]. <br />
<br />
See also the [https://www.w3.org/Consortium/pwe/#Procedures Procedures section] of the CoC. There is a list of Ombudspersons with whom issues can be raised if talking with the Chair or Team contact is not possible or preferred. <br />
<br />
Finally, under the [https://www.w3.org/2017/11/Process-20171102-diff#ParticipationCriteria W3C Process Document, (3.1 Individual Participation Criteria)] It is now required that participants in any W3C activity must abide by the terms and spirit of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct] [ PUB38 ]. “The Director may suspend or remove for cause a participant in any group (including the AB and TAG), where cause includes failure to meet the requirements of this process, the membership agreement, or applicable laws.</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105005WG Best Practices2017-11-07T15:40:49Z<p>Amy: /* Disciplinary actions */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct @add link@be..Members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br />
• Never harass or bully anyone verbally, physically or sexually.<br />
• Never discriminate on the basis of personal characteristics or group membership.<br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br />
• Respect the privacy of others and the confidentiality of data you access.<br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== Disciplinary actions ==<br />
Where a group member is considered to have failed to meet the requirements of the Code of Ethics and Professional Conduct (CEPC), Chairs and Team, may @@under consultation with W3M or an Ombudsperson@@ give warnings and/or institute temporary or more permanent bans. See: [https://www.w3.org/2002/09/discipline Disciplinary Actions]. <br />
<br />
See also the [https://www.w3.org/Consortium/pwe/#Procedures Procedures section] of the CoC. There is a list of Ombudspersons with whom issues can be raised if talking with the Chair or Team contact is not possible or preferred. <br />
<br />
Finally, under the [https://www.w3.org/2017/11/Process-20171102-diff#ParticipationCriteria W3C Process Document, (3.1 Individual Participation Criteria)] It is now required that participants in any W3C activity must abide by the terms and spirit of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct] [ PUB38 ]. “The Director may suspend or remove for cause a participant in any group (including the AB and TAG), where cause includes failure to meet the requirements of this process, the membership agreement, or applicable laws.</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105004WG Best Practices2017-11-07T15:31:58Z<p>Amy: /* Disciplinary actions */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct @add link@be..Members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br />
• Never harass or bully anyone verbally, physically or sexually.<br />
• Never discriminate on the basis of personal characteristics or group membership.<br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br />
• Respect the privacy of others and the confidentiality of data you access.<br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== Disciplinary actions ==<br />
Where a group member is considered to have failed to meet the requirements of the Code of Ethics and Professional Conduct (CEPC), Chairs and Team, may @@under consultation with W3M or an Ombudsperson@@ give warnings @and/or institute temporary or more permanent bans@. See: Disciplinary Actions @add link from PLH@. <br />
<br />
See also the [https://www.w3.org/Consortium/pwe/#Procedures Procedures section] of the CoC. There is a list of Ombudspersons with whom issues can be raised if talking with the Chair or Team contact is not possible or preferred. <br />
<br />
Finally, under the W3C Process Document, (3.1 Individual Participation Criteria) It is now required that participants in any W3C activity must abide by the terms and spirit of the W3C Code of Ethics and Professional Conduct [ PUB38 ]. “The Director may suspend or remove for cause a participant in any group (including the AB and TAG), where cause includes failure to meet the requirements of this process, the membership agreement, or applicable laws. @ink: https://www.w3.org/2017/11/Process-20171102-diff#ParticipationCriteriaf https://www.w3.org/Consortium/cepc/ @</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105003WG Best Practices2017-11-07T15:31:18Z<p>Amy: </p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct @add link@be..Members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br />
• Never harass or bully anyone verbally, physically or sexually.<br />
• Never discriminate on the basis of personal characteristics or group membership.<br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br />
• Respect the privacy of others and the confidentiality of data you access.<br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== Disciplinary actions ==<br />
Where a group member is considered to have failed to meet the requirements of the Code of Ethics and Professional Conduct (CEPC), Chairs and Team, may @@under consultation with W3M or an Ombudsperson@@ give warnings @and/or institute temporary or more permanent bans@. See: Disciplinary Actions @add link from PLH@. <br />
<br />
See also the Procedures section of the CoC. There is a list of Ombudspersons with whom issues can be raised if talking with the Chair or Team contact is not possible or preferred. <br />
<br />
Finally, under the W3C Process Document, (3.1 Individual Participation Criteria) It is now required that participants in any W3C activity must abide by the terms and spirit of the W3C Code of Ethics and Professional Conduct [ PUB38 ]. “The Director may suspend or remove for cause a participant in any group (including the AB and TAG), where cause includes failure to meet the requirements of this process, the membership agreement, or applicable laws. @ink: https://www.w3.org/2017/11/Process-20171102-diff#ParticipationCriteriaf https://www.w3.org/Consortium/cepc/ @</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105002WG Best Practices2017-11-07T15:28:23Z<p>Amy: /* Code of Conduct: */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct @add link@be..Members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br />
• Never harass or bully anyone verbally, physically or sexually.<br />
• Never discriminate on the basis of personal characteristics or group membership.<br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br />
• Respect the privacy of others and the confidentiality of data you access.<br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105001WG Best Practices2017-11-07T15:28:07Z<p>Amy: /* Code of Conduct: */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct @add link@be..Members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br />
• Never harass or bully anyone verbally, physically or sexually.<br />
• Never discriminate on the basis of personal characteristics or group membership.<br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br />
• Respect the privacy of others and the confidentiality of data you access.<br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting<br />
disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=105000WG Best Practices2017-11-07T15:26:45Z<p>Amy: /* Charing and attending Group Meetings */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
== Code of Conduct: ==<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct @add link@be..Members of the W3C community must: :<br />
<br />
• Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.<br />
• Never harass or bully anyone verbally, physically or sexually.<br />
• Never discriminate on the basis of personal characteristics or group membership.<br />
• Communicate constructively and avoid demeaning or insulting behavior or language.<br />
• Seek, accept, and offer objective work criticism, and acknowledge properly the contributions of others.<br />
• Be honest about your own qualifications, and about any circumstances that might lead to conflicts of interest.<br />
• Respect the privacy of others and the confidentiality of data you access.<br />
• With respect to cultural differences, be conservative in what you do and liberal in what you accept from others, but not to the point of accepting<br />
disrespectful, unprofessional or unfair or unwelcome behavior or advances.<br />
• Promote the rules of this Code and take action (especially if you are in a leadership position) to bring the discussion back to a more civil level whenever inappropriate behaviors are observed..<br />
<br />
Chairs and Team contacts should be sure to actively demonstrate the W3C Code of Conduct in their own behavior and encourage such behavior within their Groups. If there are problems in a group, the Chairs, Team contact should work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems<br />
<br />
== Best Practices ==<br />
W3C Chairs, Team and group members should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). Remember that the W3C is a community of experts from many different fields who have valuable contributions to make.<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand what you re saying and don't suggest that another person's comments are invalid because they have a different opinion).<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information). Do review the work of other groups to see if you are doing something which other groups have already done (i“reinventing the wheel”).<br />
* Do assess feedback provided by others to determine if it improves your proposals.<br />
* Do consult with someone else in the group if you feel your message is not being understood. Another person might be able to explain things differently and help get your message across successfully.<br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes and don’t assume that your disagreement means the work of the whole group must change or stop).<br />
* Know that your contribution is still valuable even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and you must remember allow the space for other members to participate (e.g.: don't respond to every email in a thread/every GitHub comment. Don't put yourself on the queue every time someone speaks). <br />
* Do contact your Chair, Team contact, AC rep, a PWETF member, or a W3C Ombudsperson if you feel someone has been working in way that is having a negative impact on the work of the group or if they are insulting, harassing you or unfairly impeding your own ability to work. <br />
<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=104999WG Best Practices2017-11-07T15:24:22Z<p>Amy: </p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/ members indicating that it would be useful to have a document for best practices for participating in Working Interest/Business/Community Groups and to ensure the group is inline with the W3C Code of Conduct.<br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). The W3C and WG are full of experts from many fields who have valuable contributions to make to the whole<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand you and don't suggest that another person's comments are invalid). <br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes).<br />
* Know your contribution is still valued even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and to allow the space for other members to participate and prioritize your own contributions. (e.g.: don't respond to every email in a thread/GitHub comment and don't put yourself on the queue every time someone speaks). Do review the work of other groups to see if you are reinventing the wheel.<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information)<br />
* do comment on technical issues on GitHub. The goal is to close issues. Groups don't like to publish without closing all issues.<br />
* do ask broad questions about theory and meta-issues on the email list.<br />
* do assess feedback provided by others to determine if it improves your proposals.<br />
* do consult with a friend in the group if you feel your message is not being understood. Another person might be able to explain things differently and get your message across successfully.<br />
* do contact your chair, team contact, AC rep, PWETF member, or Ombudsperson if someone in a W3C meeting makes you uncomfortable<br />
<br />
Code of Conduct<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct.<br />
<br />
Doing so means that our community:<br />
<br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication.<br />
* Avoids a dismissive attitude and behavior about others' technical opinions with which one does not agree. This can be a form of bullying which is unacceptable.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively.<br />
* Seeks, accepts, and offers objective criticism - and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional, unfair, or unwelcome behavior or advances.<br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Accepts (especially those in a leadership position) responsibility to take action whenever disrespectful or inappropriate behaviors are observed and to act to bring a discussion back to a more civil level.<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=104998WG Best Practices2017-11-07T15:22:53Z<p>Amy: /* Charing and attending Group Meetings */</p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/CG/BG members indicating that it would be useful to have a document for best practices for participating in Working Groups. This document can be considered related to Best Practices to make F2F meetings more welcoming. <br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). The W3C and WG are full of experts from many fields who have valuable contributions to make to the whole<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand you and don't suggest that another person's comments are invalid). <br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes).<br />
* Know your contribution is still valued even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and to allow the space for other members to participate and prioritize your own contributions. (e.g.: don't respond to every email in a thread/GitHub comment and don't put yourself on the queue every time someone speaks). Do review the work of other groups to see if you are reinventing the wheel.<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information)<br />
* do comment on technical issues on GitHub. The goal is to close issues. Groups don't like to publish without closing all issues.<br />
* do ask broad questions about theory and meta-issues on the email list.<br />
* do assess feedback provided by others to determine if it improves your proposals.<br />
* do consult with a friend in the group if you feel your message is not being understood. Another person might be able to explain things differently and get your message across successfully.<br />
* do contact your chair, team contact, AC rep, PWETF member, or Ombudsperson if someone in a W3C meeting makes you uncomfortable<br />
<br />
Code of Conduct[edit]<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct.<br />
<br />
Doing so means that our community:<br />
<br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication.<br />
* Avoids a dismissive attitude and behavior about others' technical opinions with which one does not agree. This can be a form of bullying which is unacceptable.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively.<br />
* Seeks, accepts, and offers objective criticism - and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional, unfair, or unwelcome behavior or advances.<br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Accepts (especially those in a leadership position) responsibility to take action whenever disrespectful or inappropriate behaviors are observed and to act to bring a discussion back to a more civil level.<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE&diff=104997PWE2017-11-07T15:22:27Z<p>Amy: /* Best Practices */</p>
<hr />
<div>== Positive Work Environment ==<br />
Public wiki regarding Positive Work Environment at W3C.<br />
<br />
== W3C Codes of Conduct ==<br />
The [https://www.w3.org/Consortium/pwe/ Positive Work Environment Task Force] owns:<br />
<br />
* the [https://www.w3.org/Consortium/cepc/ Code of Ethics and Professional Conduct (CEPC)]<br />
<br />
* the draft [https://www.w3.org/wiki/PWE/Conf-code Conference code]<br />
<br />
* the [https://www.w3.org/Consortium/pwe/#Procedures Procedures] for implementing these codes<br />
<br />
== Best Practices ==<br />
<br />
A collection of Best Practices pages for meetings, speakers and public events<br />
<br />
* [https://www.w3.org/wiki/Speaker_Resources#Speakers_Guidelines Speaker Guidelines from Coralie]<br />
<br />
* [https://www.w3.org/wiki/Global_Topic Thoughts about making W3C more global developed by an Advisory Board task force (Judy Zhu, Jay Kishigami, others?)]<br />
<br />
* [https://www.w3.org/wiki/Moderating_Meetings Moderating Meetings] by AB (by Chaals)<br />
<br />
* [[Meetings Best Practices document]] for meetings <br />
<br />
* [https://www.w3.org/wiki/WG_Best_Practices WG Best Practices] (to be edited and adjusted for TPAC 2017<br />
<br />
* [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== PWETF discussion(s) notes ==<br />
This section will be for collecting PWETF notes and discussions<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_AC notes from BOF session at AC meeting, MIT, March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_badges ideas for name badges March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201609_TPAC Breakout Session from TPAC 2016]<br />
<br />
== Outline for renewing Task Force, reviewing goals, vision, documents, and next steps ==<br />
<br />
From May 2016: [https://www.w3.org/wiki/PWE/201604_outline ideas for renewing Task Force, reviewing goals, vision, documents, and next steps ]<br />
<br />
== Upcoming ==<br />
* [[PWE/Upcoming]]</div>Amyhttps://www.w3.org/wiki/index.php?title=MeetingTaxis&diff=104963MeetingTaxis2017-11-04T22:26:42Z<p>Amy: /* Coordination tables */</p>
<hr />
<div>[[Category:EswMeetings]]<br />
<br />
Use this '''Public''' page to help coordinate the sharing of taxis, shuttles, etc. for meetings.<br />
<br />
= Meeting: TPAC 2017, Burlingame =<br />
<br />
Are you looking for the [https://www.w3.org/wiki/TPAC2017warmup TPAC 2017 "Warmup" wiki]? <br />
<br />
== Hyatt Regency Shuttle ==<br />
For those who will be staying at the Hyatt Regency, Burlingame, the hotel offers a 24 hour shuttle service:<br />
<br />
<blockquote><br />
Our hotel’s complimentary shuttle runs every 10-15 minutes. From SFO, take your luggage to the Departures Level center island and look for the area marked "Hotel Shuttle." The shuttle bus is marked "Hyatt Regency and Marriott.” For arrivals and departures between 12:00 a.m. and 4:46 a.m., free shuttles pick up guests every 30 minutes.<br />
</blockquote><br />
<br />
The shuttle has an [https://ips-systems.com/Sentry/Anon/40 online tracker service] for those who can get online at the airport.<br />
<br />
== Taxi ==<br />
''Make sure the taxi meter is in use.''<br/><br />
''REMINDER: Please, put entries in chronological order.''<br />
<br />
== Coordination tables ==<br />
'''ARRIVALS'''<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-04 || 10:49 || SFO || JetBlue 0133 || Hyatt || [[User:amy|Amy van der Hiel]] ([[User talk:amy|talk]]) || amy@w3.org || Traveling with Susan Westhaver<br />
|-<br />
| Nov-04 || 17:20 || SFO || LX0038 || Hyatt || [[User:Coralie|Coralie Mercier]] ([[User talk:Coralie|talk]]) || coralie@w3.org || Traveling with Alexandra Lacourba<br />
|-<br />
| Nov-05 || 12:25 || SFO || KL605 || Hyatt || Ivan Herman || ivan@w3.org || <br />
|-<br />
| || || || || || || || ;<br />
|-<br />
|}<br />
<br />
'''DEPARTURES'''<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-10 || 21:25 || SFO || LH0459 || Hyatt || [[User:Coralie|Coralie Mercier]] ([[User talk:Coralie|talk]]) || coralie@w3.org || <br />
|-<br />
<br />
| Nov-11|| 07:40 || SFO || JetBlue 0434 ||Hyatt ||[[User:amy|Amy van der Hiel]] ([[User talk:amy|talk]]) || amy@w3.org || traveling with Susan Westhaver<br />
|-<br />
| Nov-11 || 14:35 || SFO || KL606 || Hyatt || Ivan Herman || ivan@w3.org || <br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ; <br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|- <br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=MeetingTaxis&diff=104962MeetingTaxis2017-11-04T21:25:35Z<p>Amy: /* Coordination tables */</p>
<hr />
<div>[[Category:EswMeetings]]<br />
<br />
Use this '''Public''' page to help coordinate the sharing of taxis, shuttles, etc. for meetings.<br />
<br />
= Meeting: TPAC 2017, Burlingame =<br />
<br />
Are you looking for the [https://www.w3.org/wiki/TPAC2017warmup TPAC 2017 "Warmup" wiki]? <br />
<br />
== Hyatt Regency Shuttle ==<br />
For those who will be staying at the Hyatt Regency, Burlingame, the hotel offers a 24 hour shuttle service:<br />
<br />
<blockquote><br />
Our hotel’s complimentary shuttle runs every 10-15 minutes. From SFO, take your luggage to the Departures Level center island and look for the area marked "Hotel Shuttle." The shuttle bus is marked "Hyatt Regency and Marriott.” For arrivals and departures between 12:00 a.m. and 4:46 a.m., free shuttles pick up guests every 30 minutes.<br />
</blockquote><br />
<br />
The shuttle has an [https://ips-systems.com/Sentry/Anon/40 online tracker service] for those who can get online at the airport.<br />
<br />
== Taxi ==<br />
''Make sure the taxi meter is in use.''<br/><br />
''REMINDER: Please, put entries in chronological order.''<br />
<br />
== Coordination tables ==<br />
'''ARRIVALS'''<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-04 || 10:49 || SFO || JetBlue 0133 || Hyatt || [[User:amy|Amy van der Hiel]] ([[User talk:amy|talk]]) || amy@w3.org || Traveling with Susan Westhaver<br />
|-<br />
| Nov-04 || 17:20 || SFO || LX0038 || Hyatt || [[User:Coralie|Coralie Mercier]] ([[User talk:Coralie|talk]]) || coralie@w3.org || Traveling with Alexandra Lacourba<br />
|-<br />
| Nov-05 || 12:25 || SFO || KL605 || Hyatt || Ivan Herman || ivan@w3.org || <br />
|-<br />
| || || || || || || || ;<br />
|-<br />
|}<br />
<br />
'''DEPARTURES'''<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-10 || 21:25 || SFO || LH0459 || Hyatt || [[User:Coralie|Coralie Mercier]] ([[User talk:Coralie|talk]]) || coralie@w3.org || <br />
|-<br />
<br />
| Nov-11|| 07:40 || SFO || JetBlue 0434 ||[[User:amy|Amy van der Hiel]] ([[User talk:amy|talk]]) || amy@w3.org || traveling with Susan Westhaver|| ;<br />
|-<br />
| Nov-11 || 14:35 || SFO || KL606 || Hyatt || Ivan Herman || ivan@w3.org || <br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ; <br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|-<br />
| || || || || || || || ;<br />
|- <br />
|}</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=104790WG Best Practices2017-10-19T23:36:45Z<p>Amy: </p>
<hr />
<div><br />
This document was created in response to W3C WG/IG/CG/BG members indicating that it would be useful to have a document for best practices for participating in Working Groups. This document can be considered related to Best Practices to make F2F meetings more welcoming. <br />
<br />
= Charing and attending Group Meetings = <br />
W3C Chairs, Team and group member should:<br />
<br />
* Respect the expertise and contributions of other members of the group (e.g.: don't assume that you are "the smartest person in the room"). The W3C and WG are full of experts from many fields who have valuable contributions to make to the whole<br />
* Listen first and be sure you understand the point of view of the other person (e.g.: don't assume that others are disagreeing with you because they don't understand you and don't suggest that another person's comments are invalid). <br />
* Understand that consensus does not mean unanimity (e.g.: don't assume that your proposal, code sample, or implementation will be adopted without changes).<br />
* Know your contribution is still valued even if it is not integrated (e.g.: don't get upset if something you worked on is not implemented). Your work may be picked up in the future.<br />
* Remember the work is about more than just your area of interest (e.g.: don't let your personal or professional goals impede the progress of the group).<br />
* Remember others voices need to be heard as well as yours and to allow the space for other members to participate and prioritize your own contributions. (e.g.: don't respond to every email in a thread/GitHub comment and don't put yourself on the queue every time someone speaks). Do review the work of other groups to see if you are reinventing the wheel.<br />
* Respond from an informed and inclusive point of view (e.g.: don't respond to comments without reading the background information)<br />
* do comment on technical issues on GitHub. The goal is to close issues. Groups don't like to publish without closing all issues.<br />
* do ask broad questions about theory and meta-issues on the email list.<br />
* do assess feedback provided by others to determine if it improves your proposals.<br />
* do consult with a friend in the group if you feel your message is not being understood. Another person might be able to explain things differently and get your message across <br />
successfully.<br />
* do contact your chair, team contact, AC rep, PWETF member, or Ombudsperson if someone in a W3C meeting makes you uncomfortable<br />
<br />
Code of Conduct[edit]<br />
All W3C Meetings are run under the rules of the W3C Code of Ethics and Professional Conduct.<br />
<br />
Doing so means that our community:<br />
<br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication.<br />
* Avoids a dismissive attitude and behavior about others' technical opinions with which one does not agree. This can be a form of bullying which is unacceptable.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively.<br />
* Seeks, accepts, and offers objective criticism - and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional, unfair, or unwelcome behavior or advances.<br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Accepts (especially those in a leadership position) responsibility to take action whenever disrespectful or inappropriate behaviors are observed and to act to bring a discussion back to a more civil level.<br />
<br />
The Chair and Team contact should use these Best Practices and the W3C Code of Conduct as a guide for the kinds of behavior ot mirror and encourage in the Group. If there are interpersonal problems in a group, the Chairs, Team contact can to work toward resolution. The Chair and Team contact should be able to set guidelines for suggested behaviors and clear boundaries and warnings for any consistent problems. [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=104704WG Best Practices2017-10-12T18:31:41Z<p>Amy: /* Dos for orking positively in a WG */</p>
<hr />
<div>= a list of do’s and don’t for WG Best Practicess=<br />
based on an outline from Tzviya Siegman <br />
<br />
also possibly at add suggestions for process if there are problems in a WG<br />
see [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== Don’ts for working in a positively in a WG==<br />
* don't assume that you are the smartest person in the room<br />
The W3C and WG are full of experts from many fields who have valuable contributions to make to the whole<br />
* don't assume that others are disagreeing with you because they don't understand you and don't point out that another person's comments are incorrect or invalid<br />
Listen first and be sure you understand the point of view of the other person<br />
* don't assume that your proposal, code sample, or implementation will be adopted without changes and <br />
Consensus does not mean unanimity<br />
* don't get upset if something you worked on is not implemented. <br />
Your contribution is still valued and may be picked up in the future.<br />
* don't let your personal or professional goals impede the progress of the group<br />
The work is about more than just your area of interest<br />
* don't respond to comments without reading the background information<br />
* don't respond to every comment on a GitHub issue / don't respond to every email in a thread and don't put yourself on the queue every time someone speaks<br />
Overwhelm or being relentless is not helpful<br />
Others voices need to be heard as well<br />
<br />
<br />
<br />
== Dos for working positively in a WG ==<br />
* do comment on technical issues on GitHub. The goal is to close issues. We don’t like to publish without closing all issues.<br />
* do ask broad questions about theory and meta-issues on the email list<br />
* do contact your chair, team contact, ac rep, PWETF member, if someone in a W3C meeting makes you uncomfortable<br />
* do review the work of other groups to see if you are reinventing the wheel (is this idiom international?)<br />
* do assess feedback provided by others to determine if it improves your proposals<br />
* do consider not hitting send – save as a draft and reconsider after a few minutes or hours<br />
* do consult with a friend in the group if you feel your message is not being understood. Another person might be able to explain things differently and get your message across successfully.</div>Amyhttps://www.w3.org/wiki/index.php?title=TPAC/2017/SessionIdeas&diff=104621TPAC/2017/SessionIdeas2017-10-06T14:18:09Z<p>Amy: /* Proposed sessions */</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC/2017]] Wednesday '''Technical Plenary Day''' [http://www.w3.org/2017/11/TPAC/#breakouts Breakout sessions] in advance of the meeting. <br />
<br />
<span style="color:#ff0000">'''The sessions that will make it will be in the [[TPAC/2017#Session_Grid | Session Grid]], as well as minutes and summaries'''</span><br />
<br />
See the [[TPAC/2017/FAQ | TPAC 2017 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 (it's a good idea to let them know ahead of time)<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 (yourself, if so sign using 4 tildas; optional: name a desired session leader)<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 />
== From an idea to a breakout ==<br />
<br />
Breakout preparation (also known as the 'mad scramble') takes place Wednesday 8 November at 09:00-10:00.<br />
<br />
<span style="color:#ff0000">The sessions that will make it will be in the [[TPAC/2017#Session_Grid | Session Grid]], as well as minutes and summaries</span><br />
<br />
== Proposed sessions ==<br />
<br />
=== EXAMPLE session ===<br />
* Proposer: <br />
* Summary: <br />
* Type of session: <br />
* Goals:<br />
<br />
=== Device APIs session ===<br />
* Proposer: [[User:Vscheib|Vincent Scheib]] ([[User talk:Vscheib|talk]]) 19:48, 11 September 2017 (UTC)<br />
* Summary: Discussion of device APIs such as [https://w3c.github.io/sensors/ Generic Sensors], [https://github.com/WebBluetoothCG/web-bluetooth Web Bluetooth], [https://w3c.github.io/web-nfc/ Web NFC], [https://github.com/WICG/webusb WebUSB] and future work e.g. [https://github.com/w3c/sensors/projects/5 Level 2] features for Generic Sensors, including sensor discovery.<br />
* Goals: Discuss current implementation & specification status, meet related participants, and discuss future concepts that may apply to the [https://www.w3.org/2016/03/device-sensors-wg-charter.html Device and Sensors Working Group mission].<br />
<br />
=== Spatial Data on the Web Interest Group session ===<br />
* Proposer: Linda van den Brink<br />
* Summary: Discussion of the scope and initial priorities for the newly created [https://www.w3.org/2017/sdwig/ Spatial Data on the Web Interest Group]<br />
* Type of session: <br />
* Goals: The mission of the Spatial Data on the Web Interest Group is to develop and maintain vocabularies and best practices that encourage better sharing of spatial data on the Web; and identify areas where standards should be developed jointly by both W3C and the Open Geospatial Consortium (OGC). The Spatial Data on the Web Interest Group is a W3C entity matched by a sub-committee of OGC's Technical Committee. Collectively, the two comprise the Joint W3C/OGC Organizing Committee, the JWOC. The Interest Group follows the footsteps of the eponimous [https://www.w3.org/2015/spatial/wiki/Main_Page#Deliverables Spatial Data on the Web Working Group] that developed [https://www.w3.org/TR/sdw-bp/ Spatial Data on the Web Best Practices], the [https://www.w3.org/TR/owl-time Time Ontology in OWL], the [https://www.w3.org/TR/vocab-ssn Semantic Sensor Network Ontology] and a few other deliverables. The goal of this session is to present the Interest Group, and to gather feedback from interested parties about initial priorities for the group.<br />
<br />
=== Technical demo session ===<br />
* Proposer: Dominique Hazael-Massieux<br />
* Summary: Demos from various groups illustrating ongoing work in W3C<br />
* Type of session: Demos<br />
* Goals: An opportunity to discover what other W3C groups are working on and how that works intersect with other Web technologies. This session will be scheduled during the last breakout slot of the day.<br />
<br />
Demos include:<br />
==== Generic Sensors ====<br />
Generic Sensor API exposes sensor data to the Web in a consistent and performant manner and enables a broad range of immersive and interactive experiences on the Web:<br />
<br />
* pure web 360: high performance 360 degree panoramas and 360 videos<br />
* sensor fusion: fuse low level sensors to build your own custom sensors<br />
* ambient adaptation: adapt web content from daylight to darkness<br />
* new input mechanisms: use magnet as input in WebVR experiences<br />
* advanced motion-based games: measure the speed of your punch, walk around in a game<br />
<br />
by Kenneth Christiansen<br />
==== WebNFC ====<br />
A grocery planner Progressive Web App shows you how to bridge the physical world with the Web and makes your routine task a joy. Powered by Web NFC.<br />
<br />
by Kenneth Christiansen<br />
==== WebUSB ====<br />
Develop for Internet of Things devices with JavaScript and deploy directly to IoT device, all in your browser. Made possibly by Web USB API. <br />
<br />
by Kenneth Christiansen<br />
==== WebGPU ====<br />
<br />
GPUs have two different processing pipelines able to run on the same hardware: a "graphics" pipeline able to create images made of triangles and a "compute" pipeline able to run arbitrary parallel programs very fast. WebGL exposes the graphics pipeline but not the compute one. Some people have been able to do some computations with WebGL for example for fluid simulation or machine learning but it is suboptimal compared to what's possible with the compute pipeline.<br />
<br />
NXT and WebMetal are respectively Google's and Apple's prototypes for WebGPU. The demo will show an NXT particle system demo using both GPU graphics and compute at the same time. Compute is used to simulate the particle movement and graphics is used to display them.<br />
<br />
by Corentin Wallez<br />
<br />
==== TTML ====<br />
(gaps in CSS for subtitles and captions) <br />
<br />
by Nigel Megitt<br />
<br />
<br />
==== Web Payments & Interledger ====<br />
<br />
by Adrian Hope-Bailie<br />
<br />
==== Web Assembly ====<br />
by Brad Nelson<br />
<br />
==== CSS Grid ====<br />
by Greg Whitworth<br />
<br />
==== CSS Houdini ====<br />
by Ian Kilpatrick<br />
<br />
<br />
==== Positive Work Environment Task Force ====<br />
[[User:Amy|Amy van der Hiel]] ([[User talk:Amy|talk]]) 14:18, 6 October 2017 (UTC) and Ann Bassetti<br />
* Meetings and WG Best Practices and other community concerns<br/><br />
* open discussion<br />
* goals: to discuss and get feedback on Meetings and WG BP as well as any other concerns in the community (suggestions welcome upon sign up)</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=104616WG Best Practices2017-10-05T19:57:57Z<p>Amy: /* a list of do’s and don’t for WG Best Practicess */</p>
<hr />
<div>= a list of do’s and don’t for WG Best Practicess=<br />
based on an outline from Tzviya Siegman <br />
<br />
also possibly at add suggestions for process if there are problems in a WG<br />
see [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== Don’ts for working in a positively in a WG==<br />
* don't assume that you are the smartest person in the room<br />
The W3C and WG are full of experts from many fields who have valuable contributions to make to the whole<br />
* don't assume that others are disagreeing with you because they don't understand you and don't point out that another person's comments are incorrect or invalid<br />
Listen first and be sure you understand the point of view of the other person<br />
* don't assume that your proposal, code sample, or implementation will be adopted without changes and <br />
Consensus does not mean unanimity<br />
* don't get upset if something you worked on is not implemented. <br />
Your contribution is still valued and may be picked up in the future.<br />
* don't let your personal or professional goals impede the progress of the group<br />
The work is about more than just your area of interest<br />
* don't respond to comments without reading the background information<br />
* don't respond to every comment on a GitHub issue / don't respond to every email in a thread and don't put yourself on the queue every time someone speaks<br />
Overwhelm or being relentless is not helpful<br />
Others voices need to be heard as well<br />
<br />
<br />
<br />
== Dos for orking positively in a WG ==<br />
* do comment on technical issues on GitHub. The goal is to close issues. We don’t like to publish without closing all issues.<br />
* do ask broad questions about theory and meta-issues on the email list<br />
* do contact your chair, team contact, ac rep, PWETF member, if someone in a W3C meeting makes you uncomfortable<br />
* do review the work of other groups to see if you are reinventing the wheel (is this idiom international?)<br />
* do assess feedback provided by others to determine if it improves your proposals<br />
* do consider not hitting send – save as a draft and reconsider after a few minutes or hours<br />
* do consult with a friend in the group if you feel your message is not being understood. Another person might be able to explain things differently and get your message across successfully.</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE&diff=104615PWE2017-10-05T19:56:43Z<p>Amy: /* Best Practices */</p>
<hr />
<div>== Positive Work Environment ==<br />
Public wiki regarding Positive Work Environment at W3C.<br />
<br />
== W3C Codes of Conduct ==<br />
The [https://www.w3.org/Consortium/pwe/ Positive Work Environment Task Force] owns:<br />
<br />
* the [https://www.w3.org/Consortium/cepc/ Code of Ethics and Professional Conduct (CEPC)]<br />
<br />
* the draft [https://www.w3.org/wiki/PWE/Conf-code Conference code]<br />
<br />
* the [https://www.w3.org/Consortium/pwe/#Procedures Procedures] for implementing these codes<br />
<br />
== Best Practices ==<br />
<br />
A collection of Best Practices pages for meetings, speakers and public events<br />
<br />
* [https://www.w3.org/wiki/Speaker_Resources#Speakers_Guidelines Speaker Guidelines from Coralie]<br />
<br />
* [https://www.w3.org/wiki/Global_Topic Thoughts about making W3C more global developed by an Advisory Board task force (Judy Zhu, Jay Kishigami, others?)]<br />
<br />
* [https://www.w3.org/wiki/Moderating_Meetings Moderating Meetings] by AB (by Chaals)<br />
<br />
* Draft [[Meetings Best Practices document]] for meetings (to be prepared by TPAC 2016)<br />
<br />
* [https://www.w3.org/wiki/WG_Best_Practices WG Best Practices] (to be edited and adjusted for TPAC 2017<br />
<br />
* [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== PWETF discussion(s) notes ==<br />
This section will be for collecting PWETF notes and discussions<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_AC notes from BOF session at AC meeting, MIT, March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_badges ideas for name badges March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201609_TPAC Breakout Session from TPAC 2016]<br />
<br />
== Outline for renewing Task Force, reviewing goals, vision, documents, and next steps ==<br />
<br />
From May 2016: [https://www.w3.org/wiki/PWE/201604_outline ideas for renewing Task Force, reviewing goals, vision, documents, and next steps ]<br />
<br />
== Upcoming ==<br />
* {https://www.w3.org/wiki/PWE/Upcoming]</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=104614WG Best Practices2017-10-05T19:55:37Z<p>Amy: /* a list of do’s and don’t for WG Best Practicess */</p>
<hr />
<div>= a list of do’s and don’t for WG Best Practicess=<br />
based on an outline from Tzviya Siegman <br />
<br />
<br />
== Don’ts for working in a positively in a WG==<br />
* don't assume that you are the smartest person in the room<br />
The W3C and WG are full of experts from many fields who have valuable contributions to make to the whole<br />
* don't assume that others are disagreeing with you because they don't understand you and don't point out that another person's comments are incorrect or invalid<br />
Listen first and be sure you understand the point of view of the other person<br />
* don't assume that your proposal, code sample, or implementation will be adopted without changes and <br />
Consensus does not mean unanimity<br />
* don't get upset if something you worked on is not implemented. <br />
Your contribution is still valued and may be picked up in the future.<br />
* don't let your personal or professional goals impede the progress of the group<br />
The work is about more than just your area of interest<br />
* don't respond to comments without reading the background information<br />
* don't respond to every comment on a GitHub issue / don't respond to every email in a thread and don't put yourself on the queue every time someone speaks<br />
Overwhelm or being relentless is not helpful<br />
Others voices need to be heard as well<br />
<br />
<br />
<br />
== Dos for orking positively in a WG ==<br />
* do comment on technical issues on GitHub. The goal is to close issues. We don’t like to publish without closing all issues.<br />
* do ask broad questions about theory and meta-issues on the email list<br />
* do contact your chair, team contact, ac rep, PWETF member, if someone in a W3C meeting makes you uncomfortable<br />
* do review the work of other groups to see if you are reinventing the wheel (is this idiom international?)<br />
* do assess feedback provided by others to determine if it improves your proposals<br />
* do consider not hitting send – save as a draft and reconsider after a few minutes or hours<br />
* do consult with a friend in the group if you feel your message is not being understood. Another person might be able to explain things differently and get your message across successfully.</div>Amyhttps://www.w3.org/wiki/index.php?title=WG_Best_Practices&diff=104613WG Best Practices2017-10-05T19:55:05Z<p>Amy: Created page with "= a list of do’s and don’t for WG Best Practicess= based on an outline from Tzviya Siegman == Don’ts for working in a positively in a WG== * don't assume that you a..."</p>
<hr />
<div>= a list of do’s and don’t for WG Best Practicess=<br />
based on an outline from Tzviya Siegman <br />
<br />
<br />
== Don’ts for working in a positively in a WG==<br />
* don't assume that you are the smartest person in the room<br />
The W3C and WG are full of experts from many fields who have valuable contributions to make to the whole<br />
* don't assume that others are disagreeing with you because they don't understand you and don't point out that another person's comments are incorrect or invalid<br />
Listen first and be sure you understand the point of view of the other person<br />
* don't assume that your proposal, code sample, or implementation will be adopted without changes and <br />
Consensus does not mean unanimity<br />
* don't get upset if something you worked on is not implemented. <br />
Your contribution is still valued and may be picked up in the future.<br />
* don't let your personal or professional goals impede the progress of the group<br />
The work is about more than just your area of interest<br />
* don't respond to comments without reading the background information<br />
* don't respond to every comment on a GitHub issue / don't respond to every email in a thread and don't put yourself on the queue every time someone speaks<br />
Overwhelm or being relentless is not helpful<br />
Others voices need to be heard as well<br />
<br />
<br />
<br />
== Dos for orking positively in a WG ==<br />
* do comment on technical issues on GitHub. The goal is to close issues. We don’t like to publish without closing all issues.<br />
* do ask broad questions about theory and meta-issues on the email list<br />
* do contact your chair, team contact, ac rep, PWETF member, if someone in a W3C meeting makes you uncomfortable<br />
* do review the work of other groups to see if you are reinventing the wheel (is this idiom international?)<br />
* do assess feedback provided by others to determine if it improves your proposals<br />
* do consider not hitting send – save as a draft and reconsider after a few minutes or hours<br />
* do consult with a friend in the group if you feel your message is not being understood. Another person might be able to explain things differently and get your message across successfully.</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE&diff=104612PWE2017-10-05T19:44:37Z<p>Amy: /* Best Practices */</p>
<hr />
<div>== Positive Work Environment ==<br />
Public wiki regarding Positive Work Environment at W3C.<br />
<br />
== W3C Codes of Conduct ==<br />
The [https://www.w3.org/Consortium/pwe/ Positive Work Environment Task Force] owns:<br />
<br />
* the [https://www.w3.org/Consortium/cepc/ Code of Ethics and Professional Conduct (CEPC)]<br />
<br />
* the draft [https://www.w3.org/wiki/PWE/Conf-code Conference code]<br />
<br />
* the [https://www.w3.org/Consortium/pwe/#Procedures Procedures] for implementing these codes<br />
<br />
== Best Practices ==<br />
<br />
A collection of Best Practices pages for meetings, speakers and public events<br />
<br />
* [https://www.w3.org/wiki/Speaker_Resources#Speakers_Guidelines Speaker Guidelines from Coralie]<br />
<br />
* [https://www.w3.org/wiki/Global_Topic Thoughts about making W3C more global developed by an Advisory Board task force (Judy Zhu, Jay Kishigami, others?)]<br />
<br />
* [https://www.w3.org/wiki/Moderating_Meetings Moderating Meetings] by AB (by Chaals)<br />
<br />
* Draft [[Meetings Best Practices document]] for meetings (to be prepared by TPAC 2016)<br />
<br />
* [https://www.w3.org/2002/09/discipline Guidelines for Disciplinary Action]<br />
<br />
== PWETF discussion(s) notes ==<br />
This section will be for collecting PWETF notes and discussions<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_AC notes from BOF session at AC meeting, MIT, March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_badges ideas for name badges March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201609_TPAC Breakout Session from TPAC 2016]<br />
<br />
== Outline for renewing Task Force, reviewing goals, vision, documents, and next steps ==<br />
<br />
From May 2016: [https://www.w3.org/wiki/PWE/201604_outline ideas for renewing Task Force, reviewing goals, vision, documents, and next steps ]<br />
<br />
== Upcoming ==<br />
* {https://www.w3.org/wiki/PWE/Upcoming]</div>Amyhttps://www.w3.org/wiki/index.php?title=TPAC/2016&diff=100180TPAC/20162016-09-22T10:34:35Z<p>Amy: /* Breakout Schedule (session grid) */</p>
<hr />
<div>__TOC__<br />
<br />
<span style="color:#ff0000">'''*** DRAFT ***'''</span><br />
<br />
<div class="h-event"><br />
'''<dfn span class="p-name">[http://www.w3.org/2016/09/TPAC/ TPAC2016]</dfn>''' takes place <time class="dt-start" datetime="2016-09-19">2016-09-19</time>…<time class="dt-end" datetime="2016-09-23">23</time> M-F in <span class="p-location">Lisbon, Portugal</span>.<br />
</div><br />
<br />
<div class="h-event vevent"><br />
On <span class="dt-start" datetime="2016-09-19"><span class="value-title" title="2016-09-21">Wednesday, 21 September</span></span>, we hold a "<span class="p-name summary">Plenary Day.</span>" <span class="p-description description">As we did for [[TPAC2015]], we will organize most of the day as "camp-style" breakout sessions. We invite you to add to or comment on [[TPAC2016/SessionIdeas | Breakout session ideas]]. The people at the meeting that day will build the [[#Session_Grid | Session Grid]], drawing from ideas socialized in advance and new ideas proposed the day of the meeting.</span><br />
</div><br />
<br />
* Questions? See the [http://www.w3.org/wiki/TPAC2016/FAQ FAQ].<br />
* See Also past [[TPAC]] meetings.<br />
<br />
== Wednesday 21 September Plenary Day Schedule ==<br />
<br />
* Plenary sessions take place at [http://www.lisboacc.pt/irj/portal/lisboacc?lang=en Centro de congressos de lisboa]. See [https://www.w3.org/2016/09/TPAC/schedule.html schedule].<br />
* Breakout sessions take place in [http://www.w3.org/wiki/TPAC2016/FAQ#What_are_the_breakout_room_sizes.3F nearby rooms].<br />
* The lunch space accommodates slightly fewer people than registered; therefore breakout sessions overlap lunch time on each end.<br />
<br />
<span style="color:#ff0000">Proposed schedule:</span><br />
<div id="schedule"><br />
* ''08:00-08:30: Registration''<br />
* 08:30-08:35: '''Welcome''' - Jeff Jaffe<br />
* 08:35-09:05: '''Redecentralization of the Web''' - Tim Berners-Lee<br />
* 09:05-09:15: '''Data Breach, Reaction and Response'''(*) - Ted Guild<br />
* 09:15-10:00: '''Breakout preparation''' + '''last additions to [[TPAC2016/SessionIdeas | Breakout session ideas]]''' (Coralie Mercier)<br />
* ''09:15-10:00: Coffee break (**) - Hall 4, First Floor''<br />
* 10:00-11:00: '''Breakouts''' (see grid below)<br />
* 11:00-12:00: '''Breakouts''' (see grid below)<br />
* ''11:30-14:00: Lunch - Restaurant, First Floor'' <br />
* 13:00-14:00: '''Breakouts''' (see grid below)<br />
* 14:00-15:00: '''Breakouts''' (see grid below)<br />
* ''15:00-15:30: Coffee break - Hall 4, First Floor''<br />
* 15:30-16:30: '''Breakouts''' (see grid below)<br />
* 16:30-18:00: '''Breakout reports'''<br />
* ''18:30-21:30: Reception - Foyer E''<br />
** ''20:45-21:20: ForEveryone.net - Auditorium VI and VII'' ('''Private showing''' of a 35-minute documentary film about Sir Tim Berners-Lee, by Academy Award winning director Jessica Yu, which gives a history of the Web as well as a call to protect its future and features Tim, his family and colleagues including W3C CEO, Jeff Jaffe.)<br />
<br />
(*) Introduction to subsequent Breakout session; if you're a security expert, please consider signing up.<br><br />
(**) Breakout preparation and morning break overlap.<br />
</div><br />
<br />
=== Breakout Schedule (session grid) ===<br />
{| class="zebra"<br />
|-<br />
! Room (capacity)/Slots <br />
! 10:00-11:00 <br />
! 11:00-12:00<br />
! 13:00-14:00<br />
! 14:00-15:00<br />
! 15:30-16:30<br />
|-<br />
! Auditorium VI & VII, Ground Floor (48) <br />
| <br />
| <br />
| Positive Work environment + Global Participation Enhancement [https://www.w3.org/wiki/PWE/201609_TPAC (minutes)]<br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Privacy_compliance_in_the_EU_using_W3C_Tracking_Protection DNT]</span><br />
[https://www.w3.org/2016/09/21-dnt-minutes.html minutes]<br />
|<br />
|-<br />
! 5A, Hall 5, First Floor (48) <br />
| Web VR ([https://www.w3.org/2016/09/21-webvr-minutes.html minutes])<br />
| Decentralize + social web (#social)<br />
| WICG([http://pastebin.com/jMyKQWVk minutes])<br />
| Publications, Manifests, etc. (apps or docs)<br />
| Apache Annotator (W3C + ASF)<br />
|- <br />
! 5B, Hall 5, First Floor (48) <br />
| <br />
| <br />
| <br />
|<br />
| Thumbnails in video ([https://www.w3.org/2016/09/21-thumb-minutes.html minutes])<br />
|-<br />
! 5C, Hall 5, First Floor (48) <br />
| <br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#HTTPS_Migration_in_Local_Network HTTPS migration in local network]<br/>([https://www.w3.org/2016/09/21-https-local-minutes.html Minutes])<br />
| Block chain (intro, use cases & reqs)<br />
| WebIDL (Tobie)<br />
| <br />
|-<br />
! Auditorium III, First Floor (30) <br />
| Verifiable Claims WG ([https://www.w3.org/wiki/TPAC2016/SessionIdeas#Verifiable_Claims_Working_Group_Proposal summary]), ([https://w3c.github.io/webpayments-ig/VCTF/ proposal]), ([https://docs.google.com/presentation/d/1pFGC1G7CbizUuvbmjECfnNRL4fZk9QLxG8d3nehgwNU/edit?usp=sharing slides]), ([https://www.w3.org/2016/09/21-vctf-minutes.html minutes])<br />
| <br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Web_of_Things_PlugFest_Demos_.28Outreach.40TPAC.29 WoT PlugFest Demo Pitch]</span><br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Web_of_Things_PlugFest_Demos_.28Outreach.40TPAC.29 WoT PlugFest Demo]</span><br />
|<br />
|-<br />
! Auditorium IV, First Floor (30) <br />
| <br />
| Responsive Images: Declarative aspect ratios [https://www.w3.org/2016/09/21-respimg-minutes.html minutes]<br />
| <br />
| Micro-payments (w/browser plugin demo) [https://github.com/interledger/rfcs/blob/master/micropayments-w3c.md Notes and Minutes]<br />
| Paid Content<br />
|-<br />
! 1.07, Hall 4, First Floor (30) <br />
| Fusing language and sensor data ([https://www.w3.org/wiki/TPAC2016/session-fusing-user-and-sensor-input-summary summary])<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#What.27s_new_in_pubrules_and_automated_publishing What's new in pubrules and automated publishing] <br /> <small>[REQUEST] (needs phone; scheduled at 11:00</small>)<br />
| [https://www.w3.org/2016/09/21-eo-minutes.html Education & Outreach WG (EOWG) What is it & how can it support your work?] (Eric Eggert)<br />
|<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Future_of_Communications_on_the_Web Future of Communications on the Web] ([https://www.w3.org/2016/09/21-webcomms-minutes.html minutes])<br />
<br />
|-<br />
! 1.08, Hall 4, First Floor (30) <br />
| New Accessibility Guidelines & Mobile Accessibility<br />
| [http://www.w3.org/2016/09/21-aom-minutes.html Accessibility Object Model (AOM)]<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Subtitle_format_support_of_TextTrack_and_TextTrackCue_interfaces Subtitles & Text Track & Text TrackCue] [https://www.w3.org/2016/09/21-texttrack-minutes.html minutes]<br />
| AWPAT CG, HTML5 Testing Project (Chaals, Max)<br />
| [https://www.w3.org/2016/09/21-horizontal-minutes.html Horizontal Review] (Janina Sajka)<br />
|-<br />
! 1.05, Hall 4, First Floor (28) <br />
| <br />
| Async Web (Nolan Lawson)<br />
| <br />
| CSS Step String for block height (Koji)<br />
| Virtual Assistants ([https://www.w3.org/wiki/TPAC2016/virtual-assistants-summary summary])<br />
|-<br />
! 1.06, Hall 4, First Floor (26) <br />
| Protect against Data Breach, Web Authn 2FA (Ted G) [https://www.w3.org/2016/09/21-webauthn-minutes.html minutes]<br />
| Security JAM (news from W3C & new topics on security) [http://www.w3.org/2016/09/21-websec-minutes.html minutes]<br />
| Origin Isolation/Browsing Context Isolation (AnneVK, Mkwst) [https://www.w3.org/2016/09/21-isolation-minutes.html minutes]<br />
| [https://www.w3.org/2016/09/21-harmonize-minutes.html WAI standards harmonization roadmap] (Rich S)<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Vocabulary_development_.26_management_at_W3C Vocabulary Development, Namespaces Management] [https://www.w3.org/2016/09/21-vocabs-minutes Minutes]<br />
|-<br />
! 1.15, First Floor (26) <br />
| Storage<br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.03, First Floor (22) <br />
| <br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#High_Dynamic_Range_.28HDR.29_and_the_Web HDR and Web]<br />
| <br />
| Make W3C great again (how to make W3C a better platform for collaboration)<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Mobile_Accessibility Mobile Accessibility] - Kepeng Li (irc: #matf) [https://www.w3.org/2016/09/21-matf-minutes.html minutes]<br />
|-<br />
! 1.04, First Floor (22) <br />
| <br />
| <br />
| <br />
| Music Notation Community Group (Update)<br />
|<br />
|-<br />
|}<br />
<br />
== Aggregated Summaries ==<br />
<br />
@@will come later.<br />
<br />
<br />
{{:TPAC2016/session-hdr-summary}}<br />
<br />
{{:TPAC2016/virtual-assistants-summary}}<br />
<br />
=== Breakout title ===<br />
<pre><br />
Create breakout summary, e.g. https://www.w3.org/wiki/TPAC2016/session-foo-summary<br />
Transclude here using syntax: {{:TPAC2016/session-foo-summary}}</pre></div>Amyhttps://www.w3.org/wiki/index.php?title=TPAC/2016&diff=100179TPAC/20162016-09-22T10:34:08Z<p>Amy: /* Breakout Schedule (session grid) */</p>
<hr />
<div>__TOC__<br />
<br />
<span style="color:#ff0000">'''*** DRAFT ***'''</span><br />
<br />
<div class="h-event"><br />
'''<dfn span class="p-name">[http://www.w3.org/2016/09/TPAC/ TPAC2016]</dfn>''' takes place <time class="dt-start" datetime="2016-09-19">2016-09-19</time>…<time class="dt-end" datetime="2016-09-23">23</time> M-F in <span class="p-location">Lisbon, Portugal</span>.<br />
</div><br />
<br />
<div class="h-event vevent"><br />
On <span class="dt-start" datetime="2016-09-19"><span class="value-title" title="2016-09-21">Wednesday, 21 September</span></span>, we hold a "<span class="p-name summary">Plenary Day.</span>" <span class="p-description description">As we did for [[TPAC2015]], we will organize most of the day as "camp-style" breakout sessions. We invite you to add to or comment on [[TPAC2016/SessionIdeas | Breakout session ideas]]. The people at the meeting that day will build the [[#Session_Grid | Session Grid]], drawing from ideas socialized in advance and new ideas proposed the day of the meeting.</span><br />
</div><br />
<br />
* Questions? See the [http://www.w3.org/wiki/TPAC2016/FAQ FAQ].<br />
* See Also past [[TPAC]] meetings.<br />
<br />
== Wednesday 21 September Plenary Day Schedule ==<br />
<br />
* Plenary sessions take place at [http://www.lisboacc.pt/irj/portal/lisboacc?lang=en Centro de congressos de lisboa]. See [https://www.w3.org/2016/09/TPAC/schedule.html schedule].<br />
* Breakout sessions take place in [http://www.w3.org/wiki/TPAC2016/FAQ#What_are_the_breakout_room_sizes.3F nearby rooms].<br />
* The lunch space accommodates slightly fewer people than registered; therefore breakout sessions overlap lunch time on each end.<br />
<br />
<span style="color:#ff0000">Proposed schedule:</span><br />
<div id="schedule"><br />
* ''08:00-08:30: Registration''<br />
* 08:30-08:35: '''Welcome''' - Jeff Jaffe<br />
* 08:35-09:05: '''Redecentralization of the Web''' - Tim Berners-Lee<br />
* 09:05-09:15: '''Data Breach, Reaction and Response'''(*) - Ted Guild<br />
* 09:15-10:00: '''Breakout preparation''' + '''last additions to [[TPAC2016/SessionIdeas | Breakout session ideas]]''' (Coralie Mercier)<br />
* ''09:15-10:00: Coffee break (**) - Hall 4, First Floor''<br />
* 10:00-11:00: '''Breakouts''' (see grid below)<br />
* 11:00-12:00: '''Breakouts''' (see grid below)<br />
* ''11:30-14:00: Lunch - Restaurant, First Floor'' <br />
* 13:00-14:00: '''Breakouts''' (see grid below)<br />
* 14:00-15:00: '''Breakouts''' (see grid below)<br />
* ''15:00-15:30: Coffee break - Hall 4, First Floor''<br />
* 15:30-16:30: '''Breakouts''' (see grid below)<br />
* 16:30-18:00: '''Breakout reports'''<br />
* ''18:30-21:30: Reception - Foyer E''<br />
** ''20:45-21:20: ForEveryone.net - Auditorium VI and VII'' ('''Private showing''' of a 35-minute documentary film about Sir Tim Berners-Lee, by Academy Award winning director Jessica Yu, which gives a history of the Web as well as a call to protect its future and features Tim, his family and colleagues including W3C CEO, Jeff Jaffe.)<br />
<br />
(*) Introduction to subsequent Breakout session; if you're a security expert, please consider signing up.<br><br />
(**) Breakout preparation and morning break overlap.<br />
</div><br />
<br />
=== Breakout Schedule (session grid) ===<br />
{| class="zebra"<br />
|-<br />
! Room (capacity)/Slots <br />
! 10:00-11:00 <br />
! 11:00-12:00<br />
! 13:00-14:00<br />
! 14:00-15:00<br />
! 15:30-16:30<br />
|-<br />
! Auditorium VI & VII, Ground Floor (48) <br />
| <br />
| <br />
| Positive Work environment + Global Participation Enhancement [https://www.w3.org/wiki/PWE/201609_TPAC minutes]<br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Privacy_compliance_in_the_EU_using_W3C_Tracking_Protection DNT]</span><br />
[https://www.w3.org/2016/09/21-dnt-minutes.html minutes]<br />
|<br />
|-<br />
! 5A, Hall 5, First Floor (48) <br />
| Web VR ([https://www.w3.org/2016/09/21-webvr-minutes.html minutes])<br />
| Decentralize + social web (#social)<br />
| WICG([http://pastebin.com/jMyKQWVk minutes])<br />
| Publications, Manifests, etc. (apps or docs)<br />
| Apache Annotator (W3C + ASF)<br />
|- <br />
! 5B, Hall 5, First Floor (48) <br />
| <br />
| <br />
| <br />
|<br />
| Thumbnails in video ([https://www.w3.org/2016/09/21-thumb-minutes.html minutes])<br />
|-<br />
! 5C, Hall 5, First Floor (48) <br />
| <br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#HTTPS_Migration_in_Local_Network HTTPS migration in local network]<br/>([https://www.w3.org/2016/09/21-https-local-minutes.html Minutes])<br />
| Block chain (intro, use cases & reqs)<br />
| WebIDL (Tobie)<br />
| <br />
|-<br />
! Auditorium III, First Floor (30) <br />
| Verifiable Claims WG ([https://www.w3.org/wiki/TPAC2016/SessionIdeas#Verifiable_Claims_Working_Group_Proposal summary]), ([https://w3c.github.io/webpayments-ig/VCTF/ proposal]), ([https://docs.google.com/presentation/d/1pFGC1G7CbizUuvbmjECfnNRL4fZk9QLxG8d3nehgwNU/edit?usp=sharing slides]), ([https://www.w3.org/2016/09/21-vctf-minutes.html minutes])<br />
| <br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Web_of_Things_PlugFest_Demos_.28Outreach.40TPAC.29 WoT PlugFest Demo Pitch]</span><br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Web_of_Things_PlugFest_Demos_.28Outreach.40TPAC.29 WoT PlugFest Demo]</span><br />
|<br />
|-<br />
! Auditorium IV, First Floor (30) <br />
| <br />
| Responsive Images: Declarative aspect ratios [https://www.w3.org/2016/09/21-respimg-minutes.html minutes]<br />
| <br />
| Micro-payments (w/browser plugin demo) [https://github.com/interledger/rfcs/blob/master/micropayments-w3c.md Notes and Minutes]<br />
| Paid Content<br />
|-<br />
! 1.07, Hall 4, First Floor (30) <br />
| Fusing language and sensor data ([https://www.w3.org/wiki/TPAC2016/session-fusing-user-and-sensor-input-summary summary])<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#What.27s_new_in_pubrules_and_automated_publishing What's new in pubrules and automated publishing] <br /> <small>[REQUEST] (needs phone; scheduled at 11:00</small>)<br />
| [https://www.w3.org/2016/09/21-eo-minutes.html Education & Outreach WG (EOWG) What is it & how can it support your work?] (Eric Eggert)<br />
|<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Future_of_Communications_on_the_Web Future of Communications on the Web] ([https://www.w3.org/2016/09/21-webcomms-minutes.html minutes])<br />
<br />
|-<br />
! 1.08, Hall 4, First Floor (30) <br />
| New Accessibility Guidelines & Mobile Accessibility<br />
| [http://www.w3.org/2016/09/21-aom-minutes.html Accessibility Object Model (AOM)]<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Subtitle_format_support_of_TextTrack_and_TextTrackCue_interfaces Subtitles & Text Track & Text TrackCue] [https://www.w3.org/2016/09/21-texttrack-minutes.html minutes]<br />
| AWPAT CG, HTML5 Testing Project (Chaals, Max)<br />
| [https://www.w3.org/2016/09/21-horizontal-minutes.html Horizontal Review] (Janina Sajka)<br />
|-<br />
! 1.05, Hall 4, First Floor (28) <br />
| <br />
| Async Web (Nolan Lawson)<br />
| <br />
| CSS Step String for block height (Koji)<br />
| Virtual Assistants ([https://www.w3.org/wiki/TPAC2016/virtual-assistants-summary summary])<br />
|-<br />
! 1.06, Hall 4, First Floor (26) <br />
| Protect against Data Breach, Web Authn 2FA (Ted G) [https://www.w3.org/2016/09/21-webauthn-minutes.html minutes]<br />
| Security JAM (news from W3C & new topics on security) [http://www.w3.org/2016/09/21-websec-minutes.html minutes]<br />
| Origin Isolation/Browsing Context Isolation (AnneVK, Mkwst) [https://www.w3.org/2016/09/21-isolation-minutes.html minutes]<br />
| [https://www.w3.org/2016/09/21-harmonize-minutes.html WAI standards harmonization roadmap] (Rich S)<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Vocabulary_development_.26_management_at_W3C Vocabulary Development, Namespaces Management] [https://www.w3.org/2016/09/21-vocabs-minutes Minutes]<br />
|-<br />
! 1.15, First Floor (26) <br />
| Storage<br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.03, First Floor (22) <br />
| <br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#High_Dynamic_Range_.28HDR.29_and_the_Web HDR and Web]<br />
| <br />
| Make W3C great again (how to make W3C a better platform for collaboration)<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Mobile_Accessibility Mobile Accessibility] - Kepeng Li (irc: #matf) [https://www.w3.org/2016/09/21-matf-minutes.html minutes]<br />
|-<br />
! 1.04, First Floor (22) <br />
| <br />
| <br />
| <br />
| Music Notation Community Group (Update)<br />
|<br />
|-<br />
|}<br />
<br />
== Aggregated Summaries ==<br />
<br />
@@will come later.<br />
<br />
<br />
{{:TPAC2016/session-hdr-summary}}<br />
<br />
{{:TPAC2016/virtual-assistants-summary}}<br />
<br />
=== Breakout title ===<br />
<pre><br />
Create breakout summary, e.g. https://www.w3.org/wiki/TPAC2016/session-foo-summary<br />
Transclude here using syntax: {{:TPAC2016/session-foo-summary}}</pre></div>Amyhttps://www.w3.org/wiki/index.php?title=PWE/201609_TPAC&diff=100133PWE/201609 TPAC2016-09-21T15:42:04Z<p>Amy: /* minutes: */</p>
<hr />
<div><br />
<br />
= TPAC session on Positive Work environment + Global Participation Enhancement =<br />
=== 21 September 2016 ===<br />
<br />
=== attending: === <br />
: Tzviya Siegman, Wiley<br />
: An Qi LI, W3C<br />
: Chunming Hu, W3C<br />
: Amy van der Hiel, W3C<br />
: Florian Rivoal, Vivliostyle, Inc.<br />
: Romain Deltou, DAISY Consortium<br />
: Frank Olivier, Microsoft Corporation<br />
: Ann Bassetti<br />
: Antonio Olmo Titos, W3C<br />
: Dave Cramer, Hachette Livre<br />
: Coralie Mercier, W3C<br />
: Vagner Diniz, Nic.br<br />
: Judy Brewer, W3C<br />
<br />
=== minutes: === <br />
* TS: I am working at Wiley<br />
* AL: New area from new re-org, international, business<br />
* CH: support AL<br />
* FR: The topic is interesting personally. I volunteered to help make connections for BusDev, recruiting people. I saw how people can run into barriers in trying to join<br />
* RD: I am in Digital publishing and WCAG. I am here because of personal interest. I think an inclusive work environment is important<br />
* FO: I work in HMTL and WebApps<br />
* AB: I have been w/ PWET since its start. I have long been concerned about global participation. If you've been in a meeting with me you've likely heard me ask people to speak more slowly. I am interested to have pwet, be that - positive work environment. Something cultural. not about punishment and process. The code of conduct is not the issue. what other things are the issue?<br />
* FR: things shouldn't have to get to the reporting place<br />
* AT: I am interested to hear more about it. having lived in Japan I've seen the Asian side of things, It can be difficult to integrate<br />
* DC: I am in digital publishing. I am interested in the dynamics of discussions. I notice some people dominate discussions and others can be afraid to speak. Even groups that do wonderful work, have welcoming environments still have concerns about everybody's voice being heard.<br />
* CM: I can understand the CoC being interpreted as punishment. I am still interested in topic since the group started in 2008. I have been staff since 99. I used to be the co chair of PWE. I am now the head of Comm but stepped down because I am focusing in other areas<br />
* VD: I'm from Brazil, fro nic.br<br />
* AB: I'm interested in how to organize this. I have heard different issues around organizing. it's a human issue. Some people dominate the talking more. It can be especially a global issue, it comes in more. 1/3 of our people here are not native english speakers. I know I'd be very quiet in a meeting held in French. certain cultures are also more quiet.<br />
* FR:: to Dave, in terms of being loud. i might be loud. but I think there are two ways of being scary. by decibel or you hear the % of market share behind (magnitude of the company they represent)<br />
* TS: I think tone is an issue more than volume. Tone is much more felt than volume. more than browser presence. For example. the other day [someone] gave a presentation. she had put in hours of work, no applause, she was just picked apart. <br />
* FR: There was no applause?<br />
* TS: no<br />
* DC: sound volume and <br />
* AL: another issue is recognition for contributions<br />
* TS: yes, acknowledgement<br />
* RD: on mailing lists, too. Sometimes the sheer volume. it may have doubled. <br />
* AL: I have heard from shy Chinese members. They are maybe not used to all email. So when they ask stupid questions. someone says "go read web page" this really hurts<br />
* FR: As a counter example - an exception not a rule. The LG from Korea joined the WG. They had a valid use case. not mature enough. Both sides showed good will. They wanted to learn and work w/ us. We showed they are not there yet. would need hand holding. luckily they got hand holding. When that happens it works brilliantly<br />
* TS: everyone needs hand holding<br />
* DC: they did everything perfectly from the start. well developed approach, they took it to the WG rather than doing it on they own. so many things self<br />
* FR: to tie to the Asian difficultly. calls are aways 1 or 2 am. sometimes it may seem there's no human to do contact.<br />
* AB: when I was on the AB, we had Asian members. there is no time zone that works when geographically set up. So we did alternating times during the year. Half the time the west coast got up 5 am or 6pm. that was convenient for Aisa. then other times it was afternoon for me but midnight for them. I can say it was very aggravating when Asian counterpart didn't show up for meeting. we didn't change month by month. that was too confusing. <br />
* TS: one other issue. maybe for AL, we have an issue attracting a large percentage of population - we don't have a lot of women. we have a diversity issue. Things not just to encourage women and people of color to join but actual outreach. at IETF they do outreach to join. they have a method to fund people. then the challenge becomes maintaining membership. Both how to make people comfortable to join and keep them comfortable to stay.<br />
* Ann: is travel covered?<br />
* Av: some of this might fall under general good behavior, politeness. a sense of openness and respect to others. there are drives to commit to not be on panels of all men<br />
* VD. a big issue is gender equality. at meeting like this one or a workshop. we should make an effort to ensure we will have always women in panels. <br />
* FR: I am a feminist, and I made this promise. and even so, I forgot about it for this panel happening tomorrow<br />
* TS: Dave and I have signed a pledge. 50% women speakers <br />
* VD:. There are procedure and process. We can go further. at the next w3c conference in Brazil. more than 1/2 women speakers. we just have to put effort in this <br />
* Av: is there an action we can have here to put this idea in front of w3c?<br />
* AB: it's a great vision to have. the difficulty is to find someone appropriately skilled. Vagner. for a conference can seek. I had to find someone at Boeing when i left. Adam was a man. the work would not appropriate for a women who doesn't know the role. working toward that goal. not sure that's realistic<br />
* AL: I wanted to ask a question. In the history of W3C. its there a document with the principle for diversity, participation, etc? For the postive work environment, for basic human things like teleconferences at tolerable working times. <br />
* CM: there is the code of ethics and conduct. you have to be decent. <br />
* AB: maybe we should review this for the revitalization<br />
* Av: there are now more best practices documents<br />
* AB: Judy Zhu worked on one, we've linked to. if we're trying to aim for diversity of male and female. international as well<br />
* FR: Ann, it does depends on who members send. In the gender composition of working group, I noticed between members and invited experts. invited experts were more balanced<br />
* JB; years ago I was invited to participate in a panel at Grace Hopper conference. it is massive now. centered around the theme of women in Tech. There were 4 standards organizations who spoke on gender balance. years ago we had done it. but it's frightening how predictable the ratio was. invited expert #s was stronger. For WG participant it was not as good. Chairs were less. at the AC level there was just Ann. and at the AB. For a long time there only one woman on w3c management. This is one reason we have PWETF. Things came out of that. I was said when looking at a new WG, we should look more broadly for chair candidates. team and international side. they weren't even considering women. It was like an automatic screen out. it was really helpful to get a reminder. comparably qualified<br />
* FR: There was something like this in a search i was recently involved in. It didn't play out well<br />
* TS: chair training might really help. <br />
* AB: chairs are crucial. <br />
* JB: it is mandatory<br />
* TZ: since I've been a chair for two years it's not been done<br />
* AB: I think we can add this back to the thinking<br />
* AL: to be sure everyone is included I'd like to the keep queue locally<br />
* TS: there needs to be chair training. didn't know this for two years.<br />
* JB: staff needs to be trained too<br />
* AQ: we might put in a team day<br />
* DC: all this is pointing to one place we don't see to have untying. on boarding. huge problem. 3 years ago at a workshop Markus said to me: your company joined you're going to be in China next month. i'm dumped into TPAC. it's like what the hell is this? i'm in this 20 year old strong culture of the CSS WG. W3C has a defined culture. cultures, even. i survived because other members took care of me. <br />
* AB: team buddy. <br />
* TS: buddies are variable. we also are lucky because we have Ivan <br />
* FR: we've touched on gender. diversity. there are women around this table. few people of color. age we seem to do ok<br />
* Av: true diversity is important. We may, as TS suggested, look at better outreach<br />
* AB: we have very little representation from south america, africa, etc<br />
* JB: at a meeting in Tunisa. we meet wonderful people. <br />
* Av: Jeff gave us not just task to update documents, he asked us to think about our aspirational goals. what kind of place we want this to be to work at. This is an area where W3C could truly lead. Diversity is a very valuable goal<br />
* AL: From the hosts. we encourage warm up calls. fresh attendance to AC and TPAC. we do this for Chinese members. to help anticipate more culture shock when join. We can guide through tools rss agent. etc. We can introduce highlights in agenda. at the end we provide tips. culturally strong WG. sometimes we talk about werewolves. they feel it helps a lot.<br />
* AB: can we reuse these materials for everyone? <br />
* AL: we do it in China. <br />
* AB: could it be generalized?<br />
* AL: we could clone practice in all hosts. talk to locals. in own their own language. every season we come up w/ script to share. the feedback from members is pretty good. it's not so daunting. they got tips. trips, travel info. weather. it makes them feel "i'm welcome". to do globally<br />
* AB; i was a third grade teacher. helping people prepare for making materials<br />
* TS: I do something similar. I was copied in early email to Rob Sanders when I joined the WG, I used the same text. Now every time someone joins I send a list of things to know: email archive, links to irc. next meeting i'll send it you. You should be able to generate it automatically. the same way I get a note when someone joins the group. <br />
* AL: yes, some templates you can customize<br />
* FR: template gets sent. <br />
* AB: we could use a modernized version of guidebook. consulted and review. could be translated into local languages. at least it would be consistent. a werewolf introduction [laughter]. no but social stuff is huge. <br />
* TS: it's how you meet people. <br />
* AB: right now we've got a group who does art. maybe next will be music. <br />
* FR: another social thing they do in css. not intentionally but since a lot of us are friends. we go to Air BnB and rent an apartment. including new comers helps<br />
* AB: though that could be to the detriment of w3c. we can't get rooms<br />
* FR: We do it at TPAC less. just individual group meetings<br />
* AL: it works for a f2f<br />
* DC: to follow up. going back to issues of invited experts. what CSS has done, we try to take care of invited experts during the meetings. if 7 go out and 5 are on expense. we it split 5 ways. Florian slept in my hotel room last time<br />
* FR: this time I am sponsored. <br />
* AL: it's good to be nice to the IEs. it's the small things.<br />
* TS: this is not so small<br />
* DC: it is evidence of the culture <br />
* AB: it's great to be supportive and friendly thought we've got a long way to go<br />
* TS: it's largely a friendly group<br />
* FR: for the chairs training and training for picking chairs. now we have to address AC. telling AC reps, don't forget to nominate women. <br />
* AL: we can put into on on-boarding. starting into next year. <br />
* CH: one of my oveserveraions. i can remember one or two years ago. Baidu they did their first member submission. they didn't know who to participate. before they joined the WG there was lots of the job done by WG. They didn't know how to show their value, how to contribute. They came up w/ a member submission. They wanted to give solutions. They also asked the local team to help them contact the WG people to help to explain what happened. the idea in this case, after that they showed they proposal face to face. They debated, is it ok? Finally since this accepted for the people who proposed. they might think their ideas were ignored. they were not sure how to change situation. now they have a lot of do and they won't put more time on it. i think in this case, what can we learn? personally. 1. i'm not sure if we can work out best practice. how to participate on WG discussions. <br />
* FR: that might be hard right now. it would have been easier a few years ago. even the people who are used to this. others think incubation. first fight in w3c. <br />
* AB: all these things are true. maybe could have a W3C wide TF on how to participate. <br />
* CH: they may get debate. we can alert them. if there are some good stories for them that might help. look at best practice. <br />
* AB: I also wanted to hear from people who have been quiet. Roman, Frank, Antonio?<br />
* RD: i agree w/ all these ideas. another possible idea. I am in a group, and when we have a F2F of the TF. where the chair has the habit at end of the meeting, to make a round. to ask for final thoughts. to appeal who those who haven't spoken to be sure they have chance to talk. Sometimes they feel compelled. some people may prefer not to talk to but this encourages them. <br />
* AB: we lose value if they don't speak, or aren't called on<br />
* DC: i did that on a call for ePub. especially in the phone context, the barrier can be high. <br />
* RD: it could be difficult depending on the size of the group.<br />
* DC: this was not for a small technical point. but the larger vision so it was worth it<br />
* AT: this feels very inclusive for me. Are there statistics? i don't think people think things are broken. they just want to know how to make things better <br />
* Av: industry standard. 25% women. we are below that in W3C Team etc. <br />
* FO: Apple etc do %s at the end of the year. We might consider this.<br />
<br />
end: who might join, participate in PWET (Roman, Tzviya, Florian, Antonio?)</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE/201609_TPAC&diff=100131PWE/201609 TPAC2016-09-21T15:41:08Z<p>Amy: /* minutes: */</p>
<hr />
<div><br />
<br />
= TPAC session on Positive Work environment + Global Participation Enhancement =<br />
=== 21 September 2016 ===<br />
<br />
=== attending: === <br />
: Tzviya Siegman, Wiley<br />
: An Qi LI, W3C<br />
: Chunming Hu, W3C<br />
: Amy van der Hiel, W3C<br />
: Florian Rivoal, Vivliostyle, Inc.<br />
: Romain Deltou, DAISY Consortium<br />
: Frank Olivier, Microsoft Corporation<br />
: Ann Bassetti<br />
: Antonio Olmo Titos, W3C<br />
: Dave Cramer, Hachette Livre<br />
: Coralie Mercier, W3C<br />
: Vagner Diniz, Nic.br<br />
: Judy Brewer, W3C<br />
<br />
=== minutes: === <br />
* TS: I am working at Wiley<br />
* AL: New area from new re-org, international, business<br />
* CH: support AL<br />
* FR: The topic is interesting personally. I volunteered to help make connections for BusDev, recruiting people. I saw how people can run into barriers in trying to join<br />
* RD: I am in Digital publishing and WCAG. I am here because of personal interest. I think an inclusive work environment is important<br />
* FO: I work in HMTL and WebApps<br />
* AB: I have been w/ PWET since its start. I have long been concerned about global participation. If you've been in a meeting with me you've likely heard me ask people to speak more slowly. I am interested to have pwet, be that - positive work environment. Something cultural. not about punishment and process. The code of conduct is not the issue. what other things are the issue?<br />
* FR: things shouldn't have to get to the reporting place<br />
* AT: I am interested to hear more about it. having lived in Japan I've seen the Asian side of things, It can be difficult to integrate<br />
* DC: I am in digital publishing. I am interested in the dynamics of discussions. I notice some people dominate discussions and others can be afraid to speak. Even groups that do wonderful work, have welcoming environments still have concerns about everybody's voice being heard.<br />
* CM: I can understand the CoC being interpreted as punishment. I am still interested in topic since the group started in 2008. I have been staff since 99. I used to be the co chair of PWE. I am now the head of Comm but stepped down because I am focusing in other areas<br />
* VD: I'm from Brazil, fro nic.br<br />
* AB: I'm interested in how to organize this. I have heard different issues around organizing. it's a human issue. Some people dominate the talking more. It can be especially a global issue, it comes in more. 1/3 of our people here are not native english speakers. I know I'd be very quiet in a meeting held in French. certain cultures are also more quiet.<br />
* FR:: to Dave, in terms of being loud. i might be loud. but I think there are two ways of being scary. by decibel or you hear the % of market share behind (magnitude of the company they represent)<br />
* TS: I think tone is an issue more than volume. Tone is much more felt than volume. more than browser presence. For example. the other day [someone] gave a presentation. she had put in hours of work, no applause, she was just picked apart. <br />
* FR: There was no applause?<br />
* TS: no<br />
* DC: sound volume and <br />
* AL: another issue is recognition for contributions<br />
* TS: yes, acknowledgement<br />
* RD: on mailing lists, too. Sometimes the sheer volume. it may have doubled. <br />
* AL: I have heard from shy Chinese members. They are maybe not used to all email. So when they ask stupid questions. someone says "go read web page" this really hurts<br />
* FR: As a counter example - an exception not a rule. The LG from Korea joined the WG. They had a valid use case. not mature enough. Both sides showed good will. They wanted to learn and work w/ us. We showed they are not there yet. would need hand holding. luckily they got hand holding. When that happens it works brilliantly<br />
* TS: everyone needs hand holding<br />
* DC: they did everything perfectly from the start. well developed approach, they took it to the WG rather than doing it on they own. so many things self<br />
* FR: to tie to the Asian difficultly. calls are aways 1 or 2 am. sometimes it may seem there's no human to do contact.<br />
* AB: when I was on the AB, we had Asian members. there is no time zone that works when geographically set up. So we did alternating times during the year. Half the time the west coast got up 5 am or 6pm. that was convenient for Aisa. then other times it was afternoon for me but midnight for them. I can say it was very aggravating when Asian counterpart didn't show up for meeting. we didn't change month by month. that was too confusing. <br />
* TS: one other issue. maybe for AL, we have an issue attracting a large percentage of population - we don't have a lot of women. we have a diversity issue. Things not just to encourage women and people of color to join but actual outreach. at IETF they do outreach to join. they have a method to fund people. then the challenge becomes maintaining membership. Both how to make people comfortable to join and keep them comfortable to stay.<br />
* Ann: is travel covered?<br />
* Av: some of this might fall under general good behavior, politeness. a sense of openness and respect to others. there are drives to commit to not be on panels of all men<br />
* VD. a big issue is gender equality. at meeting like this one or a workshop. we should make an effort to ensure we will have always women in panels. <br />
* FR: I am a feminist, and I made this promise. and even so, I forgot about it for this panel happening tomorrow<br />
* TS: Dave and I have signed a pledge. 50% women speakers <br />
* VD:. There are procedure and process. We can go further. at the next w3c conference in Brazil. more than 1/2 women speakers. we just have to put effort in this <br />
* Av: is there an action we can have here to put this idea in front of w3c?<br />
* AB: it's a great vision to have. the difficulty is to find someone appropriately skilled. Vagner. for a conference can seek. I had to find someone at Boeing when i left. Adam was a man. the work would not appropriate for a women who doesn't know the role. working toward that goal. not sure that's realistic<br />
* AL: I wanted to ask a question. In the history of W3C. its there a document with the principle for diversity, participation, etc? For the postive work environment, for basic human things like teleconferences at tolerable working times. <br />
* CM: there is the code of ethics and conduct. you have to be decent. <br />
* AB: maybe we should review this for the revitalization<br />
* Av: there are now more best practices documents<br />
* AB: Judy Zhu worked on one, we've linked to. if we're trying to aim for diversity of male and female. international as well<br />
* FR: Ann, it does depends on who members send. In the gender composition of working group, I noticed between members and invited experts. invited experts were more balanced<br />
* JB; years ago I was invited to participate in a panel at Grace Hopper conference. it is massive now. centered around the theme of women in Tech. There were 4 standards organizations who spoke on gender balance. years ago we had done it. but it's frightening how predictable the ratio was. invited expert #s was stronger. For WG participant it was not as good. Chairs were less. at the AC level there was just Ann. and at the AB. For a long time there only one woman on w3c management. This is one reason we have PWETF. Things came out of that. I was said when looking at a new WG, we should look more broadly for chair candidates. team and international side. they weren't even considering women. It was like an automatic screen out. it was really helpful to get a reminder. comparably qualified<br />
* FR: There was something like this in a search i was recently involved in. It didn't play out well<br />
* TS: chair training might really help. <br />
* AB: chairs are crucial. <br />
* JB: it is mandatory<br />
* TZ: since I've been a chair for two years it's not been done<br />
* AB: I think we can add this back to the thinking<br />
* AL: to be sure everyone is included I'd like to the keep queue locally<br />
* TS: there needs to be chair training. didn't know this for two years.<br />
* JB: staff needs to be trained too<br />
* AQ: we might put in a team day<br />
* DC: all this is pointing to one place we don't see to have untying. on boarding. huge problem. 3 years ago at a workshop Markus said to me: your company joined you're going to be in China next month. i'm dumped into TPAC. it's like what the hell is this? i'm in this 20 year old strong culture of the CSS WG. W3C has a defined culture. cultures, even. i survived because other members took care of me. <br />
* AB: team buddy. <br />
* TS: buddies are variable. we also are lucky because we have Ivan <br />
* FR: we've touched on gender. diversity. there are women around this table. few people of color. age we seem to do ok<br />
* Av: true diversity is important. We may, as TS suggested, look at better outreach<br />
* AB: we have very little representation from south america, africa, etc<br />
* JB: at a meeting in Tunisa. we meet wonderful people. <br />
* Av: Jeff gave us not just task to update documents, he asked us to think about our aspirational goals. what kind of place we want this to be to work at. This is an area where W3C could truly lead. Diversity is a very valuable goal<br />
* AL: From the hosts. we encourage warm up calls. fresh attendance to AC and TPAC. we do this for Chinese members. to help anticipate more culture shock when join. We can guide through tools rss agent. etc. We can introduce highlights in agenda. at the end we provide tips. culturally strong WG. sometimes we talk about werewolves. they feel it helps a lot.<br />
* AB: can we reuse these materials for everyone? <br />
* AL: we do it in China. <br />
* AB: could it be generalized?<br />
* AL: we could clone practice in all hosts. talk to locals. in own their own language. every season we come up w/ script to share. the feedback from members is pretty good. it's not so daunting. they got tips. trips, travel info. weather. it makes them feel "i'm welcome". to do globally<br />
* AB; i was a third grade teacher. helping people prepare for making materials<br />
* TS: I do something similar. I was copied in early email to Rob Sanders when I joined the WG, I used the same text. Now every time someone joins I send a list of things to know: email archive, links to irc. next meeting i'll send it you. You should be able to generate it automatically. the same way I get a note when someone joins the group. <br />
* AL: yes, some templates you can customize<br />
* FR: template gets sent. <br />
* AB: we could use a modernized version of guidebook. consulted and review. could be translated into local languages. at least it would be consistent. a werewolf introduction [laughter]. no but social stuff is huge. <br />
* TS: it's how you meet people. <br />
* AB: right now we've got a group who does art. maybe next will be music. <br />
* FR: another social thing they do in css. not intentionally but since a lot of us are friends. we go to Air BnB and rent an apartment. including new comers helps<br />
* AB: though that could be to the detriment of w3c. we can't get rooms<br />
* FR: We do it at TPAC less. just individual group meetings<br />
* AL: it works for a f2f<br />
* DC: to follow up. going back to issues of invited experts. what CSS has done, we try to take care of invited experts during the meetings. if 7 go out and 5 are on expense. we it split 5 ways. Florian slept in my hotel room last time<br />
* FR: this time I am sponsored. <br />
* AL: it's good to be nice to the IEs. it's the small things.<br />
* TS: this is not so small<br />
* DC: it is evidence of the culture <br />
* AB: it's great to be supportive and friendly thought we've got a long way to go<br />
* TS: it's largely a friendly group<br />
* FR: for the chairs training and training for picking chairs. now we have to address AC. telling AC reps, don't forget to nominate women. <br />
* AL: we can put into on on-boarding. starting into next year. <br />
* CH: one of my oveserveraions. i can remember one or two years ago. Baidu they did their first member submission. they didn't know who to participate. before they joined the WG there was lots of the job done by WG. They didn't know how to show their value, how to contribute. They came up w/ a member submission. They wanted to give solutions. They also asked the local team to help them contact the WG people to help to explain what happened. the idea in this case, after that they showed they proposal face to face. They debated, is it ok? Finally since this accepted for the people who proposed. they might think their ideas were ignored. they were not sure how to change situation. now they have a lot of do and they won't put more time on it. i think in this case, what can we learn? personally. 1. i'm not sure if we can work out best practice. how to participate on WG discussions. <br />
* FR: that might be hard right now. it would have been easier a few years ago. even the people who are used to this. others think incubation. first fight in w3c. <br />
* AB: all these things are true. maybe could have a W3C wide TF on how to participate. <br />
* CH: they may get debate. we can alert them. if there are some good stories for them that might help. look at best practice. <br />
* AB: I also wanted to hear from people who have been quiet. Roman, Frank, Antonio?<br />
* Roman: i agree w/ all these ideas. another possible idea. I am in a group, and when we have a F2F of the TF. where the chair has the habit at end of the meeting, to make a round. to ask for final thoughts. to appeal who those who haven't spoken to be sure they have chance to talk. Sometimes they feel compelled. some people may prefer not to talk to but this encourages them. <br />
* AB: we lose value if they don't speak, or aren't called on<br />
* DC: i did that on a call for ePub. especially in the phone context, the barrier can be high. <br />
* Roman: it could be difficult depending on the size of the group.<br />
* DC: this was not for a small technical point. but the larger vision so it was worth it<br />
* AT: this feels very inclusive for me. Are there statistics? i don't think people think things are broken. they just want to know how to make things better <br />
* Amy: industry standard. 25% women. we are below that in W3C Team etc. <br />
* Frank: Apple etc do %s at the end of the year. We might consider this.<br />
<br />
end: who might join, participate in PWET (Roman, Tzviya, Florian, Antonio?)</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE/201609_TPAC&diff=100126PWE/201609 TPAC2016-09-21T15:35:51Z<p>Amy: /* minutes: */</p>
<hr />
<div><br />
<br />
= TPAC session on Positive Work environment + Global Participation Enhancement =<br />
=== 21 September 2016 ===<br />
<br />
=== attending: === <br />
: Tzviya Siegman, Wiley<br />
: An Qi LI, W3C<br />
: Chunming Hu, W3C<br />
: Amy van der Hiel, W3C<br />
: Florian Rivoal, Vivliostyle, Inc.<br />
: Romain Deltou, DAISY Consortium<br />
: Frank Olivier, Microsoft Corporation<br />
: Ann Bassetti<br />
: Antonio Olmo Titos, W3C<br />
: Dave Cramer, Hachette Livre<br />
: Coralie Mercier, W3C<br />
: Vagner Diniz, Nic.br<br />
: Judy Brewer, W3C<br />
<br />
=== minutes: === <br />
* TS: I am working at Wiley<br />
* AL: New area from new re-org, international, business<br />
* CH: support AL<br />
* FR: The topic is interesting personally. I volunteered to help make connections for BusDev, recruiting people. I saw how people can run into barriers in trying to join<br />
* RD: I am in Digital publishing and WCAG. I am here because of personal interest. I think an inclusive work environment is important<br />
* FO: I work in HMTL and WebApps<br />
* AB: I have been w/ PWET since its start. I have long been concerned about global participation. If you've been in a meeting with me you've likely heard me ask people to speak more slowly. I am interested to have pwet, be that - positive work environment. Something cultural. not about punishment and process. The code of conduct is not the issue. what other things are the issue?<br />
* FR: things shouldn't have to get to the reporting place<br />
* AT: I am interested to hear more about it. having lived in Japan I've seen the Asian side of things, It can be difficult to integrate<br />
* DC: I am in digital publishing. I am interested in the dynamics of discussions. I notice some people dominate discussions and others can be afraid to speak. Even groups that do wonderful work, have welcoming environments still have concerns about everybody's voice being heard.<br />
* CM: I can understand the CoC being interpreted as punishment. I am still interested in topic since the group started in 2008. I have been staff since 99. I used to be the co chair of PWE. I am now the head of Comm but stepped down because I am focusing in other areas<br />
* VD: I'm from Brazil, fro nic.br<br />
* AB: I'm interested in how to organize this. I have heard different issues around organizing. it's a human issue. Some people dominate the talking more. It can be especially a global issue, it comes in more. 1/3 of our people here are not native english speakers. I know I'd be very quiet in a meeting held in French. certain cultures are also more quiet.<br />
* FR:: to Dave, in terms of being loud. i might be loud. but I think there are two ways of being scary. by decibel or you hear the % of market share behind (magnitude of the company they represent)<br />
* TS: I think tone is an issue more than volume. Tone is much more felt than volume. more than browser presence. For example. the other day [someone] gave a presentation. she had put in hours of work, no applause, she was just picked apart. <br />
* FR: There was no applause?<br />
* TS: no<br />
* DC: sound volume and <br />
* AL: another issue is recognition for contributions<br />
* TS: yes, acknowledgement<br />
* RD: on mailing lists, too. Sometimes the sheer volume. it may have doubled. <br />
* AL: I have heard from shy Chinese members. They are maybe not used to all email. So when they ask stupid questions. someone says "go read web page" this really hurts<br />
* FR: As a counter example - an exception not a rule. The LG from Korea joined the WG. They had a valid use case. not mature enough. Both sides showed good will. They wanted to learn and work w/ us. We showed they are not there yet. would need hand holding. luckily they got hand holding. When that happens it works brilliantly<br />
* TS: everyone needs hand holding<br />
* DC: they did everything perfectly from the start. well developed approach, they took it to the WG rather than doing it on they own. so many things self<br />
* FR: to tie to the Asian difficultly. calls are aways 1 or 2 am. sometimes it may seem there's no human to do contact.<br />
* AB: when I was on the AB, we had Asian members. there is no time zone that works when geographically set up. So we did alternating times during the year. Half the time the west coast got up 5 am or 6pm. that was convenient for Aisa. then other times it was afternoon for me but midnight for them. I can say it was very aggravating when Asian counterpart didn't show up for meeting. we didn't change month by month. that was too confusing. <br />
* TS: one other issue. maybe for AL, we have an issue attracting a large percentage of population - we don't have a lot of women. we have a diversity issue. Things not just to encourage women and people of color to join but actual outreach. at IETF they do outreach to join. they have a method to fund people. then the challenge becomes maintaining membership. Both how to make people comfortable to join and keep them comfortable to stay.<br />
* Ann: is travel covered?<br />
* Av: some of this might fall under general good behavior, politeness. a sense of openness and respect to others. there are drives to commit to not be on panels of all men<br />
* VD. a big issue is gender equality. at meeting like this one or a workshop. we should make an effort to ensure we will have always women in panels. <br />
* FR: I am a feminist, and I made this promise. and even so, I forgot about it for this panel happening tomorrow<br />
* TS: Dave and I have signed a pledge. 50% women speakers <br />
* VD:. There are procedure and process. We can go further. at the next w3c conference in Brazil. more than 1/2 women speakers. we just have to put effort in this <br />
* Av: is there an action we can have here to put this idea in front of w3c?<br />
* AB: it's a great vision to have. the difficulty is to find someone appropriately skilled. Vagner. for a conference can seek. I had to find someone at Boeing when i left. Adam was a man. the work would not appropriate for a women who doesn't know the role. working toward that goal. not sure that's realistic<br />
* AL: I wanted to ask a question. In the history of W3C. its there a document with the principle for diversity, participation, etc? For the postive work environment, for basic human things like teleconferences at tolerable working times. <br />
* CM: there is the code of ethics and conduct. you have to be decent. <br />
* AB: maybe we should review this for the revitalization<br />
* Av: there are now more best practices documents<br />
* AB: Judy Zhu worked on one, we've linked to. if we're trying to aim for diversity of male and female. international as well<br />
* FR: Ann, it does depends on who members send. In the gender composition of working group, I noticed between members and invited experts. invited experts were more balanced<br />
* JB; years ago I was invited to participate in a panel at Grace Hopper conference. it is massive now. centered around the theme of women in Tech. There were 4 standards organizations who spoke on gender balance. years ago we had done it. but it's frightening how predictable the ratio was. invited expert #s was stronger. For WG participant it was not as good. Chairs were less. at the AC level there was just Ann. and at the AB. For a long time there only one woman on w3c management. This is one reason we have PWETF. Things came out of that. I was said when looking at a new WG, we should look more broadly for chair candidates. team and international side. they weren't even considering women. It was like an automatic screen out. it was really helpful to get a reminder. comparably qualified<br />
* FR: There was something like this in a search i was recently involved in. It didn't play out well<br />
* TS: chair training might really help. <br />
* AB: chairs are crucial. <br />
* JB: it is mandatory<br />
* TZ: since I've been a chair for two years it's not been done<br />
* AB: I think we can add this back to the thinking<br />
* AL: to be sure everyone is included I'd like to the keep queue locally<br />
* TS: there needs to be chair training. didn't know this for two years.<br />
* JB: staff needs to be trained too<br />
* AQ: we might put in a team day<br />
* DC: all this is pointing to one place we don't see to have untying. on boarding. huge problem. 3 years ago at a workshop Markus said to me: your company joined you're going to be in China next month. i'm dumped into TPAC. it's like what the hell is this? i'm in this 20 year old strong culture of the CSS WG. W3C has a defined culture. cultures, even. i survived because other members took care of me. <br />
* AB: team buddy. <br />
* TS: buddies are variable. we also are lucky because we have Ivan <br />
* FR: we've touched on gender. diversity. there are women around this table. few people of color. age we seem to do ok<br />
* Av: true diversity is important. We may, as TS suggested, look at better outreach<br />
* AB: we have very little representation from south america, africa, etc<br />
* JB: at a meeting in Tunisa. we meet wonderful people. <br />
* Av: Jeff gave us not just task to update documents, he asked us to think about our aspirational goals. what kind of place we want this to be to work at. This is an area where W3C could truly lead. Diversity is a very valuable goal<br />
* AL: From the hosts. we encourage warm up calls. fresh attendance to AC and TPAC. we do this for Chinese members. to help anticipate more culture shock when join. We can guide through tools rss agent. etc. We can introduce highlights in agenda. at the end we provide tips. culturally strong WG. sometimes we talk about werewolves. they feel it helps a lot.<br />
* AB: can we reuse these materials for everyone? <br />
* AL: we do it in China. <br />
* AB: could it be generalized?<br />
* AL: we could clone practice in all hosts. talk to locals. in own their own language. every season we come up w/ script to share. the feedback from members is pretty good. it's not so daunting. they got tips. trips, travel info. weather. it makes them feel "i'm welcome". to do globally<br />
* AB; i was a third grade teacher. helping people prepare for making materials<br />
* TS: I do something similar. I was copied in early email to Rob Sanders when I joined the WG, I used the same text. Now every time someone joins I send a list of things to know: email archive, links to irc. next meeting i'll send it you. You should be able to generate it automatically. the same way I get a note when someone joins the group. <br />
* AL: yes, some templates you can customize<br />
* FR: template gets sent. <br />
* AB: we could use a modernized version of guidebook. consulted and review. could be translated into local languages. at least it would be consistent. a werewolf introduction [laughter]. no but social stuff is huge. <br />
* TS: it's how you meet people. <br />
* AB: right now we've got a group who does art. maybe next will be music. <br />
* FR: another social thing they do in css. not intentionally but since a lot of us are friends. we go to Air BnB and rent an apartment. including new comers helps<br />
* AB: though that could be to the detriment of w3c. we can't get rooms<br />
* FR: We do it at TPAC less. just individual group meetings<br />
* AL: it works for a f2f<br />
* DC: to follow up. going back to issues of invited experts. what CSS has done, we try to take care of invited experts during the meetings. if 7 go out and 5 are on expense. we it split 5 ways. Florian slept in my hotel room last time<br />
* FR: this time I am sponsored. <br />
* AL: it's good to be nice to the IEs. it's the small things.<br />
* TS: this is not so small<br />
* DC: it is evidence of the culture <br />
* AB: it's great to be supportive and friendly thought we've got a long way to go<br />
* TS: it's largely a friendly group<br />
* FR: for the chairs training and training for picking chairs. now we have to address AC. telling AC reps, don't forget to nominate women. <br />
* AL: we can put into on on-boarding. starting into next year. <br />
* CH: one of my oveserveraions. i can remember one or two years ago. Baidu they did their first member submission. they didn't know who to participate. before they joined the WG there was lots of the job done by WG. They didn't know how to show their value, how to contribute. They came up w/ a member submission. They wanted to give solutions. They also asked the local team to help them contact the WG people to help to explain what happened. the idea in this case, after that they showed they proposal face to face. They debated, is it ok? Finally since this accepted for the people who proposed. they might think their ideas were ignored. they were not sure how to change situation. now they have a lot of do and they won't put more time on it. i think in this case, what can we learn? personally. 1. i'm not sure if we can work out best practice. how to participate on WG discussions. <br />
* FR: that might be hard right now. it would have been easier a few years ago. even the people who are used to this. others think incubation. first fight in w3c. <br />
* AB: all these things are true. maybe could have a W3C wide TF on how to participate. <br />
* chun: they may get debate. alert them. if there are some good stories for them. look at best practice. <br />
* ann: wanted to hear from people who have been quite. Roman Frank Anotnio<br />
* Roman: i agree w/ ideas. another possible idea. i am in a group, f2f, tf. where the chair has the habit at end f meeting. make a round. final thoughts. appeal who haven't spoken have chance to talk. compelled. some people may prefer not to talk to but it encourages them. <br />
* ab: we lose value if they don't speak, aren't called on<br />
* D: i did that ton a call for epub. phone context barrier can be high. if this was a situation w/out quite<br />
* roman: could be size. <br />
* dc: not small technical point. larger vision. <br />
* Antoine: this feels very inclusive for me. statistics. i don't think people think things broken. how <br />
* Amy: industry standard. 25%. we are below<br />
* Frank: apple etc do %s<br />
<br />
end: who might join, participate in PWET (Roman, Tzviya, Florian, Antonio?)</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE/201609_TPAC&diff=100121PWE/201609 TPAC2016-09-21T15:15:22Z<p>Amy: /* attending: */</p>
<hr />
<div><br />
<br />
= TPAC session on Positive Work environment + Global Participation Enhancement =<br />
=== 21 September 2016 ===<br />
<br />
=== attending: === <br />
: Tzviya Siegman, Wiley<br />
: An Qi LI, W3C<br />
: Chunming Hu, W3C<br />
: Amy van der Hiel, W3C<br />
: Florian Rivoal, Vivliostyle, Inc.<br />
: Romain Deltou, DAISY Consortium<br />
: Frank Olivier, Microsoft Corporation<br />
: Ann Bassetti<br />
: Antonio Olmo Titos, W3C<br />
: Dave Cramer, Hachette Livre<br />
: Coralie Mercier, W3C<br />
: Vagner Diniz, Nic.br<br />
: Judy Brewer, W3C<br />
<br />
=== minutes: === <br />
* TS: I am working at Wiley<br />
* AL: New area from new re-org, international, business<br />
* CH: support AL<br />
* FR: The topic is interesting personally. I volunteered to help make connections for BusDev, recruiting people. I saw how people can run into barriers in trying to join<br />
* RD: I am in Digital publishing and WCAG. I am here because of personal interest. I think an inclusive work environment is important<br />
* FO: I work in HMTL and WebApps<br />
* AB: I have been w/ PWET since its start. I have long been concerned about global participation. If you've been in a meeting with me you've likely heard me ask people to speak more slowly. I am interested to have pwet, be that - positive work environment. Something cultural. not about punishment and process. The code of conduct is not the issue. what other things are the issue?<br />
* FR: things shouldn't have to get to the reporting place<br />
* AT: I am interested to hear more about it. having lived in Japan I've seen the Asian side of things, It can be difficult to integrate<br />
* DC: I am in digital publishing. I am interested in the dynamics of discussions. I notice some people dominate discussions and others can be afraid to speak. Even groups that do wonderful work, have welcoming environments still have concerns about everybody's voice being heard.<br />
* CM: I can understand the CoC being interpreted as punishment. I am still interested in topic since the group started in 2008. I have been staff since 99. I used to be the co chair of PWE. I am now the head of Comm but stepped down because I am focusing in other areas<br />
* VD: I'm from Brazil, fro nic.br<br />
* AB: I'm interested in how to organize this. I have heard different issues around organizing. it's a human issue. Some people dominate the talking more. It can be especially a global issue, it comes in more. 1/3 of our people here are not native english speakers. I know I'd be very quiet in a meeting held in French. certain cultures are also more quiet.<br />
* FR:: to Dave, in terms of being loud. i might be loud. but I think there are two ways of being scary. by decibel or you hear the % of market share behind (magnitude of the company they represent)<br />
* TS: I think tone is an issue more than volume. Tone is much more felt than volume. more than browser presence. For example. the other day [someone] gave a presentation. she had put in hours of work, no applause, she was just picked apart. <br />
* FR: There was no applause?<br />
* TS: no<br />
* DC: sound volume and <br />
* AL: another issue is recognition for contributions<br />
* TS: yes, acknowledgement<br />
* RD: on mailing lists, too. Sometimes the sheer volume. it may have doubled. <br />
* AL: I have heard from shy Chinese members. They are maybe not used to all email. So when they ask stupid questions. someone says "go read web page" this really hurts<br />
* FR: As a counter example - an exception not a rule. The LG from Korea joined the WG. They had a valid use case. not mature enough. Both sides showed good will. They wanted to learn and work w/ us. We showed they are not there yet. would need hand holding. luckily they got hand holding. When that happens it works brilliantly<br />
* TS: everyone needs hand holding<br />
* DC: they did everything perfectly from the start. well developed approach, they took it to the WG rather than doing it on they own. so many things self<br />
* FR: to tie to the Asian difficultly. calls are aways 1 or 2 am. sometimes it may seem there's no human to do contact.<br />
* AB: when I was on the AB, we had Asian members. there is no time zone that works when geographically set up. So we did alternating times during the year. Half the time the west coast got up 5 am or 6pm. that was convenient for Aisa. then other times it was afternoon for me but midnight for them. I can say it was very aggravating when Asian counterpart didn't show up for meeting. we didn't change month by month. that was too confusing. <br />
* TS: one other issue. maybe for AL, we have an issue attracting a large percentage of population - we don't have a lot of women. we have a diversity issue. Things not just to encourage women and people of color to join but actual outreach. at IETF they do outreach to join. they have a method to fund people. then the challenge becomes maintaining membership. Both how to make people comfortable to join and keep them comfortable to stay.<br />
* Ann: is travel covered?<br />
* Av: some of this might fall under general good behavior, politeness. a sense of openness and respect to others. there are drives to commit to not be on panels of all men<br />
* VD. a big issue is gender equality. at meeting like this one or a workshop. we should make an effort to ensure we will have always women in panels. <br />
* FR: I am a feminist, and I made this promise. and even so, I forgot about it for this panel happening tomorrow<br />
* TS: Dave and I have signed a pledge. 50% women speakers <br />
* VD:. There are procedure and process. We can go further. at the next w3c conference in Brazil. more than 1/2 women speakers. we just have to put effort in this <br />
* Av: is there an action we can have here to put this idea in front of w3c?<br />
* AB: it's a great vision to have. the difficulty is to find someone appropriately skilled. Vagner. for a conference can seek. I had to find someone at Boeing when i left. Adam was a man. the work would not appropriate for a women who doesn't know the role. working toward that goal. not sure that's realistic<br />
* AL: I wanted to ask a question. In the history of w3c. its there a document with the principle for diversity, participation, etc? For the postive work environment, for basic human things like teleconferences at tolerable working times. <br />
* CM: there is the code of ethics and conduct, you have to be decent. <br />
* AB: maybe we should review this for the revitalization<br />
* Av: there are now more best practices documents<br />
* AB: Judy Zhu worked on one, we've linked to. if we're trying to aim for diversity of male and female. international as well<br />
* FR: Ann, it does depends on who members send. In the gender composition of working group, I noticed between members and invited experts. invited experts were more balanced<br />
* JB; years ago I was invited to participate in a panel at Grace Hopper conference. it is massive now. centered around the theme of women in Tech. There were 4 standards organizations who spoke on gender balance. years ago we had done it. but it's frightening how predictable the ratio was. invited expert #s was stronger. For WG participant it was not as good. Chairs were less. at the AC level there was just Ann. and at the AB. For a long time there only one woman on w3c management. This is one reason we have PWETF. Things came out of that. I was said when looking at a new WG, we should look more broadly for chair candidates. team and international side. they weren't even considering women. It was like an automatic screen out. it was really helpful to get a reminder. comparably qualified<br />
* FR: There was something like this in a search i was recently involved in. It didn't play out well<br />
* TS: chair training might really help. <br />
* AB: chairs are crucial. <br />
* JB: it is mandatory<br />
* TZ: since I've been a chair for two years it's not been done<br />
* AB: I think we can add this back to the thinking<br />
* AL: to be sure everyone is included I'd like to the keep queue locally<br />
* TS: there needs to be chair training. didn't know this for two years.<br />
* JB: staff needs to be trained too<br />
* AQ: we might put in a team day<br />
* DC: all this is pointing to one place we don't see to have untying. on boarding. huge problem. 3 years ago at a workshop Markus said to me: your company joined you're going to be in China next month. i'm dumped into TPAC. it's like what the hell is this? i'm in this 20 year old strong culture of the CSS WG. W3C has a defined culture. cultures, even. i survived because other members took care of me. <br />
* AB: team buddy. <br />
* TS: buddies are variable. we also are lucky because we have Ivan <br />
* FR: we've touched on gender. diversity. there are women around this table. few people of color. age we seem to do ok<br />
* Av: true diversity is important. We may, as TS suggested, look at better outreach<br />
* AB: we have very little representation from south america, africa, etc<br />
* JB: at a meeting in Tunisa. we meet wonderful people. <br />
* Av: Jeff gave us not just task to update documents, he asked us to think about our aspirational goals. what kind of place we want this to be to work at. This is an area where W3C could truly lead. Diversity is a very valuable goal<br />
* AL: From the hosts. we encourage warm up calls. fresh attendance to AC and TPAC. we do this for Chinese members. to help anticipate more culture shock when join. We can guide through tools rss agent. etc. We can introduce highlights in agenda. at the end we provide tips. culturally strong WG. sometimes we talk about werewolves. they feel it helps a lot.<br />
* AB: can we reuse these materials for everyone? <br />
* aq: we do it in chins. <br />
* ab: generalize. <br />
* aq: clone practice in all hosts. talk to locals. in own lanaguet. every season we come up w/ script to share. the feedback from embers is pretty good. not so daunting. got tips. trips, travel info. weather. i'm welcome. it's not something. to do globally<br />
* AB; i was a third grade teacher. helping people prepare for making materials<br />
* Ts: something similar. copied email to rob sanders. when joined wg. used same text. every time someone joins. things to know. email archive. links to irc. next meeting on this date. i'll send it you . should be able to generate it. same way someone joins group. <br />
* aq: some templates. customize<br />
* fl: template gets sent. <br />
* ab: modernized version of guidebook. consulted and review. could be translated into local lunges. at least would be consistent. a werewolf introduction. social stuff is huge. <br />
* ts: it's how you meet people. <br />
* ab; art, music. <br />
* f: another social thing in css. not intentionally, since a lot of us are friends. we go to air bnb renting an apartment. including new comers<br />
* ab: detriment to w3c. we can't get rooms<br />
* f: pac less. individual groups<br />
* aq: works for f2f<br />
* f: i put myself on the quue<br />
* dc: follow up. going back to issues of invited expert. css done. we try to take care of i.e. during the meetings. if 7 go out. 5 are on expense. we split 5 ways. florian sleep in hotel <br />
* fl: this time sponsored. <br />
* aq: be nice to i.e.<br />
* ts: not so small<br />
* dc: evidence of culture <br />
* ab: supportive friendly, long way to go<br />
* ts: friendly group<br />
* f: chairs traingin and training for picking chairs. now we have ac. telling ac reps, don't forget to nominate women. <br />
* aq: put into on boarding. starting into next year. <br />
* chunming. one of my oveserveraions. i can remember one or two years ago. baidu. first member submission. don't know who to participate. before joined wg. lots of job done by wg. don't know how to show value, contribute. came up w/ member submission. give solutions. also asked th local team to help them contact wg people to hep to explain wha happened. the idea in this case, after that they showed their props in g face to face. debate is it ok. finally since this accepted by. for the people who proposed. they might think their ideas were ignored. not sure ow to change situation. they have a lot of do. won't put more time on it. i think in this case, what can we learn. personally. 1. not sure if we can workout best practice. how to participate on wg discussions. <br />
* f: hard right now. easier a few years ago. even the people who are used to this. others think incubation. first fight in w3c. <br />
* ab: all things true. maybe could have a w3c wide tf on how to participate. <br />
* chun: they may get debate. alert them. if there are some good stories for them. look at best practice. <br />
* ann: wanted to hear from people who have been quite. Roman Frank Anotnio<br />
* Roman: i agree w/ ideas. another possible idea. i am in a group, f2f, tf. where the chair has the habit at end f meeting. make a round. final thoughts. appeal who haven't spoken have chance to talk. compelled. some people may prefer not to talk to but it encourages them. <br />
* ab: we lose value if they don't speak, aren't called on<br />
* D: i did that ton a call for epub. phone context barrier can be high. if this was a situation w/out quite<br />
* roman: could be size. <br />
* dc: not small technical point. larger vision. <br />
* Antoine: this feels very inclusive for me. statistics. i don't think people think things broken. how <br />
* Amy: industry standard. 25%. we are below<br />
* Frank: apple etc do %s<br />
<br />
end: who might join, participate in PWET (Roman, Tzviya, Florian, Antonio?)</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE/201609_TPAC&diff=100120PWE/201609 TPAC2016-09-21T15:14:45Z<p>Amy: </p>
<hr />
<div><br />
<br />
= TPAC session on Positive Work environment + Global Participation Enhancement =<br />
=== 21 September 2016 ===<br />
<br />
=== attending: === <br />
: Tzviya Siegman, Wiley<br />
: An Qi LI, W3C<br />
: Chunming Hu, W3C<br />
: Amy van der Hiel, W3C<br />
: Florian Rivoal, Vivliostyle, Inc.<br />
: Romain Deltou, DAISY Consortium<br />
: Frank Olivier, Microsoft Corporation<br />
: Ann Bassetti<br />
: Antonio Olmo Titos, W3C<br />
: Dave Cramer, Hachette Livre<br />
: Coralie Mercier, W3C<br />
: Vagner Diniz, Nic.br<br />
<br />
=== minutes: === <br />
* TS: I am working at Wiley<br />
* AL: New area from new re-org, international, business<br />
* CH: support AL<br />
* FR: The topic is interesting personally. I volunteered to help make connections for BusDev, recruiting people. I saw how people can run into barriers in trying to join<br />
* RD: I am in Digital publishing and WCAG. I am here because of personal interest. I think an inclusive work environment is important<br />
* FO: I work in HMTL and WebApps<br />
* AB: I have been w/ PWET since its start. I have long been concerned about global participation. If you've been in a meeting with me you've likely heard me ask people to speak more slowly. I am interested to have pwet, be that - positive work environment. Something cultural. not about punishment and process. The code of conduct is not the issue. what other things are the issue?<br />
* FR: things shouldn't have to get to the reporting place<br />
* AT: I am interested to hear more about it. having lived in Japan I've seen the Asian side of things, It can be difficult to integrate<br />
* DC: I am in digital publishing. I am interested in the dynamics of discussions. I notice some people dominate discussions and others can be afraid to speak. Even groups that do wonderful work, have welcoming environments still have concerns about everybody's voice being heard.<br />
* CM: I can understand the CoC being interpreted as punishment. I am still interested in topic since the group started in 2008. I have been staff since 99. I used to be the co chair of PWE. I am now the head of Comm but stepped down because I am focusing in other areas<br />
* VD: I'm from Brazil, fro nic.br<br />
* AB: I'm interested in how to organize this. I have heard different issues around organizing. it's a human issue. Some people dominate the talking more. It can be especially a global issue, it comes in more. 1/3 of our people here are not native english speakers. I know I'd be very quiet in a meeting held in French. certain cultures are also more quiet.<br />
* FR:: to Dave, in terms of being loud. i might be loud. but I think there are two ways of being scary. by decibel or you hear the % of market share behind (magnitude of the company they represent)<br />
* TS: I think tone is an issue more than volume. Tone is much more felt than volume. more than browser presence. For example. the other day [someone] gave a presentation. she had put in hours of work, no applause, she was just picked apart. <br />
* FR: There was no applause?<br />
* TS: no<br />
* DC: sound volume and <br />
* AL: another issue is recognition for contributions<br />
* TS: yes, acknowledgement<br />
* RD: on mailing lists, too. Sometimes the sheer volume. it may have doubled. <br />
* AL: I have heard from shy Chinese members. They are maybe not used to all email. So when they ask stupid questions. someone says "go read web page" this really hurts<br />
* FR: As a counter example - an exception not a rule. The LG from Korea joined the WG. They had a valid use case. not mature enough. Both sides showed good will. They wanted to learn and work w/ us. We showed they are not there yet. would need hand holding. luckily they got hand holding. When that happens it works brilliantly<br />
* TS: everyone needs hand holding<br />
* DC: they did everything perfectly from the start. well developed approach, they took it to the WG rather than doing it on they own. so many things self<br />
* FR: to tie to the Asian difficultly. calls are aways 1 or 2 am. sometimes it may seem there's no human to do contact.<br />
* AB: when I was on the AB, we had Asian members. there is no time zone that works when geographically set up. So we did alternating times during the year. Half the time the west coast got up 5 am or 6pm. that was convenient for Aisa. then other times it was afternoon for me but midnight for them. I can say it was very aggravating when Asian counterpart didn't show up for meeting. we didn't change month by month. that was too confusing. <br />
* TS: one other issue. maybe for AL, we have an issue attracting a large percentage of population - we don't have a lot of women. we have a diversity issue. Things not just to encourage women and people of color to join but actual outreach. at IETF they do outreach to join. they have a method to fund people. then the challenge becomes maintaining membership. Both how to make people comfortable to join and keep them comfortable to stay.<br />
* Ann: is travel covered?<br />
* Av: some of this might fall under general good behavior, politeness. a sense of openness and respect to others. there are drives to commit to not be on panels of all men<br />
* VD. a big issue is gender equality. at meeting like this one or a workshop. we should make an effort to ensure we will have always women in panels. <br />
* FR: I am a feminist, and I made this promise. and even so, I forgot about it for this panel happening tomorrow<br />
* TS: Dave and I have signed a pledge. 50% women speakers <br />
* VD:. There are procedure and process. We can go further. at the next w3c conference in Brazil. more than 1/2 women speakers. we just have to put effort in this <br />
* Av: is there an action we can have here to put this idea in front of w3c?<br />
* AB: it's a great vision to have. the difficulty is to find someone appropriately skilled. Vagner. for a conference can seek. I had to find someone at Boeing when i left. Adam was a man. the work would not appropriate for a women who doesn't know the role. working toward that goal. not sure that's realistic<br />
* AL: I wanted to ask a question. In the history of w3c. its there a document with the principle for diversity, participation, etc? For the postive work environment, for basic human things like teleconferences at tolerable working times. <br />
* CM: there is the code of ethics and conduct, you have to be decent. <br />
* AB: maybe we should review this for the revitalization<br />
* Av: there are now more best practices documents<br />
* AB: Judy Zhu worked on one, we've linked to. if we're trying to aim for diversity of male and female. international as well<br />
* FR: Ann, it does depends on who members send. In the gender composition of working group, I noticed between members and invited experts. invited experts were more balanced<br />
* JB; years ago I was invited to participate in a panel at Grace Hopper conference. it is massive now. centered around the theme of women in Tech. There were 4 standards organizations who spoke on gender balance. years ago we had done it. but it's frightening how predictable the ratio was. invited expert #s was stronger. For WG participant it was not as good. Chairs were less. at the AC level there was just Ann. and at the AB. For a long time there only one woman on w3c management. This is one reason we have PWETF. Things came out of that. I was said when looking at a new WG, we should look more broadly for chair candidates. team and international side. they weren't even considering women. It was like an automatic screen out. it was really helpful to get a reminder. comparably qualified<br />
* FR: There was something like this in a search i was recently involved in. It didn't play out well<br />
* TS: chair training might really help. <br />
* AB: chairs are crucial. <br />
* JB: it is mandatory<br />
* TZ: since I've been a chair for two years it's not been done<br />
* AB: I think we can add this back to the thinking<br />
* AL: to be sure everyone is included I'd like to the keep queue locally<br />
* TS: there needs to be chair training. didn't know this for two years.<br />
* JB: staff needs to be trained too<br />
* AQ: we might put in a team day<br />
* DC: all this is pointing to one place we don't see to have untying. on boarding. huge problem. 3 years ago at a workshop Markus said to me: your company joined you're going to be in China next month. i'm dumped into TPAC. it's like what the hell is this? i'm in this 20 year old strong culture of the CSS WG. W3C has a defined culture. cultures, even. i survived because other members took care of me. <br />
* AB: team buddy. <br />
* TS: buddies are variable. we also are lucky because we have Ivan <br />
* FR: we've touched on gender. diversity. there are women around this table. few people of color. age we seem to do ok<br />
* Av: true diversity is important. We may, as TS suggested, look at better outreach<br />
* AB: we have very little representation from south america, africa, etc<br />
* JB: at a meeting in Tunisa. we meet wonderful people. <br />
* Av: Jeff gave us not just task to update documents, he asked us to think about our aspirational goals. what kind of place we want this to be to work at. This is an area where W3C could truly lead. Diversity is a very valuable goal<br />
* AL: From the hosts. we encourage warm up calls. fresh attendance to AC and TPAC. we do this for Chinese members. to help anticipate more culture shock when join. We can guide through tools rss agent. etc. We can introduce highlights in agenda. at the end we provide tips. culturally strong WG. sometimes we talk about werewolves. they feel it helps a lot.<br />
* AB: can we reuse these materials for everyone? <br />
* aq: we do it in chins. <br />
* ab: generalize. <br />
* aq: clone practice in all hosts. talk to locals. in own lanaguet. every season we come up w/ script to share. the feedback from embers is pretty good. not so daunting. got tips. trips, travel info. weather. i'm welcome. it's not something. to do globally<br />
* AB; i was a third grade teacher. helping people prepare for making materials<br />
* Ts: something similar. copied email to rob sanders. when joined wg. used same text. every time someone joins. things to know. email archive. links to irc. next meeting on this date. i'll send it you . should be able to generate it. same way someone joins group. <br />
* aq: some templates. customize<br />
* fl: template gets sent. <br />
* ab: modernized version of guidebook. consulted and review. could be translated into local lunges. at least would be consistent. a werewolf introduction. social stuff is huge. <br />
* ts: it's how you meet people. <br />
* ab; art, music. <br />
* f: another social thing in css. not intentionally, since a lot of us are friends. we go to air bnb renting an apartment. including new comers<br />
* ab: detriment to w3c. we can't get rooms<br />
* f: pac less. individual groups<br />
* aq: works for f2f<br />
* f: i put myself on the quue<br />
* dc: follow up. going back to issues of invited expert. css done. we try to take care of i.e. during the meetings. if 7 go out. 5 are on expense. we split 5 ways. florian sleep in hotel <br />
* fl: this time sponsored. <br />
* aq: be nice to i.e.<br />
* ts: not so small<br />
* dc: evidence of culture <br />
* ab: supportive friendly, long way to go<br />
* ts: friendly group<br />
* f: chairs traingin and training for picking chairs. now we have ac. telling ac reps, don't forget to nominate women. <br />
* aq: put into on boarding. starting into next year. <br />
* chunming. one of my oveserveraions. i can remember one or two years ago. baidu. first member submission. don't know who to participate. before joined wg. lots of job done by wg. don't know how to show value, contribute. came up w/ member submission. give solutions. also asked th local team to help them contact wg people to hep to explain wha happened. the idea in this case, after that they showed their props in g face to face. debate is it ok. finally since this accepted by. for the people who proposed. they might think their ideas were ignored. not sure ow to change situation. they have a lot of do. won't put more time on it. i think in this case, what can we learn. personally. 1. not sure if we can workout best practice. how to participate on wg discussions. <br />
* f: hard right now. easier a few years ago. even the people who are used to this. others think incubation. first fight in w3c. <br />
* ab: all things true. maybe could have a w3c wide tf on how to participate. <br />
* chun: they may get debate. alert them. if there are some good stories for them. look at best practice. <br />
* ann: wanted to hear from people who have been quite. Roman Frank Anotnio<br />
* Roman: i agree w/ ideas. another possible idea. i am in a group, f2f, tf. where the chair has the habit at end f meeting. make a round. final thoughts. appeal who haven't spoken have chance to talk. compelled. some people may prefer not to talk to but it encourages them. <br />
* ab: we lose value if they don't speak, aren't called on<br />
* D: i did that ton a call for epub. phone context barrier can be high. if this was a situation w/out quite<br />
* roman: could be size. <br />
* dc: not small technical point. larger vision. <br />
* Antoine: this feels very inclusive for me. statistics. i don't think people think things broken. how <br />
* Amy: industry standard. 25%. we are below<br />
* Frank: apple etc do %s<br />
<br />
end: who might join, participate in PWET (Roman, Tzviya, Florian, Antonio?)</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE/201609_TPAC&diff=100093PWE/201609 TPAC2016-09-21T13:00:59Z<p>Amy: messy minutes of session discussion</p>
<hr />
<div><br />
Tzviya Wiley<br />
An Qi<br />
chun min<br />
amy<br />
Florian Rival<br />
Romain, Daisy<br />
Frank, MS<br />
Ann<br />
Antonio<br />
Dave Kramer <br />
cm<br />
Vagner<br />
<br />
Tzviya<br />
Angel: work from new re-org, international, business<br />
chunming:<br />
FR: topic interesting personally. volunteered to BusDev, recruiting people. run into barriers, try to join<br />
Romain: Digital publishing, Wcag. here because of personal interest. inclusive work environment importune<br />
Frank: HMTL WebApps<br />
AB: been w/ pwet. long been concerned global. speak more slowly. interest to have pwet, be that. cultural. not about punishment and process. coc. not the issue. what other things issue<br />
FR: shouldn't get to that<br />
Antonio; hear more about it. having seen Asian side of things, difficult to integrate<br />
Dave: digital publishing. interested in dynamics of discussions. some people dominate discussions. afraid to speak. even groups that do wonderful work. have welcoming enviormentments. have concerns about everybody's voice being heard.<br />
cm: interpreted punishment. still interested in topic. 2008. staff since 99. used to be the co chair pwe. head of comm. because focusing <br />
VD: brazil. nic.br<br />
<br />
AB: how to organize. heard organize. human issue. dominate talk more. global issue comes in more. 1/3 people here are native english speakers. i'd be very quiet in language held in French. certain cultures more quiet.<br />
Florian: to Dave, in terms of being loud. i might be. two ways of being scary. by decibel. or you hear the % of market share behind (magnitude of company)<br />
TS: tone more than volume. tone is much more felt than volume. more than browser presence. example. someone gave presentation. just picked apart. <br />
Florian: not appaluse<br />
Dave: sound volume and <br />
An Qi: recognition for contributions<br />
Tzviya: acknowledgement<br />
roman: mailing lists, volume. it may have doubled. <br />
An Qi: heard from shy chinese members. not used to all email. so when ask stupid questions. someone says "go read web page" this really hurts<br />
Florian: counter example. an exception not a rule. the LG from Korea. joined from WG. valid use case. not mature enough. both showed good will. to learn and work w/ us. showed not there yet. would need hand holding. luckily they got hand holding works brilliantly<br />
TS: everyone needs hand holding<br />
Dave: they did everything perfectly from start. well developed approach. to WG rathe than own. so many things self<br />
Florian: to tie to Asian difficultly. always 1 or 2 am. no human to do contact.<br />
Ann: when on AB. had Asian members. there is no time zone that works when geographically set up. alternating year. half time west coast got up 5 am or 6pm. that was convenient for Aisa. then other times it was afternoon for me but midnight for them. it was very aggrivating. when Asian counterpart didn't show up for meeting. we didn't change month by month. that was too confusing. <br />
<br />
Tzviya. one other issue. maybe for an qi, we have an issue attracting a large percentage of population. we don't have a lot of women. we have a diversity issue. things not just to encourage women and people of clor to join. actual outreach at IETF to join. how to fund people. what they do. then the challenge becomes maintain gin membership. how to make comfortable keep comfortable. ASF.<br />
Ann: travel covered. <br />
tzviay<br />
AmY; politeness. openness. <br />
Vagner. gender equality. meeting like this one. workshop. we should make an effort to ensure we will have always women in panels. <br />
<br />
Florian: made this promise. forgot panel. <br />
T: dave and I have signed. 50% women speakers <br />
Vagner. procedure. process. go further. tnext w3c conference. more than 1/2 women speakers. we just have to put effort in this <br />
Amy: action: put in front of w3c<br />
<br />
Ann: great vision to have. find someone appropriately skilled Vagner. for conference. I had to find someone at Boeing when i left. Adam was a man. not appropriate for a women who doesn't know the role. working toward that goal. not sure that's realistic<br />
An Qi: ask question. history of w3c. document. the principle for diversity. participation. postive work envoromnt. basic human things. teleconferences tolerable working times. <br />
cm: code of ethics and conduct. have to be decent. <br />
Ab: review for renew<br />
<br />
Amy: best practices<br />
<br />
Ann: Judy Zhu linked to. if we're trying to aim for diversity of male and female. international <br />
<br />
Florian: Ann, depends on who members send. gender composition of working group. members and invited experts. invited experts were more balanced<br />
<br />
JB; years ago i was invited to participate in a panel at Grace Hopper conference. massive now. centered around them of women. 4 standards organizations. on gender balance. years ago we had done it. frightening how predictable. invited was stronger. wG participants. was not as good. hairs was less. Ac and then there Ann. AB. only one woman on w3c managemetn. one reason we have pewter. things came out of that. new wg. look more broadly for chair candidates. team and intitiatonrs side. they weren't even considering women. automatic screen out. it was really helpful to get a reminder. comparably qualified<br />
<br />
Floridan: recently involved. didn't play out well<br />
<br />
TS: chair training. owe. <br />
<br />
AB: chairs are crucial. <br />
JB: mandatory<br />
TZ: since chair not done<br />
AB: add back to thinking<br />
AQ: to include: keep queen locally<br />
<br />
TS: need chair training. didn't know for two years.<br />
JB: staff to be trained<br />
AQ: put in team day<br />
Dc: all this is pointing to one place we don't see to have untying. on boarding. huge problem that 3 years ago at a workshop. markus said your company joined you're going to be in china next month. i'm dumped into pac. it's like what the hell is this? i'm in this 20 year old strong culture. css wg. w3c has a defined culture. cultures. i survived because other members took care of me. <br />
AB: team buddy. <br />
ts: buddy is variable. we also have Ivan <br />
F: we've touched on gender. diversity. there are women around this table. few people of color. age we seem to do ok<br />
Amy: true diversity. outreach<br />
Ab: very little south america, africa, etc<br />
JB: don't see interest. meeting in Tunis. <br />
Amy: aspirational<br />
AQ: hosts. warm up calls. fresh attendance to A and tpa. do for chinese. anticipate more culture shock when join .guide through tools rss agent. introduce highlights in agenda. at the end we provide tips. culturaly strong wg. sometimes we talk about werewolves. they feel it helps a lot.<br />
ab: can we reuse these materials for everyone. <br />
aq: we do it in chins. <br />
ab: generalize. <br />
aq: clone practice in all hosts. talk to locals. in own lanaguet. every season we come up w/ script to share. the feedback from embers is pretty good. not so daunting. got tips. trips, travel info. weather. i'm welcome. it's not something. to do globally<br />
<br />
AB; i was a third grade teacher. helping people prepare for making materials<br />
Ts: something similar. copied email to rob sanders. when joined wg. used same text. every time someone joins. things to know. email archive. links to irc. next meeting on this date. i'll send it you . should be able to generate it. same way someone joins group. <br />
aq: some templates. customize<br />
fl: template gets sent. <br />
ab: modernized version of guidebook. consulted and review. could be translated into local lunges. at least would be consistent. a werewolf introduction. social stuff is huge. <br />
ts: it's how you meet people. <br />
ab; art, music. <br />
f: another social thing in css. not intentionally, since a lot of us are friends. we go to air bnb renting an apartment. including new comers<br />
ab: detriment to w3c. we can't get rooms<br />
f: pac less. individual groups<br />
aq: works for f2f<br />
f: i put myself on the quue<br />
dc: follow up. going back to issues of invited expert. css done. we try to take care of i.e. during the meetings. if 7 go out. 5 are on expense. we split 5 ways. florian sleep in hotel <br />
fl: this time sponsored. <br />
aq: be nice to i.e.<br />
ts: not so small<br />
dc: evidence of culture <br />
ab: supportive friendly, long way to go<br />
ts: friendly group<br />
f: chairs traingin and training for picking chairs. now we have ac. telling ac reps, don't forget to nominate women. <br />
aq: put into on boarding. starting into next year. <br />
chunming. one of my oveserveraions. i can remember one or two years ago. baidu. first member submission. don't know who to participate. before joined wg. lots of job done by wg. don't know how to show value, contribute. came up w/ member submission. give solutions. also asked th local team to help them contact wg people to hep to explain wha happened. the idea in this case, after that they showed their props in g face to face. debate is it ok. finally since this accepted by. for the people who proposed. they might think their ideas were ignored. not sure ow to change situation. they have a lot of do. won't put more time on it. i think in this case, what can we learn. personally. 1. not sure if we can workout best practice. how to participate on wg discussions. <br />
f: hard right now. easier a few years ago. even the people who are used to this. others think incubation. first fight in w3c. <br />
ab: all things true. maybe could have a w3c wide tf on how to participate. <br />
chun: they may get debate. alert them. if there are some good stories for them. look at best practice. <br />
ann: wanted to hear from people who have been quite. Roman Frank Anotnio<br />
Roman: i agree w/ ideas. another possible idea. i am in a group, f2f, tf. where the chair has the habit at end f meeting. make a round. final thoughts. appeal who haven't spoken have chance to talk. compelled. some people may prefer not to talk to but it encourages them. <br />
ab: we lose value if they don't speak, aren't called on<br />
D: i did that ton a call for epub. phone context barrier can be high. if this was a situation w/out quite<br />
roman: could be size. <br />
dc: not small technical point. larger vision. <br />
Antoine: this feels very inclusive for me. statistics. i don't think people think things broken. how <br />
<br />
Amy: industry standard. 25%. we are below<br />
Frank: apple etc do %s</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE&diff=100085PWE2016-09-21T12:05:56Z<p>Amy: /* PWETF discussion(s) notes */</p>
<hr />
<div>== Positive Work Environment ==<br />
Public wiki regarding Positive Work Environment at W3C.<br />
<br />
== W3C Codes of Conduct ==<br />
The [https://www.w3.org/Consortium/pwe/ Positive Work Environment Task Force] owns:<br />
<br />
* the [https://www.w3.org/Consortium/cepc/ Code of Ethics and Professional Conduct (CEPC)]<br />
<br />
* the draft [https://www.w3.org/wiki/PWE/Conf-code Conference code]<br />
<br />
* the [https://www.w3.org/Consortium/pwe/#Procedures Procedures] for implementing these codes<br />
<br />
== Best Practices ==<br />
<br />
A collection of Best Practices pages for meetings, speakers and public events<br />
<br />
* [https://www.w3.org/wiki/Speaker_Resources#Speakers_Guidelines Speaker Guidelines from Coralie]<br />
<br />
* [https://www.w3.org/wiki/Global_Topic Thoughts about making W3C more global developed by an Advisory Board task force (Judy Zhu, Jay Kishigami, others?)]<br />
<br />
* [https://www.w3.org/wiki/Moderating_Meetings Moderating Meetings] by AB (by Chaals)<br />
<br />
* Draft [[Meetings Best Practices document]] for meetings (to be prepared by TPAC 2016)<br />
<br />
== PWETF discussion(s) notes ==<br />
This section will be for collecting PWETF notes and discussions<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_AC notes from BOF session at AC meeting, MIT, March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_badges ideas for name badges March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201609_TPAC Breakout Session from TPAC 2016]<br />
<br />
== Outline for renewing Task Force, reviewing goals, vision, documents, and next steps ==<br />
<br />
From May 2016: [https://www.w3.org/wiki/PWE/201604_outline ideas for renewing Task Force, reviewing goals, vision, documents, and next steps ]</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE&diff=100084PWE2016-09-21T12:05:03Z<p>Amy: /* PWETF discussion(s) notes */</p>
<hr />
<div>== Positive Work Environment ==<br />
Public wiki regarding Positive Work Environment at W3C.<br />
<br />
== W3C Codes of Conduct ==<br />
The [https://www.w3.org/Consortium/pwe/ Positive Work Environment Task Force] owns:<br />
<br />
* the [https://www.w3.org/Consortium/cepc/ Code of Ethics and Professional Conduct (CEPC)]<br />
<br />
* the draft [https://www.w3.org/wiki/PWE/Conf-code Conference code]<br />
<br />
* the [https://www.w3.org/Consortium/pwe/#Procedures Procedures] for implementing these codes<br />
<br />
== Best Practices ==<br />
<br />
A collection of Best Practices pages for meetings, speakers and public events<br />
<br />
* [https://www.w3.org/wiki/Speaker_Resources#Speakers_Guidelines Speaker Guidelines from Coralie]<br />
<br />
* [https://www.w3.org/wiki/Global_Topic Thoughts about making W3C more global developed by an Advisory Board task force (Judy Zhu, Jay Kishigami, others?)]<br />
<br />
* [https://www.w3.org/wiki/Moderating_Meetings Moderating Meetings] by AB (by Chaals)<br />
<br />
* Draft [[Meetings Best Practices document]] for meetings (to be prepared by TPAC 2016)<br />
<br />
== PWETF discussion(s) notes ==<br />
This section will be for collecting PWETF notes and discussions<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_AC notes from BOF session at AC meeting, MIT, March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_badges ideas for name badges March 2016]<br />
<br />
* [Breakout Session from TPAC 2016]<br />
<br />
== Outline for renewing Task Force, reviewing goals, vision, documents, and next steps ==<br />
<br />
From May 2016: [https://www.w3.org/wiki/PWE/201604_outline ideas for renewing Task Force, reviewing goals, vision, documents, and next steps ]</div>Amyhttps://www.w3.org/wiki/index.php?title=TPAC/2016&diff=100083TPAC/20162016-09-21T11:27:33Z<p>Amy: /* Breakout Schedule (session grid) */</p>
<hr />
<div>__TOC__<br />
<br />
<span style="color:#ff0000">'''*** DRAFT ***'''</span><br />
<br />
<div class="h-event"><br />
'''<dfn span class="p-name">[http://www.w3.org/2016/09/TPAC/ TPAC2016]</dfn>''' takes place <time class="dt-start" datetime="2016-09-19">2016-09-19</time>…<time class="dt-end" datetime="2016-09-23">23</time> M-F in <span class="p-location">Lisbon, Portugal</span>.<br />
</div><br />
<br />
<div class="h-event vevent"><br />
On <span class="dt-start" datetime="2016-09-19"><span class="value-title" title="2016-09-21">Wednesday, 21 September</span></span>, we hold a "<span class="p-name summary">Plenary Day.</span>" <span class="p-description description">As we did for [[TPAC2015]], we will organize most of the day as "camp-style" breakout sessions. We invite you to add to or comment on [[TPAC2016/SessionIdeas | Breakout session ideas]]. The people at the meeting that day will build the [[#Session_Grid | Session Grid]], drawing from ideas socialized in advance and new ideas proposed the day of the meeting.</span><br />
</div><br />
<br />
* Questions? See the [http://www.w3.org/wiki/TPAC2016/FAQ FAQ].<br />
* See Also past [[TPAC]] meetings.<br />
<br />
== Wednesday 21 September Plenary Day Schedule ==<br />
<br />
* Plenary sessions take place at [http://www.lisboacc.pt/irj/portal/lisboacc?lang=en Centro de congressos de lisboa]. See [https://www.w3.org/2016/09/TPAC/schedule.html schedule].<br />
* Breakout sessions take place in [http://www.w3.org/wiki/TPAC2016/FAQ#What_are_the_breakout_room_sizes.3F nearby rooms].<br />
* The lunch space accommodates slightly fewer people than registered; therefore breakout sessions overlap lunch time on each end.<br />
<br />
<span style="color:#ff0000">Proposed schedule:</span><br />
<div id="schedule"><br />
* ''08:00-08:30: Registration''<br />
* 08:30-08:35: '''Welcome''' - Jeff Jaffe<br />
* 08:35-09:05: '''Redecentralization of the Web''' - Tim Berners-Lee<br />
* 09:05-09:15: '''Data Breach, Reaction and Response'''(*) - Ted Guild<br />
* 09:15-10:00: '''Breakout preparation''' + '''last additions to [[TPAC2016/SessionIdeas | Breakout session ideas]]''' (Coralie Mercier)<br />
* ''09:15-10:00: Coffee break (**) - Hall 4, First Floor''<br />
* 10:00-11:00: '''Breakouts''' (see grid below)<br />
* 11:00-12:00: '''Breakouts''' (see grid below)<br />
* ''11:30-14:00: Lunch - Restaurant, First Floor'' <br />
* 13:00-14:00: '''Breakouts''' (see grid below)<br />
* 14:00-15:00: '''Breakouts''' (see grid below)<br />
* ''15:00-15:30: Coffee break - Hall 4, First Floor''<br />
* 15:30-16:30: '''Breakouts''' (see grid below)<br />
* 16:30-18:00: '''Breakout reports'''<br />
* ''18:30-21:30: Reception - Foyer E''<br />
** ''20:45-21:20: ForEveryone.net - Auditorium VI and VII'' ('''Private showing''' of a 35-minute documentary film about Sir Tim Berners-Lee, by Academy Award winning director Jessica Yu, which gives a history of the Web as well as a call to protect its future and features Tim, his family and colleagues including W3C CEO, Jeff Jaffe.)<br />
<br />
(*) Introduction to subsequent Breakout session; if you're a security expert, please consider signing up.<br><br />
(**) Breakout preparation and morning break overlap.<br />
</div><br />
<br />
=== Breakout Schedule (session grid) ===<br />
{| class="zebra"<br />
|-<br />
! Room (capacity)/Slots <br />
! 10:00-11:00 <br />
! 11:00-12:00<br />
! 13:00-14:00<br />
! 14:00-15:00<br />
! 15:30-16:30<br />
|-<br />
! Auditorium VI & VII, Ground Floor (48) <br />
| <br />
| <br />
| Positive Work environment + Global Participation Enhancement<br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Privacy_compliance_in_the_EU_using_W3C_Tracking_Protection DNT]</span><br />
|<br />
|-<br />
! 5A, Hall 5, First Floor (48) <br />
| Web VR<br />
| Decentralize + social web (#social)<br />
| WICG<br />
| Publications, Manifests, etc. (apps or docs)<br />
| Apache Annotator (W3C + ASF)<br />
|- <br />
! 5B, Hall 5, First Floor (48) <br />
| <br />
| <br />
| <br />
|<br />
| Thumbnails in video<br />
|-<br />
! 5C, Hall 5, First Floor (48) <br />
| <br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#HTTPS_Migration_in_Local_Network HTTPS migration in local network]<br/>([https://www.w3.org/2016/09/21-https-local-minutes.html Minutes])<br />
| Block chain (intro, use cases & reqs)<br />
| WebIDL (Tobie)<br />
| Art! (tired of geek work? Take an art break!) AnnB, Coralie, others<br />
|-<br />
! Auditorium III, First Floor (30) <br />
| Verifiable Claims WG proposal<br />
| <br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Web_of_Things_PlugFest_Demos_.28Outreach.40TPAC.29 WoT PlugFest Demo Pitch]</span><br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Web_of_Things_PlugFest_Demos_.28Outreach.40TPAC.29 WoT PlugFest Demo]</span><br />
|<br />
|-<br />
! Auditorium IV, First Floor (30) <br />
| <br />
| Responsive Images: Declarative aspect ratios<br />
| <br />
| Micro-payments (w/browser plugin demo)<br />
| Paid Content<br />
|-<br />
! 1.07, Hall 4, First Floor (30) <br />
| Fusing language and sensor data<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#What.27s_new_in_pubrules_and_automated_publishing What's new in pubrules and automated publishing] <br /> <small>[REQUEST] (needs phone; scheduled at 11:00</small>)<br />
| Education & Outreach WG (EDWG) What is it & how can it support your work? (Eric Eggert)<br />
|<br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Future_of_Communications_on_the_Web Future of Communications on the Web]</span><br />
<br />
|-<br />
! 1.08, Hall 4, First Floor (30) <br />
| New Accessibility Guidelines & Mobile Accessibility<br />
| Accessibility Object Model (AOM)<br />
| Subtitles & Text Track & Text TrackCue<br />
| AWPAT CG, HTML5 Testing Project (Chaals, Max)<br />
| Horizontal Review (Janina Sajka)<br />
|-<br />
! 1.05, Hall 4, First Floor (28) <br />
| <br />
| Async Web (Nolan Lawson)<br />
| <br />
| CSS Step String for block height (Koji)<br />
| Virtual Assistants<br />
|-<br />
! 1.06, Hall 4, First Floor (26) <br />
| Protect against Data Breach, Web Authn 2FA (Ted G)<br />
| Security JAM (news from W3C & new topics on security)<br />
| Origin Isolation/Browsing Context Isolation (AnneVK, Mkwst)<br />
| WAI standards harmonization roadmap (Rich S)<br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Vocabulary_development_.26_management_at_W3C Vocabulary Development, Namespaces Management]<br />
|-<br />
! 1.15, First Floor (26) <br />
| Storage<br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.03, First Floor (22) <br />
| <br />
| [https://www.w3.org/wiki/TPAC2016/SessionIdeas#High_Dynamic_Range_.28HDR.29_and_the_Web HDR and Web]<br />
| <br />
| Make W3C great again (how to make W3C a better platform for collaboration)<br />
|<br />
|-<br />
! 1.04, First Floor (22) <br />
| <br />
| <br />
| <br />
| Music Notation Community Group (Update)<br />
|<br />
|-<br />
|}<br />
<br />
== Aggregated Summaries ==<br />
<br />
@@will come later.<br />
<br />
=== Breakout title ===<br />
<pre><br />
Create breakout summary, e.g. https://www.w3.org/wiki/TPAC2016/session-foo-summary<br />
Transclude here using syntax: {{:TPAC2016/session-foo-summary}}</pre></div>Amyhttps://www.w3.org/wiki/index.php?title=TPAC/2016&diff=99798TPAC/20162016-09-14T02:49:16Z<p>Amy: /* Wednesday 21 September Plenary Day Schedule */</p>
<hr />
<div>__TOC__<br />
<br />
<span style="color:#ff0000">'''*** DRAFT ***'''</span><br />
<br />
<div class="h-event"><br />
'''<dfn span class="p-name">[http://www.w3.org/2016/09/TPAC/ TPAC2016]</dfn>''' takes place <time class="dt-start" datetime="2016-09-19">2016-09-19</time>…<time class="dt-end" datetime="2016-09-23">23</time> M-F in <span class="p-location">Lisbon, Portugal</span>.<br />
</div><br />
<br />
<div class="h-event vevent"><br />
On <span class="dt-start" datetime="2016-09-19"><span class="value-title" title="2016-09-21">Wednesday, 21 September</span></span>, we hold a "<span class="p-name summary">Plenary Day.</span>" <span class="p-description description">As we did for [[TPAC2015]], we will organize most of the day as "camp-style" breakout sessions. We invite you to add to or comment on [[TPAC2016/SessionIdeas | Breakout session ideas]]. The people at the meeting that day will build the [[#Session_Grid | Session Grid]], drawing from ideas socialized in advance and new ideas proposed the day of the meeting.</span><br />
</div><br />
<br />
* Questions? See the [http://www.w3.org/wiki/TPAC2016/FAQ FAQ].<br />
* See Also past [[TPAC]] meetings.<br />
<br />
== Wednesday 21 September Plenary Day Schedule ==<br />
<br />
* Plenary sessions take place at [http://www.lisboacc.pt/irj/portal/lisboacc?lang=en Centro de congressos de lisboa]. See [https://www.w3.org/2016/09/TPAC/schedule.html schedule].<br />
* Breakout sessions take place in [http://www.w3.org/wiki/TPAC2016/FAQ#What_are_the_breakout_room_sizes.3F nearby rooms].<br />
* The lunch space accommodates slightly fewer people than registered; therefore breakout sessions overlap lunch time on each end.<br />
<br />
<span style="color:#ff0000">Proposed schedule:</span><br />
<div id="schedule"><br />
* ''08:00-08:30: Registration''<br />
* 08:30-08:35: '''Welcome''' - Jeff Jaffe<br />
* 08:35-09:05: '''Redecentralization of the Web''' - Tim Berners-Lee<br />
* 09:05-09:15: '''Data Breach, Reaction and Response'''(*) - Ted Guild<br />
* 09:15-10:00: '''Breakout preparation''' + '''last additions to [[TPAC2016/SessionIdeas | Breakout session ideas]]''' (Coralie Mercier)<br />
* ''09:15-10:00: Coffee break (**) - Hall 4, First Floor''<br />
* 10:00-11:00: '''Breakouts''' (see grid below)<br />
* 11:00-12:00: '''Breakouts''' (see grid below)<br />
* ''11:30-14:00: Lunch - Restaurant, First Floor'' <br />
* 13:00-14:00: '''Breakouts''' (see grid below)<br />
* 14:00-15:00: '''Breakouts''' (see grid below)<br />
* ''15:00-15:30: Coffee break - Hall 4, First Floor''<br />
* 15:30-16:30: '''Breakouts''' (see grid below)<br />
* 16:30-18:00: '''Breakout reports'''<br />
* ''18:30-21:30: Reception - Foyer E''<br />
** ''20:45-21:20: ForEveryone.net - Auditorium VI and VII'' ('''Private showing''' of a 35-minute documentary film about Sir Tim Berners-Lee, by Academy Award winning director Jessica Yu, which gives a history of the Web as well as a call to protect its future and features Tim, his family and colleagues including W3C CEO, Jeff Jaffe.)<br />
<br />
(*) Introduction to subsequent Breakout session; if you're a security expert, please consider signing up.<br><br />
(**) Breakout preparation and morning break overlap.<br />
</div><br />
<br />
=== Breakout Schedule (session grid) ===<br />
{| class="zebra"<br />
|-<br />
! Room (capacity)/Slots <br />
! 10:00-11:00 <br />
! 11:00-12:00<br />
! 13:00-14:00<br />
! 14:00-15:00<br />
! 15:30-16:30<br />
|-<br />
! Auditorium VI & VII, Ground Floor (48) <br />
| <br />
| <br />
| <br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Privacy_compliance_in_the_EU_using_W3C_Tracking_Protection DNT]</span><br />
|<br />
|-<br />
! 5A, Hall 5, First Floor (48) <br />
| <br />
| <br />
| <br />
| <br />
|<br />
|- <br />
! 5B, Hall 5, First Floor (48) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 5C, Hall 5, First Floor (48) <br />
| <br />
|<br />
| <br />
| <br />
|<br />
|-<br />
! Auditorium III, First Floor (30) <br />
| <br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Web_of_Things_PlugFest_Demos_.28Outreach.40TPAC.29 WoT PlugFest Demo Pitch]</span><br />
| <span style="color:#ff0000">reserved for [https://www.w3.org/wiki/TPAC2016/SessionIdeas#Web_of_Things_PlugFest_Demos_.28Outreach.40TPAC.29 WoT PlugFest Demo]</span><br />
|<br />
|<br />
|-<br />
! Auditorium IV, First Floor (30) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.07, Hall 4, First Floor (30) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.08, Hall 4, First Floor (30) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.05, Hall 4, First Floor (28) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.06, Hall 4, First Floor (26) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.15, First Floor (26) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.03, First Floor (22) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
! 1.04, First Floor (22) <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|-<br />
|}<br />
<br />
== Aggregated Summaries ==<br />
<br />
@@will come later.<br />
<br />
=== Breakout title ===<br />
<pre><br />
Create breakout summary, e.g. https://www.w3.org/wiki/TPAC2015/session-foo-summary<br />
Transclude here using syntax: {{:TPAC2016/session-foo-summary}}</pre></div>Amyhttps://www.w3.org/wiki/index.php?title=TPAC2016/SessionIdeas&diff=99688TPAC2016/SessionIdeas2016-09-12T00:50:46Z<p>Amy: adding PWETF session info</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2016]] Wednesday '''Technical Plenary Day''' [http://www.w3.org/2016/09/TPAC/#breakouts Breakout sessions] in advance of the meeting. <br />
<br />
<span style="color:#ff0000">'''The sessions that will make it will be in the [https://www.w3.org/wiki/TPAC/2016#Session_Grid breakouts grid], as well as minutes and summaries '''</span><br />
<br />
See the [http://www.w3.org/wiki/TPAC2016/FAQ TPAC 2016 FAQ] for more information. See [https://www.w3.org/wiki/TPAC2015/SessionIdeas TPAC 2015 Session Ideas].<br />
<br />
'''Note''': During TPAC week, working groups may [https://www.w3.org/wiki/TPAC/2016/ad-hoc-meetings schedule] [http://www.w3.org/2016/09/TPAC/#adhoc Ad-hoc meetings].<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 />
<br />
=== Privacy compliance in the EU using W3C Tracking Protection ===<br />
<br />
<span style="color:#ff0000">'''constraint:''' This breakout needs to take place at 2pm</span><br />
<br />
* Proposer: Matthias Schunter [mts-std@schunter.org], Carl Cargill (chairs), Dave Singer, Roy Fielding (editors) on behalf of the [https://www.w3.org/2011/tracking-protection/ TPWG] <br />
* Session overview: We believe that the emerging EU privacy regulations may impact cookie handling and tracking. We also believe that the TPWG Candidate Recommendations have the potential to simplify compliance with these regulations.<br />
<br />
The topics we want to address in this breakout are:<br />
1. Learn how to implement the Tracking Protection recommendations.<br />
2. Share implementation experiences and ask questions<br />
3. Learn about and discuss (emerging) EU privacy regulations<br />
2. Provide feedback on the draft recommendations<br />
4. Discuss with us the future of the working group<br />
<br />
* type of session: tutorial + discussion<br />
* Session goals: Gather TPWG Implementers and TPWG feedback<br />
* additional speakers/panelists: <br />
** Tutorial on EU Privacy Regulations (by Rob van Eijk; Technologist at the Dutch Privacy Authority)<br />
** Tutorial: On Implementing TPWG (by Mike O'Neil, Baycloud Systems)<br />
<br />
=== Brainstorming: design & usability of W3C pages ===<br />
<br />
* Proposer: [[User:Antonio | Antonio]], on behalf of [http://www.w3.org/People/domain/systeam Systeam].<br />
* Session overview: the look & feel of W3C pages and sub-sites is not consistent, and there are usability and a11y issues that we want to address. What are the biggest complaints that users have? How can we start unifying the design of pages without annoying their long-time users, and without causing confusion? What are the most cost-effective ways to modernise our design? Who among the membership or general audience want to help, and how?<br />
* type of session: round table, brainstorming, ''un-talk''.<br />
* Session goals: gather ideas, gauge the actual importance of the issue.<br />
* additional speakers/panelists: (Guillaume?)<br />
<br />
=== What's new in pubrules and automated publishing ===<br />
<br />
* Proposer: [[User:Antonio | Antonio]], on behalf of [http://www.w3.org/People/domain/systeam Systeam].<br />
* Session overview: announcement of latest developments in pubrules, automatic publication and related tools; followed by feedback, ideas and discussion about possible roadmap.<br />
* type of session: moderately geeky discussion.<br />
* Session goals: learn how to develop and publish specs efficiently at the end of 2016.<br />
* additional speakers/panelists: (Vivien? Philippe? Ted?)<br />
<br />
=== Horizontal review summit ===<br />
<br />
* Proposer: Michael Cooper, Janina Sajka<br />
* Session overview: Gather the groups that conduct horizontal review to share challenges and techniques in making effective impact on specifications, and propose ways to improve horizontal review effectiveness. Horizontal review is structured review across specifications for issues that impact broad stakeholder groups. W3C [https://www.w3.org/Guide/Charter.html#horizontal-review currently conducts horizontal review] for accessibility to people with disabilities, architectural principles, internationalization, privacy, and security. This session is primarily oriented at people who engage in horizontal review. People engaged in specification development who would like to learn how to engage with the process or suggest ways to improve the process are also welcome.<br />
* type of session: open discussion<br />
* Session goals: Identify challenges to conducting effective and timely horizontal review; share tips review groups use to increase engagement; propose ways to improve the horizontal review process across W3C.<br />
<br />
=== Achieving 5 Star Open Data with PDF ===<br />
* Proposer: Leonard Rosenthol & Larry Masinter<br />
* Summary: We are looking to start a community group to work on a series of best practices (and then leading to more) around the best use of PDF for achieving the full 5 stars of Open Data.<br />
* Type of session: Presentation about features of PDF focused on open data, followed by an open discussion about how to best use them and how to kick off a CG.<br />
* Goals: Find a group of people who are interested and willing to help get this CG going and work towards the development of various educational and practical material.<br />
<br />
=== CANCELLED: Spatial Data on the Web meets Web of Things (Outreach@TPAC) ===<br />
<br />
* Proposer: Darko Ancic and Kerry Taylor<br />
* Session overview: Discuss vocabularies needed for WoT<br />
* No longer required as time has been allocated at 4pm on Tuesday in the Spatial Data on the Web meeting<br />
* A slot also to be dedicated during the WoT meeting on Thursday TBA<br />
<br />
=== Web of Things PlugFest Demos (Outreach@TPAC) ===<br />
The following is an initial draft and subject to be updated based on the IG discussion.<br />
<br />
* Proposer: Kaz Ashimura for the WoT IG<br />
* Session overview: We'll present what "PlugFest" is like in the morning and show actual PlugFest demos in the afternoon.<br />
* type of session: Presentation (morning; preferably AM2 session) and Demo (afternoon; preferably PM1 session)<br />
* Session goals: Show what is done by the WoT IG to all the W3C Members and encourage people to collaborate with the group (and join the group :).<br />
* additional speakers/panelists: PlugFest participants<br />
<br />
=== Web & Virtual Reality ===<br />
<br />
* Proposer: Anssi Kostiainen, Ningxin Hu, Frank Olivier<br />
* Session overview: open discussion on the current state and future direction of the Web & VR. [https://w3c.github.io/webvr/ WebVR API] ([https://github.com/w3c/webvr/ GitHub]) currently in incubation in the [https://www.w3.org/community/webvr/ WebVR Community Group] ([https://w3c.github.io/webvr/charter/ Charter]) provides access to Virtual Reality devices, such as the Oculus Rift or Google Cardboard, in your browser. Beyond the WebVR API, there are further opportunities for the web platform to make use of and integrate with VR devices (360 video and images from HTML, VR as progressive enhancement, declarative 3D scenes and 3D scene graph APIs...)<br />
* type of session: open discussion <br />
* Session goals: identify opportunities for standardization efforts, gather further input for the upcoming [https://www.w3.org/2016/06/vr-workshop/ W3C Workshop on Web & Virtual Reality]<br />
<br />
=== Security Jam ===<br />
<br />
The session will be dedicated to share the recent progress on security related topics in W3C, coevring at least web crypto and web authentication, and will discuss also tools for security reviews. In addition, participants are expected to share some security features <br />
* title : Security Jam<br />
* proposer : Virginie GALINDO <br />
* session overview : Discuss recent progress on security in W3C and collect new needs<br />
* style : quick overview of context and open discussion (colorful postit and toffees provided)<br />
* session goal: socialize recent W3C progress and collect any new need<br />
<br />
=== Advancing Web Platform Application Testing (HTML Testing) ===<br />
<br />
* Proposer: Dapeng Liu、Charles McCathie Nevile<br />
* Session overview: We'll present the current status of AWPAT CG and show demo<br />
* type of session: Presentation, Demo, and open discussion<br />
* Session goals: Show what is done by the AWPAT CG to all the W3C Members and encourage people to collaborate with the group (and join the group)<br />
* additional speakers/panelists<br />
<br />
=== Make W3C Great Again ===<br />
<br />
* Proposer: Dom Hazael-Massieux<br />
* Session overview: Part of Dom's job will now include making W3C a better place for collaborative work; he thus wants to hear from both newbies and oldtimers what they think are both the greatest barriers but also the many little annoyances to working on specs, test suites and bringing ideas in W3C<br />
* type of session: open discussion<br />
* Session goals: Roadmap to making W3C great again<br />
* additional speakers/panelists<br />
<br />
=== Future of Communications on the Web ===<br />
<br />
* Proposer: Dom Hazael-Massieux<br />
* Session overview: The WebRTC 1.0 API has opened the road to make the Web a platform for audio & video communications on the Web; while this provides a great starting point, there are still many other aspects of a successful communication platform that the Web doesn't cover, for instance:<br />
** keeping connections up when browser is in background<br />
** integrating a presence mechanism<br />
** scalability improvements<br />
** device handover<br />
** audio priority management (e.g. phone vs webrtc comm)<br />
This session aims at identifying these gaps and determining when and where they might be addressed, or how to continue the conversation about them.<br />
<br />
* type of session: talks + discussions<br />
* Session goals: identify gaps in the Web as a communication platform<br />
* additional speakers/panelists<br />
<br />
<br />
=== Micro-payments - A new business model for a Web without Ads and tracking ===<br />
<br />
* Proposer: [[User:Ahopebai | Adrian Hope-Bailie]], on behalf of [http://interledger.org The Interledger Community Group].<br />
* Session overview: Brave browser has [https://blog.brave.com/introducing-brave-payments/ announced] that they are incorporating micro-payments into their browser. The current state of Web payments requires that this system limit itself to using Bitcoin for this purpose. Using an open protocol like Interledger, browsers and content producers could make and accept payments using whatever method they desire without the need for user interaction to select a payment method.<br />
<br />
In this session the Interledger Community Group will discuss the experiments it is doing to solve the micro-payments challenge and open up the discussion on prior efforts and what we can do differently this time.<br />
<br />
* Type of session: round table, brainstorming, ''un-talk'' (The Interledger CG meets the following day for a deeper dive).<br />
* Session goals: demonstrate work done to date in the Interledger CG (or any other group), gather ideas, discuss next steps.<br />
* Additional speakers/panelists: (Andrew Betts?)<br />
<br />
=== Apps or Documents? Manifests, JSON, and the Future of Publications ===<br />
*Proposers: Dave Cramer and Tzviya Siegman<br />
*Summary: Complex documents, like applications, often consist of multiple web resources. But the Web doesn't have much to say about collections of resources. Web documents can link to each other, and link relations let you say a few things about what's on the other end of the link. But you can't easily say two documents are part of a larger entity or this metadata applies to a group of documents.<br />
*Type of session: open discussion<br />
*Goals of session: Discuss the role of Web App Manifest in apps and publications. Will JSON save us all? What about the future of books in browsers? We'll discuss PWP, BFF, EPUB, and other relevant acronyms.<br />
<br />
<br />
=== Positive Work Environment Task Force ===<br />
*Proposers: Ann Bassetti and Amy van der Hiel<br />
*Summary: The W3C Positive Work Environment Task Force would like to get feedback from the W3C community on their concerns and suggestions and to explore our goals and ideals as a community. Discussions may include: revitalizing the TF; Chairs training; best practices; diversity and inclusion; and our aspirations for the kind of community W3C can be.<br />
*Type of session: open discussion<br />
*Goals of session: discussion, feedback and community building. We invite members of the community to join and be involved in the TF.</div>Amyhttps://www.w3.org/wiki/index.php?title=PWE&diff=99409PWE2016-08-25T22:04:23Z<p>Amy: /* Best Practices */</p>
<hr />
<div>== Positive Work Environment ==<br />
Public wiki regarding Positive Work Environment at W3C.<br />
<br />
== W3C Codes of Conduct ==<br />
The [https://www.w3.org/Consortium/pwe/ Positive Work Environment Task Force] owns:<br />
<br />
* the [https://www.w3.org/Consortium/cepc/ Code of Ethics and Professional Conduct (CEPC)]<br />
<br />
* the draft [https://www.w3.org/wiki/PWE/Conf-code Conference code]<br />
<br />
* the [https://www.w3.org/Consortium/pwe/#Procedures Procedures] for implementing these codes<br />
<br />
== Best Practices ==<br />
<br />
A collection of Best Practices pages for meetings, speakers and public events<br />
<br />
* [https://www.w3.org/wiki/Speaker_Resources#Speakers_Guidelines Speaker Guidelines from Coralie]<br />
<br />
* [https://www.w3.org/wiki/Global_Topic Thoughts about making W3C more global developed by an Advisory Board task force (Judy Zhu, Jay Kishigami, others?)]<br />
<br />
* [https://www.w3.org/wiki/Moderating_Meetings Moderating Meetings] by AB (by Chaals)<br />
<br />
* Draft [[Meetings Best Practices document]] for meetings (to be prepared by TPAC 2016)<br />
<br />
== PWETF discussion(s) notes ==<br />
This section will be for collecting PWETF notes and discussions<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_AC notes from BOF session at AC meeting, MIT, March 2016]<br />
<br />
* [https://www.w3.org/wiki/PWE/201603_badges ideas for name badges March 2016]<br />
<br />
<br />
== Outline for renewing Task Force, reviewing goals, vision, documents, and next steps ==<br />
<br />
From May 2016: [https://www.w3.org/wiki/PWE/201604_outline ideas for renewing Task Force, reviewing goals, vision, documents, and next steps ]</div>Amyhttps://www.w3.org/wiki/index.php?title=Best_Practices_for_Effective_Meetings&diff=99366Best Practices for Effective Meetings2016-08-23T22:55:19Z<p>Amy: /* During Presentations and Discussion */</p>
<hr />
<div><br />
@@Note: a meetings best practices document will be linked from meeting pages and be given out in printed form at the TPAC 2016 meeting in Lisbon. The best practices document and the below pages were created in response to asking W3C meeting attendees about how to make meetings more welcoming (with some special attention given to those non-native speakers or from non-Western countries). <br />
This document is partially based on: [https://www.w3.org/wiki/Global_Topic Global Topic] and [https://www.w3.org/wiki/Speaker_Resources Speaker Resources ]. Information that all W3C meetings operate under the Code of Conduct is also to be included. <br />
@@<br />
<br />
As an international community, W3C benefits greatly from the many unique strengths, perspectives and ideas that can be gained from collaboration across cultures and countries. However, to function well as a truly global community, we must also work to be aware of and sensitive to any differences and inclusive of different work styles and needs. <br />
<br />
In the tech world, including groups like the W3C, meetings can often seem heavily biased with US-centric or Western communication styles and meeting habits. At W3C we strive to be inclusive and want to have the benefit of feedback from all our many participants including those who are non-native English speakers, and/or with non-Western backgrounds as well as to encourage open collaboration in a professional and respectful manner. <br />
<br />
<br />
Below are some best practices for meetings with international participation.<br />
<br />
== Preparing for Meetings: ==<br />
Chairs and meeting Facilitators should:<br />
* supply supporting materials ahead of time to give the audience a chance to get familiar with the subject.<br />
* ensure that handouts, slides, and other material are in accessible formats.<br />
<br />
For large group presentations, see specific [https://www.w3.org/wiki/Speaker_Resources best practices for speakers]<br />
<br />
== During Presentations and Discussion == <br />
For group presentations, Chairs and Facilitators should consider the value of wide group participation and understand why individual participants might be [https://www.w3.org/wiki/Global_Topic#Motivate_people_to_speak_up hesitant to speak] and understand they can mitigate this by: <br />
* having a big screen on which to project the IRC channel, so people can see the live discussions from the screen.<br />
* helping to repeat any questions or comments.<br />
* using modern tools (IRC, Slack, etc) to get input from participants.<br />
* for remote participants, being sure to share screens where possible and being sure the discussion is being minuted in IRC.<br />
* recognizing commenters who have not been heard from or who are most likely to move the conversation forward and encourage their thoughts and participation.<br />
* also recognizing those commenters who may, by their style, tone or length of speech, derail or negatively escalate a discussion, and respectfully but firmly steer the discussion to a more neutral or courteous direction. <br />
* summarizing what was said and decided at the end of each discussion and to ask for further questions and clarifications. <br />
<br />
Presenters/Chairs should:<br />
* make their objectives clear: by clarifying whether the subject is for information, for discussion, or for decision.<br />
* show any open issues lists and discuss the issues one by one, to get people involved and allow them to follow along.<br />
* speak clearly, taking particular care with names, words, and phrases that the audience may not know (e.g.: use simple language; expand acronyms, and minimise slang, jargon, colloquialisms and idioms.).<br />
* speak at a rate that people can follow easily, including people who are not native speakers of one's language (for most people, this means "Speak Slowly") and use pacing to give one's audience time to process information<br />
* be **very** careful using jokes and humour as people's sense of humour can be very different. In addition, most jokes are very hard to understand for non-native speakers, and will distract them from your content.<br />
* describe succinctly pertinent parts of graphics, videos, and other visuals as some people may not be able to see your visuals as it is normal in W3C for people to attend meetings remotely with only audio and the IRC text "transcript". Also be sure the screen and the spoken content should reinforce each other. This reinforcement is particularly helpful for those having difficulty following the presentation.<br />
<br />
All Meeting participants should: <br />
* allow people to speak other languages in case of some difficult words, e.g. in Chinese or Japanese.<br />
* try to be gentle about any mistakes that people, especially non-English native speakers, make in speaking and patient in encouraging people to express themselves.<br />
* try to speak factually, succinctly, helpfully, and respectfully when presenting ones own ideas and when responding to others. <br />
* treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths.<br />
<br />
== Code of Conduct ==<br />
All W3C Meetings are run under the rules of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct]. <br />
<br />
Doing so means that our community: <br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication. <br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively. <br />
* Seeks, accepts, and offers objective criticism, and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional or unfair or unwelcome behavior or advances while being, in terms of respecting cultural differences, "conservative in what you do and liberal in what you accept from others".<br />
* Accepts (especially those in a leadership position) their responsibility to take action whenever disrespectful or inappropriate behaviors are observed to bring a discussion back to a more civil level .</div>Amyhttps://www.w3.org/wiki/index.php?title=Best_Practices_for_Effective_Meetings&diff=99363Best Practices for Effective Meetings2016-08-23T21:32:45Z<p>Amy: </p>
<hr />
<div><br />
@@Note: a meetings best practices document will be linked from meeting pages and be given out in printed form at the TPAC 2016 meeting in Lisbon. The best practices document and the below pages were created in response to asking W3C meeting attendees about how to make meetings more welcoming (with some special attention given to those non-native speakers or from non-Western countries). <br />
This document is partially based on: [https://www.w3.org/wiki/Global_Topic Global Topic] and [https://www.w3.org/wiki/Speaker_Resources Speaker Resources ]. Information that all W3C meetings operate under the Code of Conduct is also to be included. <br />
@@<br />
<br />
As an international community, W3C benefits greatly from the many unique strengths, perspectives and ideas that can be gained from collaboration across cultures and countries. However, to function well as a truly global community, we must also work to be aware of and sensitive to any differences and inclusive of different work styles and needs. <br />
<br />
In the tech world, including groups like the W3C, meetings can often seem heavily biased with US-centric or Western communication styles and meeting habits. At W3C we strive to be inclusive and want to have the benefit of feedback from all our many participants including those who are non-native English speakers, and/or with non-Western backgrounds as well as to encourage open collaboration in a professional and respectful manner. <br />
<br />
<br />
Below are some best practices for meetings with international participation.<br />
<br />
== Preparing for Meetings: ==<br />
Chairs and meeting Facilitators should:<br />
* supply supporting materials ahead of time to give the audience a chance to get familiar with the subject.<br />
* ensure that handouts, slides, and other material are in accessible formats.<br />
<br />
For large group presentations, see specific [https://www.w3.org/wiki/Speaker_Resources best practices for speakers]<br />
<br />
== During Presentations and Discussion == <br />
For group presentations, Chairs and Facilitators should consider the value of wide group participation and understand why individual participants might be [https://www.w3.org/wiki/Global_Topic#Motivate_people_to_speak_up hesitant to speak] and understand they can mitigate this by: <br />
* having a big screen on which to project the IRC channel, so people can see the live discussions from the screen.<br />
* help to repeat any questions or comments.<br />
* use modern tools (IRC, Slack, etc) to get input from participants.<br />
* for remote participants, be sure to share screens where possible and be sure the discussion is being minuted in IRC.<br />
* recognize commenters who have not been heard from or who are most likely to move the conversation forward and encourage their thoughts and participation.<br />
* also recognize those commenters who may, by their style, tone or length of speech, derail or negatively escalate a discussion, and respectfully and gently steer the conversation if it seems to be changing to counterproductive topics or tone. <br />
* summarize what was said and decided at the end of each discussion and to ask for further questions and clarifications. <br />
<br />
Presenters/Chairs should:<br />
* make their objectives clear: to clarify whether the subject is for information, for discussion, or for decision<br />
* show the open issues list, and discuss the issues one by one, to get people involved and allow them to follow along.<br />
* speak clearly, taking particular care with names, words, and phrases that the audience may not know (e.g.: use simple language; expand acronyms, and minimise slang, jargon, colloquialisms and idioms.).<br />
* speak at a rate that people can follow easily, including people who are not native speakers of your language (for most people, this means "Speak Slowly") and use pacing to give your audience time to process information<br />
* be **very** careful using jokes and humour as people's sense of humour can be very different. In addition, most jokes are very hard to understand for non-native speakers, and will distract them from your content.<br />
* describe succinctly pertinent parts of graphics, videos, and other visuals as some people may not be able to see your visuals. Iit is normal in W3C for people to attend meetings remotely with only audio and the IRC text "transcript". Also be sure the screen and the spoken content should reinforce each other. This reinforcement is particularly helpful for those having difficulty following the presentation.<br />
<br />
All Meeting participants should: <br />
* allow people to speak other languages in case of some difficult words, e.g. in Chinese or Japanese.<br />
* be gentle about any mistakes that people, especially non-English native speakers, make in speaking and patient in encouraging people to express themselves.<br />
* treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths.<br />
<br />
== Code of Conduct ==<br />
All W3C Meetings are run under the rules of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct]. <br />
<br />
Doing so means that our community: <br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication. <br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively. <br />
* Seeks, accepts, and offers objective criticism, and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional or unfair or unwelcome behavior or advances while being, in terms of respecting cultural differences, "conservative in what you do and liberal in what you accept from others".<br />
* Accepts (especially those in a leadership position) their responsibility to take action whenever disrespectful or inappropriate behaviors are observed to bring a discussion back to a more civil level .</div>Amyhttps://www.w3.org/wiki/index.php?title=Best_Practices_for_Effective_Meetings&diff=99358Best Practices for Effective Meetings2016-08-23T20:25:23Z<p>Amy: </p>
<hr />
<div><br />
Note: this document will be linked from meeting pages and be given out in printed form at the TPAC 2016 meeting in Lisbon. It and the below pages were created in response to requests from W3c meeting attendees about how to make meetings more welcoming for non-native speakers (with special attention given to those from non-Western countries). <br />
This document is partially based on: [https://www.w3.org/wiki/Global_Topic Global Topic] and [https://www.w3.org/wiki/Speaker_Resources Speaker Resources ]. Information that all W3C meetings operate under the Code of Conduct also to be included. <br />
<br />
---<br />
<br />
As an international community, W3C benefits greatly from the many unique strengths, perspectives and ideas that can be gained from collaboration across cultures and countries. However, to function well as a truly global community, we must also work to be aware of and sensitive to any differences and inclusive of different work styles and needs. <br />
<br />
In the tech world, including groups like the W3C, meetings can often seem heavily biased with US-centric or Western communication styles or meeting habits. At W3C we strive to be inclusive and want to have the benefit of feedback from all our many participants including those who are non-native English speakers, and/or with non-Western backgrounds. <br />
<br />
<br />
<br />
Below are some best practices for meetings with international participation.<br />
<br />
== Preparing for Meetings: ==<br />
Chairs and meeting Facilitators should:<br />
* supply supporting materials ahead of time to give the audience a chance to get familiar with the subject.<br />
* ensure that handouts, slides, and other material are in accessible formats.<br />
<br />
For large group presentations, see specific [https://www.w3.org/wiki/Speaker_Resources best practices for speakers]<br />
<br />
== During Presentations and Discussion == <br />
For group presentations, Chairs and Facilitators should consider the value of wide group participation and understand why individual participants might be [https://www.w3.org/wiki/Global_Topic#Motivate_people_to_speak_up hesitant to speak] and understand they can mitigate this by: <br />
* having a big screen on which to project the IRC channel, so people can see the live discussions from the screen.<br />
* help to repeat any questions or comments.<br />
* use modern tools (IRC, Slack, etc) to get input from participants.<br />
* for remote participants, be sure to share screens where possible and be sure the discussion is being minuted in IRC.<br />
* recognize commenters who have not been heard from or who are most likely to move the conversation forward and encourage their thoughts and participation.<br />
* also recognize those commenters who may, by their style, tone or length of speech, derail or negatively escalate a discussion, and respectfully and gently steer the conversation if it seems to be changing to counterproductive topics or tone. <br />
* summarize what was said and decided at the end of each discussion and to ask for further questions and clarifications. <br />
<br />
Presenters/Chairs should:<br />
* make their objectives clear: to clarify whether the subject is for information, for discussion, or for decision<br />
* show the open issues list, and discuss the issues one by one, to get people involved and allow them to follow along.<br />
* speak clearly, taking particular care with names, words, and phrases that the audience may not know (e.g.: use simple language; expand acronyms, and minimise slang, jargon, colloquialisms and idioms.).<br />
* speak at a rate that people can follow easily, including people who are not native speakers of your language (for most people, this means "Speak Slowly") and use pacing to give your audience time to process information<br />
* be **very** careful using jokes and humour as people's sense of humour can be very different. In addition, most jokes are very hard to understand for non-native speakers, and will distract them from your content.<br />
* describe succinctly pertinent parts of graphics, videos, and other visuals as some people may not be able to see your visuals. Iit is normal in W3C for people to attend meetings remotely with only audio and the IRC text "transcript". Also be sure the screen and the spoken content should reinforce each other. This reinforcement is particularly helpful for those having difficulty following the presentation.<br />
<br />
All Meeting participants should: <br />
* allow people to speak other languages in case of some difficult words, e.g. in Chinese or Japanese.<br />
* be gentle about any mistakes that people, especially non-English native speakers, make in speaking and patient in encouraging people to express themselves.<br />
* treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths.<br />
<br />
== Code of Conduct ==<br />
All W3C Meetings are run under the rules of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct]. <br />
<br />
Doing so means that our community: <br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication. <br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively. <br />
* Seeks, accepts, and offers objective criticism, and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional or unfair or unwelcome behavior or advances while being, in terms of respecting cultural differences, "conservative in what you do and liberal in what you accept from others".<br />
* Accepts (especially those in a leadership position) their responsibility to take action whenever disrespectful or inappropriate behaviors are observed to bring a discussion back to a more civil level .</div>Amyhttps://www.w3.org/wiki/index.php?title=Best_Practices_for_Effective_Meetings&diff=99357Best Practices for Effective Meetings2016-08-23T20:23:51Z<p>Amy: </p>
<hr />
<div><br />
Note: this document will be linked from meeting pages and be given out in printed form at the TPAc 2016 meeting in Lisbon. It and the below pages were created in response to requests from W3c meeting attendees about how to make meetings more welcoming for non-native speakers (with special attention given to those from non-Western countries). <br />
This document is partially based on: [https://www.w3.org/wiki/Global_Topic Global Topic] and [https://www.w3.org/wiki/Speaker_Resources Speaker Resources ]. Information that all w3c meetings operate under the code of conduct also to be included. <br />
<br />
---<br />
<br />
As an international community, W3C benefits greatly from the many unique strengths, perspectives and ideas that can be gained from collaboration across cultures and countries. However, to function well as a truly global community, we must also work to be aware of and sensitive to any differences and inclusive of different work styles and needs. <br />
<br />
In the tech world, including groups like the W3C, meetings can often seem heavily biased with US-centric or Western communication styles or meeting habits. At W3C we strive to be inclusive and want to have the benefit of feedback from all our many participants including those who are non-native English speakers, and/or with non-Western backgrounds. <br />
<br />
<br />
<br />
Below are some best practices for meetings with international participation.<br />
<br />
== Preparing for Meetings: ==<br />
Chairs and meeting Facilitators should:<br />
* supply supporting materials ahead of time to give the audience a chance to get familiar with the subject.<br />
* ensure that handouts, slides, and other material are in accessible formats.<br />
<br />
For large group presentations, see specific [https://www.w3.org/wiki/Speaker_Resources best practices for speakers]<br />
<br />
== During Presentations and Discussion == <br />
For group presentations, Chairs and Facilitators should consider the value of wide group participation and understand why individual participants might be [https://www.w3.org/wiki/Global_Topic#Motivate_people_to_speak_up hesitant to speak] and understand they can mitigate this by: <br />
* having a big screen on which to project the IRC channel, so people can see the live discussions from the screen.<br />
* help to repeat any questions or comments.<br />
* use modern tools (IRC, Slack, etc) to get input from participants.<br />
* for remote participants, be sure to share screens where possible and be sure the discussion is being minuted in IRC.<br />
* recognize commenters who have not been heard from or who are most likely to move the conversation forward and encourage their thoughts and participation.<br />
* also recognize those commenters who may, by their style, tone or length of speech, derail or negatively escalate a discussion, and respectfully and gently steer the conversation if it seems to be changing to counterproductive topics or tone. <br />
* summarize what was said and decided at the end of each discussion and to ask for further questions and clarifications. <br />
<br />
Presenters/Chairs should:<br />
* make their objectives clear: to clarify whether the subject is for information, for discussion, or for decision<br />
* show the open issues list, and discuss the issues one by one, to get people involved and allow them to follow along.<br />
* speak clearly, taking particular care with names, words, and phrases that the audience may not know (e.g.: use simple language; expand acronyms, and minimise slang, jargon, colloquialisms and idioms.).<br />
* speak at a rate that people can follow easily, including people who are not native speakers of your language (for most people, this means "Speak Slowly") and use pacing to give your audience time to process information<br />
* be **very** careful using jokes and humour as people's sense of humour can be very different. In addition, most jokes are very hard to understand for non-native speakers, and will distract them from your content.<br />
* describe succinctly pertinent parts of graphics, videos, and other visuals as some people may not be able to see your visuals. Iit is normal in W3C for people to attend meetings remotely with only audio and the IRC text "transcript". Also be sure the screen and the spoken content should reinforce each other. This reinforcement is particularly helpful for those having difficulty following the presentation.<br />
<br />
All Meeting participants should: <br />
* allow people to speak other languages in case of some difficult words, e.g. in Chinese or Japanese.<br />
* be gentle about any mistakes that people, especially non-English native speakers, make in speaking and patient in encouraging people to express themselves.<br />
* treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths.<br />
<br />
== Code of Conduct ==<br />
All W3C Meetings are run under the rules of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct]. <br />
<br />
Doing so means that our community: <br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication. <br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively. <br />
* Seeks, accepts, and offers objective criticism, and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional or unfair or unwelcome behavior or advances while being, in terms of respecting cultural differences, "conservative in what you do and liberal in what you accept from others".<br />
* Accepts (especially those in a leadership position) their responsibility to take action whenever disrespectful or inappropriate behaviors are observed to bring a discussion back to a more civil level .</div>Amyhttps://www.w3.org/wiki/index.php?title=Best_Practices_for_Effective_Meetings&diff=99356Best Practices for Effective Meetings2016-08-23T20:11:47Z<p>Amy: </p>
<hr />
<div><br />
As an international community, W3C benefits greatly from the many unique strengths, perspectives and ideas that can be gained from collaboration across cultures and countries. However, to function well as a truly global community, we must also work to be aware of and sensitive to any differences and inclusive of different work styles and needs. <br />
<br />
In the tech world, including groups like the W3C, meetings can often seem heavily biased with US-centric or Western communication styles or meeting habits. At W3C we strive to be inclusive and want to have the benefit of feedback from all our many participants including those who are non-native English speakers, and/or with non-Western backgrounds. <br />
<br />
@Hopefully keep this to a length to allow it to printed out on one page? Also need to explain what a "Facilitator" is - short version: helps meeting run smoothly and fairly. Also need to strike balance between good (non-egressive) meeting behavior and international?@<br />
<br />
Below are some best practices for meetings with international participation.<br />
<br />
== Preparing for Meetings: ==<br />
Chairs and meeting Facilitators should:<br />
* supply supporting materials ahead of time to give the audience a chance to get familiar with the subject.<br />
* ensure that handouts, slides, and other material are in accessible formats.<br />
<br />
For large group presentations, see specific [https://www.w3.org/wiki/Speaker_Resources best practices for speakers]<br />
<br />
== During Presentations and Discussion == <br />
For group presentations, Chairs and Facilitators should consider the value of wide group participation and understand why individual participants might be [https://www.w3.org/wiki/Global_Topic#Motivate_people_to_speak_up hesitant to speak] and understand they can mitigate this by: <br />
* having a big screen on which to project the IRC channel, so people can see the live discussions from the screen.<br />
* help to repeat any questions or comments.<br />
* use modern tools (IRC, Slack, etc) to get input from participants.<br />
* for remote participants, be sure to share screens where possible and be sure the discussion is being minuted in IRC.<br />
* recognize commenters who have not been heard from or who are most likely to move the conversation forward and encourage their thoughts and participation.<br />
* also recognize those commenters who may, by their style, tone or length of speech, derail or negatively escalate a discussion, and respectfully and gently steer the conversation if it seems to be changing to counterproductive topics or tone. <br />
* summarize what was said and decided at the end of each discussion and to ask for further questions and clarifications. <br />
<br />
Presenters/Chairs should:<br />
* make their objectives clear: to clarify whether the subject is for information, for discussion, or for decision<br />
* show the open issues list, and discuss the issues one by one, to get people involved and allow them to follow along.<br />
* speak clearly, taking particular care with names, words, and phrases that the audience may not know (e.g.: use simple language; expand acronyms, and minimise slang, jargon, colloquialisms and idioms.).<br />
* speak at a rate that people can follow easily, including people who are not native speakers of your language (for most people, this means "Speak Slowly") and use pacing to give your audience time to process information<br />
* be **very** careful using jokes and humour as people's sense of humour can be very different. In addition, most jokes are very hard to understand for non-native speakers, and will distract them from your content.<br />
* describe succinctly pertinent parts of graphics, videos, and other visuals as some people may not be able to see your visuals. Iit is normal in W3C for people to attend meetings remotely with only audio and the IRC text "transcript". Also be sure the screen and the spoken content should reinforce each other. This reinforcement is particularly helpful for those having difficulty following the presentation.<br />
<br />
All Meeting participants should: <br />
* allow people to speak other languages in case of some difficult words, e.g. in Chinese or Japanese.<br />
* be gentle about any mistakes that people, especially non-English native speakers, make in speaking and patient in encouraging people to express themselves.<br />
* treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths.<br />
<br />
== Code of Conduct ==<br />
All W3C Meetings are run under the rules of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct]. <br />
<br />
Doing so means that our community: <br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication. <br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively. <br />
* Seeks, accepts, and offers objective criticism, and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional or unfair or unwelcome behavior or advances while being, in terms of respecting cultural differences, "conservative in what you do and liberal in what you accept from others".<br />
* Accepts (especially those in a leadership position) their responsibility to take action whenever disrespectful or inappropriate behaviors are observed to bring a discussion back to a more civil level .</div>Amyhttps://www.w3.org/wiki/index.php?title=Best_Practices_for_Effective_Meetings&diff=99355Best Practices for Effective Meetings2016-08-23T20:07:06Z<p>Amy: /* During Presentations and Discussion */</p>
<hr />
<div><br />
As an international community, W3C benefits greatly from the many unique strengths, perspectives and ideas that can be gained from collaboration across cultures and countries. However, to function well as a truly global community, we must also work to be aware of and sensitive to any differences and inclusive of different work styles and needs. <br />
<br />
In the tech world, including groups like the W3C, meetings can often seem heavily biased with US-centric or Western communication styles or meeting habits. At W3C we strive to be inclusive and want to have the benefit of feedback from all our many participants including those who are non-native English speakers, and/or with non-Western backgrounds. <br />
<br />
@Hopefully shorten this to allow to print out on one page?@<br />
@ Explain what a "Facilitator" is - short version: helps meeting run smoothly and fairly@<br />
<br />
Below are some best practices for meetings with international participation.<br />
<br />
== Preparing for Meetings: ==<br />
Chairs and meeting Facilitators should:<br />
* supply supporting materials ahead of time to give the audience a chance to get familiar with the subject.<br />
* ensure that handouts, slides, and other material are in accessible formats.<br />
<br />
For large group presentations, see specific [https://www.w3.org/wiki/Speaker_Resources best practices for speakers]<br />
<br />
== During Presentations and Discussion == <br />
For group presentations, Chairs and Facilitators should consider the value of wide group participation and understand why individual participants might be [https://www.w3.org/wiki/Global_Topic#Motivate_people_to_speak_up hesitant to speak] and understand they can mitigate this by: <br />
* having a big screen on which to project the IRC channel, so people can see the live discussions from the screen.<br />
* help to repeat any questions or comments.<br />
* use modern tools (IRC, Slack, etc) to get input from participants.<br />
* for remote participants, be sure to share screens where possible and be sure the discussion is being minuted in IRC <br />
* recognize commenters who have not been heard from or who are most likely to move the conversation forward and call upon them for their comments.<br />
* also recognize those commenters who may by their tone or length of speech and respectfully and gently steer the conversation if it seems to be changing to aggressive or counterproductive topics or tones. <br />
* summarize what was said and decided at the end of each discussion and to ask for further questions and clarifications. <br />
<br />
Presenters/Chairs should:<br />
* make their objectives clear: to clarify whether the subject is for information, for discussion, or for decision<br />
* show the open issues list, and discuss the issues one by one, to get people involved and allow them to follow along.<br />
* speak clearly, taking particular care with names, words, and phrases that the audience may not know (e.g.: use simple language; expand acronyms, and minimise slang, jargon, colloquialisms and idioms.).<br />
* speak at a rate that people can follow easily, including people who are not native speakers of your language (for most people, this means "Speak Slowly") and use pacing to give your audience time to process information<br />
* be **very** careful using jokes and humour as people's sense of humour can be very different. In addition, most jokes are very hard to understand for non-native speakers, and will distract them from your content.<br />
* describe succinctly pertinent parts of graphics, videos, and other visuals as some people may not be able to see your visuals. Iit is normal in W3C for people to attend meetings remotely with only audio and the IRC text "transcript". Also be sure the screen and the spoken content should reinforce each other. This reinforcement is particularly helpful for those having difficulty following the presentation.<br />
<br />
All Meeting participants should: <br />
* allow people to speak other languages in case of some difficult words, e.g. in Chinese or Japanese.<br />
* be gentle about any mistakes that people, especially non-English native speakers, make in speaking and patient in encouraging people to express themselves.<br />
* treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths.<br />
<br />
== Code of Conduct ==<br />
All W3C Meetings are run under the rules of the [https://www.w3.org/Consortium/cepc/ W3C Code of Ethics and Professional Conduct]. <br />
<br />
Doing so means that our community: <br />
* Forbids harassing or bullying anyone verbally, physically or sexually - and encourages respectful and appropriate communication. <br />
* Forbids discrimination on the basis of personal characteristics or group membership - and encourages courtesy, consideration and openness to difference.<br />
* Avoids demeaning or insulting behavior or language - and encourages communicating constructively. <br />
* Seeks, accepts, and offers objective criticism, and acknowledges properly the work contributions of others.<br />
* Forbids disrespectful, unprofessional or unfair or unwelcome behavior or advances while being, in terms of respecting cultural differences, "conservative in what you do and liberal in what you accept from others".<br />
* Accepts (especially those in a leadership position) their responsibility to take action whenever disrespectful or inappropriate behaviors are observed to bring a discussion back to a more civil level .</div>Amy