├── CODE_OF_CONDUCT.md ├── IG-CONTRIBUTING.md ├── LICENSE.md ├── README.md ├── ie-policy.md ├── minutes ├── 2024-12-05.md ├── 2025-01-09.md ├── 2025-01-23.md ├── 2025-02-06.md ├── 2025-02-20.md ├── 2025-03-06.md ├── 2025-03-20.md ├── 2025-04-03.md ├── 2025-04-17.md ├── 2025-05-01.md ├── 2025-05-15.md └── 2025-05-29.md ├── multipage.md ├── timeline.svg └── w3c.json /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | All documentation, code and communication under this repository are covered by the [W3C Code of Conduct](https://www.w3.org/policies/code-of-conduct/). 4 | -------------------------------------------------------------------------------- /IG-CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | Contributions to this repository are intended to become part of Interest Group documents governed by the [Software and Document License](https://www.w3.org/copyright/software-license/). By committing here, you agree to that licensing of your contributions. 2 | 3 | If you are not the sole contributor to a contribution (pull request), please identify all contributors in the pull request comment. 4 | 5 | To add a contributor (other than yourself, that's automatic), mark them one per line as follows: 6 | 7 | ``` 8 | +@github_username 9 | ``` 10 | 11 | If you added a contributor by mistake, you can remove them in a comment with: 12 | 13 | ``` 14 | -@github_username 15 | ``` 16 | 17 | If you are making a pull request on behalf of someone else but you had no part in designing the feature, you can remove yourself with the above syntax. 18 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | All documents in this Repository are licensed by contributors 2 | under the 3 | [W3C Software and Document License](https://www.w3.org/copyright/software-license/). 4 | 5 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # W3C Sustainable Web Interest Group 2 | Welcome to the repository for the [W3C Sustainable Web Interest Group](https://www.w3.org/groups/ig/sustainableweb/). 3 | 4 | ## Mission 5 | 6 | Digital Sustainability is an evolving field that is complex and undergoing significant change due to technological advances such as Artificial Intelligence and legislative shifts. The complexity of these rapid changes increases the need and urgency to provide guidance for those expected to meet climate-related goals and targets. 7 | 8 | The mission of the [W3C Sustainable Web Interest Group](https://www.w3.org/groups/ig/sustainableweb/) is to improve digital sustainability so that the Web works better for all people and the planet. 9 | 10 | We do this through advancing the development of the [Web Sustainability Guidelines (WSG)](https://w3c.github.io/sustainableweb-wsg/), its [supplementary materials](https://github.com/w3c/sustainableweb-wsg), and advocacy work (in digital sustainability) to educate and advise on any implementations of our work and its importance in the context of their organizations. 11 | 12 | See also the [Sustainable Web Interest Group Charter](https://www.w3.org/2024/10/ig-sustainableweb-charter.html). 13 | 14 | ### History 15 | 16 | ![Timeline of the W3C Sustainable Web Interest Group's history from Community Group to it's current status.](timeline.svg) 17 | 18 | Formed in 2013, the [Sustainable Web Design Community Group](https://www.w3.org/community/sustyweb/) brought together like-minded individuals from various backgrounds with a passion for sustainability. While it originally served as a method of sharing useful resources on digital sustainability, the need to do more for both people and the planet urged the group to start regular Zoom meetings, and a plan was formed. 19 | 20 | Organizing into five committees (based on the four categories noted in the WSGs and a team focused on metrics), the community group spent three years carefully writing and cultivating the Web Sustainability Guidelines into its current Draft Report. 21 | 22 | As a W3C Interest group we continue the work of this Community Group, further improving upon the hard work that has been achieved over this period. 23 | 24 | ## Participate 25 | 26 | ### Frequently Asked Questions 27 | 28 | What work is the Interest Group producing? 29 | > We are currently creating a set of international guidelines that aim to advocate advisory best practices around digital sustainability. With coverage around user-experience design, Web development, development operations, and business/product strategy; the Web Sustainability Guidelines (WSG) aims to prioritize people and the planet in the product creation cycle. 30 | > 31 | > Using evidence-based methodologies, this set of guidelines will enable implementers to reduce their digital carbon footprint and practice sustainable design and development, meeting regulatory compliance targets as well as industry best practices. 32 | 33 | Who should participate in this group? 34 | > The Sustainable Web Interest Group encourages active participation from a diverse community. You should consider participating in this Interest Group, in particular, if you are in one of the following communities: 35 | > - Vendors of Web browsers seeking to improve the sustainability of the browsing experience. 36 | > - Organizations and agencies that focus on marketing, web design / development, devops, and related digital services. 37 | > - Individuals or organizations with a background or interest in promoting and / or implementing digital sustainability. 38 | > - Sustainability-specific organizations, especially those looking to improve reporting and practices or those that serve our industry. 39 | > - Software vendors or open source projects developing digital sustainability solutions utilizing the WSGs. 40 | > - Government organizations seeking to standardize or develop policies around digital sustainability. 41 | > - Academic researchers or scientists with an interest in digital sustainability and eco-design. 42 | > - Industry association or standards body representatives. 43 | 44 | How can I join the group as an official participant? 45 | > - If you are affiliated with a [W3C member organization](https://www.w3.org/Consortium/Member/List), consider [joining our Interest Group](https://www.w3.org/groups/ig/sustainableweb/join/) (you will require a W3C account to participate). 46 | > - If you do not work for a W3C Member organization, please first consider whether your employer can [join W3C](https://www.w3.org/Consortium/join) and [get the benefits of Membership](https://www.w3.org/Consortium/membership-benefits). 47 | > - If that is not an option and you think that you have the expertise and availability to participate, please check our [Invited Expert Policy](ie-policy.md) for [becoming a member](https://www.w3.org/groups/ig/sustainableweb/join/) of our Interest Group. 48 | 49 | ### Methods 50 | 51 | If you wish to contribute, the below methods are how our group facilitates the delivery of our activities. 52 | 53 | #### GitHub 54 | 55 | This Interest Group primarily conducts its technical work through GitHub. We welcome contributions through issue-raising and pull requests on our publicly available repositories for both our [Interest Group](https://github.com/w3c/sustainableweb-ig/) and the [Web Sustainability Guidelines](https://github.com/w3c/sustainableweb-wsg/) (WSG). 56 | 57 | - Issue Tracker ([Interest Group](https://github.com/w3c/sustainableweb-ig/issues) / [WSG](https://github.com/w3c/sustainableweb-wsg/issues)) 58 | 59 | #### Feedback 60 | 61 | We welcome individuals who are unaffiliated with our group to provide feedback on our work through whatever means they feel will help encourage the improvement of our work or early adoption. 62 | 63 | Examples of this may include: 64 | 65 | - Providing feedback and commentary through articles or blog posts. 66 | - Showcasing implementations, test cases, and early adoption of our work. 67 | - Speaking about or presenting materials that will educate and inform. 68 | - Creating tooling to enable implementations of the WSGs. 69 | 70 | #### Meetings 71 | 72 | Typically, participation in Face-to-face meetings and telephone conferences relating to the Interest Group is open just to W3C Members and Invited Experts. IG members can get details of meetings taking place through [this calendar](https://www.w3.org/groups/ig/sustainableweb/calendar/) and by examining our [meeting agenda](https://github.com/w3c/sustainableweb-ig/issues?q=label%3Aagenda+), also available in [Google Docs](https://docs.google.com/document/d/1mDp2Ao_FaurV4GCVkoYFz2NtgYhmeRAjYLKvqMAIEbk/edit?usp=sharing). 73 | 74 | We use **Zoom** for meetings, and some people may use video. We also record meetings for those unable to attend. Please consider this if choosing to participate in our events. 75 | 76 | #### Slack 77 | 78 | We coordinate regularly over Slack. We have regular discussions in the **#sustainability** channel with other members who have an interest in the topic of digital sustainability. You can join the Slack community [through this invite](https://www.w3.org/slack-w3ccommunity-invite). 79 | 80 | **Note:** If you have any questions regarding the Interest Group, feel free to DM a chair or editor and we will get back to you. We're friendly people, honest! 81 | 82 | #### Mailing List 83 | 84 | To keep up-to-date with our activity, make sure you're signed up to our [public mailing list](https://lists.w3.org/Archives/Public/public-sustainableweb/) (as this is where major announcements get posted). 85 | 86 | #### Events 87 | 88 | Our Interest Group may on occasion choose to run workshops to help organizations, groups, and individuals better understand how to meet the targets laid out in the Web Sustainability Guidelines (WSG). In addition, as part of our outreach efforts participants may choose to speak at or attend various events to spread the word about or gain industry feedback on our work. 89 | 90 | ## Participants 91 | 92 | The co-chairs of the Sustainable Web Interest Group are: 93 | 94 | - **Ines Akrap** (Storyblok) 95 | - **Tim Frick** (Mightybytes) 96 | - **Mike Gifford** (CivicActions) 97 | 98 | The editor of the Web Sustainability Guidelines (WSG) is: 99 | 100 | - **Alexander Dawson** (Invited Expert) 101 | 102 | The W3C Team Contact for the group is: 103 | 104 | - **Tzviya Siegman** (W3C) 105 | 106 | See also the [list of participants](https://www.w3.org/groups/ig/sustainableweb/participants/) involved in the Interest Group. 107 | -------------------------------------------------------------------------------- /ie-policy.md: -------------------------------------------------------------------------------- 1 | # Invited Expert Policy for the Sustainable Web Interest Group 2 | 3 | Status: This has been reviewed by the IG Chairs. 4 | 5 | # Policy 6 | 7 | W3C Invited Experts are individuals who are invited by a chair of a Working or Interest Group to participate in that group. The chair and the W3C staff must agree that the individual brings particular expertise to the group prior to inviting the individual. 8 | 9 | The [Sustainable Web Interest Group charter](https://www.w3.org/2024/10/ig-sustainableweb-charter.html) states that “The group [...] welcomes non-Members to contribute technical submissions for consideration, although active contributors are expected to join the group.” 10 | 11 | The Chairs expect to invite individuals to participate in the Interest Group as Invited Experts in a manner consistent with the [W3C Invited Expert policy](https://www.w3.org/invited-experts/) and IG Charter. The Chairs will also take into consideration whether individuals: 12 | 13 | * Have participated in the [Sustainable Web Design Community Group](https://www.w3.org/community/sustyweb/) and have contributed to the work of that group. 14 | * Have contributed to the Sustainable Web IG (e.g., via the mailing list or GitHub) as non-participants. 15 | * Have expertise that the Chairs deem important to the success of the group, even if they have not previously contributed to either the CG or IG. 16 | 17 | Once the Chairs have extended an invitation to someone to join as an Invited Expert, that person should review the [instructions for joining the group](https://www.w3.org/groups/ig/sustainableweb/instructions/). 18 | 19 | Individuals are welcome to contact the Chairs to initiate a discussion about participation as an Invited Expert. 20 | 21 | # FAQ 22 | 23 | ## I don't work for a W3C Member. Can I join the group? 24 | 25 | Potentially, yes (per this policy). 26 | 27 | ## I work for a W3C Member. Can I join as an Invited Expert? 28 | 29 | No. Individuals who work for a W3C Member organization participate as representatives of their organization and not via the Invited Expert program. 30 | 31 | ## Are there patent licensing obligations associated with participation in an Interest Group? 32 | 33 | No. There are no patent licensing obligations associated with participation in an Interest Group. However see the [disclosure obligations](https://www.w3.org/policies/patent-policy/20200915/#sec-disclosure-requirements) for Interest Group participants. 34 | 35 | ## Can I subscribe to the mailing list even if I am not a participant? 36 | 37 | Yes. Anyone may [subscribe to the group’s mailing list](mailto:public-sustainability-request@w3.org?subject=subscribe) and post to it. (People who join the group are automatically subscribed.) 38 | -------------------------------------------------------------------------------- /minutes/2024-12-05.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2024-12-05 2 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/11 3 | **Attendees:** Ines Akrap (*Chair*), Tim Frick (*Chair*), Mike Gifford (*Chair*), Alexander Dawson (*Editor*), Tzviya Siegman (*W3C*), Adam Newman, Alekh Gupta, Andrea Davanzo, Christian H Brown, Emily Trotter, François Burra, Greg MacDonald, Hidde De Vries, Ignacio Rondini, Jeroen Hulscher, Kazuhito Kidachi, Laurent Devernay, Louise Towler, Łukasz Mastalerz, Nahuai Badiola, Neil Clark, Nick Sollecito, Sarah Zama, Thorsten Jonas 4 | ## Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/ "Code of Conduct") 5 | Alex Dawson gave a quick overview of the work that happened so far 6 | Tim Frick: if you want to get involved, bookmark the links shared incl the [GitHub page](https://github.com/w3c/sustainableweb-ig/ "Github") and #sustainability in the W3C Slack. If you want to get involved as someone who works for a W3C member, you can join, if not, you can join as an Invited Expert (there’s a bit of process and we expect some commitment). 7 | 8 | Tim Frick: first set of guidelines was a first pass, we’re now hoping to make them more measurable. 9 | 10 | Tim Frick: we’ll need to find a new meeting time that works for everyone in the group. 11 | 12 | ## [Propose a roadmap](https://github.com/w3c/sustainableweb-ig/issues/10 "issue 10") 13 | Alexander Dawson: If anyone would like to see things added to the list, feel free to do so. 14 | 15 | Tzviya Siegman: we’ll publish a W3C Statement, not a W3C Recommendation, it will have wide review and AC review. Within the sustainability community we had good feedback, some positive, some less so (eg measurability). 16 | 17 | Mike Gifford: part of why we do this is there’s a need for governments to have best practices. It is urgent too, as there’s nothing out there. 18 | 19 | Tim Frick: we’ll use the word “guidelines” until we find out what’s recommendations vs guidelines. Agreed re Mike’s point of speed. 20 | 21 | Tim: Let’s figure out what we can do with what we have, create guidelines (not nec standards). We can look at TFs. Think about what TF you’d like to be on. 22 | 23 | Andrea: 2 weeks ago I was at a Low-Carbon conference. Lots of pressure to go ahead with guidelines. E,g, question about what is best back-end language. Java was worst, JS, second worst, Swift is best. 24 | 25 | Laurent: France & Europe are trying to establish a repository of best practices for ecodesign of digital services but we need something more global to get everyone on the same level, something similar to WCAG (even if it is not possible to be strictly similar to this for sustainability). 26 | 27 | Louise: there are things that are measurable and less measurable. Can we triage what’s more or less work? 28 | 29 | Tim: Yes, that is one of the things we can use help with. 30 | 31 | Alex: we did look at what could be machine tested vs what needs manual testing. A model sustainability community has is ok, but also flawed, if we can have the community of interested parties together in a task force we can analyse that information, that can feed into tooling that can produce better quantifiable evidence that can feed back into Web Sustainability Guidelines. And also show when one thing is better than the other. Community needs it and we do too. [Issue about creating task force](https://github.com/w3c/sustainableweb-ig/issues/8#issuecomment-2485963377 "issue 8") For the current set we look at GLI (?), if there are better models and metrics we can integrate those too. We want to back it up with relevant and large studies. 32 | 33 | Thorsten: in talks/workshops I see a lot that folks want to know how to prioritise. What we haven’t looked at much yet is all the unnecessary data that is being stored, that is not being used. Rather than choice of programming language etc. 34 | 35 | Lukasz: @@@ 36 | 37 | Tim: we can go through the guidelines 1 by 1 and review. We’ll need to discuss what goes into the IG vs other groups. 38 | Tzviya: The community group met once a month; most community groups meet weekly, I think we need to meet at least every two weeks. 39 | 40 | ## Release schedule: living document vs stable releases (https://github.com/w3c/sustainableweb-ig/issues/5) 41 | Alex: we had a process for the first version of WSG. We had a living document, where alterations could be made, this was the drafts. Then in the base directory we had public versions, snapshots basically that were released on a set schedule, once we found them stable enough to qualify for that. We could go down that methodology, and various members of the group seemed happy. 42 | 43 | Andrea: sometimes it takes a while for changes to publish, would like this to be faster pace. 44 | 45 | Alex: goal of stable snapshots is so that governments and larger organisations can rely on them 46 | 47 | Tzviya: agreed with Andrea, and the documents are dated, so it is possible to point to a specific release date 48 | 49 | Alex: For non-normative/supplementary guidance and resources, it’d be perfectly fine to have them in one repository, but some might prefer that. 50 | -------------------------------------------------------------------------------- /minutes/2025-01-09.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-01-09 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/14 4 | 5 | Attendees: Ines Akrap (Chair), Tim Frick (Chair), Mike Gifford (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Morgan Murrah, Oliver Winks (Root & Branch), François Burra (Climate Product Leaders), Denis DIDIER (Groupe ISIA-FR)Sarah Zama (University of Oxford) Nicola Bonotto (Piano D), Kazuhito Kidachi (Mitsue-Links), Francesco Fullone (Daruma Consulting), Christian H Brown (Mitsue-Links), Neil Clark, Adam Newman, Hannah Smith, Chris Adams 6 | 7 | ## Introductions & Code of Conduct 8 | Consent to record meeting and share recording to email list. 9 | 10 | ## Open Issues: 11 | Create task forces for WSG 12 | * Measurability TF: Laurent Devernay, Lukasz Mastalerz, Adam Newman, Hannah Smith, Neil Clark, Nicola Bonotto, Oliver Winks 13 | * Web Dev TF: Kazuhito Kidachi, Elene Guerrero, Hidde de Vries, Oliver Winks 14 | * UX: Emily Trotter, Christian Brown, @ehorrell, Tim Frick 15 | * Business Strategy and PM: François Burra, Francesco Fullone, Christian H Brown, @ehorrell, Hidde de Vries, Denis DIDIER, Chris Adams, Tim Frick 16 | Contact various organisations (cloud / hosting / browser vendors, standards bodies, etc) to request if they would get involved and help improve the guidelines. 17 | 18 | Review feature requests and set timeline / schedule for specification 19 | Discuss the below features, set a timeline or schedule date for the WSG (any other feature ideas please submit as we are open to anything that will help mature the spec). 20 | Review Overlapping Guidelines 21 | 22 | Standards Referencing 23 | Tzviya: less of a problem to link to standards like ISO than proprietary links than Azure, but we can revisit proprietary later. Because there is so much happening now with standards, it makes sense to have links to ISO, IEEE, IETF 24 | Neil: it would be helpful to have additional resources as well, including proprietary 25 | Alex: we can have separation of concerns within doc 26 | Hannah: very keen to support work on gathering together actionable resources such as case studies or specific, tangible examples or working out how to make what’s there more navigable. It would support needs we keep hearing from those out in the community trying to take steps - what are each of these resources and how do they help each guideline more specifically. Hit me up for a chat if of interest to explore 😀 27 | 28 | Tooling Support 29 | Discussion about need from browsers and tool developers to understand how to expose sustainability data to users and for testing purposes. 30 | Mike: ATAG could be useful if integrated within WSG as it would provide structured guidance for implementation from those helping users make sustainable choices. 31 | Tzviya: this should be a fundamental goal of the group 32 | 33 | Translations 34 | Alex: we’ll address after writing 35 | Measurability 36 | How do we define which tools are most impactful, most effortful, system boundaries/trade-offs. We’d like to build up implementation report from tooling. This will come from Measurability TF. See basis of STAR. 37 | Educational Materials 38 | We will work on bolstering image, help people understand materials. This feeds into adoption 39 | Useful Tooling 40 | List useful tools 41 | 42 | Save the date: Next meeting is Jan 23 2025. 43 | -------------------------------------------------------------------------------- /minutes/2025-01-23.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-01-23 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/16 4 | 5 | Attendees: Ines Akrap (Chair), Tim Frick (Chair), Mike Gifford (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Kazuhito Kidachi (Mitsue-Links), Łukasz Mastalerz, Nicola Bonotto (Piano D), Tristan Nitot (TAG & OCTO Technology), Laurent Devernay Satyagraha (Greenspector), Andrea Davanzo (Open University), Ryan Sholin (Overt Impact), Francesco Fullone (Daruma Consulting), Chris Adams (GSF), Crystal Preston-Watson (Salesforce), Christian H Brown (Mitsue-Links), Denis Didier, Adam Newman, Oliver Winks, Sara Zama (Oxford), Jennifer Strickland (Mitre) 6 | 7 | ## Introductions & Code of Conduct 8 | Consent to record meeting and share recording to email list. 9 | 10 | ## Open Issues: 11 | Our Draft Note deadline 12 | * First Draft: 30 June 2025 13 | * Final Draft: 31 Dec 2025 14 | * Measurability: 31 Mar 2026 15 | * W3C Draft Note: 22 Apr 2026 (Earth Day) 16 | 17 | ## Create task forces for WSG 18 | * Discuss where broader subjects (content, marketing, AI) should be placed. 19 | * Overview and allow people to get names down for different groups. 20 | * Break into groups: 21 | * Assign a scribe 22 | * Nominate & vote for Task Force leads. 23 | * Quick group review of existing guidelines. 24 | * Discussion on how best to audit the guidelines (keep as is, remove, add, update, fix). 25 | * Note: Measurability TF will discuss how best to approach better metrics data. 26 | * Create a rough timeline for objectives / meetings / strategy. 27 | * Begin work using groups Google Doc (if helpful) to achieve objectives. 28 | 29 | See detailed minutes from individual groups: 30 | 31 | Business/strat - no leader yet, is this applicable to one site/page? Some legislation requiring working on csrd 32 | 33 | WebDev: avoid clashing with a11y specs, reconsider approach to specific tech like JS, because would have to mention other tech like php, should say dynamic/static pages. 34 | 35 | Measurability: Łukasz - trying to understand the goal, want to understand creators to reduce, discuss usability of guidelines, research on our own v use what exists. Will probably use what exists, but we know that it’s unlikely to be measurable with high precision, so we will have to aim for executable. 36 | 37 | UX: discussed process, new members - will check who else wants to participate. Many people missing today. Discussed a11y, performance, and identified ways UX impacts the people affected and how it can quickly make people understand the work we are doing. 38 | 39 | Hosting/Infra: Trying to understand audience/scope, what is measurable and understandable. Are these binary questions or for discussion? We tried to understand who we might bring in and interview - people from public cloud, orgs with existing sustainability reports, etc and focused on some specific guidelines and how they might be improved. 40 | 41 | ## AOB 42 | Question about how to submit editorial comments about WSG. Alex will accept GitHub Pull Requests, issues, Google Docs, email, or carrier pigeon. Get the information to Alex, and he will synethesize it into the ReSpec document. 43 | 44 | 45 | Save the date: Next meeting is Feb 06 2025. 46 | -------------------------------------------------------------------------------- /minutes/2025-02-06.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-02-06 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/18 4 | 5 | Attendees: Ines Akrap (Chair), Tim Frick (Chair), Mike Gifford (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Laurent Devernay Satyagraha, Andrea Davanzo, Łukasz Mastalerz, Kazuhito Kidachi, Hidde de Vries, Christian H Brown, Nahuai Badiola, Denis DIDIER, Nicola Bonotto, Francesco Fullone, Crystal Preston-Watson, Neil Clark, Sarah Zama 6 | 7 | 8 | ## Introductions & Code of Conduct 9 | Consent to record meeting and share recording to email list. 10 | 11 | ## Open Issues: 12 | Shift guideline descriptions > “additional content”. 13 | * The best approach to re-structure a guideline: shift vs extract vs discard 14 | * Alex suggested a show/hide approach to keep everything in one place 15 | * Andrea challenging sustainability aspect of such a large document: not everyone needs/wants all the descriptions and links 16 | * Hidde WCAG experience: Normative vs non-normative approach 17 | * Sarah suggesting to get input from users: usability vs. sustainability 18 | 19 | Better tagging system: label choices for SCs. 20 | * Expanding system for better search/filter: input from the group on categories 21 | * Examples: 22 | * sustainablewebdesign.org 23 | * filtered WCAG 24 | 25 | What challenges are task forces facing in making progress? 26 | * WebDev: time to get feedback very long (Andrea) 27 | * Tzviya suggested alternatives: Github instead of Slack, having more alignment meetings 28 | * Metrics: what are the questions we are trying to answer + how measurable are current guidelines (Lukasz) 29 | * Tzviya shared article: https://arxiv.org/pdf/2406.09645 30 | * Suggestion to separate measurement by Internet layers (Tzviya) 31 | * Could the same model be applied to different guidelines (Lukasz) 32 | * Not possible to answer CO2 question for more than 15% of the guidelines (Lukasz) 33 | * Make sure to be transparent and open on the measuring models (Andrea) 34 | * Decide if metric is measurable or not as a first step and let users decide on the model to use (suggest some) (Nicola) 35 | * Recommendation, not strict definition (Neil) 36 | * Unclear if it makes sense to create similar groupings like A/AA/AAA like WCAG or groupings like estimation of emissions, UX information, so that there is data with score by category (Ines) 37 | * Andrea’s comments 38 | * Looking from an ESG perspective, we could potentially score from social and gov aspect as well. For A11y could refer to WCAG, and similar. If we are looking at different pathways, the filtering system could work well (tagging, roles, etc) 39 | 40 | * Which task forces still need leads/co-leads/support? If any TFs need leads/co-leads or help arranging discussion on Slack. GitHub, Zoom, or any other form of communications reach out to Tim, Ines, Mike, Alex, or Tzviya 41 | 42 | 43 | -------------------------------------------------------------------------------- /minutes/2025-02-20.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-02-20 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/20 4 | 5 | Attendees: Tim Frick (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Łukasz Mastalerz, Nahuai Badiola, Rose Newell, Ryan Sholin, Tristan Nitot, Jen Strickland, Kazuhito Kidachi, Hannah Smith, François Burra, Alisa Bonsignore, Oliver Winks, Chris Adams, Adam Newman, Christian H Brown, Neil Clark 6 | 7 | ## Introductions & Code of Conduct 8 | Consent to record meeting and share recording to email list. 9 | 10 | ## Open Issues: 11 | Alex: WSG Progress Report 12 | * 3 New SC’s (Sustainable APIs - we had a listing for sustainable media queries to reduce carbon footprint, so we added one about sust JS, Client VS Server new SC re: redundant processing and whether better to do processing on client or server side, Automated Tooling thanks to Rose, new SC about scrapers and bots and declaration of non-humans for opt-out purposes). 13 | * New JSON API for STAR (IG and WSG readme - does not require people to go to GitHub, more user-friendly. 15 | * 6 updated or merged SC’s across Web Dev, Infrastructure, & Business. 16 | ** Merged SCs: 17 | *** (former 3.19) into 3.18 18 | ** Updated SCs: 19 | *** 2.16, 3.8, 4.2, 4.3, 5.20 20 | * Lots of other bugs and fixes applied & plenty of new URLs. 21 | 22 | Task forces: how to jumpstart progress? 23 | * Workload expectations - Infra doing well, metrics needs more clearly defined goal. Discussion about refining goals of the group, clarifying the roles and audiences. Recommendation to share data and background about sustainability (possibly in adjacent docs). For metrics, Important to mention that we are stressing improvement over time instead of an end goal. Mention that we are talking about intensity impact not total impact (e.g. if org grows). 24 | * Going from 95% to 96% in terms of the quality of the guidelines is great. There is no global report on adoption of digital sustainability. We can talk about anecdotal information, but it’s not enough to give confidence to people taking the first step. We need ROI at scale. There are so many playbooks and guidelines, but perhaps the biggest issue is to convince people to take the first step. Perhaps helping them assess where they are with maturity could be a good idea. 25 | * What if we shift focus of WSG to be a way to test (maybe we GWF and MDN?) to help people come together to report on sustainable web sites? (spitball idea) 26 | * Alex: many SCs are not measurable. We could potentially produce a report similar to the report we did on http archive. If we have some kind of numbers that we are working with then we can say that we could have this (numeric) impact. 27 | * It’s unclear from looking at WSG how to subset the SCs - which are the priorities. (ranking system like A, AA, AAA could be helpful) 28 | * What can we do to help you accomplish tasks between meetings? 29 | 30 | Guidelines restructuring discussion 31 | * Move guideline text into “Additional Content” (discussed last meeting). proposal to separate non-normative text to separate doc. General consensus 32 | * Defaulting to multi-page with full-page option / two spec versions alike WHATWG. Group agrees to multi-page with full-page option. 33 | * Filtering SC by tag [discipline / category / pathway] (discussed last meeting). 34 | * Put references in supplement and group by SC, highlighting best content. Maintenance of links could become challenging, so it will be easier to keep it up to date separately. 35 | * There is interest in grouping by role - i.e. “I am an API developer”, “I am a UX developer”, “I am a product manager”, where should I look first? So these are easier to digest coming to the WSGs for the first time. 36 | 37 | 38 | -------------------------------------------------------------------------------- /minutes/2025-03-06.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-03-06 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/22 4 | 5 | Attendees: Ines Akrap (Chair), Tim Frick (Chair), Mike Gifford (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Kazuhito Kidachi, Hidde de Vries, Sarah Zama, Jennifer Strickland, Laurent Devernay Satyagraha, Eloisa Guerrero, Tristan Nitot, Adam Newman, Denis DIDIER, François Burra, Crystal Preston-Watson, Ryan Sholin, Chris Adams, Christian H Brown, Hannah Smith, Andrea Davanzo 6 | 7 | ## Introductions & Code of Conduct 8 | Consent to record meeting and share recording to email list. 9 | 10 | ## Open Issues: 11 | Alex: WSG Progress Report 12 | * Relationships introduction section - updated information about relationships to various other Sustainability docs 13 | * SC Update (2.17: Avoid Overburdening) 14 | * Guideline Update (3.2: Remove unnecessary or redundant information) 15 | * Guideline Update (3.3: Modularize bandwidth-heavy components within projects) 16 | * Readability improvements! 17 | ** Guideline Title is sentence case & more informative 18 | ** Additional Content redesign (for improved visibility) - made more visible 19 | ** Guideline Descriptions (now Intent) moved to Additional Content 20 | ** Multipage by default (full-document still works) - Hidde offered to improve a11y 21 | * Bunch of other bugs squashed along the way 22 | 23 | Tzviya encouraged feedback on these major updates. 24 | 25 | Hannah asked about the relationship to pages like sustainablewebdesign.org and APIs. Alex explained the interconnectedness of all documents in the W3C repo. Tim explained that updates sustainablewebdesign.org when there is a major update. 26 | 27 | Alex intends to release a batch of release notes at the end of March (quarterly release notes). 28 | 29 | SBTi - Yesterday we got a contact with Science Based Targets Initiatives, which should improve our measurability work. 30 | 31 | ## Touch base with TFs https://github.com/w3c/sustainableweb-ig/issues/8 32 | * UX: Ines sent a poll for a TF meeting https://www.when2meet.com/?29396289-egXBJ. Still need a TF leader 33 | * Infra/Hosting: Ryan: no edits on in last weeks, but we are working on a draft with Laurent 34 | * Hannah: Is the measurability TF meeting? Unclear, but feel free to get it started 35 | 36 | AOB: Green IO NY coming up: Here’s the link to the Green IO conference: https://greenio.tech/conferences 37 | 38 | Poorly minuted discussion of relationship between tooling and W3C guidelines 39 | 40 | Alert: US and Canada change to Daylight Saving Time before the next meeting (20 March). Europe changes to summer time at the end of March. This meeting will stay at 1400 UTC for March. We will switch to 1300 UTC in April. 41 | -------------------------------------------------------------------------------- /minutes/2025-03-20.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-03-20 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/26 4 | 5 | Attendees: Ines Akrap (Chair), Mike Gifford (Chair), Alexander Dawson (Editor), Łukasz Mastalerz, Tzviya Siegman (W3C), Thorsten Jonas, Kazuhito Kidachi, Ryan Sholin, François Burra (Climate Product Leaders), Nahuai Badiola, Adam Newman, Rose Newell, Hidde de Vries, Francesco Fullone, Alekh Gupta, Alisa Bonsignore, Andrea Davanzo, Crystal Preston-Watson, Jennifer Strickland, Laurent Devernay Satyagraha, Oliver Winks, Shane Herath 6 | 7 | Regrets: Tim Frick, Christian Brown 8 | 9 | ## Introductions & Code of Conduct 10 | Consent to record meeting and share recording to email list. 11 | 12 | ## Open issues: 13 | 14 | - Alex: WSG Progress Report 15 | 16 | - New SC ([Sustainable Brand Development](https://w3c.github.io/sustainableweb-wsg/index.html#success-criterion-sustainable-brand-development-human-testable)) - improved general readability of doc, thanks to Rose 17 | 18 | - Lots of under the hood bits and pieces ongoing! - adding tagging. Tzviya added tool to GH to view diffs in text rendering 19 | 20 | * Timeline update: June draft - goal is to have first draft to share with larger W3C by June 30, need to get Alex materials with enough time to incorporate materials 21 | 22 | Measurability has a later deadline 23 | 24 | - [Abstaining W3C group related issues](https://github.com/w3c/sustainableweb-wsg/issues/30)? - W3C has groups that deal with a11y, security, privacy. We don’t want to step on their toes or recreate their work. We want to make sure our SCs are not redundant. It might be better to follow the example in things like WCAG with “privacy considerations” “security considerations” which point to privacy/sec specs and highlight the guidelines that are relevant. Maybe we can point to WCAG, privacy etc and highlight which of our SCs are relevant. 25 | 26 | Andrea: if we have too many points of reference, then this starts to look like an implementation of other specifications 27 | 28 | Hidde: I’m in favor of having a specific section “accessibility considerations” that points to WCAG, but not a 1:1 mapping, happy to help write the section 29 | 30 | Thorsten: there are a11y SCs in UX section as well. I will add them to the doc. There are very specific considerations for UX, and I would prefer to have reference to WCAG. 31 | 32 | Ryan: There are security considerations for hosting/infrastructure as well 33 | 34 | Alex: I flagged the ones that are explicitly covered by WCAG and others. We also have SCs that are not as explicit, but related. 35 | 36 | Rose: I’m concerned about what the security/sustainability plan is. Should you hide WP admin log in? That comes under security, but in reality, it’s not a huge security issue - but it’s a bigger sustainability issue. So it’s more our remit. 37 | 38 | Alex: The WCAG example is not removed, but there is a list of SCs that have privacy implications. We do have some that feel like they should be removed, though. If we are providing something on the sustainability angle, it’s fine. 39 | 40 | Ryan: We can say that we won’t provide info about how to set up a cdn here, just the sustainability info. 41 | 42 | Rose: RE:CDNs, there are legal/privacy issues in the EU that should be noted. Lawsuits in Germany regarding Google Fonts. (Self-hosting also allows other optimisations.) 43 | 44 | Tzviya: We write for the long haul, not just for today. Stay in our WSG lane, narrow focus, link out. We will also have horizontal review (i18n, security, privacy, a11y) that will help with these aspects. 45 | 46 | Ines: What about Web Perf? What do we do with something that crosses over in a negative way? Not all perf recommendations are sustainable. 47 | 48 | Tzviya: Take Perf off the list. It’s not an underlying horizontal value of W3C. We can meet with WebPerf once we have our SCs more organized 49 | 50 | Alex: someone suggested including a trade-offs section along with benefits (If you do implement this, you need to be aware of the following problems…)   51 | 52 | **Consensus:** We removing SCs that are completely covered by other specs with a “Considerations” section. We keep those that are more within the Sustainability story. 53 | 54 | - Accessibility: 3.5 & 5.19 (SC2), _UX: 2.14, 2.20, 2.21 (but these UX criteria are all unique and should probably not be removed)_ 55 | 56 | - Privacy: 5.20 57 | 58 | - Security: 3.16, 4.6 (SC4), 5.12 (SC5) 59 | 60 | - WebPerf: too many to count! 61 | 62 | * [Categories for Tagging / Filtering](https://github.com/w3c/sustainableweb-wsg/issues/14#issuecomment-2612676839) 63 | 64 | - Reuse Guideline Cats (A11y / Privacy / WebSec / HTML / CSS / JS / etc) 65 | 66 | - Job Title (UX / FE Dev / BE Dev / Infra / Biz / Product / …) 67 | 68 | - Planetary (Tags tied to sustainability targets? | GRI > Mineral / Water / etc.) 69 | 70 | - Standards (SDGs / RGESN / AFNOR / Any other tie-ins we have) 71 | 72 | - Other (Testable / Impact / Effort) 73 | 74 | - Any other filters / thoughts on filters? 75 | 76 | Alex: we have pre-defined tags from some, such as testable, impact. Effort. We have relationships with a11y, privacy, etc. There are related Standards: AFNOR, SDGs, AWS, etc. Should we do job titles, planetary goals? I’ll share a spreadsheet for people to fill in first. See for tagging functionality in action. 77 | 78 | Ines: When you used WSG, what was missing to help you find the proper guideline 79 | 80 | - TF Breakouts 81 | 82 | Other discussion/questions: 83 | 84 | - Rose: Laurent and I discussed that there is nothing in WSG for users. Where does it go? 85 | 86 | - Tzviya: education materials would be helpful, but it isn’t for WSG. Regular users won’t look at WSG 87 | 88 | - Jen: write a doc in UX group, and we’ll find a home for it because people want to know what they can do 89 | 90 | - Lukasz: Imagine we had a perfect way to measure impact of every guideline. How will consumers of WSG use them?  91 | 92 | - Adam: It would be specific to each guideline. It would be about amount of reduction, etc 93 | 94 | - Ines: I’ll make this homework. We will discuss this in Slack 95 | 96 | - Tzviya: a metric system would enable users to prioritize 97 | 98 | - Alex: we could sort the doc using metrics and tagging so that the SCs with biggest impact and most relevance are at the top -------------------------------------------------------------------------------- /minutes/2025-04-03.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-04-03 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/37 4 | 5 | Attendees: Ines Akrap (Chair), Mike Gifford (Chair), Tim Frick (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Łukasz Mastalerz, Ryan Sholin, Rose Newell, Hidde de Vries, Thorsten Jonas, Kazuhito Kidachi, Oliver WInks, Eloisa Guerrero, Adam Newman, Chris Adams, Christian H Brown, Jennifer Strickland, Laurent Devernay Satyagraha, Neil Clark 6 | 7 | ## Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/) - consent to record and share 8 | 9 | ## Community + News: 10 | - In-person cloud sustainability speaker wanted for SF Climate Week event, 4/24 - 11 | - Tim: If you’re interested please reach out 12 | 13 | - Green IO NYC, 5/15-16, details + reg link: 14 | - Tim: If you’d like to go to IO in NYC, we’d like as many folks from this group as possible, feel free to reach out to me. Tzviya and I will do a workshop 15 | 16 | - Branch magazine 17 | 18 | - 19 | 20 | - Chris: we’re looking for contributors 21 | 22 | - Chris: the Green Web Foundation got a little bit of funding to explore grid aware websites, went a little bit wider with it and outlined some topics in the CfC. We’re looking for folks who dream of a more sustainable web. Reach me here, or [on LinkedIn](https://www.linkedin.com/posts/green-web-foundation_our-latest-call-for-contributions-to-the-activity-7313558260911857665-QDts?utm_source=share\&utm_medium=member_desktop\&rcm=ACoAAABm1l0BbWA0yfBII3qorrH90vnZOI-51PY). 23 | 24 | - Other announcements 25 | 26 | - Ryan: I am in Copenhagen starting a new role at Electricity Maps. 27 | 28 | ## Open issues: 29 | 30 | - [Release notes for Q1-2025 published](https://github.com/w3c/sustainableweb-wsg/releases) 31 | 32 | - Alex: I added a changelog to the doc itself. We also shared recent updates in the Slack channel, but it is useful to have an overview of what has happened since CG -> IG transition. Feel free to have a look through it 33 | 34 | - [GitHub Issues better tagged](https://github.com/w3c/sustainableweb-wsg/issues) (would Kanban overview be useful?) 35 | 36 | - Alex: We tagged the issues better in the [GH rep](https://github.com/w3c/sustainableweb-wsg/issues) and tagged which TF they belong to so that it’s easier to see which questions are relevant to whom. If people would find it useful I can put them into a kanban board. 37 | 38 | - Tim: love a good kanban board. (others agree) 39 | 40 | - Alex: will send a link to the chairs, will need someone from W3C Team to set it up. 41 | 42 | - GSF’s upcoming workshop (Chris): The GSF is organising a series of SCI for Web workshops in May and June. The GSF and W3C are both membership organisations funded by members so we are working out a way to involve W3C Sustainability IG Invited Experts, to allow free access and avoid duplication of existing work. 43 | 44 | - Chris: worked with GSF and was invited to lead the process for web within the org. We’re trying to figure out how to make it apply to web and make guidance useful to use. There is quite a lot of overlap between what is happening in the Web Sustainability IG and at Green Software Foundation. GSF and W3C are both membership orgs. We’re trying to work out how to make these groups + invited experts collaborate, should be able to share more about how to get involved before the next meeting. This will be about the boundary setting between what is counted and not counted in terms of measuring carbon emissions. 45 | 46 | - Tzviya: we’re keen to make sure we’re all working together and ideally avoid creating slightly overlapping specifications. 47 | - Chris: would prob be starting mid May, meeting every 2 weeks or so, a lot of async work, trying to land something in July. 48 | - Oli: At Root & Branch we have a draft version of a specification that looks at the maps, “SCI for web”, we have an example of how that may work. Would be good to get some eyes on. 49 | - Chris - this is why we want to have invited experts involved in the paper - please keep channels open. This is why we need W3C IG involvement - because these people have already been thinking about this in a structured fashion. Our accounting system was based on Shell’s metrics (See [this podcast interview with Killian Daly of Energy Tag where we touch on where Scope 2](https://podcasts.castplus.fm/e/p8lxlvl8-how-to-tell-when-energy-is-green-with-killian-daly) came from and [this interview with Laurent Segelene on the topic - see 8:07](https://news.wickedproblems.uk/p/laurent-segalen-an-electric-nato)). 50 | - Oli: can send it to everyone who;s interested, will share with you Chris. 51 | - Tim: please share the orgs you’re thinking of publishing this at. 52 | - Oli: currently working with University of Sussex - want things to be openly available, not disappearing in dusty journals, maybe publish through W3C to ensure it gets enough eyes on it as possible. Not saying it is the only way to measure SCI for the web but it’s good to pick it apart. 53 | 54 | - **Rose:** [Chapter intro sections](https://englishroseberlin-my.sharepoint.com/:w:/p/rose/EZe1ored0pVCoyZtLnr6GM4B0zp1oHNEvU3lqqDsm25ZZw?rtime=O1PIl2Vx3Ug) (re-written for clarity - draft) 55 | 56 | - Original: [UX](https://w3c.github.io/sustainableweb-wsg/#user-experience-design) / [WebDev](https://w3c.github.io/sustainableweb-wsg/#web-development) / [Infrastructure](https://w3c.github.io/sustainableweb-wsg/#hosting-infrastructure-and-systems) / [Business](https://w3c.github.io/sustainableweb-wsg/#business-strategy-and-product-management) 57 | 58 | - Please provide feedback here or in TF Slack channels! 59 | 60 | - Rose: we looked at a lot of things re restructuring things, and tried to make things more harmonised. The link above is the draft for how the sections will look in the future. Have been moving things in different places, and there’s a new section further up where the other benefits are included, to make it easier to show to C level. We’ve also tried to make it less audience specific. Where I need support from you: web sustainability not my main expertise, so please help check if I didn’t miss anything. My next task will be to go to individual chapters and clarify questions I have. I don’t want to take away work from Alex, but help him focus. 61 | 62 | - Tim: thanks for all your work on this. 63 | 64 | - Tzviya: for now the docs are in Word. If this doesn’t work for you, it will eventually go to GitHub. 65 | 66 | ## TF Breakouts 67 | 68 | Other discussion/questions: 69 | 70 | - Infra/Hosting : review in progress by Ryan. Then we should share this with an external reviewer, for instance from Google. 71 | 72 | - Measurability: discussed separating out the act of measuring the inputs, from making claims about the sustainability outcomes from this using a model. With this approach at present, it’s _the job of the model_ to turn this input into some kind of claim about the environmental consequences. 73 | 74 | - UX: Link to Miro Board we use: 75 | -------------------------------------------------------------------------------- /minutes/2025-04-17.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-04-17 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/39 4 | 5 | **Attendees:** Ines Akrap (Chair), Mike Gifford (Chair), Tim Frick (Chair), Alexander Dawson (Editor), Shane Herath, Kazuhito Kidachi, Alisa Bonsignore, Jennifer Strickland, Thorsten Jonas, Laurent Devernay Satyagraha, François Burra, James Christie, Sarven Capadisli, Nicola Bonotto, Andrea Davanzo, Denis DIDIER, Chris Adams, Emma Horrell, Francesco Fullone, Rose Newell. 6 | 7 | ## Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/) - consent to record and share 8 | 9 | ## Questions/comments from the last meeting. 10 | None. 11 | 12 | ## Community + News: 13 | - Green IO NYC, 5/15-16 14 | - Follow-up on GSF Workshop (Chris) 15 | - New B Corp Standards: (includes web accessibility!) https://www.bcorporation.net/en-us/standards/performance-requirements/ 16 | 17 | ## [Open issues](https://github.com/w3c/sustainableweb-ig/issues): 18 | 19 | - **Alex:** I’ll be working to implement the great issues we’ve had so far once the tagging system goes live, keep up the good work! 20 | - **Alex:** Filtering Preview (via tags) - Defaults? 21 | - Filtering works in full-document view, you can filter by category, more than one works, it doesn’t interfere with multi-page or ReSpec, only activates when called. 22 | - **Rose:** Editorial progress update 23 | - As before, working on improving the readability of the document. Will be working on each chapter's content. 24 | 25 | ## Major sections (Blockers & Updates) 26 | 27 | - UX - Getting more people onboard, challenges with getting started (format choice). 28 | - WebDev - Also need more contributors but doing well. 29 | - Infrastructure - None. 30 | - Business - None. 31 | - Measurability - Working towards how to calculate testability. 32 | 33 | ## TF Breakouts 34 | 35 | No W3C members present so no recording or breakouts this time (Sorry!). 36 | 37 | ## Other discussion/questions: 38 | 39 | - Old SustyWeb content (redirect to resolve SEO issue?) 40 | - Decision to implement redirect, will be actioned with old copies available via GH releases. 41 | -------------------------------------------------------------------------------- /minutes/2025-05-01.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-05-01 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/40 4 | 5 | 6 | **Attendees:** Mike Gifford (Chair), Tim Frick (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Adam Newman, Oliver Winks, Alisa Bonsignore, Andrew Wright, Jennifer Strickland, sarah zama, Chris Adams, Rose Newell, Emma Horrell, guest: Asim Hussain 7 | 8 | 9 | ## Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/) - consent to record and share 10 | 11 | 12 | ## Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/) 13 | 14 | - Andrew Wright intro’d 15 | 16 | ## Questions/comments from the last meeting. 17 | 18 | - AD: Kanban board for open issues 19 | 20 | - TS: If not Invited Expert officially reach out to Tzviya to ensure policies followed IP etc 21 | 22 | ## Community + News 23 | 24 | - Chris: Yesterday there was this event organized by BEREC (Body of European Regulators for Electronic Communications) - External workshop on the ecodesign of digital services for greener networks and ICTs 25 | 26 | - 27 | 28 | - Recordings from the day will online in the coming weeks (youtube channel link) 29 | 30 | - 31 | 32 | - EED workshop on May 5th 33 | 34 | - Link to sign up 35 | 36 | - 37 | 38 | - Green web fdn write up of the last workshop ( 39 | 40 | - 41 | 42 | - May be useful for the sustainability-infra group 43 | 44 | - Asim 45 | 46 | - intro’d SCI, geared away from reporting totals and towards measurable units of functionality (to drive action). Requires drawing of boundaries around functionality. The larger the boundary the less responsibility (and action). The tighter the boundary the more accountable (encourages more action). Example scenario this addresses - “it is possible to optimise for energy and emissions but sales go up and totals go up” so you can’t optimise against totals. SCI addresses this by reducing to measurable (and repeatable) units of functionality that can be compared like for like. Consider personas: engineering vs energy. Energy team mandated to reduce emissions from energy demand (through procurement of market contracts). Engineers need to make decisions independent of the energy team’s mandate. 47 | 48 | - SCI for AI. New proposal (no consensus). 2 personas, provider / consumer. Functional unit examples per token, per second, per execution. Focus is not how much emissions from AI, focus on who are the personas, what they do and measuring that. 49 | 50 | - Collab with SCI for Web (Chris Adams - / Asim Hussain) 51 | 52 | - TS W3C rep. AD rep too. Do we adopt any model(s) that emerge from that group? Which bits are relevant to the guidelines? 53 | 54 | - AH: assemblies (workshops) gather feedback (personas, actions first then metrics to be worked out over longer periods). This group can feedback through TS / AD. Regular (e.g. quarterly) syncs (no decisions to not break bylaws) 55 | 56 | - CA: workshops will be announced soon 57 | 58 | - TS: possibly GSF people to be involved in this W3C group 59 | 60 | ## Major sections (Blockers & Updates) 61 | 62 | - UX - Thorsten raised a question around Workflow resolution, [2.4](https://github.com/w3c/sustainableweb-wsg/issues/54). UX task force workflow discussion (transitioning from Miro to Google Docs), as [noted in these slides](https://docs.google.com/presentation/d/1cpiz8qZvJIxzcfk5ygCXVi_fd7nOT_GdqjHd5-zoMXg/edit?usp=sharing), and asking folks to contribute contents on the existing guidelines by [noting in one’s individual column in this sheet](https://docs.google.com/spreadsheets/d/10BrvQPLAsvChJ2TKm2LUx-oDIsibM0ltw_Q08ie85KA/edit?usp=sharing) 63 | 64 | - WebDev - 65 | 66 | - Infrastructure - 67 | 68 | - Business - 69 | 70 | - Measurability - Figure out how prioritization of SCs works. 71 | 72 | - AN: comment about the difference between general guidelines and bespoke guidelines (application level context) and how do we bridge that in measurability of SCs. TBD in measurability TF. 73 | 74 | - Adam: put in a suggestion of how to look at each criteria a. Is the consumer of the guidelines looking for general advice or specific - 75 | 76 | ## Other discussion/questions 77 | 78 | - [Alex’s tagging spreadsheet](https://docs.google.com/spreadsheets/d/1wa_kTpAqF1n1fQKDlmV1kgXlqAWR1nTKd_FG3nTAq-8/edit?usp=sharing) 79 | 80 | - Alex working on **standards** (sorting Reference links into a supplement). 81 | 82 | - TFs please verify & correct **considerations** & **categories**. (If more categories or titles are required, feel free to suggest!) 83 | 84 | - TFs please categorize by **Job Title** (you can use more than one!). (If more categories or titles are required, feel free to suggest!) 85 | 86 | - **Mike:** Impact / Effort Scoring:\ 87 | A/AA/AAA, red/yellow/green, gold/silver/bronze, A-F, High-Low. - delayed until next meeting 88 | 89 | - TS: if anyone needs help with meetings in between or async work TS can help facilitate! 90 | 91 | -------------------------------------------------------------------------------- /minutes/2025-05-15.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-05-15 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/43 4 | 5 | **Attendees:** Alexander Dawson (Editor), Łukasz Mastalerz, Thorsten Jonas, Hidde de Vries, Rose Newell, Chris Adams, Andrew Wright, Francesco Fullone, Kazuhito Kidachi, Adam Newman. 6 | 7 | ## Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/) 8 | - consent to record and share 9 | 10 | ## Questions/comments from the last meeting. 11 | - **Alexander:** Any questions/comments? 12 | - **Alexander:** We wanted to work on the various breakouts today but because various people are away there is not really enough of us to break into many groups. We could do status updates. 13 | - **Chris:** Only 7 of us here, raise hands to see who is in what group.2 in business, 1 in performance (or was it measurement?), 2 in UX 14 | - **Alex:** also hosting and infrastructure 15 | - **Rose:** It looks like Ryan has been making progress on hosting based on Slack. 16 | - **Alex:** Yes. Hidde has been making progress on the web dev repo, github. 17 | - **Hidde:** Trying to see what happened in the past 2 weeks we were trying to cover. You’ve merged some things. Not sure what’s happened, been away myself. 18 | - **Alex:** Not much in the last 2 weeks, been busy moving resources into an external document for easier management. 19 | - **AleX:** UX is the group the chairs are most concerned about 20 | - **Thorsten:** Catching up, been busy, will write comments. Trying to catch up in the coming days. When schedule frees there will be more time to make progress. 21 | - **Rose:** Business - quite advanced, but Tim says trouble making progress. 22 | - **Chris:** Accurate prognosis, been able to join meetings. 23 | - **Alex:** Only thing Mike brought up was that some overlap in business guidelines - could be condensed. Too broad. 24 | - **Chris:** We’ve discussed scoping recommendations so they are aimed at people with different degrees of authority - different things would be asked to different people. I am not sure how we rearrange based on status. It’s a challenge using these because I don’t get to make that decision. 25 | - **Rose:** Need to ensure the Business and Product Management section links back to other sections, avoid generic advice, and generally promote a culture of enablement (across all authority levels). 26 | 27 | ## Task Force Breakouts (30m) 28 | - Breakout docs 29 | - [WSG Updates 2025](https://drive.google.com/drive/folders/1k5pzPq2AtBeriymXyMOiuu6mrMhN_ZVb) - contains the specific task force docs 30 | - [WSG 2025 Updates: Business & Product Strategy Task Force](https://docs.google.com/document/d/1vbJ5t7hosd_Gl9eL0CO3hb_buNzgtKXjs2v_hozP-d8/edit?tab=t.0#heading=h.nox05a1520oa) 31 | 32 | ## Community + News: 33 | - Who is planning to attend [TPAC 2025](https://www.w3.org/2025/11/TPAC/) 10-14 November, Kobe JP? 34 | - Alexander: Tzviya may be going, not sure about others 35 | - Hidde: I’m going, could represent us 36 | - Alexander: we could potentially run a breakout session 37 | - Rose: What is the procedure for outreach and talking about things we’ve not worked on ourselves? 38 | - Alexander: We've got a lot of info in the GitHub readme, we could produce more. 39 | - Rose: could be the same as “brand messaging house”. Want to speak more cohesively and consistently. 40 | - Hidde: What's a brand messaging house? 41 | - Rose: usually shaped like a pyramid, makes sure people speak the same way. Usually orgs with press departments produce these to make sure folks don’t miss the key points, so people stay “on brand” (example shared in chat). 42 | - Hidde, in chat: Had to go, would like to work on this with Rose. 43 | - GSF: SCI for web workshop signup now available: 44 | - https://workshops.greensoftware.foundation/sci-web-workshop 45 | - (You will need to be in a GSF member organisation to take part, but it’s free to join as a non profit and there will be regular sharebacks from W3C member, and updates will be shared via that email list 46 | 47 | ## [Open issues](https://github.com/w3c/sustainableweb-ig/issues) ([Kanban](https://github.com/orgs/w3c/projects/198)) 48 | 49 | - UX: [#54](https://github.com/w3c/sustainableweb-wsg/issues/54), [#64](https://github.com/w3c/sustainableweb-wsg/issues/64) 50 | - Biz: [#61](https://github.com/w3c/sustainableweb-wsg/issues/61), [#62](https://github.com/w3c/sustainableweb-wsg/issues/62), [#63](https://github.com/w3c/sustainableweb-wsg/issues/63), [#65](https://github.com/w3c/sustainableweb-wsg/issues/65) (Mike) 51 | 52 | ## Major sections (Blockers & Updates) 53 | 54 | - Reminder (Non-measurability) TF’s, [First Draft: 30 June](https://github.com/w3c/sustainableweb-wsg/?tab=readme-ov-file#schedule)! 55 | 56 | ## Other discussion/questions: 57 | 58 | - Follow on notes as Adam Newman 59 | - There are two ways the guidelines are being written 60 | - We need to agree upon the interpretation and how to test an implementation in order to measure it. We must also consider the parameters we want to express. 61 | - Lukas: 62 | - The different guidelines are likely to have different levels of impact depending on the kind of web application in use. Some web performance interventions will be more effective on a video streaming site, compared to a typical wikipedia page. 63 | - C: 64 | - If one of the challenges with measurability is having confidence about how effective all the interventions are, can you at least have a subset of sample reference model web sites or web apps to test them against? There are datasets like the HTTP Archive which give us an idea of the most common sites and similar properties they have. Other research projects have taken a reference site, with reference traffic patterns to demonstrate the impact of different changes ([see the ecovisor paper](https://ar5iv.labs.arxiv.org/html/2210.04951), for looking into how different architectural changes that impact the carbon intensity common uses of servers), and the [Wagtail bakery GOLD repo for use with GMT](https://github.com/thegreenwebfoundation/bakerydemo-gold-benchmark/) 65 | -------------------------------------------------------------------------------- /minutes/2025-05-29.md: -------------------------------------------------------------------------------- 1 | # Sustainable Web IG Minutes 2025 2025-05-29 2 | 3 | ## Agenda https://github.com/w3c/sustainableweb-ig/issues/45 4 | 5 | **Attendees:** Tim Frick (Chair), Alexander Dawson (Editor), Tzviya Siegman (W3C), Kazuhito Kidachi, Thorsten Jonas, Jen Strickland, Łukasz Mastalerz, Alisa Bonsignore, Shane Herath, Rose Newell, Nick Lewis, Morgan Murrah, Ryan Sholin, Susannah Hill, Adam Newman 6 | 7 | ## Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/) 8 | - consent to record and share 9 | 10 | 11 | 1. Introductions & [Code of Conduct](https://www.w3.org/policies/code-of-conduct/) 12 | - Susannah Hill: based in CA, US, near SF. Founded Cloud Sustainability Watch. 13 | - Nick Lewis: based in SW UK. Advocate for digital sustainability for many years. Runs sustainable dev, low-carbon website showcase. 14 | 15 | 2. Questions/comments from the last meeting. 16 | - Barreling towards progress for the end of June. 17 | 18 | 3. Task Force Breakouts 19 | - Group Feedback (Blockers & Updates) 20 | - UX: Everyone getting on the same page, scheduling an async meeting. Rose will review before June 30, update and will have agreed upon working method 21 | - Hosting: assembled todo list, 3 more sections to go through first edits, have open questions, and there’s some legacy language that needs to be updated 22 | - Metrics: We have a good understanding of tasks to focus on - guideline prioritization based on characteristics of SCs (role, software, user input). There will be a separate task to build UI for this. Second is building baseline and measure. We need to clearly goal of guidelines and metrics TF. We will post in GitHub and ask for feedback. Minimize environmental impact of web (tb defined), and goal for TF: help users achieve greatest progress toward minimizing impact. One of the main goals is to reduce demand for manufacturing and use of hardware, and if everything can be framed in that context, we have something to guide us even in the SCs that are “immeasurable”. This aligns with SCI as well. 23 | - Product/Biz: this is the section that interfaces with the rest of the world. There are many new resources (Climate leaders v2, B Corp standards), We need to figure out if there is anything new to add. 24 | 25 | 4. Community + News 26 | - **WSG Update (Alex):** New [Resources Supplement](https://w3c.github.io/sustainableweb-wsg/resources.html) ([PR 67](https://github.com/w3c/sustainableweb-wsg/pull/67)) 27 | - WSG links to Resources in the document head (Supplements). - easier to maintain a separate document, useful resource on its own, makes WSG more evergreen 28 | - Each WSG SC cross-references ([example](https://w3c.github.io/sustainableweb-wsg/#external-variables)) to its Resources (URLs) via a “jump to section” feature (next to and works like testability for STAR). 29 | - WSG now has a new filter category (Standards) based on [relationships](https://w3c.github.io/sustainableweb-wsg/#relationships) found in references we currently have in the resources supplement. 30 | - Some SC’s were lacking evidence, so I researched and added more links. 31 | **Note:** more on the way, I’ve got a backlog of research & links to verify. 32 | 33 | - [STAR techniques](https://w3c.github.io/sustainableweb-wsg/star.html#user-experience-design) are visually aligned to the WSG and grouped by SC. 34 | 35 | - Non-destructive minor copy tweaks that apply globally to the WSG copy have been applied to help improve general readability. (thanks to Rose!) 36 | 37 | - **Benefits:** Easier to maintain/garden links. Resources is a useful doc on its own (for general susty “further reading”). The spec is more evergreen with fewer links to go stale (when we go note/statement). WSG is now 500kb lighter - so more performant on loading! 38 | 39 | - New [Considerations](https://w3c.github.io/sustainableweb-wsg/#considerations) section (Accessibility / Privacy / Security) cross-overs 40 | New filter category (Considerations) matching the above (using tag data). 41 | New filter category (Categories) based on guideline tags & spreadsheet. 42 | 43 | - A few other bugs and quirks also got squashed. 44 | 45 | 5. Other discussion/questions 46 | - Increasing frequency of meetings - we will go to weekly meetings, further discussion at next meeting 47 | - Virtual "f2f" (extended session) - planning a 2.5 -3 hour virtual meeting in the summer. We’ll share proposed dates in GitHub. 48 | -------------------------------------------------------------------------------- /multipage.md: -------------------------------------------------------------------------------- 1 | # ReSpec Multipage 2 | 3 | - **Version:** 0.3.1 4 | - **Creator:** Alexander Dawson 5 | 6 | ## Features 7 | 8 | - It supports ReSpec generation mode, HTML Exports, and PR Preview. 9 | - Uses Vanilla JavaScript with no dependencies (lightweight). 10 | - Progressively enhances (no JavaScript it'll just show the full-document version). 11 | - Uses anchor fragments (it can work offline) and is low maintenance. 12 | - If no fragment exists or an invalid fragment is used it'll point to the first page. 13 | - If the fragment exists it'll show the correct page and jump to the section. 14 | - Supports printing that page (or the full document if in that mode). 15 | - Works across desktop and handheld browsers (good compatibility). 16 | 17 | ## HTML 18 | 19 | The below is **required** to be included, and customized for every page so the buttons work: 20 | 21 | ```html 22 |
    23 |
  1. Previous page
    None
    2. 24 |
  2. Full document
    3. 25 |
  3. Next page
    None
    4. 26 |
27 | ``` 28 | 29 | ## CSS 30 | 31 | The below must be included within the `` element: 32 | 33 | ```css 34 | @media print { #toc { display: none !important; } } 35 | @media (scripting: enabled) { 36 | .hide { display: inherit !important; height: 1px; left: -1000px; overflow: hidden; position: absolute; top: -1px; width: 1px; } 37 | .show { height: auto; left: auto; overflow: unset; position: static; top: auto; width: auto; } } 38 | .pageButtons { margin-top: 2em; padding-left: 0; } 39 | .pageButtons, .pageButtons li, .pageButtons tbody { display: flex; flex: 1; gap: 10px; } 40 | .pageButtons a { align-items: center; border: medium solid #d9d9d9; background-color: #F3F3F3; display: flex; font-weight: bold; flex: 1; padding: 0.5em 1em; } 41 | .previousPage { justify-content: left; } .fullDocument { justify-content: center; } .nextPage { justify-content: right; text-align: right; } 42 | @media (scripting: none) { 43 | @media print { #toc { display: block !important; } } 44 | .pageButtons { display: none;} 45 | .hide { display: block !important; height: auto; left: auto; overflow: unset; position: static; top: auto; width: auto; } } 46 | ``` 47 | 48 | ## JavaScript 49 | 50 | The below must be included within the `` element: 51 | 52 | ```javascript 53 | 168 | ``` 169 | **Note:** Code comments can be removed and section names should be configured to match your specification TOC. 170 | 171 | The below must be included in the `respecConfig` section: 172 | 173 | ```javascript 174 | var respecConfig = { 175 | lint: { "local-refs-exist": false, }, 176 | postProcess: [addMultipage] } 177 | ``` -------------------------------------------------------------------------------- /timeline.svg: -------------------------------------------------------------------------------- 1 | Oct2024Apr2024Oct2023Sept2023Apr2023Aug2023Apr2022Apr2013STAR JSON APIReleasedW3C InterestGroupCharteredSTARReleasedWSG JSON APIReleasedFirst PublicWSG DraftCompletedInitial WSGDraftCG CharterEstablishedFirst WSGMeetingCommunityGroupOpenedFeb2025 -------------------------------------------------------------------------------- /w3c.json: -------------------------------------------------------------------------------- 1 | { 2 | "group": ["ig/sustainableweb"], 3 | "contacts": ["tzviya"], 4 | "repo-type": "project" 5 | } 6 | --------------------------------------------------------------------------------