Security 2020

[foxdavidj]

Part II Chapter 11: Security

Content team

Authors	Reviewers	Analysts	Draft	Queries	Results
@nrllh @tomvangoethem	@cqueern @bazzadp @edmondwwchan	@AAgar @tomvangoethem	Doc	*.sql	Sheet

Content team lead: @nrllh

Welcome chapter contributors! You'll be using this issue throughout the chapter lifecycle to coordinate on the content planning, analysis, and writing stages.

The content team is made up of the following contributors:

• Authors
• Reviewers
• Analysts

New contributors: If you're interested in joining the content team for this chapter, just leave a comment below and the content team lead will loop you in.

Note: To ensure that you get notifications when tagged, you must be "watching" this repository.

Milestones

0. Form the content team

• Jul 6th: Project owners have selected an author to be the content team lead
• Jul 13th: The content team has at least one author, reviewer, and analyst (minimally viable team formed)

1. Plan content

• Jul 20th: The content team has completed the chapter outline in the draft doc
• Jul 27th: Analysts have triaged the feasibility of all proposed metrics

2. Gather data

• Jul 27th: Analysts have added all necessary custom metrics and drafted a PR to track query progress

• Aug 1 - 31: August crawl

• Sep 7th: Analysts have queried all metrics and saved the output to the results sheet

3. Validate results

• Sep 14th: The content team has reviewed the results sheet

4. Draft content

• Nov 12th: Authors have completed the first draft in the doc
• Nov 26th: The content team has prototyped all data visualizations

5. Publication

• Nov 26th: The content team has reviewed the final draft, converted to markdown, and filed a PR to add it to the 2020 content directory

• Dec 9th: Target launch date

[tomvangoethem]

I'd like to volunteer as an analyst. I've used HTTPArchive in some of my (academic) research, so I have some familiarity with the datasets.

[nrllh]

@rviscomi as spoken recently, I would also like to join in this chapter.

[foxdavidj]

@tomvangoethem added you as an analyst :)

[cqueern]

Hello Team. I would like to participate as a Reviewer please. 😀

[rviscomi]

@nrllh thank you for agreeing to be the lead author for the Security chapter! As the lead, you'll be responsible for driving the content planning and writing phases in collaboration with your content team, which will consist of yourself as lead, any coauthors you choose as needed, peer reviewers, and data analysts.

The immediate next steps for this chapter are:

1. Establish the rest of your content team. The larger the scope of the chapter, the more people you'll want to have on board.
2. Start sketching out ideas in your draft doc.
3. Catch up on last year's chapter and the project methodology to get a sense for what's possible.

There's a ton of info in the top comment, so check that out and feel free to ping myself or @OBTo with any questions!

[tunetheweb]

I'm happy to review this chapter again this year btw. Added myself to first comment.

[tunetheweb]

@ivanr @april would you have any interesting in helping out in this chapter this year? Last year's chapter for context: https://almanac.httparchive.org/en/2019/security

[nrllh]

@tomvangoethem, assigned you also as author ;)

[foxdavidj]

Hey @nrllh, just checking in:

1. How is the the chapter coming along? We're tying to have the outline and metrics settled on by the end of the week so we have time to configure the Web Crawler to track everything you need.
2. Can you remind your team to properly add and credit themselves in your chapter's Google Doc?
3. Anything you need from me to keep things moving forward?

[nrllh]

@tomvangoethem @cqueern @bazzadp can you please request edit access and then credit yourself in Google Doc?

[edmondwwchan]

Hello team, may I contribute as a reviewer too?

[nrllh]

@edmondwwchan welcome to the club!
Please request an edit access and credit yourself in the doc.

[foxdavidj]

@nrllh How's the chapter outline coming along? We want to have that wrapped up by the end of the week so we have time to set up our Web Crawler :)

[foxdavidj]

@nrllh in case you missed it, we've adjusted the milestones to push the launch date back from November 9 to December 9. This gives all chapters exactly 7 weeks from now to wrap up the analysis, write a draft, get it reviewed, and submit it for publication. So the next milestone will be to complete the first draft by November 12.

However if you're still on schedule to be done by the original November 9 launch date we want you to know that this change doesn't mean your hard work was wasted, and that you'll get the privilege of being part of our "Early Access" launch.

Please see the link above for more info and reach out to @rviscomi or me if you have any questions or concerns about the timeline. We hope this change gives you a bit more breathing room to finish the chapter comfortably and we're excited to see it go live!

[foxdavidj]

@AAgar @tomvangoethem @nrllh Looks like the queries have been written but not added to your chapters data sheet. Can one of you take care of adding the results to the sheet this week?

[nrllh]

We are not done yet with the analysis. Once we're done, we can add the results to the sheet. @OBTo

[max-ostapenko]

Hi @AAgar @tomvangoethem , we plan to reuse some of your data in Privacy chapter (cookie attributes in particular). Please let me know if I can help visualise it asap.

[tomvangoethem]

Hey @max-ostapenko, I haven't gotten to the visualisation yet :-/ I guess it's fine to have the same figures in different chapters - assuming the interpretation will still be different?

[tomvangoethem]

@max-ostapenko I added the results of the cookie attributes to the sheets; you can check the visualisations here. Let me know if you have any comments/suggestions!

[rviscomi]

@nrllh @tomvangoethem please have your markdown submitted by EOD today to be included in Wednesday's launch.

[tomvangoethem]

The initial markdown has been submitted; evolution and conclusion sections still need to be written, images still need to be added, and text should be further edited. I'll work on that tomorrow.