Privacy 2022

[rviscomi]

Privacy 2022

If you're interested in contributing to the Privacy 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
@tomvangoethem	@tomvangoethem @nrllh	@miketaylr @spanicker @iskander-sanchez-rola @SaptakS	@max-ostapenko @ydimova	@miketaylr	@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

• May 1: The content team has at least one author, reviewer, and analyst

1. Plan content

• May 15 The content team has completed the chapter outline in the draft doc

2. Gather data

• 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

• 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 Privacy 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-privacy on Slack for team coordination

[SaptakS]

Happy to co-author or review

[iskander-sanchez-rola]

I'd like to support as a Peer Reviewer.

[spanicker]

Interested to co-author or review

[miketaylr]

Interested as reviewer or editor.

[max-ostapenko]

Would like to continue analysing this chapter

[tomvangoethem]

I'd be interested to join as co-author or reviewer

[foxdavidj]

Hey @tomvangoethem, would you be interested in taking the Chapter Lead role for the Privacy chapter?

We'd love to have you 🎉 🎉

[nrllh]

I would be interested in co-authoring here

[tomvangoethem]

I'd be happy to take the Chapter Lead role, @foxdavidj!

[foxdavidj]

@tomvangoethem @spanicker @SaptakS @nrllh @miketaylr @iskander-sanchez-rola @max-ostapenko

Hey everyone, excited to see we've got a full team 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.

@tomvangoethem as the Chapter Lead can you assist in finding a time that works for everyone? You can see my availability via my calendly here: 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/1k1r96lPxQZcTUkKErhHjM0fltONEJQQF0Mgr_8h7FQg/edit

[max-ostapenko]

Any of the calendly slots before May 9 works fine for me.

[miketaylr]

Sounds good. For me, Fridays are wide open. Mondays are pretty available. Tuesday => Thursday is "maybe, it depends" territory. But I'm happy to move things around if I need to.

[tomvangoethem]

Would this Friday at 16:30 CEST work for everyone? (@spanicker @SaptakS @nrllh @miketaylr @iskander-sanchez-rola @max-ostapenko @foxdavidj)

Also a gentle reminder to join the #web-almanac-privacy channel on Slack

[ydimova]

I would like to contribute as an analyst

[rviscomi]

@tomvangoethem @spanicker @nrllh @miketaylr @iskander-sanchez-rola @SaptakS @max-ostapenko @ydimova make sure you all have access to the planning doc and start brainstorming topics to include in this year's chapter. What's new in the world of privacy, or what topics would be good to revisit from previous years? I heard from @foxdavidj that the team met today and has some great ideas, so it'd be good to get those on paper and start iterating on the narrative. We're hoping to have the outline nailed down by May 15 so that we can make any needed changes to the custom metrics in the June crawl before it kicks off. Thanks everyone!

[foxdavidj]

@tomvangoethem 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).

[tomvangoethem]

I added a rough sketch of the outline; some updates are likely to follow this weekend :-)

[foxdavidj]

@spanicker @nrllh @miketaylr @iskander-sanchez-rola @SaptakS

Looks like @tomvangoethem has added a rough outline to the planning doc. Please add your thoughts to it as well.

Especially since the deadline for adding any new custom metrics (impl, approval, merge) is less than 2 weeks away.

[foxdavidj]

@tomvangoethem How's the chapter coming along?

[tomvangoethem]

@foxdavidj The outline is there; with the new observer custom metrics we'll be looking at property accesses and function calls that are frequently used by fingerprinting scripts. For the former, we're constructing a set of properties and functions; for the latter a PR is pending. I expect to have both ready before the deadline :)

One thing that we should still do regarding custom metrics, is to check whether there's any changes to CMP frameworks that require updates of the current custom metrics. @max-ostapenko, could you maybe have a look into that?

[foxdavidj]

@max-ostapenko @ydimova Now that the crawl has started, please create a PR (example) to track the progress of writing the queries needed for the chapter.

Heads up to @tomvangoethem, as you'll likely be needed to confirm what needs to be queried

[foxdavidj]

@max-ostapenko @ydimova @tomvangoethem any progress on the Query PR (example)?

[max-ostapenko]

@foxdavidj @tomvangoethem @ydimova #2971
The overview of queries to be reused and a to do list.

[foxdavidj]

@tomvangoethem @max-ostapenko @ydimova

The June crawl has completed and all of the data is available to start being queried.

How are you all feeling about having all of the queries written by the end of the month? If there's anything you have questions about, just let me know

[max-ostapenko]

@ydimova @tomvangoethem the spreadsheet is complete with all the available visualisations, please have a look and looking forward to clarifying/adjust/detail anything.

[foxdavidj]

Hey all, @tomvangoethem @spanicker @nrllh,

How is the chapter looking. I'm not seeing any Draft progress and the deadline is fast approaching. Is there an external doc all of you are collaborating in?

Because I'm afraid to say that right now this chapter is at risk of being closed so we can focus our effort and attention on other chapters.

[tomvangoethem]

@foxdavidj We're indeed lagging behind on the text. I will start writing tomorrow, and aim to finish by Wednesday (ideally with some help from @spanicker & @nrllh). While the text won't be reviewed/edited by September 1st, I think that at the moment it still seems feasible to make the September 15th deadline.

[foxdavidj]

@miketaylr @iskander-sanchez-rola @SaptakS Can you start reviewing what has been written in the chapter so far? Chunks are still left to be written but itd be best to start the review process to make the most of the time we have left

[foxdavidj]

@tomvangoethem We're now past the September 15th deadline. Can you give me an update?

Looks like there are still a couple sections (like the conclusion) that need to be finished up. I'd really like to get this in front of editors ASAP

[tomvangoethem]

@foxdavidj I've finished the last data-related section. Will make sure that the introduction & conclusion sections are done by tomorrow.

[tomvangoethem]

All the content's there. Having some additional reviews (@spanicker @miketaylr @SaptakS) would be nice!

@foxdavidj Should we already move the Doc to Markdown, or should the editing be done first?