- From: Tantek Çelik via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jul 2020 06:42:21 +0000
- To: public-device-apis-log@w3.org
tantek has just created a new issue for https://github.com/w3c/dap-charter: == DASWG: Leave System WakeLock API in WICG until there is a second implementer == Per [DAS charter feedback](https://lists.w3.org/Archives/Public/public-new-work/2020Jun/0012.html): We believe it would be prudent for the System WakeLock API to go through the WICG process until it gets implementation commitment from at least a second browser vendor. Having said that, we would be comfortable with having WICG incubated specs being explicitly listed as charter as work items the working group could adopt at a future date. However, we'd like to see them listed in a manner similar to the [Web Apps WG Charter's section on WICG Specs](https://www.w3.org/2019/05/webapps-charter.html#wicgspecs) (i.e., separated out of the main deliverables list for the working group). cc: [@dwsinger](https://github.com/dwsinger) [@pes10k](https://github.com/pes10k) [@marcoscaceres](https://github.com/marcoscaceres) (Originally published at: https://tantek.com/2020/188/b4/das-system-wakelock-api-wicg) Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/101 using your GitHub account
Received on Tuesday, 7 July 2020 06:42:24 UTC