Merge pull request #83 from w3c/TzviyaSiegman-patch-3

Aug 7 minutes

Author: TzviyaSiegman

minutes/2025-08-07.md

@@ -0,0 +1,98 @@
+# Sustainable Web IG Minutes 2025-08-07
+
+## Agenda https://github.com/w3c/sustainableweb-ig/issues/81
+
+**Attendees:** Mike Gifford (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Tim Frick (Chair), Chris Adams, Eloisa Guerrero, Andrew Wright, Ryan Sholin, Jenn Strickland, Rose Newell, François Burra, Emma Horrell, Nick Lewis
+
+
+## Recording
+Permission to record and share recordings widely
+https://drive.google.com/file/d/13yJEtfaFnghMoU-XiaawOdcNsJ61bmgO/view?usp=sharing
+
+
+## Agenda + Notes
+
+1. Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/)
+
+2. **Reminder:** You can join any TF you wish (more than one / change / etc).
+
+3. **Questions/comments** from the last meeting.
+
+4. Tzviya Github walkthrough / discussion (Note: [W3C Guide](https://www.w3.org/guide/github/)) See also https://github.com/w3c/sustainableweb-wsg/blob/main/IG-CONTRIBUTING.md
+
+5. **Task Force Breakouts**
+   - Group Feedback (Blockers & Updates)
+
+   - Discussion regarding accessibility statements. Mike Gifford provided these two relevant links
+       - <https://www.w3.org/WAI/planning/statements/>
+       - <https://www.gov.uk/government/publications/sample-accessibility-statement>
+   - UX:
+     - Check in on spreadsheet :
+     - Jen will start setting up for upcoming workshops (Thorsten is on holiday for two weeks, Rose is focused on July milestone)
+     - Discuss UX measurement
+     - Notes from UX Group breakout:
+       - Thanks to Rose and Andrew for their work on the UX document
+       - Decided on a colour code for linguistic changes (shade in yellow) and for global changes (shade in blue) - colour coding advice at the top of the spreadsheet
+       - Update on TPAG registration process
+- WebDev:
+
+  - Not meeting right now
+
+- Hosting:
+
+  - Not meeting right now
+
+- Product/Biz:
+
+  - Meeting scheduled for Aug 19, 10am CST/5pm CET
+
+  - Zoom link: <https://us02web.zoom.us/j/83492131319?pwd=tdV2b40ALNxuTRCl0TfzUJp19yK2QH.1&jst=3>
+
+  - Miro board: <https://miro.com/app/board/uXjVJcdX6x4=/>
+
+  - Proposed agenda in Slack; will move to GitHub
+
+    - [Link to agenda in Miro](https://miro.com/app/board/uXjVJcdX6x4=/?moveToWidget=3458764636720631933\&cot=14)
+
+  - Notes:
+
+    - One of the key goals of the 19th meeting is figuring out how to get this section in shape to get it accepted as an _advisory note.
+    - We have some folks able to join at the 17:30 point
+- Measurability:
+  - In last Tuesday’s meeting, Measurability TF has created a [spreadsheet](https://github.com/w3c/sustainableweb-wsg/issues/)
+
+    - Identify any things that are straightforward to measure, e.g. minification is binary measurement
+
+    - Can always adjust measurability
+
+  - Tzviya: Looking at webdev section -- How are we tying back the definitions to our criteria
+
+  - Alex: Come up with a set of predefined characteristics that we want to look for that improve sustainability, backed up by evidence-based material, and a sort of metric/measurement of it, e.g. amount of bandwidth production can be done across all of success criteria, how much bandwidth reduction do all of the SC present? Contribute to their overall score.
+
+  - Ryan: Does this make it more complicated?
+
+  - Alex: It reduces complexity if you’re predefining certain things. Gives us a specific threshold for what we’re working in.
+
+  - Tzviya: How do we fill out the spreadsheet? How would I assess how each one of these are low or medium?
+
+  - Alex: Assume best guess based on what we know about sustainability. Do we think that this would be high, medium, or low, based on what we know? Because we’re time-pressured we have to do this ad-hoc style; would be better to have a more rigorous way to do this.
+
+  - Tzviya: We need information in order to make a decision on whether something is high or medium or low.
+
+  - Alex: The only way we can gather that kind of evidence, there’s a lot of best practices or assumed knowledge based on what we know about sustainability and its ramifications and indirect consequences-- the only way to put this into practice would be through tooling. We need to create a tool that would go through these SCs and to say if we want to test certain things like CPU, GPU, bandwidth, and test against a cohort of websites, do some benchmarking. Need to gather data from a larger scale. 
+
+  - Alex has list of variables at https://websitesustainability.com/cache/files/variables.pdf
+
+  - Ryan: Should we write down those assumptions? Make another list?
+
+  Next step - figure out which variables to cross-index for GRI info in Fershad's spreadsheet
+
+2. Community + News
+
+3. [Open Issues](https://github.com/w3c/sustainableweb-ig/issues) ([Kanban](https://github.com/orgs/w3c/projects/198))
+
+   - [**WSG**](https://github.com/w3c/sustainableweb-wsg)**:** Discuss <https://github.com/w3c/sustainableweb-wsg/issues/94> take a look at this issue. We need consensus around definition of Sustainability as Alex reviews and revises Intro
+
+   - **IG:** None
+
+4. Other discussion/questions