Preparing for Candidate Recommendation

[marcoscaceres]

Hi fellow Editors, the W3C would like is to formalize a plan to move this spec to CR in the coming months. In order to do that, we have a fair amount of work to do...

I'm wondering if we can set up some video-based working sessions so we can work through:

• bug triage
• delegate tasks - set some deadlines for each editor.
• bug fixes
• Identify and mark things "at risk" (and/or remove single engine things)... yes, this is gonna really REALLY suck and piss a lot of people off :( Let's get through this.

Timezones are going to be a challenge, but we can spread out the pain and meet at different times.

I'm hoping we can meet every 2 weeks for 1-2 hours to work through things. US West Coast would have to be around 4pm, so to align with morning in the East Coast of Australia...

For EU folks, any time in your morning works for me from Monday to Thursday.

CR-Related Issues

https://github.com/w3c/manifest/milestone/1

Things that should be removed from the CR

• purpose: badge
• platform member - not implemented for image resources Provide guidance to UAs on appropriate names for "platform" members #862

We need to confirm if these are fully supported

• display member - how many modes are supported?
• orientation member - how many orientations?

Members

• description member - anyone using this for anything? moved to manifest-app-info
• related_applications member - Related applications members (at risk?) #877
• prefer_related_applications member - Related applications members (at risk?) #877
• categories member - Remove store metadata into own spec or note? #876 moved to manifest-app-info
• screenshots member - Remove store metadata into own spec or note? #876 moved to manifest-app-info
• iarc_rating_id member - Remove store metadata into own spec or note? #876 moved to manifest-app-info

[kenchris]

Sounds good to me!

[marcoscaceres]

@kenchris, could you do Monday mornings around 9am your time? That's 5pm for me.

[kenchris]

Yes, that is doable for me. Just not today :-)

[aarongustafson]

Happy to contribute here. Midnight for me will be tough 😉

We should also update the MDN docs as part of this effort: https://github.com/mdn/browser-compat-data/tree/0137d48523c8ac12e67c26c655ee1e026ba45c2d/html/manifest

[anssiko]

@kenchris on the critical path but I’ll be surely working with him on related tasks to make this more fun.

[marcoscaceres]

@aarongustafson, let's find a suitable time in your late afternoon for us to meet - we don't all need to meet at once. About MDN data, see question in #859.

[marcoscaceres]

@aarongustafson just spotted that you commented in #859! Thanks for following up there.

[aarongustafson]

As an FYI, I just took a pass through the open issues and moved a few to the ImageResource spec.

[mgiuca]

I have a fairly hard time window of 23:30–7:30 UTC on a given work day. (That's 9:30 to 17:30 Sydney time, same time zone as Marcos.) I also *probably* don't have too much to contribute on the W3C process side so I am happy to sit it out if you can find a time that works for Aaron but not me.

…

On Tue, 12 May 2020 at 09:24, Aaron Gustafson ***@***.***> wrote: As an FYI, I just took a pass through the open issues and moved a few to the ImageResource spec. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#865 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABXYUORUJDAN3AAF7ITOW3RRCCHBANCNFSM4M5URSXQ> .

[marcoscaceres]

@mgiuca, maybe you could join us for 30 mins on Mondays for quick chat/triage? Otherwise, if we can settle on a date/time with @aarongustafson we could do a 1 hour working session during your available hours? @aarongustafson, could you do 4:30-5:30pm on your Tuesdays?

@anssiko, I'll add you to the invite for Monday - but please drop in and out as needed... not need to commit for the full time.

[marcoscaceres]

Also, this is open to anyone... if you'd like to work on stuff, and have time, I'll add you to the meeting so you can join us on Zoom.

[aarongustafson]

@aarongustafson, could you do 4:30-5:30pm on your Tuesdays?

I'm on a Monday, Wednesday, Friday work schedule and my Tuesdays & Thursdays are spent keeping my 4yo occupied. If it's possible to do some day other than Tuesday or Thursday, I should be able to make it work. Otherwise, you can meet whenever and I can catch up async or you can just assign me tasks 😉

[marcoscaceres]

Ok, cool. Thanks @aarongustafson, updated the invite to be your Monday instead.

[kenchris]

I haven't received an invite

[mgiuca]

@mgiuca, maybe you could join us for 30 mins on Mondays for quick chat/triage?

AU Mondays or Pacific? Perhaps suggest a precise time and I'll check and we can move around if necessary. (I didn't get an invite either, please send and I will check if it is suitable, otherwise you can proceed without me.)

Unfortunately, I have a lot of constraints (which are pretty hard constraints due to child care duties):

• I don't work on AU Tuesdays (Monday for most of the world).
• I work from 9:30 to 17:30 on Monday, Wednesday–Friday Sydney time.
• I can't devote a lot of time to this on an ongoing basis; Web App Manifest is no longer the main focus of my work, though I am still able to help out on an ad hoc basis, as time allows.

[marcoscaceres]

First pass of spec - not looking issues yet:

• ExternalApplicationResource could be at risk
• platform is under-defined
• Using WedIDL as the data model is problematic -but we want to keep a non-normative IDL section (or something that is as easy to read).

For incubation, we should make a determination if beforeinstallprompt (BIP) will be incubated. Keep pushing Mozilla or WebKit on Web Share Target.

We are marking CR-relevant bugs with "CR label" on GitHub.

related_applications - we need to check relationship to getRelatedApplications() API and maybe it should move this member into that incubation - with support from Mozilla to keep incubating. Check that Web Payments doesn't depend on related_applications.

[marcoscaceres]

Working backwards on the issues ... we got up to issue #554 on Monday 18th of May.

[marcoscaceres]

@mgiuca, AU Mondays at 5:00pm Sydney time. You would only need to join for 30 mins max - we could prioritize anything you'd like to discuss - or to give us opinions on things or check Chrome implementation details.

[aarongustafson]

Ok, cool. Thanks @aarongustafson, updated the invite to be your Monday instead.

THANK YOU!

[mgiuca]

OK, I see the event in my calendar now. I'll attend the one on Monday and will decide future ones on a case-by-case basis. Thanks for setting it up.

[mgiuca]

Process-wise, we probably should label everything that isn't "defer" to "CR" and then drop the use of "defer". Otherwise, any new issue that gets filed will be considered for CR (and we'd like to have that list shrink over time, rather than grow with any new issues that people file).

[christianliebel]

Process-wise, we probably should label everything that isn't "defer" to "CR" and then drop the use of "defer". Otherwise, any new issue that gets filed will be considered for CR (and we'd like to have that list shrink over time, rather than grow with any new issues that people file).

@mgiuca We decided to move all CR-labeled issues into the new CR milestone (https://github.com/w3c/manifest/milestone/1) and keep the Defer label. All issues are now either part of the milestone or marked with Defer. New issues should then either be assigned to the milestone or the Defer label, issues that belong to neither of which are untriaged.

[mgiuca]

Fantastic, thanks for the work on triaging these. 29 to go!