Chairs, I want to thank you for the re-introduction of the issues tracker. This will greatly assist in tracking issues and building consensus. Below is an example of a case where I thought consensus had been achieved, but arguably where the Tony and Mike continued to disagree. We always hope to have everyone agree, but in some cases, unanimous consensus may not be possible. In other cases, we may not have explored the problem far enough. It's clear to me, that the consensus process is important.
I hope that the issue tracker will help a lot in this area--but it may not be sufficient. In the past, we have had email votes, but the feedback was these email votes are guidance only. This leaves me confused as to how consensus is being achieved. Can the chairs clarify on what you believe the process is for the OAuth WG? There is also an issue that at times consensus is asked for far too early when the proposals to be voted on are often unacceptable to a significant community (case in point, the scenario below). As everyone knows, I've been in the same position several times myself. I often have the view that the problem isn't being addressed. Before moving to a vote, there may need to be agreement on the problem definition first, any necessary constraints, and the requirements for a solution. I want to acknowledge everyone's efforts here. This has been a big specification with lots of issues to solve. We're at the end-game and it can be frustrating ironing out the final issues. I have greater confidence that items will be properly tracked and handled but would like to see the consensus process improved/communicated as well. Best Regards, Phil Begin forwarded message: > From: "oauth issue tracker" <[email protected]> > Date: April 15, 2011 8:37:23 AM PDT > Cc: [email protected] > Subject: [OAUTH-WG] [oauth] #14: Restoring Client Assertion Credentials to > the framework specification > > #14: Restoring Client Assertion Credentials to the framework specification > > There was no clear consensus on the list to remove this. > > -- > --------------------------------+------------------------------------------- > Reporter: Tony Nadalin | Owner: > Type: defect | Status: new > Priority: major | Milestone: Deliver OAuth 2.0 spec > Component: v2 | Version: > Severity: Active WG Document | Keywords: > --------------------------------+------------------------------------------- > > Ticket URL: <http://trac.tools.ietf.org/wg/oauth/trac/ticket/14> > oauth <http://tools.ietf.org/oauth/> > > _______________________________________________ > OAuth mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
