- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 May 2017 22:49:50 +0000
- To: public-device-apis-log@w3.org
> @rwaldron : what is the name you would prefer ? For the record, @rwaldron has expressed his opinion on the API design multiple times in https://github.com/w3c/magnetometer/issues/16 too. So have I. As mentioned above, there are plenty of pending issues that need to be addressed here to gather group consensus around this design. This is how I'd approach moving forward in this situation, ymmv: 1. Synthetize the issue and the various propositions made (including code and their pros and cons), either in #16 or in a new issue, with appropriate references to #16 and this conversation. 2. Drive consensus around the solution that is the most technologically sound and that better respects the [priority of constituencies](https://www.w3.org/TR/html-design-principles/#priority-of-constituencies). 3. Eventually file issues against the generic sensor spec if it turns out the agreed-upon solution might require changes there. 4. List the specific terminology and relevant definitions and proposing them as pull requests where they belong (probably split between the explainer and the generic sensor spec for the calibration stuff). 5. Make a new PR that specifies the solution reached in (2) and references the terminology defined in (4). -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/magnetometer/pull/21#issuecomment-300634565 using your GitHub account
Received on Wednesday, 10 May 2017 22:49:57 UTC