Re: [geolocation-api] Publish as FPWD (#42)

In prep for FPWD: 

> must record the group’s decision to request advancement.

https://www.w3.org/2021/04/07-dap-minutes.html#r04

> must obtain Director approval.

@xfq, I can't recall the name of the repo where to file the request :( Could you assist me with this? 

> must publicly document all new features (class 4 changes) to the technical report since the previous publication.

https://w3c.github.io/geolocation-api/#changes-since-last-publication

> must publicly document if other substantive changes (class 3 changes) have been made, and should document the details of such changes.

https://w3c.github.io/geolocation-api/#changes-since-last-publication

> should publicly document if editorial changes have been made, and may document the details of such changes.

https://github.com/w3c/geolocation-api/commits/gh-pages

> must formally address all issues raised about the document since the previous maturity level.

All issues have been responded to in:
https://github.com/w3c/geolocation-api/issues

> must provide public documentation of any Formal Objections.

None. 

> should report which, if any, of the Working Group's requirements for this document have changed since the previous step.

None.

> should report any changes in dependencies with other groups.

WebAppSec for Permission API? 

> should provide information about implementations known to the Working Group.

Implementation in Blink, WebKit, and Gecko. 




-- 
GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/42#issuecomment-816359543 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 9 April 2021 02:38:13 UTC