: Numerous #w3cTPAC breakout sessions have been proposed. * https://github.com/w3c/tpac2025-breakouts/issues/?q=is%3Aissue%20state%3Aopen%20sort%3Acreated-ascIf you plan to participate in TPAC breakouts, whether in-person or remote, take a look and give the ones that look interesting to you thumbs-up 👍, heart ❤️, or rocket 🚀 reactions.For more information about TPAC 2025 Breakout sessions and how they work, see: * https://github.com/w3c/tpac2025-breakouts
's status on Monday, 27-Oct-2025 22:23:00 EDT
Numerous #w3cTPAC breakout sessions have been proposed. * https://github.com/w3c/tpac2025-breakouts/issues/?q=is%3Aissue%20state%3Aopen%20sort%3Acreated-asc If you plan to participate in TPAC breakouts, whether in-person or remote, take a look and give the ones that look interesting to you thumbs-up 👍, heart ❤️, or rocket 🚀 reactions. For more information about TPAC 2025 Breakout sessions and how they work, see: * https://github.com/w3c/tpac2025-breakouts
: Last week I participated in #w3cTPAC 2024¹ in Anaheim, California. It was quite packed, and often started early, from 8am informal breakfast meetings at a nearby IHOP, to Working Group, Community Group, and other small group meetings every day (but Wednesday) til 18:00.Midweek at TPAC was the usual Breakouts Day where a record 87 breakouts² were proposed³ and run by members of the community, deftly organized into rooms, timeslots, and a handful of themes⁴ by the W3C Team. In the evening there was an open Plenary Session⁵ open to all instead of an Advisory Committee (AC) meeting, where the result of the recent W3C Board Election⁶ was announced. Congratulations to the newly elected W3C Board of Directors!I’m still compiling my own notes and observations. For now, the minutes of (nearly?) all the meetings and breakouts are available if you know how to find them.Hint: W3C minutes URLs have the form (without spaces):https:// www . w3 . org / YYYY / MM / DD-IRCNAME-minutes . htmlE.g. to find the second day (2024-09-24) of CSS Working Group (which just uses "css", all lower case, as their IRC channel name) minutes, you would go to:* https://www.w3.org/2024/09/24-css-minutes.htmlEvery Working Group and Community Group links to its IRC Channel (all lowercase), and breakout proposals link to the channel used for each breakout. Thus the minutes links to specific groups on specific days are left as a web discovery exercise for the reader.Last year: https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac¹ https://www.w3.org/wiki/TPAC/2024² https://www.w3.org/2024/09/TPAC/breakouts.html#grid³ https://github.com/w3c/tpac2024-breakouts/⁴ https://github.com/orgs/w3c/projects/57/views/1⁵ https://www.w3.org/2024/09/26-tpac-minutes.html⁶ https://www.w3.org/2024/09/26-tpac-minutes.html#x215
's status on Thursday, 03-Oct-2024 18:02:00 EDT
Last week I participated in #w3cTPAC 2024¹ in Anaheim, California. It was quite packed, and often started early, from 8am informal breakfast meetings at a nearby IHOP, to Working Group, Community Group, and other small group meetings every day (but Wednesday) til 18:00. Midweek at TPAC was the usual Breakouts Day where a record 87 breakouts² were proposed³ and run by members of the community, deftly organized into rooms, timeslots, and a handful of themes⁴ by the W3C Team. In the evening there was an open Plenary Session⁵ open to all instead of an Advisory Committee (AC) meeting, where the result of the recent W3C Board Election⁶ was announced. Congratulations to the newly elected W3C Board of Directors! I’m still compiling my own notes and observations. For now, the minutes of (nearly?) all the meetings and breakouts are available if you know how to find them. Hint: W3C minutes URLs have the form (without spaces): https:// www . w3 . org / YYYY / MM / DD-IRCNAME-minutes . html E.g. to find the second day (2024-09-24) of CSS Working Group (which just uses "css", all lower case, as their IRC channel name) minutes, you would go to: * https://www.w3.org/2024/09/24-css-minutes.html Every Working Group and Community Group links to its IRC Channel (all lowercase), and breakout proposals link to the channel used for each breakout. Thus the minutes links to specific groups on specific days are left as a web discovery exercise for the reader. Last year: https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac ¹ https://www.w3.org/wiki/TPAC/2024 ² https://www.w3.org/2024/09/TPAC/breakouts.html#grid ³ https://github.com/w3c/tpac2024-breakouts/ ⁴ https://github.com/orgs/w3c/projects/57/views/1 ⁵ https://www.w3.org/2024/09/26-tpac-minutes.html ⁶ https://www.w3.org/2024/09/26-tpac-minutes.html#x215
: Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee¹), #W3CAB (W3C Advisory Board² @ab@w3c.social), and #W3CBoard³ meetings in Hiroshima, Japan.The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the Board of the W3C Corporation, the #w3cTAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹.The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²): * https://www.w3.org/wiki/AC/Meetings#2024_SpringMost of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact.Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_ABLike most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels.For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:* 📄 report: https://www.w3.org/reports/ai-web-impact/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/exploration/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf* ▶️ video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch* ▶️ video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch* 🗓 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention)* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf* 🖼 slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values¹⁴), more complex to author (requires sidefiles¹⁵), harder to publish (requires site admin root access), likely to become inaccurate (Ruby’s postulate¹⁶), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.* 🗓 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/I’ll update this list with additional resources as they are made publicly viewable.If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#mondayReferences:¹ https://w3.org/wiki/AC² https://w3.org/wiki/AB³ https://w3.org/wiki/Board⁴ https://www.w3.org/Consortium/Process/⁵ https://www.w3.org/2023/Process-20231103/#ACMeetings⁶ https://w3.org/tag⁷ https://www.w3.org/groups/wg/⁸ https://chapters.w3.org/⁹ https://www.w3.org/invited-experts/#ac-observer¹⁰ https://www.w3.org/wiki/TPAC¹¹ https://www.w3.org/events/ac/2024/ac-2024/¹² https://www.w3.org/membership/list/¹³ https://en.wiktionary.org/wiki/hallway_track¹⁴ https://microformats.org/wiki/existing-rel-values¹⁵ https://indieweb.org/sidefile-antipattern¹⁶ https://intertwingly.net/slides/2004/devcon/68.html
's status on Sunday, 14-Apr-2024 21:41:00 EDT
Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee¹), #W3CAB (W3C Advisory Board² @ab@w3c.social), and #W3CBoard³ meetings in Hiroshima, Japan. The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the Board of the W3C Corporation, the #w3cTAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹. The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²): * https://www.w3.org/wiki/AC/Meetings#2024_Spring Most of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact. Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly. Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_AB Like most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels. For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed: * 📄 report: https://www.w3.org/reports/ai-web-impact/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/exploration/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf * ▶️ video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch * ▶️ video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch * 🗓 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention) * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf * 🖼 slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values¹⁴), more complex to author (requires sidefiles¹⁵), harder to publish (requires site admin root access), likely to become inaccurate (Ruby’s postulate¹⁶), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post. * 🗓 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/ I’ll update this list with additional resources as they are made publicly viewable. If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#monday References: ¹ https://w3.org/wiki/AC ² https://w3.org/wiki/AB ³ https://w3.org/wiki/Board ⁴ https://www.w3.org/Consortium/Process/ ⁵ https://www.w3.org/2023/Process-20231103/#ACMeetings ⁶ https://w3.org/tag ⁷ https://www.w3.org/groups/wg/ ⁸ https://chapters.w3.org/ ⁹ https://www.w3.org/invited-experts/#ac-observer ¹⁰ https://www.w3.org/wiki/TPAC ¹¹ https://www.w3.org/events/ac/2024/ac-2024/ ¹² https://www.w3.org/membership/list/ ¹³ https://en.wiktionary.org/wiki/hallway_track ¹⁴ https://microformats.org/wiki/existing-rel-values ¹⁵ https://indieweb.org/sidefile-antipattern ¹⁶ https://intertwingly.net/slides/2004/devcon/68.html
: Ben Werdmuller recently published an inspiring and thought-provoking blog post: “Subscribing to the blogs of people I follow on Mastodon”. Beyond the insights and excellent developer how-to in his post, I believe it points to something larger: a fundamental thoughtfulness difference between writing rapid short-form posts (whether tweets or toots) and medium or longer form writing (on blogs or journals), and the impact of that difference on readers: that the act of reading more thoughtful writing nudges & reinforces a reader into a more thoughtful state of mind. If you have not read Derek Powazek’s watershed blog post “The Argument Machine”, I highly recommend you do so. In the nearly ten years since his post, Derek’s hypothesis of Twitter’s user interface design being the ultimate machine to create & amplify disputes has been repeatedly demonstrated. Derek’s post predated Mastodon’s release by nearly three years. Ironically, by replicating much of Twitter’s user experience, Mastodon has in many ways also replicated its Argument Machine effects, except distributed across more servers. I’ve witnessed numerous otherwise rational, well-intentioned individuals write reactive posts on Mastodon, exactly what the Twitter-like interface encourages. Quick emotional responses rather than slower, more thoughtful posts and replies. I’ve seen the artificial urgency of tweets & toots bleed over into emotional essays on public mailing lists. New participants join a list and immediately make entitled demands. Fearful bordering on paranoid assumptions are used to state assertions of “facts” without citations. Arguments are made that appeal to emotion (argumentum ad passiones) rather than reasoning from principles and shared values. Implicit in Ben’s post, “Subscribing to the blogs of people” (emphasis mine), is a preference for reading longer form writing, published on a site a human owns & identifies with (a la #indieweb), neither silo nor someone else’s garage. The combination of taking more time (as longer form writing encourages) and publishing on a domain associated with your name, your identity, enables & incentivizes more thoughtful writing. More thoughtful writing elevates the reader to a more thoughtful state of mind. There is also a self-care aspect to this kind of deliberate shift. Ben wrote that he found himself “craving more nuance and depth” among “quick, in-the-now status updates”. I believe this points to a scarcity of thoughtfulness in such short form writings. Spending more time reading thoughtful posts not only alleviates such scarcity, it can also displace the artificial sense of urgency to respond when scrolling through soundbyte status updates. When I returned from #W3CTPAC, I made a list of all the thoughts, meetings, sessions that I wanted to write-up and publish as blog posts to capture my experiences, perspectives, and insights beyond any official minutes. Yet due to distractions such as catching up on short form posts, it took me over a week to write-up even a summary of my TPAC week, nevermind the queue of per-topic notes I wanted to write-up. To even publish that I had to stop and cut-off reading short form posts, as well as ignoring (mostly postponing) numerous notifications. There’s a larger connection here between thoughtful reading, and finding, restoring, and rebuilding the ability to focus, a key to thoughtful writing. It requires not only reducing time spent on short form reading (and writing), but also reducing notifications, especially push notifications. That insight led me to wade into and garden the respective IndieWeb wiki pages for notifications, push notifications, and document a new page for notification fatigue. That broader topic of what do to about notifications is worth its own blog post (or a few), and a good place to end this post. Thanks again Ben for your blog post. May we spend more time reading & writing such thoughtful posts.
's status on Thursday, 05-Oct-2023 02:55:00 EDT
Ben Werdmuller recently published an inspiring and thought-provoking blog post: “Subscribing to the blogs of people I follow on Mastodon”. Beyond the insights and excellent developer how-to in his post, I believe it points to something larger: a fundamental thoughtfulness difference between writing rapid short-form posts (whether tweets or toots) and medium or longer form writing (on blogs or journals), and the impact of that difference on readers: that the act of reading more thoughtful writing nudges & reinforces a reader into a more thoughtful state of mind. If you have not read Derek Powazek’s watershed blog post “The Argument Machine”, I highly recommend you do so. In the nearly ten years since his post, Derek’s hypothesis of Twitter’s user interface design being the ultimate machine to create & amplify disputes has been repeatedly demonstrated. Derek’s post predated Mastodon’s release by nearly three years. Ironically, by replicating much of Twitter’s user experience, Mastodon has in many ways also replicated its Argument Machine effects, except distributed across more servers. I’ve witnessed numerous otherwise rational, well-intentioned individuals write reactive posts on Mastodon, exactly what the Twitter-like interface encourages. Quick emotional responses rather than slower, more thoughtful posts and replies. I’ve seen the artificial urgency of tweets & toots bleed over into emotional essays on public mailing lists. New participants join a list and immediately make entitled demands. Fearful bordering on paranoid assumptions are used to state assertions of “facts” without citations. Arguments are made that appeal to emotion (argumentum ad passiones) rather than reasoning from principles and shared values. Implicit in Ben’s post, “Subscribing to the blogs of people” (emphasis mine), is a preference for reading longer form writing, published on a site a human owns & identifies with (a la #indieweb), neither silo nor someone else’s garage. The combination of taking more time (as longer form writing encourages) and publishing on a domain associated with your name, your identity, enables & incentivizes more thoughtful writing. More thoughtful writing elevates the reader to a more thoughtful state of mind. There is also a self-care aspect to this kind of deliberate shift. Ben wrote that he found himself “craving more nuance and depth” among “quick, in-the-now status updates”. I believe this points to a scarcity of thoughtfulness in such short form writings. Spending more time reading thoughtful posts not only alleviates such scarcity, it can also displace the artificial sense of urgency to respond when scrolling through soundbyte status updates. When I returned from #W3CTPAC, I made a list of all the thoughts, meetings, sessions that I wanted to write-up and publish as blog posts to capture my experiences, perspectives, and insights beyond any official minutes. Yet due to distractions such as catching up on short form posts, it took me over a week to write-up even a summary of my TPAC week, nevermind the queue of per-topic notes I wanted to write-up. To even publish that I had to stop and cut-off reading short form posts, as well as ignoring (mostly postponing) numerous notifications. There’s a larger connection here between thoughtful reading, and finding, restoring, and rebuilding the ability to focus, a key to thoughtful writing. It requires not only reducing time spent on short form reading (and writing), but also reducing notifications, especially push notifications. That insight led me to wade into and garden the respective IndieWeb wiki pages for notifications, push notifications, and document a new page for notification fatigue. That broader topic of what do to about notifications is worth its own blog post (or a few), and a good place to end this post. Thanks again Ben for your blog post. May we spend more time reading & writing such thoughtful posts.
: I recently wrote a high level summary blog post:W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023https://tantek.com/2023/262/b1/w3c-technical-plenary-tpacof my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.Posting this note to explicitly #hashtag that article with topics mentioned therein:#Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPubbecause I forgot to put explicit categories (p-category markup) in the article post.Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.Post glossary:article post https://indieweb.org/articlenote post https://indieweb.org/notep-category https://indieweb.org/p-categorytags https://indieweb.org/tags
's status on Sunday, 24-Sep-2023 21:33:00 EDT
I recently wrote a high level summary blog post: W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023 https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac of my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before. Posting this note to explicitly #hashtag that article with topics mentioned therein: #Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub because I forgot to put explicit categories (p-category markup) in the article post. Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works. Post glossary: article post https://indieweb.org/article note post https://indieweb.org/note p-category https://indieweb.org/p-category tags https://indieweb.org/tags
: going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST.Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others!So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications.We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb.We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others.@snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856
's status on Monday, 11-Sep-2023 19:06:00 EDT
going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST. Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others! So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications. We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb. We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others. @snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856
: Led two virtual #w3cTPAC breakout sessions this week:* Environmental Concerns and #Sustainability (#s12y) of Web Technologies[1]* What is the value of and are the values of @W3C[2]and helped @seaotta with:* What is the WebWeWant.fyi[3]Notes:[1] https://www.w3.org/2021/10/19-sustainability-minutes.html[2] https://www.w3.org/2021/10/22-what-values-minutes.html [3] https://www.w3.org/2021/10/19-webwewant-minutes.htmlAlso participated in Accessibility & CSS (https://www.w3.org/2021/10/20-cssa11y-minutes.html).Preparing for, speaking, facilitating, and participating in virtual TPAC sessions a second year in a row was very draining. Despite that, I thought the sessions went fairly well overall.Most passionate and contentious was the session on sustainability, especially regarding what we should (or should not) do @W3C. There was a lot more alignment on the seriousness and urgency to act than I expected, and I was pleased to see that.There was a lot of support for figuring out how to establish Sustainability as an aspect of Horizontal Review of all technical specifications, as important as Accessibility (a11y), Internationaliation (i18n), Security, and Privacy. This would likely require an explicit Interest Group, with a charter, discussed and voted on by the W3C’s Advisory Committe (AC).Our shared sense of urgency made it clear we needed to start something sooner rather than later. A Community Group (CG) makes the most sense in the short term, chartered to work on both immediate horizontal review and the establishement of a more official Interest Group.I created a #sustainability channel on the W3C’s Community Slack instance to start informal discussions to get a Community Group started.Join us: https://twitter.com/w3c/status/1252972104456306688
's status on Friday, 22-Oct-2021 21:33:00 EDT
Led two virtual #w3cTPAC breakout sessions this week: * Environmental Concerns and #Sustainability (#s12y) of Web Technologies[1] * What is the value of and are the values of @W3C[2] and helped @seaotta with: * What is the WebWeWant.fyi[3] Notes: [1] https://www.w3.org/2021/10/19-sustainability-minutes.html [2] https://www.w3.org/2021/10/22-what-values-minutes.html [3] https://www.w3.org/2021/10/19-webwewant-minutes.html Also participated in Accessibility & CSS (https://www.w3.org/2021/10/20-cssa11y-minutes.html). Preparing for, speaking, facilitating, and participating in virtual TPAC sessions a second year in a row was very draining. Despite that, I thought the sessions went fairly well overall. Most passionate and contentious was the session on sustainability, especially regarding what we should (or should not) do @W3C. There was a lot more alignment on the seriousness and urgency to act than I expected, and I was pleased to see that. There was a lot of support for figuring out how to establish Sustainability as an aspect of Horizontal Review of all technical specifications, as important as Accessibility (a11y), Internationaliation (i18n), Security, and Privacy. This would likely require an explicit Interest Group, with a charter, discussed and voted on by the W3C’s Advisory Committe (AC). Our shared sense of urgency made it clear we needed to start something sooner rather than later. A Community Group (CG) makes the most sense in the short term, chartered to work on both immediate horizontal review and the establishement of a more official Interest Group. I created a #sustainability channel on the W3C’s Community Slack instance to start informal discussions to get a Community Group started. Join us: https://twitter.com/w3c/status/1252972104456306688
: At #w3cTPAC this week: @CSSWG, #Future of @W3C, #WICG. Come say hi!Still reflecting on #XOXOFest themes & learnings. Particularly how much online abuse & harassment is growing. Let’s chat about this at TPAC, brainstorm if/how we can improve web building blocks to reduce harm, especially toward marginalized individuals & communities.
's status on Monday, 16-Sep-2019 02:36:00 EDT
At #w3cTPAC this week: @CSSWG, #Future of @W3C, #WICG. Come say hi! Still reflecting on #XOXOFest themes & learnings. Particularly how much online abuse & harassment is growing. Let’s chat about this at TPAC, brainstorm if/how we can improve web building blocks to reduce harm, especially toward marginalized individuals & communities.
: at #w3cTPAC all weekMT: @CSSWG made a new draftW: Explained & facilitated @W3C Plenary day #BarCampThF #WPWG #WICG
's status on Wednesday, 08-Nov-2017 16:19:00 EST
at #w3cTPAC all week MT: @CSSWG made a new draft W: Explained & facilitated @W3C Plenary day #BarCamp ThF #WPWG #WICG