Security 2024

[nrllh]

Security 2024

If you're interested in contributing to the Security 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
@GJFR	@GJFR, @vikvanderlinden	@lord-r3, @SaptakS, @AlbertoFDR, @clarkio	@JannisBush	@cqueern, @joeleonjr	@tomvangoethem

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.
• [ ] 📆 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 Security 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-security on Slack for team coordination

[lord-r3]

I would volunteer to review this chapter.

[vikvanderlinden]

I'd be happy to join as author for this chapter!

[JannisBush]

I would like to join as either an author or an analyst for this chapter.

[SaptakS]

Having led the chapter twice, I would be happy to take the role of a reviewer this time.

[turban1988]

I am interested in being an reviewer.

[GJFR]

I'd like to volunteer as author!

[AlbertoFDR]

I would like to review this chapter.

[joeleonjr]

I'd be happy to join as an author or analyst. Specifically, I'm interested in reviewing the data for secrets leaking in front-end source code. I think this could be a cool addition to the project. Also, happy to edit in case that'd be helpful.

[nrllh]

I'd be happy to join as an author or analyst. Specifically, I'm interested in reviewing the data for secrets leaking in front-end source code. I think this could be a cool addition to the project. Also, happy to edit in case that'd be helpful.

That sounds great Joe, welcome!

[clarkio]

Hi all, I'm a bit late to this but wanted to offer up help and support as I've contributed in the last security chapter as a reviewer and author. @lirantal (who has also contributed before) might be interested as well. If you're all set for this year, no worries but do keep us in mind in the future. Thanks!

[nrllh]

Hi all, I'm a bit late to this but wanted to offer up help and support as I've contributed in the last security chapter as a reviewer and author. @lirantal (who has also contributed before) might be interested as well. If you're all set for this year, no worries but do keep us in mind in the future. Thanks!

Thanks for offering your help and support! We'd like to have you involved again this year. Which role would you be interested in?

[clarkio]

Oh nice ok. I'm interested in reviewing if that works.

[tomvangoethem]

Hey folks! How are you feeling about the upcoming deadline regarding outlining the chapter? It could be nice to set up a quick call with all volunteers of this chapter to get quickly aligned on how everyone envisions it. @GJFR, could you perhaps set up a meeting? (preferably early this upcoming coming week, though later would also work). Thanks & looking forward to seeing the chapter take more shape 👍

[GJFR]

Hi everyone!

I’m currently still on holiday, and will only be back on the 7th of May. We can already plan our meeting though.

@vikvanderlinden, @joeviggiano, @lord-r3, @SaptakS, @AlbertoFDR, @clarkio could you fill out this whenisgood? https://whenisgood.net/5gpmxp7

You should be able to select your own timezone. If none of these slots work for you, please let me know.

Looking forward to discussing the chapter!

[GJFR]

Friendly reminder to fill in the whenisgood if you haven't already. To give our analysts enough time to take care of the custom metrics, let's lock in a meeting date by Tuesday.

If you can't make it for some reason, feel free to share any ideas you might have in our HTTP Archive Slack channel.

[GJFR]

Hi @joeleonjr, it seems like we accidentally tagged another Joe! This should be solved now. Have you already registered on HTTP Archive's Slack channel? I can't seem to find you there.

[joeleonjr]

Just joined! Apologies for the delay.

[GJFR]

No worries! You can check the planning doc to get up to speed on what we want to include in this year's chapter.

Next deadline is June 1st, by which all custom metrics have to be finished. Best to check with your co-analyst @JannisBush about that.

Don't hesitate to contact me if something is not clear!