Bug 16674 - Feature discouragement in issue process - can use "too late to add features" as a technical argument in a counter-proposal
Feature discouragement in issue process - can use "too late to add features" ...
Status: NEW
Product: HTML WG
Classification: Unclassified
Component: working group Decision Policy
unspecified
PC All
: P2 normal
: ---
Assigned To: Maciej Stachowiak
HTML WG Bugzilla archive list
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-10 03:06 UTC by Maciej Stachowiak
Modified: 2012-04-10 19:02 UTC (History)
5 users (show)

See Also:


Attachments
Diff implementing a "too late for new features" option for counter-proposals (1.01 KB, patch)
2012-04-10 03:48 UTC, Maciej Stachowiak
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Stachowiak 2012-04-10 03:06:51 UTC
As we approach LC2 and beyond, it becomes important to slow down the rate of feature additions, so that the spec can be stabilized. Post-HTML5 versions should be the staging ground for new features. Therefore,  we should allow counter-proposals to use "too late to add features" as a technical argument against a proposal that suggests adding features. This is not necessarily dispositive in itself, but would weigh against the relative harm of adding a requested feature in a future version.
Comment 1 Maciej Stachowiak 2012-04-10 03:48:05 UTC
Created attachment 1111 [details]
Diff implementing a "too late for new features" option for counter-proposals
Comment 2 Sam Ruby 2012-04-10 15:56:20 UTC
(In reply to comment #1)
> Created attachment 1111 [details]
> Diff implementing a "too late for new features" option for counter-proposals

I support this change, and note that it is merely codifying something that already is occurring:

http://www.w3.org/html/wg/wiki/ISSUE-194/NoChange
http://www.w3.org/html/wg/wiki/User:Eoconnor/ISSUE-195