-
Notifications
You must be signed in to change notification settings - Fork 21
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
Explore the possibility of doing more joint deliverables with DAS #90
Comments
Thanks @marcoscaceres. Accordingly, I've opened an issue in the DAS WG charter repo w3c/das-charter#123 to solicit input on this proposal from the DAS WG point of view and track respective updates. Personally, I look forward to an even more fruitful collaboration in this device-centric web capabilities space. |
@marcoscaceres @LJWatson, the DAS WG has now carefully reviewed this proposal and suggest the following scope for our joint deliverables slightly adjusted from the earlier expectations: w3c/das-charter#126 Please let us know whether the WebApps WG would like to pursue this joint effort forward. The DAS WG participants are looking forward to an expanded, fruitful collaboration in this device-centric web capabilities space with all the WebApps WG participants. cc @reillyeon |
Still interested, but need a little bit more time. |
Closing as we now have the joint deliverables. |
A few of us would like to explore the possibility of doing more joint deliverables with the Device and Sensors WG (DAS). In particular, it would be great to jointly work on:
And possibly some others, but those would be a good start.
I've sent a PR to update the WebApps Charter.
The working group already has one joint deliverable with DAS: the Contacts Picker API.
Having the above specs as joint deliverables would provide more possibility for input by a larger set of members.
cc @reillyeon, @plehegar, @anssiko, @tantek.
The text was updated successfully, but these errors were encountered: