search

HTTPArchive / almanac.httparchive.org

HTTP Archive's annual "State of the Web" report made by the web community
https://almanac.httparchive.org
Apache License 2.0
603 stars 162 forks source link

Security 2024 #3604

Open nrllh opened 4 months ago

nrllh commented 4 months ago

Security 2024

Security illustration

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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Content-Team-Leads'-Guide)** is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress. - **[Authors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Reviewers'-Guide)** are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases. - **[Analysts](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Editors'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Section-Leads'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle) doc.

Milestone checklist

0. Form the content team

1. Plan content

2. Gather data

3. Validate results

4. Draft content

5. Publication

6. Virtual conference

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 commented 4 months ago

I would volunteer to review this chapter.

vikvanderlinden commented 4 months ago

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

JannisBush commented 4 months ago

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

SaptakS commented 4 months ago

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

turban1988 commented 4 months ago

I am interested in being an reviewer.

GJFR commented 4 months ago

I'd like to volunteer as author!

AlbertoFDR commented 4 months ago

I would like to review this chapter.

joeleonjr commented 3 months ago

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 commented 3 months ago

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 commented 3 months ago

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 commented 3 months ago

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 commented 3 months ago

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

tomvangoethem commented 3 months ago

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 commented 3 months ago

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 commented 2 months ago

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 commented 2 months ago

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 commented 2 months ago

Just joined! Apologies for the delay.

GJFR commented 2 months ago

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!