PWA 2020

[foxdavidj]

Part II Chapter 14: PWA

Content team

Authors	Reviewers	Analysts	Draft	Queries	Results
@hemanth	@thepassle @jadjoubran @pearlbea @gokulkrishh @jaisanth @logicalphase	@bazzadp	Doc	*.sql	Sheet

Content team lead: @hemanth

Welcome chapter contributors! You'll be using this issue throughout the chapter lifecycle to coordinate on the content planning, analysis, and writing stages.

The content team is made up of the following contributors:

• Authors
• Reviewers
• Analysts

New contributors: If you're interested in joining the content team for this chapter, just leave a comment below and the content team lead will loop you in.

Note: To ensure that you get notifications when tagged, you must be "watching" this repository.

Milestones

0. Form the content team

• Jul 6th: Project owners have selected an author to be the content team lead
• Jul 13th: The content team has at least one author, reviewer, and analyst (minimally viable team formed)

1. Plan content

• Jul 20th: The content team has completed the chapter outline in the draft doc
• Jul 27th: Analysts have triaged the feasibility of all proposed metrics

2. Gather data

• Jul 27th: Analysts have added all necessary custom metrics and drafted a PR to track query progress

• Aug 1 - 31: August crawl

• Sep 7th: Analysts have queried all metrics and saved the output to the results sheet

3. Validate results

• Sep 14th: The content team has reviewed the results sheet

4. Draft content

• Nov 12th: Authors have completed the first draft in the doc
• Nov 26th: The content team has prototyped all data visualizations

5. Publication

• Nov 26th: The content team has reviewed the final draft, converted to markdown, and filed a PR to add it to the 2020 content directory

• Dec 9th: Target launch date

[logicalphase]

I'm still really hoping to author or co-author this section. The last three years I've been actively involved in introducing PWAs to the wider web communities. So along with last year's references I've developed a lot of reference material on adoption.

[jadjoubran]

Also interested in peer reviewing this chapter 👍

[thepassle]

I'd also be interested in doing review work here 🙂

[foxdavidj]

@hemanth thank you for agreeing to be the lead author for the PWA chapter! As the lead, you'll be responsible for driving the content planning and writing phases in collaboration with your content team, which will consist of yourself as lead, any coauthors you choose as needed, peer reviewers, and data analysts.

The immediate next steps for this chapter are:

1. Establish the rest of your content team. Several other people were interested or nominated (see below), so that's a great place to start. The larger the scope of the chapter, the more people you'll want to have on board.
2. Start sketching out ideas in your draft doc.
3. Catch up on last year's chapter and the project methodology to get a sense for what's possible.

There's a ton of info in the top comment, so check that out and feel free to ping myself or @rviscomi with any questions!

@thepassle @jadjoubran @logicalphase @pearlbea I've put you down as reviewers for now, and will leave it to @hemanth to reassign at their discretion

@abraham @tpiros we'd still love to have you contribute as a peer reviewer or coauthor as needed. Let us know if you're still interested!

[hemanth]

Awesome @rviscomi!
Looking forward to work will all the co-authors and reviewers, PWA FTW!

[logicalphase]

@hemanth I'd be happy to co-author this. I've got the time and significant experience with PWAs. Just let me know. Cheers.

[hemanth]

Sure @logicalphase let us discuss, there was one more purpose who was interested too.

[hemanth]

For the July 13th checklist completion we have:

Author + Analysts: @hemanth
Reviewers: @thepassle @jadjoubran @logicalphase @pearlbea

Reviewers: please confirm with a thumbs up to this comment, if you are still interested in reviewing, thank you!

[hemanth]

Meanwhile, for July 20th item on the checklist, I have added a potential chapter outline please have a look and leave a comment on the document or in the issue here, thank you!

//cc Reviewers: @thepassle @jadjoubran @logicalphase @pearlbea

[logicalphase]

Outstanding @hemanth I'm looking forward to working with you and the team. Will review your materials, and reply. Please let me know if you need anything else right now.

[foxdavidj]

Hey @hemanth, looks like things are moving along pretty smoothly. Is there anything you need from me to keep things moving forward, and have the chapter outline and metrics settled on by the end of the week?

Also, can you remind your team to properly add and credit themselves in your chapter's Google Doc?

[thepassle]

Also, can you remind your team to properly add and credit themselves in your chapter's Google Doc?

Looks like I need some permissions — I requested them in the google doc. I imagine this'll be true for the other reviewers, too. 🙂 Fyi

[foxdavidj]

You should get access shortly :)

[tungpatrick]

Hey @OBTo @hemanth! I would love to help as an analyst, however, I am actually a fairly new 'analyst' and am very new to HTTP Archive. Will this be a problem? I definitely think this is quite grand, so I wanted to ask before I partake in such a role.

[tpiros]

Since I'm involved in the Media and Jamstack chapters, I will withdraw from this one if that's OK :) (or at least I'll unsubscribe if I'm not needed anyway :) )

[romaincurutchet]

Hey, I was referring to this thread: https://discuss.httparchive.org/t/progressive-web-apps-in-the-http-archive/1401
In particular, I like the metrics under the section "Service Workers Analysis".

[tunetheweb]

Yes that is basically the methodology we are following for this years chapter (Thomas wrote last years chapter and the queries he created for that are being reused for this years chapter with a few more).

We are currently analysing the results of this data now and will publish our thoughts later in the year. If curious you can see the SQL used and the results sheet of those queries from the links at the top of this issue.

[tunetheweb]

Hey @hemanth / @logicalphase did you get a chance to look over the stats yet? Do let us know if you think that's enough info to write the chapter or if there are any other stats you think you'll need and I can look to see if possible.

P.S. Hope you're recovering from your surgery @logicalphase and don't feel pressured to reply if still dealing with that - your health is more important!

[hemanth]

Thanks @bazzadp!

I went through the PWA Sheet and it as almost all the information required for the chapters under our radar.

Also, from our pervious discussions the metrics on BackgroundSync is as per the expectations right?

[tunetheweb]

Also, from our pervious discussions the metrics on BackgroundSync is as per the expectations right?

Yes it appears to be. If you are aware of any examples in the wild using this then feel free to ping me and can see if it’s in the data, but for now, it doesn’t appear to be used much at all! And particularly the periodic versions.

[foxdavidj]

@hemanth in case you missed it, we've adjusted the milestones to push the launch date back from November 9 to December 9. This gives all chapters exactly 7 weeks from now to wrap up the analysis, write a draft, get it reviewed, and submit it for publication. So the next milestone will be to complete the first draft by November 12.

However if you're still on schedule to be done by the original November 9 launch date we want you to know that this change doesn't mean your hard work was wasted, and that you'll get the privilege of being part of our "Early Access" launch.

Please see the link above for more info and reach out to @rviscomi or me if you have any questions or concerns about the timeline. We hope this change gives you a bit more breathing room to finish the chapter comfortably and we're excited to see it go live!

[hemanth]

Yes @OBTo

That's great news, sorry was AFK for couple of days.

Will restart pawing at this and eager to see this go live too!

[hemanth]

@logicalphase @thepassle @jadjoubran @pearlbea @gokulkrishh @jaisanth

We should meet and have a quick discussion on the few of the steps we need to take to reach the finish line sooner.
I understand that we are in different timezones and it is hard to find the best time...but let me propose 7.30PM PST 11/08/2020, hope that sounds like a plan.

[hemanth]

@logicalphase @thepassle @jadjoubran @pearlbea @gokulkrishh @jaisanth

The draft is ready for review please have a look and comment wherever it makes sense, have a look at the charts and let us know if they sound good or require additions or deletions.

Shoutouts to @bazzadp for fine tuning the graphs (lot of graphs!) 🙏

[tunetheweb]

@thepassle @jadjoubran @pearlbea @gokulkrishh @jaisanth @logicalphase any further comments on @hemanth 's draft?

Would be good to move this forward into converting this to Markdown but we should make sure you've all reviewed and fed back any commands before then as easier to manage the chapter in Google Docs initially.

[thepassle]

Sorry, I missed this. I'll take a look and dive in tomorrow 🙂

[gokulkrishh]

@hemanth @bazzadp Added a few suggestions via comments in the doc. Feel free to reject it if you feel it is not accurate. 💯
Awesome work on the content.

Excited for the full report of web almanac 2020 and CDS 🤗.

[thepassle]

Just went through the draft and left some comments 👍 Nice work so far

[tunetheweb]

@hemanth did you get a chance to look over and address the feedback? We need to start converting this ti Markdown is we want to make the launch date in one week's time.

[hemanth]

@bazzadp I have addressed all the feedback comments, there is only one graph that's pending with more information, post which we must be good to convert it to markdown. 👍

[rviscomi]

@hemanth that's great! I'd recommend that you start on the markdown conversion now and leave a placeholder for the outstanding graph, for example you can use a Jinja comment:

{# TODO(analysts, authors): Add graph for the XYZ metric. #}

That way we can review the markdown in a PR while the data viz is pending. That should help keep this chapter on schedule while we wait.

[hemanth]

@rviscomi Are we using any specific tool or any text to md CLI tool do?

[rviscomi]

Whatever is easiest for you. Personally, I'll copy the plain text from the doc, paste it into a text editor, and manually add the markdown syntax. @bazzadp has also had some useful advice about the process here and here.

[hemanth]

Had that as the second that, yeah, sounds like we are better off doing it manually, will start working on it.

[rviscomi]

Sounds great, thanks for working on it

[hemanth]

#1613 is ready with MD.

//cc @rviscomi @bazzadp