Finalize assignments: Chapter 4. Media #6
Comments
|
Added @ahmadawais as a reviewer. Thanks Ahmad! |
|
Awesome! @rviscomi looking forward to helping. :) |
rviscomi
changed the title
|
@Yonet is interested in writing about WebXR. I think that could fit as a subsection of this chapter. @colinbendell @dougsillars @ahmadawais how does that sound? Not sure what kind of stats we'd be able to extract from HTTP Archive about XR but nonetheless I'm excited to include it as a topic for discussion/exploration. @Yonet what stats/metrics would be representative of "the state of WebXR"? If our dataset can't directly answer those questions we could always cite the data from outside sources. |
|
cool!
How high do we expect the adoption of WebXR to be? If the adoption rate is
low, I wonder if maybe we should create a different section called
'emerging' to highlight this (and other?) new standards?
thoughts?
/colin
…On Thu, 23 May 2019 at 11:31, Rick Viscomi ***@***.***> wrote:
@Yonet <https://github.com/Yonet> is interested in writing about WebXR. I
think that could fit as a subsection of this chapter. @colinbendell
<https://github.com/colinbendell> @dougsillars
<https://github.com/dougsillars> @ahmadawais
<https://github.com/ahmadawais> how does that sound?
Not sure what kind of stats we'd be able to extract from HTTP Archive
about XR but nonetheless I'm excited to include it as a topic for
discussion/exploration. @Yonet <https://github.com/Yonet> what
stats/metrics would be representative of "the state of WebXR"? If our
dataset can't directly answer those questions we could always cite the data
from outside sources.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&email_token=AAMMERLWXFCAWL54SWSDO2TPW22DLA5CNFSM4HOOLZT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWCTFNY#issuecomment-495268535>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMMERN34DU5RY3L2OCQAQ3PW22DLANCNFSM4HOOLZTQ>
.
|
|
I do think adoption will be low. Not even sure how to detect it, I'll defer to @Yonet for that. As for how to organize it, I think it could fit in this chapter as a self-contained subsection. I'd prefer keeping it under the "Media" heading than something else that is more miscellaneous. |
|
sounds good.
…On Thu, 23 May 2019 at 14:11, Rick Viscomi ***@***.***> wrote:
I do think adoption will be low. Not even sure how to detect it, I'll
defer to @Yonet <https://github.com/Yonet> for that. As for how to
organize it, I think it could fit in this chapter as a self-contained
subsection. I'd prefer keeping it under the "Media" heading than something
else that is more miscellaneous.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&email_token=AAMMERKYO5P7637NQJVDFFDPW3M3NA5CNFSM4HOOLZT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDBJ7Q#issuecomment-495326462>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMMERO6Z5RPRVVZZJOAWYTPW3M3NANCNFSM4HOOLZTQ>
.
|
|
I agree that this will be a VERY low number in HTTP Archive data. I like the idea of "emerging media" as a section.. we could put XR, and perhaps other ideas there too. As for detection - I know A-Frame - are there other libraries? There are 42 sites in April 2019 mobile that reference "aframe.min.js" A small subset, but an interesting one. |
|
@dougsillars @colinbendell is your idea to have "Emerging" as a section in the Media chapter, or to create a new chapter? @Yonet, also curious to hear your thoughts on detection and organization. |
|
Rick, out of curiosity, does HTTP Archive use an emulated Chrome Mobile, or
does it use the Android build of Chrome Mobile? If it's the actual Android
build, we could better detect XR api use since it's available in that build
(but not on desktop AFAIK).
/colin
…On Fri, 24 May 2019 at 08:53, Rick Viscomi ***@***.***> wrote:
@dougsillars <https://github.com/dougsillars> @colinbendell
<https://github.com/colinbendell> is your idea to have "Emerging" as a
section in the Media chapter, or to create a new chapter?
@Yonet <https://github.com/Yonet>, also curious to hear your thoughts on
detection and organization.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&email_token=AAMMERNKZKFPS7XQD7O3MHLPW7QMNA5CNFSM4HOOLZT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWFHNJI#issuecomment-495613605>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMMERPZWEP3WYMAUZLLIXLPW7QMNANCNFSM4HOOLZTQ>
.
|
|
Ah. It's emulated. Does that preclude us from detecting it, or just make it harder? |
|
I think just harder. I'd let @Yonet chime in with ideas for metrics and how
we would collect.
…On Fri, 24 May 2019 at 09:15, Rick Viscomi ***@***.***> wrote:
Ah. It's emulated. Does that preclude us from detecting it, or just make
it harder?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&email_token=AAMMERKB74IIS23HWT64FZLPW7TARA5CNFSM4HOOLZT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWFJU7A#issuecomment-495622780>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMMERJOQEQYSQPP5E5ZN2DPW7TARANCNFSM4HOOLZTQ>
.
|
|
👋 |
|
Hey @kornelski, would you be interested in reviewing this chapter? |
|
@rviscomi I think "Emerging" section makes sense since you still have to turn on experimental flags to be able to use WebXR. |
|
Agreed. What stats would you want to use to summarize the state of XR? |
|
@rviscomi Yes, if you have any questions about images/compression/optimization I'm happy to help. |
|
Thanks @kornelski, I've added you as a reviewer and sent you an invitation to join the Reviewers team. @colinbendell @dougsillars @Yonet @kornelski @ahmadawais I've pulled in the list of metrics from the brainstorming doc and edited them into the first post of this issue. Please take a look and let us know what you'd change. Today is the last day to change metrics before we hand things off to the Data Analyst team. @Yonet I still need a couple of things from you. Please go to https://github.com/HTTPArchive and accept the invitation to join the Authors team. This ensures that you get author-specific communications, I can assign issues to you, and you can edit issues like this one. After joining, please edit this issue to include any metrics you'd need to measure the state of WebXR. We don't have any metrics as of now. |
|
@rviscomi everything looks on point 👍 Suggestion: Can we have a sub-category metric to see how websites use SVGs. Especially when it comes to tools like SVGO that optimize SVGs by removing comments and certain other stuff. Not sure if it's doable. |
|
Sure, authors/reviewers are free to organize their chapter as they see fit. What metrics would you like to see in an SVG category? That would help us determine whether it's doable. |
|
I'd like to be able to see how optimized SVGs are? Are there SVGs with hidden layers and raster images in them. Not sure how that would work, but doing a mass check against SVGs with rules like ones mentioned here with a SVGO could be a useful metric. |
|
@rviscomi thank you! I am looking to see what data I am able to get as far as adaption. |
|
ok. I think we are good here with no shortage of metrics. @Yonet can you suggest which metrics you'd want to track? |
|
@Yonet any update on which WebXR metrics you'd like us to look at? Thanks for the suggestion @ahmadawais, the SVGO metric was added to the list. |
* start traduction * process trad * # This is a combination of 9 commits. # This is the 1st commit message: update # The commit message #2 will be skipped: # review # The commit message #3 will be skipped: # review #2 # The commit message #4 will be skipped: # advance # The commit message #5 will be skipped: # update # The commit message #6 will be skipped: # update translation # The commit message #7 will be skipped: # update # The commit message #8 will be skipped: # update # # update # The commit message #9 will be skipped: # update * First quick review (typofixes, translating alternatives) * Preserve original line numbers To facilitate the review of original text vs. translation side-by-side. Also: microtypo fixes. * Review => l338 * End of fine review * Adding @allemas to translators * Rename mise-en-cache to caching * final updates * update accessibility * merge line * Update src/content/fr/2019/caching.md Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com> * Update src/content/fr/2019/caching.md If it's not too much effort, could you also fix this in the English version as part of this PR as looks wrong there: 6% of requests have a time to time (TTL) should be: 6% of requests have a Time to Live (TTL) Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com> * Update src/content/fr/2019/caching.md Do we need to state that all the directives are English language terms or is that overkill? If so need to check this doesn't mess up the markdown->HTML script. Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com> Co-authored-by: Boris SCHAPIRA <borisschapira@gmail.com> Co-authored-by: Barry Pollard <barry_pollard@hotmail.com>
* start traduction * process trad * # This is a combination of 9 commits. # This is the 1st commit message: update # The commit message #2 will be skipped: # review # The commit message #3 will be skipped: # review #2 # The commit message #4 will be skipped: # advance # The commit message #5 will be skipped: # update # The commit message #6 will be skipped: # update translation # The commit message #7 will be skipped: # update # The commit message #8 will be skipped: # update # # update # The commit message #9 will be skipped: # update * First quick review (typofixes, translating alternatives) * Preserve original line numbers To facilitate the review of original text vs. translation side-by-side. Also: microtypo fixes. * Review => l338 * End of fine review * Adding @allemas to translators * Rename mise-en-cache to caching * final updates * update accessibility * merge line * Update src/content/fr/2019/caching.md Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com> * Update src/content/fr/2019/caching.md If it's not too much effort, could you also fix this in the English version as part of this PR as looks wrong there: 6% of requests have a time to time (TTL) should be: 6% of requests have a Time to Live (TTL) Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com> * Update src/content/fr/2019/caching.md Do we need to state that all the directives are English language terms or is that overkill? If so need to check this doesn't mess up the markdown->HTML script. Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com> * generate caching content in french * Update src/content/fr/2019/caching.md Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com> * Update src/content/fr/2019/caching.md Co-Authored-By: Barry Pollard <barry_pollard@hotmail.com> Co-authored-by: Boris SCHAPIRA <borisschapira@gmail.com> Co-authored-by: Barry Pollard <barry_pollard@hotmail.com>
Due date: To help us stay on schedule, please complete the action items in this issue by June 3.
To do:
Current list of metrics:
<source sizes><picture>or<srcset><meta>vs http👉AI (coauthors): Assign peer reviewers. These are trusted experts who can support you when brainstorming metrics, interpreting results, and writing the report. Ideally this chapter will have 2 or more reviewers who can promote a diversity of perspectives.
👉 AI (coauthors): Finalize which metrics you might like to include in an annual "state of web media" report powered by HTTP Archive. Community contributors have initially sketched out a few ideas to get the ball rolling, but it's up to you, the subject matter experts, to know exactly which metrics we should be looking at. You can use the brainstorming doc to explore ideas.
The metrics should paint a holistic, data-driven picture of the web image/video landscape. The HTTP Archive does have its limitations and blind spots, so if there are metrics out of scope it's still good to identify them now during the brainstorming phase. We can make a note of them in the final report so readers understand why they're not discussed and the HTTP Archive team can make an effort to improve our telemetry for next year's Almanac.
Next steps: Over the next couple of months analysts will write the queries and generate the results, then hand everything off to you to write up your interpretation of the data.
Additional resources:
The text was updated successfully, but these errors were encountered: