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

Hey Folks, @plehegar met this week to chat about the path forward. We looked at the requirements from the Process 2020 and, because we've added new features to the spec, we need to publish a FPWD... which turns out to be a great thing because it means we can significantly modernize the spec, then (relatively) quickly move it to be a "living standard".  

So, basically, this will be the plan: 

 * rewrite the spec, modernizing it to use Infra, etc. 
 * update the spec to deal with the visibility issue.

We can publish a FPWD whenever we like. Ideally we will do that straight after our meeting in a few weeks - which will give me time to make the above changes. After FPWD, @plehegar suggested we wait one month before going to CR. We can sit on CR until we get browser alignment on the page visibility issue (there are some web compat issues, so we need to decide which model is best and then figure out which engine needs updating). Alternatively, we move quickly to REC, then republish an updated REC to fix the visibility issue ~6 months down the line.  

If it's ok with everyone, I'd like to "officially" become Editor of this spec. I'd also be keen to have someone be a co-editor, to also edit or help review PRs (maybe someone new who hasn't edited before - preferably from an underrepresented community in our working group). Any taker to be my co-pilot? 


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


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

Received on Thursday, 25 March 2021 23:09:19 UTC