<div dir="ltr">hi all, hi Bruce<div><br></div><div>We've never proposed that any new initiation path be created for changes to any kind of bylaws. This is all about the approval process, nothing to do with the "where do proposed changes arise from" question - it's out of scope for WS1 to deal with that, in my view.</div><div><br></div><div>So whether a bylaws change is fundamental or standard, it should still come up through the ICANN community, be subject to the usual consultation processes etc, and then there is a co-approval process.</div><div><br></div><div>That is why it isn't appropriate to go through the usual escalation process. Instead, that would should have been done. If it hasn't been done, there isn't any proposal to co-decide on - and if the Board was trying to rush a change to fundamental bylaws, the community would very quickly decide no.</div><div><br></div><div>SO -- the approach we need to take is to have the escalation steps available if demanded, but otherwise move straight from a proposed change to a fundamental bylaw triggering the Conference Call step, to decision. If the SOs and ACs decide a forum is needed that could also be held, as per the decision of the # set out in the table, but otherwise and uniquely for this sole Approval power, the question proceeds to decision.</div><div><br></div><div>cheers</div><div>Jordan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 12 November 2015 at 13:16, Bruce Tonkin <span dir="ltr"><<a href="mailto:Bruce.Tonkin@melbourneit.com.au" target="_blank">Bruce.Tonkin@melbourneit.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello All,<br>
<br>
Just picking up on the post from Tijani.<br>
<br>
>> I think for the Fundamental Bylaws modification, the Board (or the community) proposes the modification In case the community proposes the modification It should go through the escalation process we described for the other powers to trigger the modification process, consult about its pertinence, formulate the proposal and then decide to submit the proposal, but perhaps with other thresholds then, and if the board accepts the proposal, it will put it to public comment In case the Board is the trigger of the modification, the community should go through the escalation process to approve or reject the proposal.<br>
<br>
Practically for the creation or change of fundamental bylaws, I expect the Board would run the following process:<br>
<br>
- post the proposed bylaw or change to existing bylaw for public comment<br>
<br>
- seek direct input from each SO and AC on whether they support that change<br>
<br>
- only approve the change if there is the relevant level of support from the SOs and ACs<br>
<br>
<br>
I understand that the community power could be an escalation if somehow the Board approves a change without first getting input from the SOs and ACs - but I think that situation will be highly unlikely. Board approval is usually a final step - and essentially the Board approves when it is convinced there is a consensus in the community for the change.<br>
<br>
Also as I have noted before - it is rare if ever (I can't recall a case) that the Board ever initiates a bylaw change on its own. The change has usually come as a result of a community process - e.g. a policy recommendation from a SO, a recommendation from a cross-community working group, a recommendation from an AoC review team, or a recommendation from one of our other organizational reviews.<br>
<br>
Regards,<br>
Bruce Tonkin<br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr" style="font-size:small">Jordan Carter<br><br>Chief Executive <br><b>InternetNZ</b><br></div><div dir="ltr" style="font-size:small"><br>+64-4-495-2118 (office) | +64-21-442-649 (mob)<br>Email: <a href="mailto:jordan@internetnz.net.nz" style="color:rgb(17,85,204)" target="_blank">jordan@internetnz.net.nz</a> <br>Skype: jordancarter<br></div><div style="font-size:small">Web: <a href="http://www.internetnz.nz" target="_blank">www.internetnz.nz</a> </div><div dir="ltr" style="font-size:small"><br><i>A better world through a better Internet </i></div><br></div></div></div></div></div></div></div></div>
</div>