Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generic-sensor based geolocation API? #32

Closed
dontcallmedom opened this issue Jun 19, 2017 · 4 comments · Fixed by #36
Closed

Generic-sensor based geolocation API? #32

dontcallmedom opened this issue Jun 19, 2017 · 4 comments · Fixed by #36

Comments

@dontcallmedom
Copy link
Member

Should the group's scope include a revisited Geolocation API based on the Generic Sensor Framework? Should there be some incubated proposal before considering it?

@anssiko
Copy link
Member

anssiko commented Sep 14, 2017

Here's the Geolocation Sensor proposal:

https://wicg.github.io/geolocation-sensor/

@dontcallmedom, even if we were to incubate this spec in WICG, I'd prefer to have the spec live under the w3c GH org rather than wicg to not need to move the issues around after assumed transition to the DAS WG by the end of the year. Would that be fine? Last time I checked moving issues with all their associated metadata was impossible when migrating repos.

@xfq
Copy link
Member

xfq commented Sep 15, 2017

@anssiko

Is https://help.github.com/articles/about-repository-transfers/ enough? Or maybe we can find out how specs like IntersectionObserver were moved.

@anssiko
Copy link
Member

anssiko commented Sep 15, 2017

@xfq, thanks! It seems GitHub has improved its repo transfer process. Given this, I'd be fine hosting this repo under wicg during incubation.

@anssiko
Copy link
Member

anssiko commented Sep 18, 2017

I just proposed the Geolocation Sensor to WICG:

https://discourse.wicg.io/t/proposal-geolocation-sensor-based-on-the-generic-sensor-api/2355

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants