LC comments accountability Re: Ideas on simplification of process and operations

A few ideas around LC comments, DDoS and their accountability

Le 7 juil. 2010 à 06:15, Robin Berjon a écrit :
> LC can be gruelling when you're faced with a comment DDoS, but on the other hand if we don't have LC we don't get (all) comments.

My experience from handling LC, attending transition calls and discussing with people, in a ironic way, the LC DDoS is the result of the process itself. :) 

1. Implementers who are directly active and working on the specification usually give feedback during the WD phase.
2. People who feel that they will not be heard, or are more distant with the specification (in terms of interests to actually implement it) wait for the Last Call to be sure that their comments will be taken into account.

Possible ideas for solving the issues (with their own drawbacks):

* A Working Group where implementers have strong impacts in what goes into the specification and recognized as such in the charter and decision process.
* Raising the comments accountability (timeframe for answering, acknowledging the comment, etc) during WD phase. 
* Social mechanisms to encourage positive participation (right to comment depending on your involvement ala StackOverflow)



-- 
Karl Dubost
Montréal, QC, Canada
http://www.la-grange.net/karl/

Received on Wednesday, 7 July 2010 13:35:12 UTC