WebAssembly 2022

If you're interested in contributing to the WebAssembly 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
@ColinEberhardt	@ColinEberhardt	@binji, @RReverser	@JamieWhitMac	@rviscomi	@siakaramalegos

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 WebAssembly 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-webassembly on Slack for team coordination

Hi, I’m Colin Eberhardt, the author of the WebAssembly Weekly newsletter and general wasm enthusiast 👋

I’m interested in the author / analyst roles, but would be good to discuss the detail, make sure I am comfortable with the commitment.

Hi, @ColinEberhardt that's great news! You can find out more about each role in the wiki - see the side bar for each one: https://github.com/HTTPArchive/almanac.httparchive.org/wiki

The author is usually the content lead as well since it makes sense to guide the team where you want the writing to go. For the analyst role, anyone who knows SQL decently could work. Last year I did most of the analyst work for the chapter I authored, so it's definitely doable to do both, though more work. Rick is going to lead a workshop for analysts sometime this week so new people are welcome! If you know other experts in the space, it would be great to get them to sign up as reviewers. Having multiple reviewers is better than just one, if possible.

@ColinEberhardt here's the workshop for anyone interested in being an analyst! https://twitter.com/HTTPArchive/status/1516060214109298693

@ColinEberhardt I sent you an email to do a check-in - I know we're still waiting for some more volunteers but want to get you started so that doesn't hold you back. Let me know if you didn't get it.

Hi @siakaramalegos - I’ve not spotted that email. Was it to my gmail address? F can you resend, or perhaps DM via Twitter?

@ColinEberhardt just re-sent it to the gmail address in your GH profile. It doesn't look like I can DM you on Twitter, but feel free to DM me if you don't see the email!

@ColinEberhardt we need some more volunteers to make this chapter viable and achieve the first milestone on May 1. It puts the chapter at risk of being dropped if we can't make a viable team. Can you recruit some more people? For viability we need at least 1 reviewer and 1 analyst in addition to at least 1 author. It's nice to have 3+ reviewers though.

I'd like to help out here too! I think I'd do best as a reviewer, but perhaps could help out in other aspects as well.

@ColinEberhardt @binji to confirm, are either of you interested in taking on the analyst role?

That's great @binji - I'll be in touch shortly, it would be great to chat.

@rviscomi I could potentially take on the analyst role, but am looking to 'recruit' one of my colleagues. I should know in the next day or so.

@ColinEberhardt @binji I know we're still figuring out the structure of the team, but it'd be great to make sure you have access to the planning doc and start adding your ideas to the outline. What's new in WASM this year, or what would be interesting to revisit from last year? We've added the ability for the WebPageTest agents to analyze WASM files at runtime, so if you need to make any changes to it (new metrics or any other improvements), those need to be added before the June crawl kicks off. So we're hoping to have the outline completed on May 15, to give us an idea of what changes need to be made and leave enough time to get those changes in. Thanks!

Hi all, after chatting with @ColinEberhardt I've agreed to take on the analyst role for this chapter.

Looking forward to working on this, finding out what's new with WASM usage, and how it's changing the web.

Looks like @RReverser is up for being a reviewer too - looks like we have a team!

@ColinEberhardt go ahead and update the table and check off milestone 1 - congrats!!

Thanks @siakaramalegos - can you please give me the required privileges to allow me to edit this issue?

Invited you to the GitHub team there @ColinEberhardt

@siakaramalegos I've completed a very rough outline, discussing with our analyst and reviewer. if you need any more detail, let me know.

We will likely be wanting to make some changes / additions to the crawler. I've started the process via a very simple tidy-up PR:

https://github.com/HTTPArchive/wasm-stats/pull/1

Once this is merged we're going to add a few new features. Should all be ready ahead of the June crawl.

@binji, @RReverser just a reminder that the outline is due in 2 days. Please request edit access to the google doc, add your name and email to confirm participation, and provide feedback on the outline that Colin started. This deadline is critical as we only have 2 more weeks afterward to finalize custom metrics. Thanks!

@ColinEberhardt and team, is the outline complete? The deadline was May 15. We now have less than 2 weeks to finalize any custom metrics so getting to outline completion is critical. When it's complete, please check the milestone off. Thanks for your contributions!

I’m happy to call it complete - I discussed it verbally with @binji a few days ago. I’m busy working on custom metrics with @JamieWhitMac, so all progressing nicely

@ColinEberhardt @JamieWhitMac How are the custom metrics and list of metrics going? Checking in since the custom ones need to be merged before the crawl starts on June 1 so the team needs time to review it. Also the list of all metrics is due on June 1.

Hi @siakaramalegos thanks for checking in. The non-standard metric we're including has been merged and the list of metrics is in a comment on the PR above, just need to review with @ColinEberhardt and we'll consider those complete.

In case you missed it: https://blog.scottlogic.com/2022/06/20/state-of-wasm-2022.html

Hi @tunetheweb - yes, I did spot that. I'm the author 😀

D'Oh! Missed that 🤣

FYI, all the data is now available and ready to query, so now is the time to focus on finishing writing the queries, then running them and populating the results sheet so that the writing can start on time. Let us know if you need any help!

@JamieWhitMac it looks like the analysis is almost complete - can you give us an idea of % complete and timeline on the rest?

@ColinEberhardt when do you think you can begin the draft? Just as a reminder, the due date at the end of the month is for post-review and post-edit, so you'll need to set aside at least a week for those and preferably more.

Hi @siakaramalegos - my plan is to tackle the writing this week. I'll keep you updated on progress.

Just so that you don't worry if I don't respond, I'll be away starting tomorrow till 24th of August. I'll be still happy to review the draft upon return.

Thanks for the heads-up @RReverser - I'll try to get something ready for you to review ahead of that.