Media 2022

[rviscomi]

Media 2022

If you're interested in contributing to the Media 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
@eeeps	@eeeps @akshay-ranganath	@nhoizey @yoavweiss	@eeeps @akshay-ranganath	@MichaelLewittes	@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

• 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 Media 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-media on Slack for team coordination

[MichaelLewittes]

I could help with editing ("Publication"), having worked in media and been a print and digital editor for more than two decades.

[nhoizey]

I can be a reviewer on this chapter.

[eeeps]

I'd love to be an author, analyst, or even lead again (though if anyone else wants to take that, by all means!)

[akshay-ranganath]

I can help in analysis and authoring the chapter.

[siakaramalegos]

@eeeps going to put you as lead again for now since no one else has volunteered yet :)

[jyrkialakuijala]

I'd be happy to contribute as an co-author of this chapter, or possibly only in the content planning part and helping to scope this chapter. I have experience in image format and codec design -- WebP lossless and JPEG XL, LCP's relation to progressive images, and other work related to faster web sites (Brotli, WOFF2).

[siakaramalegos]

@jyrkialakuijala cool! Co-authors tend to contribute to writing. If you're wanting to be more of a guide, then reviewer might be a better role. Reviewers contribute at the outline stage as well as reviewing the written article. Or you could focus on writing in specific content areas, depending on how the content lead wants to organize the content.

On the content lead topic, I apparently jumped the gun, and Rick wants to wait for more volunteers just in case. Ideally, we get new voices each year, but that can be hard. :) So holding off on that though I'd still like to meet with you @eeps to get the ball rolling in the interim (see email).

[siakaramalegos]

@jyrkialakuijala I forgot to give you think wiki link - on the right-hand side you can see links for detailed descriptions of each role https://github.com/HTTPArchive/almanac.httparchive.org/wiki

[siakaramalegos]

@eeeps @akshay-ranganath just verifying you've already given your email addresses to @rviscomi to set you up in Big Query so you're not charged

[rviscomi]

👋 Hi everyone, please make sure you have access to the content team doc so we can start making progress on Milestone 1, which is to complete the chapter outline by May 15.

Also FYI we have a #web-almanac-media channel on Slack where you can coordinate on chapter progress.

@eeeps as the content team lead you'll effectively be the project manager for this chapter. You'll help to make sure that everyone is on the same page and the chapter stays on schedule. I'll hand it off to you to coordinate with the rest of the team on the next milestones.

[rviscomi]

🛎️ @nhoizey @eeeps @akshay-ranganath @MichaelLewittes reminder to access the planning doc and start adding your ideas to the outline. What's new with media on the web this year, or what topics would be interesting to revisit from previous years? We're hoping to have the outline completed by May 15 to give us enough time to add any needed custom metrics to the June crawl before it kicks off. Thanks!

[MichaelLewittes]

@nhoizey @eeeps @akshay-ranganath Want to meet on Monday to discuss? I'm on Eastern Time (ET). Let me know what works for everyone.

[eeeps]

Let's! Sent an invite. I know the time might not work great for @nhoizey...
Also starting things off with an outline based on last year's queries/chapter, to give us a starting point.

[nhoizey]

@eeeps 7pm is sometimes manageable, even with kids! 😅

(Sorry for the late answer, I was on holiday until today.)

[siakaramalegos]

@akshay-ranganath @nhoizey 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 Eric started. This deadline is critical as we only have 2 more weeks afterward to finalize custom metrics. Thanks!

[eeeps]

@siakaramalegos we went over the outline as a team in a zoom earlier in the week, and had some discussions about changes. I've just integrated those, and think we can fairly call the outline complete 🎉

[rviscomi]

FYI I've added @yoavweiss as a chapter reviewer for his help on HTTPArchive/custom-metrics#30. No expectations of reviewing the content necessarily, but want to make sure we do give credit in the by-lines.

[yoavweiss]

Thanks! :)

[siakaramalegos]

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

@eeeps 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.

[siakaramalegos]

@eeeps can you please provide an update here? It doesn't look like there has been any progress so I want to know the plan to get back on track. Thanks

[eeeps]

@siakaramalegos
Apologies, I have been (and am!)

1. behind
2. working a lot locally instead of pushing
3. behind on GH notifications...

Status, with one week to go: query PR is merged; some charts are done; draft is half written. Plan A was to have a fully-written draft (with charts) to turn over to the review/edit folks today but I am going to need at least today to finish the writing. The review/edit folks are aware of the time crunch and have time to devote to this this week, so it seems possible to have a reviewed draft completed by the end of the week.

[siakaramalegos]

hi @eeeps where is the draft? I don't see it in the draft document.

[eeeps]

@siakaramalegos I've been working locally in Markdown. Just copied and pasted over to the draft document. Unfortunately I didn't make as much progress as I wanted to this week and still have a few sections to write, before handing over to the editing team.

[eeeps]

@siakaramalegos I did not quite make the progress I wanted to this week, either. I am going to be away from keyboards until Monday morning, but should be able to devote all day Monday to this and am hoping to finally turn things over to @MichaelLewittes and @nhoizey by Tuesday.

[MichaelLewittes]

Will look out for it then. Thanks!

…

On Fri, Sep 2, 2022 at 12:02 AM Eric Portis ***@***.***> wrote: @siakaramalegos <https://github.com/siakaramalegos> I did not quite make the progress I wanted to this week, either. I am going to be away from keyboards until Monday morning, but should be able to devote all day Monday to this and am hoping to finally turn things over to @MichaelLewittes <https://github.com/MichaelLewittes> and @nhoizey <https://github.com/nhoizey> by Tuesday. — Reply to this email directly, view it on GitHub <#2884 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW6KSXORZPEBZEVUXCH5NH3V4F36ZANCNFSM5TH7YI5A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[siakaramalegos]

@eeeps any progress? We're running out of time and the reviewers need time as well

[eeeps]

@siakaramalegos The draft has now been reviewed by both @nhoizey (technical) and @MichaelLewittes (editorial). I'm starting the process of converting to markdown and creating a PR.

[eeeps]

I think the #3143 is ready to merge!

[svgeesus]

I noticed this in the 2022 Media chapter:

One caveat: AVIF and PNG allow tagging images with wide-gamut color spaces using format-specific shorthands, without using ICC profiles. We started down the path of trying to detect wide-gamut AVIFs and PNGs that don’t use ICC profiles, but accounting for the various ways they are encoded—and the ways our tooling reported on them—proved a bit too complex to tackle this year. Maybe next year!

It was unclear to me, for PNG if you were talking about gAMA and cHRM on the one hand or cICP on the other. I would expect usage for PNG to be low either way, gAMA and cHRM because it is easier and more common to drop an ICC profile into iCCP, and cICP because it is so new.

The usage in AVIF is all CICP H.273 metadata, same as PNG cICP.

The W3C PNG Working Group, which maintains the PNG specification, would be interested to help you detect usage of these next year. Is there a pointer to the difficulties that were encountered when trying to do that, this year?

cc/ @eeeps @siakaramalegos @rviscomi

[eeeps]

@svgeesus Thank you for reaching out!!

I was not talking about any particular PNG chunk, because all we had to work from was what is reported by exiftool and ImageMagick identify at some default settings... not the actual PNGs or any ability to parse them ourselves.

For AVIFs,exiftool reported the "nclx" string in a field called Quicktime.ColorRepresentation, which I made some progress on parsing and mapping to color space names before giving up.

All I could figure out for wide-gamut PNGs (without ICC) were the XY primaries, which turned up in identify's output, under chromaticity. I wasn't sure if I could map those to named color spaces.

One piece of example output (for an AVIF), and my half-finished attempts at parsing it, are here: https://observablehq.com/@eeeps/color-space-determiner

If we can figure out a way to reliably turn what we're currently getting from exiftool/identify into reliable color space categorization, well that's fantastic. I do wonder if making this better in the underlying tooling would be more useful for more people, though (if, of course, much harder).