PWA 2022

[rviscomi]

PWA 2022

If you're interested in contributing to the PWA 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
@diekus	@diekus @Suzzicks	@aarongustafson @webmaxru @Schweinepriester @tropicadri @beth-panx @tropicadri	@beth-panx	@siwinlo	@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 PWA 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-pwa on Slack for team coordination

[Suzzicks]

I can help if you want me to Lead or Author this topic.

[webmaxru]

Hello! My pleasure to be a Reviewer for this year again!

[Schweinepriester]

Hello everyone! 👋 Same as @webmaxru, I'm happy to be a reviewer again :)

[siwinlo]

hello! I'd be happy to join as an editor!

[foxdavidj]

@webmaxru @Schweinepriester @siwinlo

Hi all, we need your help. We currently don't have a Lead for this chapter, which means we'll likely 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 so much for your interest in helping us assemble the chapter this year

[Schweinepriester]

Maybe @Suzzicks wants to step up and be Lead? :)

I had typed the following before I realized @Suzzicks said "Lead or Author", preserving just in case 0:-)

 Perhaps last years great lead @demianrenzulli, last years capabilities lead and PWA enthusiast @christianliebel and/or fugu🐡 aficionado/champion @tomayac? :)

[foxdavidj]

Thanks for the suggestions @Schweinepriester.

@christianliebel @demianrenzulli @tomayac Would any of you be interested in the Chapter Lead role for the PWA chapter?

Regarding @Suzzicks, we unfortunately we haven't been able to get a hold of her

[tomayac]

@tropicadri is fully focused on PWA on Google's side, maybe she's interested? I will help out with the Capabilities chapter already and can't commit to more at the moment.

[foxdavidj]

@tropicadri Would you be interested in being an author for this years PWA chapter in the Web Almanac?

[tropicadri]

As much as I would want to, I don't have the bandwidth to lead. I can help but I can't be the main point of contact.

[webmaxru]

Let me chat with PWA v-team of Microsoft about someone leading that

[rviscomi]

⚠️ @Suzzicks @webmaxru @Schweinepriester @tropicadri @siwinlo it looks like this chapter still doesn't have a lead or an analyst and the outline hasn't been started yet. We might have to drop this chapter if it doesn't seem like there's enough interest to sustain it.

Could you help us find contributors who can staff this chapter? Meanwhile, it'd be great to start brainstorming ideas in the doc and when we get the team fully formed we can hopefully get back on track quickly.

@webmaxru is anyone at Microsoft interested in contributing?

[tropicadri]

@snugug would you have any interest in leading this chapter for the web almanac?

[webmaxru]

@webmaxru is anyone at Microsoft interested in contributing? I'm on it - will keep you posted asap, let's wait with the decision on dropping this chapter for a few more days please.

Meanwhile, I requested an access to the working doc - ready to be an interim Lead to create doc structure and start adding some ideas.

[aarongustafson]

I’m happy to contribute however it would be helpful.

[webmaxru]

@aarongustafson Awesome! Could you then volunteer as a content team lead?

[aarongustafson]

@webmaxru If need be. If there are others who want to lead—particularly smart folks whose perspectives we don’t often hear—I’m open to working in a supporting capacity, but if there are still no takers and we’re down to the wire, I’m happy to step up.

[Snugug]

@Snugug would you have any interest in leading this chapter for the web almanac?

Thanks for offering! I unfortunately don't think I've got capacity to lead this right now. I also echo what @aarongustafson has said that it'd be great to get perspective from folks we don't often hear.

[aarongustafson]

Maybe @diekus or @beth-panx would be interested?

[beth-panx]

@aarongustafson - Since I haven't been involved in this before, I am happy to be your reviewer/analyst and contribute wherever I can this year.

[foxdavidj]

Hey @aarongustafson would you be willing to step up as the Content lead for the chapter? If so we'd love to have you!

[diekus]

Hola. I can help if required!

[aarongustafson]

@foxdavidj I would actually love to see @diekus lead this effort if you’re cool with it. I am happy to sign on as a reviewer and even an editor.

[foxdavidj]

@diekus @aarongustafson @beth-panx @Schweinepriester @siwinlo @Suzzicks @tropicadri @webmaxru

@diekus We'd love to have you as the Chapter Lead for the PWA chapter! Excited to have you :)

As the PWA team lead you'll be responsible for setting the narrative for the chapter's contents, coordinating with the rest of the contributors, and generally keeping it on schedule. The top comment contains all the information/links you need, otherwise let me know if there's anything we can clarify.

A few things so we can kick-start this chapter:

1. @diekus It looks like @Suzzicks would be interested in co-authoring with you. As the chapter lead, if this is something you'd be interested in, can you follow-up with them? And then edit the top comment to reflect any changes?
2. To kick things off, I'd love to set up a 30 minute call within the next week to put any new faces to names, and give @diekus feedback on their ideas for the chapter's outline. @diekus can you find a time that works well for the team? You can see my availability via my calendly here (no need to book through it, though): https://calendly.com/foxdavid/30min

Excited to see this chapter come together.

[diekus]

Hola @foxdavidj . It'd be great to co-author with @Suzzicks! I'll look into calendars and get up to speed on all the documentation in the first post.

[diekus]

I am assuming this is the best way to communicate with the team. I am flexible to meet during the week, but as I am based in London my preferred times are (early-ish) morning West Coast times. Can I get an idea of where you're all based to make sure we convey on a time that's friendly hopefully for all of us?

[tropicadri]

I'm in california, so pacific time, also throwing this your way: https://whenavailable.com/ I used to coordinate meeting times with groups. You create the survey and then share the link, people vote with their availability.

[diekus]

Wicked Adri! Please mark your availability for: PWA Web Almanac Chapter kick off https://whenavailable.com/invite/v8MNlWxkHdwcm5m34PeN

[siwinlo]

Hi there! This week is Global Eng week at Etsy (where I work) and so it's a little hectic - that being said, I'm signed up as an editor so I'm not sure that it's crucial for me to meet at this juncture. Let me know if I can get looped in a little later on in the process perhaps?

Thank you!

On Tue, May 17, 2022 at 4:18 PM Diego Gonzalez @.***> wrote:

Wicked Adri! Please mark your availability for: PWA Web Almanac Chapter kick off https://whenavailable.com/invite/v8MNlWxkHdwcm5m34PeN

— Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2895#issuecomment-1129279555, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ7P73FFPKRF6YV6CF743I3VKP5JNANCNFSM5TH72LYA . You are receiving this because you were mentioned.Message ID: @.***>

-- Siwin Lo

siwinlo.com | siwinlo.github.io | www.linkedin.com/in/siwinlo

[webmaxru]

Hello team! I'm based in Oslo, Norway - CEST timezone. Looking forward to meeting you online|