<div dir="ltr"><div class="gmail_extra"><div><div dir="ltr"><span style="border-collapse:separate;border-spacing:0px"><div><span style="border-collapse:separate;border-spacing:0px"><span style="border-collapse:separate;border-spacing:0px"><span style="border-collapse:collapse"><div>
<br></div></span></span></span></div></span></div></div><br><div class="gmail_quote">On Tue, May 13, 2014 at 11:55 AM, Norbert Bollow <span dir="ltr"><<a href="mailto:nb@bollow.ch" target="_blank">nb@bollow.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><br></div>
Also, a key element of rough consensus processes is that those who are<br>
critical of a proposal must be given the opportunity to explain what in<br>
their view is wrong with the proposal, and there must be a culture of<br>
listening to and considering such arguments.<br>
<br>
“Rough consensus” means that after listening to and considering the<br>
arguments of those who hold critical views, there is still an<br>
overwhelming majority in support of the proposal.<br>
<br>
In my opinion, rough consensus processes are a very valuable tool when<br>
institutionalized in a proper context, as is the case e.g. in IETF.<br>
<br>
Using the term “rough consensus” for what happened at NetMundial is in<br>
my view not only factually wrong, but also comes with a significant<br>
risk of muddying the waters to the point where it becomes near<br>
impossibly difficult of explaining to people what rough consensus<br>
processes are and why the outcome documents of (genuine!) rough<br>
consensus processes should be considered to have significant weight and<br>
credibility -- within the scope of the expertise that is broadly<br>
distributed among the group that has reached rough consensus (which<br>
scope is of course rather limited in the case of the IETF.)<br></blockquote><div><br></div><div>I'd agree that we need to be careful with the use of words here. We already have enough trouble with "multistakeholderism"!</div>
<div>Was what we set out to do at NETmundial subject to consensus call procedure (whether full or rough consensus)? Were we in position to possibly check all the boxes for such a procedure? It's not really clear to me NETmundial was designed to do that. However, this perception (of something of a consensus) may be due to the fact that the NETmundial Declaration still is the outcome of negotiations or of a bargain (if you will) among several parties with divergent interests. In those conditions, the outcome is inevitably seen as something most parties agree on, to some extent, if only though compromising and concessions. </div>
<div><br></div><div>Now maybe we need a (more) proper way to document what the disagreements are/were as well as to define the kind of agreement that (the NETmundial outcome) actually is. </div><div><br></div><div>Cheers!</div>
<div>mawaki </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Greetings,<br>
Norbert<br>
<br>
<br>____________________________________________________________<br>
You received this message as a subscriber on the list:<br>
<a href="mailto:governance@lists.igcaucus.org">governance@lists.igcaucus.org</a><br>
To be removed from the list, visit:<br>
<a href="http://www.igcaucus.org/unsubscribing" target="_blank">http://www.igcaucus.org/unsubscribing</a><br>
<br>
For all other list information and functions, see:<br>
<a href="http://lists.igcaucus.org/info/governance" target="_blank">http://lists.igcaucus.org/info/governance</a><br>
To edit your profile and to find the IGC's charter, see:<br>
<a href="http://www.igcaucus.org/" target="_blank">http://www.igcaucus.org/</a><br>
<br>
Translate this email: <a href="http://translate.google.com/translate_t" target="_blank">http://translate.google.com/translate_t</a><br>
<br></blockquote></div><br></div></div>