- From: Henri Sivonen <hsivonen@hsivonen.fi>
- Date: Thu, 15 Jan 2015 14:56:52 +0200
- To: David Dorwin <ddorwin@google.com>
- Cc: "public-html-media@w3.org" <public-html-media@w3.org>
On Wed, Jan 7, 2015 at 8:42 PM, David Dorwin <ddorwin@google.com> wrote: > As noted in my previous email, there are now EME issues on GitHub. :-( This is a general lock-in problem with GitHub. The excuse why it's OK to host repos there is that a DVCS makes it OK to host anywhere, but then issues get filed on GitHub instead of Bugzillas with commitment to long-term availability of bug history, so there's a risk of losing the trail of why changes were made in case the GitHub issue tracker ever goes away. > In addition, there are four new bugs in Bugzilla: > > 27740 - Suggest changing interface name 'MediaKeyStatuses' to > 'MediaKeyStatusMap' > 27739 - Change event name 'keyschange' to 'keychange'. > 27738 - Need to change name of 'message' event to avoid confusion. There's an additional bug that's blocked on naming things: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27124 ; and there's a bug that's almost about naming things: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27283 While naming is important in the sense that bad names confuse developers who are supposed to work with the API, naming issues really are a total bikeshed. Moreover, once implementations ship, there will be more value in stable names than in perfect names. If the Task Force continues to signal indecision and instability regarding to naming, there's a risk of prolonged vendor prefixing, and vendor prefixing is fundamentally hostile to interop, since different browsers implement things that are different as far as the calling code is concerned. I'd like to ask to Task Force to, please, decide the above 5 naming bugs very, very soon (as in: within about a week) and then stick to the names. > Finally, the following are blocked on a response from the person that > [re]opened them: > > Henri: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27268 Sorry about the delay here. I've replied. -- Henri Sivonen hsivonen@hsivonen.fi https://hsivonen.fi/
Received on Thursday, 15 January 2015 12:57:15 UTC