almanac.httparchive.org
almanac.httparchive.org copied to clipboard
HTTPArchive
Security 2022
Security 2022
If you're interested in contributing to the Security chapter of the 2022 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.
Content team
| Lead | Authors | Reviewers | Analysts | Editors | Coordinator |
|---|---|---|---|---|---|
| @SaptakS | @SaptakS @feross @lirantal | @kushaldas @tomvangoethem @nrllh @clarkio | @VictorLeP @vikvanderlinden @GJFR | - | @foxdavidj |
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] May 1: The content team has at least one author, reviewer, and analyst
1. Plan content
- [x] May 15 The content team has completed the chapter outline in the draft doc
2. Gather data
- [x] June 1: Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress
- June 1 - 15: HTTP Archive runs the June crawl
3. Validate results
- [x] August 1: Analysts have queried all metrics and saved the output to the results sheet
4. Draft content
- [ ] September 1: The content team has written, reviewed, and edited the chapter in the doc
5. Publication
- [ ] September 15: The completed chapter and all required metadata and figures are converted to markdown and submitted to GitHub
- September 26: Target launch date š
Chapter resources
Refer to these 2022 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 š¬ #web-almanac-security on Slack for team coordination
Happy to co-author or review (if there are others who want to author instead of the same team).
Hey @SaptakS, would you be interested in taking the Chapter Lead role for the Security chapter?
@foxdavidj I don't think I will have enough availability to take the Chapter Lead role this time.
@awareseven @cqueern @edmondwwchan @nrllh @tomvangoethem
Would any of you be interested in leading the chapter this year? I know some of you have already signed up to be a reviewer, but we're in need of a Lead in order to get this chapter off the ground.
And as contributors in past years, we'd love to welcome you back to the role
Given other commitments Iām not going to be able to lead. Sorry.
Sent from my mobile device.
On Apr 25, 2022, at 4:57 PM, foxdavidj @.***> wrote:
ļ»æ @awareseven @cqueern @edmondwwchan @nrllh @tomvangoethem
Would any of you be interested in leading the chapter this year? I know some of you have already signed up to be a reviewer, but we're in need of a Lead in order to get this chapter off the ground.
And as contributors in past years, we'd love to welcome you back to the role
ā Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.
@awareseven @cqueern @edmondwwchan @nrllh @tomvangoethem
Hi all. We need some help finding a Lead for this chapter. Right now it looks like we'll miss our first milestone (May 1st) which will put the chapter at risk of being dropped.
Can you all reach out to anyone you feel may be a good fit for a Lead/Authoring role for the chapter?
Thanks
@lirantal would you have any interesting in getting involved in this chapter this year?
@SaptakS @feross @kushaldas @tomvangoethem
Hey everyone, excited to see we've got a full team (aside from an analyst) for the chapter!
To kick things off, I'd love to set up a 30 minute call within the next two weeks to put any new faces to names, and start the planning and brainstorming process.
@SaptakS as the Chapter Lead can you assist in finding a time that works for everyone? You can see my availability via my calendly here (no need to book through it): https://calendly.com/foxdavid/30min
Also, here is an agenda for what we might want to discuss on the kickoff call: https://docs.google.com/document/d/1xiwSs7yfCybdmYekJZukFgCmXhHnD2PTL4L1lkprsCw/edit
@tunetheweb thank you for the mention. Between @clarkio and myself, we'd love to join this year's report. I think it would be too short of a notice to join as analysts. Potentially can make it as authors, but definitely note us down as reviewers. We'd love to take part!
@SaptakS can you add both lirantal and clarikio to the content team in the chapter comment above?
Hey @SaptakS,
Heads-up that we're fast approaching the May 15th deadline of having an outline for the chapter put together.
Instead of waiting for the kick-off meeting, it'd be a good idea to start working on the outline with the team. Especially if there are any new custom metrics the chapter requires.
@lirantal @clarkio do you want me to add both of you as author or reviewer? I would like at least one more author (since security is usually pretty big chapter), so it would be great if at least one of you would be interested to be a co-author.
@SaptakS looks like there are two authors so I'm happy to join as a reviewer and/or editor if that is helpful to you all
@AAgar would you be interested in being an analyst for the Security chapter this year?
Hi guys, I would like to help out but I think the workload would be too high if I'm the only analyst, because of other projects. However @VictorLeP en @vikvanderlinden, you mentioned that you're also interested in joining?
Hi guys, I would like to help out but I think the workload would be too high if I'm the only analyst, because of other projects. However @VictorLeP en @vikvanderlinden, you mentioned that you're also interested in joining?
Yes, I would like to join as an analyst as well :)
Hi guys, I would like to help out but I think the workload would be too high if I'm the only analist, because of other projects. However @VictorLeP en @vikvanderlinden, you mentioned that you're also interested in joining?
Yes, me too!
@VictorLeP @vikvanderlinden added you both in the analyst. Can you both join #web-almanac-security channel in slack if you are not there already? Also please open the draft docs and request edit access.
@lirantal @clarkio can you also do the above?
@SaptakS Doesn't look like you edited the github chapter description above with the analysts names. Can you quick edit it?
Seems like I forgot to click on the submit button. Added now.
Looks like you missed @GJFR :cry:
@SaptakS How are you feeling about the chapter outline? We're fast approaching the date where any new custom metrics need to be written, tested, and merged into the web crawler (May 27).
Hi all. I can volunteer as a reviewer. Few words about myself: ex-Akamai where I worked a lot with WAF/bot management, security of 3rd party JS. CISSP/CCSP/pen tester/yadda-yadda. Now at MSFT, tinkering with Azure internals.
@foxdavidj we have a rough outline ready. I think we can start looking into writing custom metrics, if any needed.
@SaptakS terrific news. It may be helpful to document/notate in the planning doc what custom metrics you'd be looking for so your analysts can work on building them.
Reminder that they need to be impl'd, approved, and merged by May 27th. So time quickly running short