Re: [geolocation-sensor] Mark as Discontinued Draft and continue in Geolocation API (#60)

>And yet, the fact remains that we had to make Device Orientation and Motion, Geolocation, and Screen Wake Lock API joint deliverables. Why do you think that is, @anssiko?

The proposal to make these joint deliverables came from you @marcoscaceres in https://github.com/w3c/webappswg/issues/90 and your rationale was "more possibility for input by a larger set of members". That is, you are asking a question you are in a position to answer, not me.

Related to this, considering the normal approach is for W3C members to join a Working Group responsible for the work they want to provide input on, it is understandable that the wider web community is asking questions, including in this very issue.

As a reminder to the wider web community watching: the [W3C Process](https://www.w3.org/2023/Process-20231103/) governs participation across [all W3C Working Groups](https://www.w3.org/groups/wg/) equally. This means all W3C Working Groups are governed by the same rules and follow the same process. None of them is limiting participation to ensure fairness in technical decision-making. All WGs are open for any [W3C member organization](https://www.w3.org/membership/list/) to join. There's also a separate Invited Expert path for individuals.

Again, while here, with my chair hat on, I feel obligated to refute @marcoscaceres' claims regarding wide review:

Please talk to the leaders of the horizontal groups to hear how the Devices and Sensors Working Group is conducting its wide reviews if you're not convinced. The Working Group is carefully following the W3C Process to ensure the entire set of stakeholders of the web community is informed of the progress of the Working Group, is able to perform reviews and provide comments on the specifications.

What comes to the Geolocation Sensor deliverable specific claims, the Working Group has most recently focused on listening to the wider web community's feedback on use cases, in particular for background operations. The work on the API definition has been on hold while we've solicited further feedback. What has become clear is that there's strong developer and end user demand for these use cases and that implementers have indicated they need more time.

As said already, the Working Group believes it is important to allow this discussion to happen, not suppress these voices.

Thank you to all the contributors who've shared helpful feedback. Please don't feel discouraged by these arguments that may seem intimidating and please continue to do the right thing.

Your voice continues to be heard. The Working Group is listening. Peace.

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/60#issuecomment-2149801436 using your GitHub account


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

Received on Wednesday, 5 June 2024 12:57:02 UTC