W3C home > Mailing lists > Public > public-geolocation@w3.org > June 2020

Re: [geolocation-api] Republish REC? (#42)

From: Philippe Le Hegaret via GitHub <sysbot+gh@w3.org>
Date: Wed, 10 Jun 2020 13:02:29 +0000
To: public-geolocation@w3.org
Message-ID: <issue_comment.created-641991417-1591794148-sysbot+gh@w3.org>
TL;DR: use Process 2019 even if it's not ideal.

Long version:

Current choices are listed in the next [steps](https://w3c.github.io/transitions/nextstep.html?shortname=geolocation-api).

Do you consider the part "Controlled by feature policy" to be a [new feature](https://www.w3.org/2019/Process-20190301/#correction-classes)? My guess is that it isn't, since it does _not add new functionality_.

If I'm correct, the path with Process 2019 would be to [Publish a Candidate Recommendation with substantive changes (but no new features)](https://www.w3.org/Guide/transitions?profile=CR&cr=rec-amended). 

This would put you to [publish the amended REC](https://w3c.github.io/spec-releases/milestones/?noFPWD=true) in September 2020.

If you pick the Proceess 2020 route, the current prediction is September 1 for it to become effective. You would first have to move your charter to P2020. That's around 30 days. This mean you could republish the original REC, with the changes appearing as proposed corrections (see [ Revising a Recommendation: Substantive Changes](https://w3c.github.io/w3process/#revised-rec-substantive)) in October 2020.   You can then republish the REC, with the proposed changes folded in, around January 2021 (time is eaten by the Call for Exclusion started in October).

Now, the pros and cons:
- P2019 path gives the full updated REC in September, but forces you to publish a CR and a PR to get there.
- P2020 path doesn't force you to publish a CR and a PR but, because P2020 isn't effective yet and your charter doesn use it, you stuck until October, at the earliest.

So, in summary, if you can bear the thought of going through a CR first, I recommend the path P2019 since it gets you to the updated REC sooner.

GitHub Notification of comment by plehegar
Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/42#issuecomment-641991417 using your GitHub account
Received on Wednesday, 10 June 2020 13:02:31 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 10 June 2020 13:02:32 UTC