Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define and categorize metrics #1

Closed
3 tasks done
rviscomi opened this issue Mar 4, 2019 · 3 comments
Closed
3 tasks done

Define and categorize metrics #1

rviscomi opened this issue Mar 4, 2019 · 3 comments

Comments

@rviscomi
Copy link
Member

rviscomi commented Mar 4, 2019

Refer to the Content Brainstorm doc for the latest draft

  • define a list of high-level "sections" (eg content, experience, distribution, publishing, etc)
  • define a list of mid-level "chapters" (eg for content: JS, CSS, img, etc)
  • define a list of low-level metrics (eg for JS: bytes, bootup time, libraries, etc)
@rviscomi
Copy link
Member Author

Leaving this open as we finalize subject matter experts assigned to each chapter.

Note to self for next time: assigning experts to chapters first gives us the chance to get their input on the metrics much sooner.

@rviscomi rviscomi transferred this issue from HTTPArchive/httparchive.org May 21, 2019
@rviscomi rviscomi changed the title [Web Almanac] Define and categorize metrics Define and categorize metrics May 21, 2019
@tunetheweb
Copy link
Member

@rviscomi approximately how many metrics do you expect in a chapter?

The original post had the following:

Subject Matter Expert (Author)
Responsible for providing an interpretation of the HTTP Archive data for specific chapters aligned with their area of expertise. For example, in the JS chapter, explain what the implications are for the number of bytes and CPU execution time to be rising. 1-2 paragraphs per metric are expected plus an intro and summary conclusion. Think of it like one blog post in a series written by many authors.
During the planning phase 5, experts should ensure that their chapters contain the necessary metrics to accurately capture their state. Also help us identify if there are any metrics that we are currently unable to capture so we can work on getting them in place for next year’s edition.
Time commitment: 2 hours in April to coordinate on chapters’ metrics, 4 hours in August to write interpretations.

So you thinking about 5 metrics in a chapter with a paragraph or two for each? Or 3? Or 10? Or 100? While it can of course depend on the topic and the author, I think it would be good to set a rough benchmark as a guideline so we're all roughly on the same page.

@rviscomi
Copy link
Member Author

rviscomi commented May 25, 2019

@bazzadp great question. 10 metrics per chapter on average sounds like a good amount. It's a balance between being comprehensive while respecting authors' time and readers' attention.

And 1-2 paragraphs per metric SGTM. We want readers to understand the implications of each statistic but we don't need to be overly verbose to get the point across.

These are loose guidelines and authors have the freedom to write more or less as they see fit. During the review process we can make adjustments as needed.

@rviscomi rviscomi closed this as completed Jun 4, 2019
@rviscomi rviscomi added this to the Chapter planning complete milestone Jun 4, 2019
@j9t j9t mentioned this issue Jul 23, 2020
10 tasks
dtikhonov pushed a commit to dtikhonov/almanac.httparchive.org that referenced this issue Feb 12, 2021
@logicalphase logicalphase mentioned this issue Jul 19, 2021
6 tasks
rviscomi pushed a commit that referenced this issue Nov 24, 2021
Test query for 'encoding -> format use'
@foxdavidj foxdavidj mentioned this issue May 17, 2022
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants