TPAC planning and specification status report

[LJWatson]

TPAC will be virtual this year. W3C is finalising the details but it is likely there will be events for the whole W3C community during the week of 26 to 31 October (as originally planned), with WG able to organise their own meetings in/around that week.

There are two things we need you to do:

1. Let @marcoscaceres and I know before 17 July if you want meeting time to talk about your specification.
2. Post a specification status report before 30 September.

The specification status report should include:

• What progress has your spec made in the last 12 months?
• Is anything blocking your spec from moving to CR?
• If yes, what is your plan to unblock it and do you need any help?

Your specification status report from 2019 is at #782

[marcoscaceres]

We are going to book 1 hour Q+A session for external parties and the community.

However, we already meet for 4 hours a week on this spec, so we don't need anything more formal from TPAC. Nevertheless, we will provide a status update.

[marcoscaceres]

We could also do two, 45 mins sessions... one covering Europe and another covering East/West coast with Australia.

[dmurph]

I'm not sure where this would fit - but I would really love to have a group discussion about the manifest unique ID issue #586. I can prepare some material to help describe the problem. I think we can definitely solve this with a good conversation.

Would this be something that would work in a Q&A session? Or would we be able to schedule specific time for it? If the later, then I can try to make sure the relevant people are in the meeting.

[dmurph]

@marcoscaceres Gentle ping - WDYT about that suggestion? Do you have any advice about how I can organize this?

[marcoscaceres]

Hi @dmurph, sorry, just coming back to this. I'll book some time for us to chat... Do you have pref timezone wise?

[marcoscaceres]

I added two proposed meeting times to the TPAC cal:
https://calendar.google.com/calendar/u/0?cid=Y19tczEyajVndXFhczdnZmg5ZjRiN3YydGY1MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t

Folks, let me know if those work and please feel free to add yourself - WG members should have received an invite to change/update the calendar.

[christianliebel]

LGTM! Looking forward to seeing you all!

[dmurph]

Great, thank you! I'm in PST, but I can attend outside of that as well.

[aarongustafson]

I will be able to make the US one.

[anssiko]

EU time LGTM. I look forward to soliciting input on the remaining CR milestone issues from the broader group.

[marcoscaceres]

What progress has your spec made in the last 12 months?

We did the following...

• Use HTML machinery to fetch manifests (Use HTML machinery to fetch manifests #894) - Adding link[rel=manifest] whatwg/html#5581
• Move some members to App Information Note (Editorial: Move some members to App Information Note #900)
• wrote a lot of tests.
• BREAKING CHANGES:
  • remove platform from ManifestImageResource (BREAKING CHANGE: remove platform from ManifestImageResource #913)
  • Replace "badge" with "monochrome" (BREAKING CHANGE: Replace "badge" with "monochrome" #833)
  • Remove beforeinstallprompt and appinstalled events. (Remove beforeinstallprompt and appinstalled events. #836)
  • remove serviceworker member (BREAKING CHANGE: remove serviceworker member #825)
• Added shortcuts member to the explainer and spec (Add shortcuts feature to the explainer and spec #768)
• Various fixes to ImageResource processing algorithms: (Various fixes to ImageResource processing algorithms #811)
• Rewrite installation process and install prompting logic (Rewrite installation process and install prompting logic #790)

Is anything blocking your spec from moving to CR?

We still have a lot of open issues + still need to do the non-IDL rewrite.

If yes, what is your plan to unblock it and do you need any help?

We keep working on it...

[dmurph]

Update on the conversation in #586 - this seems resolved, but I can go over the problem here if people find that valuable.

[dmurph]

Also interested in other vendor's thoughts about display_override pull request #932