Sustainability 2024

[nrllh]

Sustainability 2024

If you're interested in contributing to the Sustainability chapter of the 2024 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor. You might be interested in exploring the changes to this year's version here.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@ldevernay	@burakguneli, @ldevernay, @ines-akrap, @AlexDawsonUK	@airbr, @mgifford	@cthornewill, @Falafelqueen	@cqueern	@turban1988

Expand for more information about each role 👀

• The content team lead is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress.
• Authors are subject matter experts and lead the content direction for each chapter. Chapters typically have one or two authors. Authors are responsible for planning the outline of the chapter, analyzing stats and trends, and writing the annual report.
• Reviewers are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases.
• Analysts are responsible for researching the stats and trends used throughout the Almanac. Analysts work closely with authors and reviewers during the planning phase to give direction on the types of stats that are possible from the dataset, and during the analyzing/writing phases to ensure that the stats are used correctly.
• Editors are technical writers who have a penchant for both technical and non-technical content correctness. Editors have a mastery of the English language and work closely with authors to help wordsmith content and ensure that everything fits together as a cohesive unit.
• The section coordinator is the overall owner for all chapters within a section like "User Experience" or "Page Content" and helps to keep each chapter on schedule.

Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors.

For an overview of how the roles work together at each phase of the project, see the Chapter Lifecycle doc.

Milestone checklist

0. Form the content team

• [x] 📆 April 15 Complete program and content committee - 🔑 Organizing committee
  • The content team has at least one author, reviewer, and analyst.

1. Plan content

• [x] 📆 May 1 First meeting to outline the chapter contents - 🔑 Content team
  • The content team has completed the chapter outline.

2. Gather data

• [x] 📆 June 1 Custom metrics completed - 🔑 Analysts
  • Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress.
• [x] 📆 June 1 HTTP Archive Crawl - 🔑 HA Team
  • HTTP Archive runs the June crawl.

3. Validate results

• [x] 📆 August 15 Query Metrics & Save Results - 🔑 Analysts
  • Analysts have queried all metrics and saved the output.

4. Draft content

• [x] 📆 September 15 First Draft of Chapter - 🔑 Authors
  • Authors has written the chapter.
• [x] 📆 October 10 Review & Edit Chapter - 🔑 Reviewers & Editors
  • Reviewers and Editors has processed the the chapter.

5. Publication

• [ ] 📆 October 15 Chapter Publication (Markdown & PR) - 🔑 Authors
  • Authors has converted the chapter to markdown and drafted a PR.
• [ ] 📆 November 1 Launch of 2024 Web Almanac 🚀 - 🔑 Organizing committee

6. Virtual conference

• [ ] 📆 November 20 Virtual Conference - 🔑 Content Team

Chapter resources

Refer to these 2024 Sustainability resources throughout the content creation process: 📄 Google Docs for outlining and drafting content 🔍 SQL files for committing the queries used during analysis 📊 Google Sheets for saving the results of queries 📝 Markdown file for publishing content and managing public metadata 💻 Collab notebook for collaborative coding in Python - if needed 💬 #web-almanac-sustainability on Slack for team coordination

[burakguneli]

Hello, I would love to contribute as one of those roles if there is any availability: author, reviewer, analyst

[ldevernay]

You can count me in as an author. I'd be glad to be lead author again if others agree. I already have some plans for this chapter, in relation to WSG from the W3C. I'll reach other former contributors to know if they want to contribute again. BTW, this should be in User Experience, not content creation, like accessibility, performance and such.

[mgifford]

I am definitely interested in helping with this! So glad it is happening again this year.

[ines-akrap]

Hi, I am also happy to contribute, in any role :)

[cthornewill]

Hi, I would also like to contribute to this chapter and I am also pretty open to whichever role.

[AlexDawsonUK]

I would be happy to contribute as well. As one of the editors of the WSGs I'd be happy to act as a reviewer / author (or other role as appropriate) to make sure the content here technically aligns with the evidence threshold we have in the WSGs (if that's at all useful).

[ldevernay]

@AlexDawsonUK : that's totally my point here. I hope this chapter will help rise awareness on the WSG and check where we're at with some of its recommendations.

[airbr]

Hello, I am very enthusiastic about this but I have not got much idea where to start or what role may be best if any role. I would like to support this work in some way.

[ldevernay]

From experience, I think all help is welcome. Helping discuss what fits in this chapter and analyzing results or even helping gather data through BigQuery. Reviewing the chapter could also bring additional insights.

[Falafelqueen]

Hello, I would also love to be involved and am available for any role. 🌱

[mgifford]

So what is the status now? There are a few of us keen to help.

[ldevernay]

We've got until April 15th to gather the team but now would be a good time for everyone to join the dedicated Slack so that we could discuss this.

[nrllh]

Another amazing team here, thank you all! You all are assigned.

@mgifford, could you let us know which role you'd like to contribute to?

[mgifford]

@nrllh I'm still not sure how to help. Seems like reviewers are needed.  I might be able to help with the data analysis, but not my strongest skill set.

[turban1988]

Hi @ldevernay , Thank you very much for volunteering to lead the writing of this chapter! Could you please organize a kick-off meeting for this chapter (example: https://github.com/HTTPArchive/almanac.httparchive.org/issues/3603#issuecomment-2064351177) to organize the writing of the chapter?

Furthermore, it would be helpful if you and all other contributors (@burakguneli, @ldevernay, @ines-akrap @AlexDawsonUK, @airbr, @mgifford, @cthornewill, @Falafelqueen,@cqueern) could join the slack channel of the HTTPArchive (https://join.slack.com/t/httparchive/shared_invite/zt-2hfkn28ts-~uXN4UGS0mXsKpzzhtZcow)

Thanks!

[ldevernay]

Hi all, I hope I'll see you all soon on the Slack channel. You also need to ask for permission to write on the Google doc we'll be using from now on. I will also try to setup a call for all of us to get to know each other and start working on this. (handling time zones might prove tricky)