-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
PWA 2021 #2153
Comments
It's my pleasure to support PWA chapter as a reviewer! |
Welcome @webmaxru! |
If I may, I'd support PWA as a reviewer as well :) |
@demianrenzulli thanks for your interest in authoring this chapter! As the content team lead, you'll be responsible for the scope and direction of the chapter and keeping it on schedule. We automatically monitor the staffing and progress of each chapter based on the state of the initial comment so please keep that updated as you add new contributors and meet each milestone. We've created a Google Doc for this chapter, which you're encouraged to use to collaborate with the content team on the initial outline, metrics, and ultimately the final draft. Next steps for this chapter are:
@OBTo will be the section coordinator for this chapter, so they'll be periodically checking in with you directly to make sure the chapter is staying on schedule. Reach out to them here in this issue if you have any questions about the process. More information about the content team lead and author roles and responsibilities are available for reference in the wiki if needed. To anyone else interested in contributing to this chapter, please comment below to join the team! |
📟 paging 2019/2020 contributors: @tomayac @jeffposnick @logicalphase @ahmadawais @jrharalson @hemanth @thepassle @jadjoubran @pearlbea @gokulkrishh @jaisanth @tunetheweb Would any of you be interested to contribute to the 2021 chapter? This chapter could use your help with reviewing and/or analyzing. It'd be great to have your support! |
Yeah I'd be happy to help out as reviewer where possible :) |
Count me in for reviews, thank you! |
Thanks for your interest folks! It seems like @tunetheweb acted as analyst for the 2020 section. Hi Barry! Nice to meet you. You're more than welcome to collaborate on that role once again, but if you can't make it this year, and we don't find another contributor willing to work as analyst, I would be happy to take that role as well. We might be able to reuse several of the 2020 queries, plus other ideas we have in mind. |
For the rest of the reviewers: it's the first time I contribute, so I'm not sure how you interacted in the past, but I'll touch base with Rick and other contributors to see how we can get organized for this year's PWA section 👍👍👍 |
Hey @demianrenzulli , I'm one of the leads her for the Web Almanac project. I stepped in as the analyst last year as we were short, but wouldn't say PWAs are my area of expertise so would be great if someone else could take the mantle here. But definitely more than happy to help guide them and help out where I can. A lot of the queries was based on @tomayac 's work from 2019, and in particular this blog post of his that he used as the basis of that first year's chapter. See also #1258 (comment) for more info on regenerating that data for last year (we'll help get that data for you again assuming you want it). Not sure if you wanna chip in here @tomayac ? Though know you are involved in Capabilities chapter too.
Best thing is for all authors to open the draft word doc, request edit permission, and then start listing ideas of what metrics or sections you'd like to keep from 2019 and 2020, and what you'd like to introduce. Start to get a chapter outline based on that and comment and suggest things. The more ideas the better at the beginning, and then can see which ones are realistic and whittle it down. The earlier you start this, the less pressure you'll feel later :-) And btw you can get links to the results sheets (and the queries) from 2019 and 2020 at the bottom of the chapters to see what data those authors had to play with, to help with that: |
I've signed up for capabilities and am reluctant to overcommit. More than happy to answer ad-hoc questions you may have, though. |
Thanks a lot @tunetheweb!! If, based on previous experiences you think it's "doable" for someone to be both the author and analyst, I would be happy to collaborate on both sides. As mentioned, this is my first time contributing, so yours, @tomayac and other folk's guidance, would be highly appreciated. There are a bunch of resources here that I need to process before moving to the next step. I'll keep this issue updated. |
It's definitely doable to be an author and analyst, you wouldn't be the first. Each role peaks in activity at different times during the project, so it should be manageable for a single person assuming you can set aside a few hours each week. |
Hey @demianrenzulli excited to work with you and the rest of the group this year on the Almanac. I'm your go to guy if you've got any questions or need help so don't hesitate to reach out to me on github, the Slack (@OBTo) or email ([email protected]). Few first steps:
Excited to work with you all this year. |
This is great @OBTo! Nice to meet you too. My apologies for the delayed response, but we had a couple of things for I/O week, and some articles I've been working on for Web.dev. I'm planning to start working on this by tomorrow. I'll make sure to also touch base with the rest of the collaborators. We had some internal conversations already, and would be great to hear thoughts from the rest of the folks in this group. I hope we can create a great PWA chapter this year! |
Looks like I need some rights to be able to add myself there, I've requested them in the doc. |
How does Tuesday (May 25) 11a ET / 8a PT / 4p BST work for that 30m chat? Timezones here: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=5&day=25&hour=15&min=0&sec=0&p1=64&p2=179&p3=224&p4=136&p5=37&iv=1800 @demianrenzulli @webmaxru @Schweinepriester @thepassle @hemanth |
Good for me.
|
That time: next Tuesday 11ET, works for me! Thanks for organizing this @OBTo! |
Works fine for me! |
That's awesome! Thanks so much @alexburleh. I'll add that chart to the article doc, along with the reference to your analysis👍 |
@alexburleh any chance you could share the chart data in CSV format so we could run it through our data viz process for visual consistency with other charts? @demianrenzulli @tunetheweb we should be sure to annotate the chart with |
Any chance we could get the raw data instead of the chart @alexburleh ? That way we can use our own chart style (appreciate you got it very close, but still slightly different and those stylist highlights might look odd). And also means we can make it interactive on desktop like the other charts (not that interactive to be fair - just hover effects, but still!) Also FYI, in your report you have a typo in the header: |
Ah we gotta stop doing this @rviscomi !!! |
@rviscomi @tunetheweb Gentlemen, 1) attached is the CSV for the above diagram 2) Barry, thanks for the typo, will fix that :) |
Thanks @alexburleh - what's the total number to convert to %? |
Those in csv are the % already, which all add up to 100. The total
researched number was ~570K if I remember correctly. @tunetheweb
…On Tue, Oct 5, 2021, 21:50 Barry Pollard ***@***.***> wrote:
Thanks @alexburleh <https://github.com/alexburleh> - what's the total
number to convert to %?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2153 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV3QFWJUI7OL4Q2HEULRCGTUFMUETANCNFSM43UFNIXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Ah comma delimited - you crazy Continental Europeans 😁 |
Don't blame me :) I just know how to download the csv out of Google sheets
file :)
…On Tue, Oct 5, 2021, 21:56 Barry Pollard ***@***.***> wrote:
Ah comma delimited - you crazy Continental Europeans 😁
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2153 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV3QFWI7YTYLM6LBDRI246DUFMU2NANCNFSM43UFNIXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Added to sheet: https://docs.google.com/spreadsheets/d/16AkIdDBBkCR5Kgb7kyfYvnNLQBu23Vsh7MUSFHW9RtA/edit#gid=1817367668 What do you all think of this as a visualisation?: |
This looks very aligned to the way the rest of the charts look like. Thanks a lot for working on this @tunetheweb! |
For some reason the chart deviates from raw data. For example Biz and
Industrial should be 14%, not 1.4 and Computers and Electronics should be
2.1, not 0. Sensitive subjects should be 0.9, not 9.3. Online communities
should be less then 1%, not 7.6
I may have missed something too.
…On Tue, Oct 5, 2021, 22:26 Barry Pollard ***@***.***> wrote:
Added to sheet:
https://docs.google.com/spreadsheets/d/16AkIdDBBkCR5Kgb7kyfYvnNLQBu23Vsh7MUSFHW9RtA/edit#gid=1817367668
What do you all think of this as a visualisation?:
[image: Bar chart of PWA Categories]
<https://user-images.githubusercontent.com/10931297/136072717-67937490-a86c-46e7-8dbf-3cb9512b1b4e.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2153 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV3QFWLUB4Q6YMSE6ZWJJ3LUFMYMRANCNFSM43UFNIXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Sorry that's not really the style we use so would prefer to be consistent here rather than introduce new themes. @demianrenzulli can could out particular stats in the writing if he wants. |
Sure:) Your decision. It was just the suggestion. BTW just to make sure - I
meant not top 3 or 5 from top to bottom, but top 3 or 5 percentage wise :),
so Biz and Industries, Arts and Ent, Home & Garden etc.
Anyways guys, do as you need to :) I have no further Qs :)
…On Tue, Oct 5, 2021, 23:29 Barry Pollard ***@***.***> wrote:
Good. My only suggestion would be to color top 3 or 5 categories with one
color and the rest with other. Could be easier to view.
Sorry that's not really the style we use so would prefer to be consistent
here rather than introduce new themes. @demianrenzulli
<https://github.com/demianrenzulli> can could out particular stats in the
writing if he wants.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2153 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV3QFWOKEGN45PPEKNLT2JLUFM7W3ANCNFSM43UFNIXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hi @davrous! |
Many thanks to all for taking a look at the doc and leaving comments. |
Hi :)
It is probably a misprint in my little block -
Mobsted recently published THEY World State of PWA.... may be "their"?
…On Wed, Oct 13, 2021, 00:13 Demian Renzulli ***@***.***> wrote:
Many thanks to all for taking a look at the doc and leaving comments.
@rviscomi <https://github.com/rviscomi>: we have been making some final
changes with @tunetheweb <https://github.com/tunetheweb> and the draft
should be ready for the editorial review now. Looking forward to any
comments and suggestions you might have!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2153 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV3QFWPZT3ACNKMDGTCAK43UGSCE3ANCNFSM43UFNIXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
@rviscomi @demianrenzulli @davrous : here is a tweet from PWA Builder to confirm stats from their side: https://twitter.com/pwabuilder/status/1454250060326318082?s=21 |
The PWA 2021 chapter is completed and has been merged! Well done all involved - especially @demianrenzulli for holding the ship together. The first 2021 chapter merged! 🎉 Quite an achievement. Can't wait until it's launched. @demianrenzulli @webmaxru @Schweinepriester @thepassle @hemanth @tropicadri @andreban @jeffposnick @tunetheweb @rviscomi @OBTo |
Hi folks! Thanks again for collaborating in this year's PWA chapter!! The chapter has already been released: https://almanac.httparchive.org/en/2021/pwa Please, feel free to share or retweet the HTTP Archive announcement: https://twitter.com/HTTPArchive/status/1461029997804720131 cc // @webmaxru @Schweinepriester @thepassle @hemanth @tropicadri @andreban @jeffposnick |
Thanks for leading the project, @demianrenzulli! |
Sure thing! Thank you @webmaxru and thanks for the great insights everyone, it was great working with you, and once again many thanks to @tunetheweb for his contributions, support (and patience)!! @rviscomi has shared this interest form so you can sign up and be contacted when the 2022 chapter starts. |
@demianrenzulli @webmaxru @Schweinepriester @thepassle @hemanth @tropicadri @andreban @jeffposnick @tunetheweb Thank you all for your hard work getting this chapter over the finish line in time for the pre-release—the PWA chapter has been the most-read chapter in the past few weeks, English and Russian translation combined! Congratulations on finishing the chapter, and I'm excited to see us launch the rest of the chapters along side it on Wednesday 🎉 When you get 5 minutes, I'd really appreciate if you could fill out our contributor survey to tell us (the project leads) about your experience. It's super helpful to hear what went well or what could be improved for next time. 🙏 |
Part II Chapter 15: PWA
If you're interested in contributing to the PWA chapter of the 2021 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
Expand for more information about each role
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
1. Plan content
2. Gather data
3. Validate results
4. Draft content
5. Publication
Chapter resources
Refer to these 2021 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
The text was updated successfully, but these errors were encountered: