On 2015-07-16 9:21 PM, Martin Thomson wrote:
On Thu, Jul 16, 2015 at 5:44 PM, Benjamin Kelly <[email protected]> wrote:
FWIW, I've sent an intent to implement for the Streams API, but I won't be
able to actually start work until Q4. I just listed that as "favorable"
for now. Not sure if we need a clearer "we intend to implement this but
just haven't been able to start yet" status.
I would rather have:
- done (Firefox X)
- planned (with some vague time frame)
- "under investigation" or "no current plans"
Streams seems straightforward enough. navigator.connect would fall
into the last category.
I think we need to have a way to signal that we are not going to
implement a specific feature in addition to those categories (without
delving into the specific example here, but yes this is one of those
features.) That sends a useful signal to other browser vendors and web
developers. I know that for us, it would be hugely helpful to know if
vendor X is actively planning to not implement a certain feature when
weighing the pros and cons of working on something. I can imagine the
same would be useful for other vendors, and it would be nice if we did that.
Thinking about this more, I really don't see why we should try to narrow
down the list to fewer items. I feel like our default position on a
random spec is "no opinion", because we aren't aware of the content.
After someone studies it a bit, we can spend a while to consider it, and
then defer it to some point into the future (as in "in support of,
without current plans"), or decide to work on it soon, or decide that we
should not work on it, etc. Of course, we can't get too fine grained to
keep things comprehensible and realistic to keep updated, but a couple
of additional categories wouldn't hurt!
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
