<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On Saturday 26 October 2013 05:23 PM,
Jeremy Malcolm wrote:<br>
</div>
<blockquote
cite="mid:9E000712-0B79-408E-8E01-B1ACB1BE89F4@ciroap.org"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>On 26 Oct 2013, at 11:53 am, <a moz-do-not-send="true"
href="mailto:parminder@itforchange.net">parminder@itforchange.net</a>
wrote:</div>
<div><br>
</div>
<blockquote type="cite">
<blockquote type="cite">Yes it is the same, with those
suggestions incorporated, and reviewed.</blockquote>
<span></span><br>
<span>Thanks for the information, Jeremy...</span><br>
<span></span><br>
<span>Who reviewed and incorporated the suggestions, and
'finalised' the statement.</span><br>
</blockquote>
<div><br>
</div>
<div>The steering committee (except Marianne who presented
apologies) at a meeting the previous night.</div>
</blockquote>
<br>
In fact, the lack of clarity of the process is so high that I no
longer know who are members of steering committee... Dont those who
consider themselves members of the BB group kind of need to know
such basic stuff...<br>
<br>
One process issue that was raised repeatedly at the BB f2f meeting
was about clarity about steering committee members and where they
'came from'..... there was a demand that their association with
groups/ organisation etc be very clear, along with nature of funding
support etc, and I would add - if not explicit on the respective
websites - a basic statement of organisational objectives, vision/
mission etc, and list of activities and the such...<br>
<br>
parminder <br>
<br>
<br>
<blockquote
cite="mid:9E000712-0B79-408E-8E01-B1ACB1BE89F4@ciroap.org"
type="cite"><br>
<blockquote type="cite"><span></span><span>My only suggestion was
not incorporated - neither responded to... </span></blockquote>
<div><br>
</div>
<div>That, though, was just an oversight - I really apologise for
that. I actually thought that we had incorporated the only two
outstanding points and evidently overlooked this one, or thought
it had already been incorporated. </div>
<div><br>
</div>
<div>Somewhat explaining this lapse, we were very pressed for time
as we wanted it to go public on the last day of the IGF, and by
that time the BB server was already down, though I didn't yet
realise how badly. I spent a few hours that night trying to
bring it back up. </div>
<br>
<blockquote type="cite"><span>It was</span><br>
<span>regarding the main operative part of the sentence - the
second sentence -</span><br>
<span>which seek multistakeholder model of holding the
conference. I had</span><br>
<span>proposed that we instead ask specifically for civil
society to be an equal</span><br>
<span>partner in all processes of holding the conference..... </span></blockquote>
<div><br>
</div>
<div>However I do think this is covered pretty well anyway, if you
take the statement as a whole. </div>
<div><br>
</div>
<div>-- </div>
<div>
<div>
<div>Jeremy Malcolm PhD LLB (Hons) B Com</div>
<div>Internet and Open Source lawyer, consumer advocate, geek </div>
<div>host -t NAPTR 5.9.8.5.2.8.2.2.1.0.6.<a
moz-do-not-send="true" href="http://e164.org">e164.org</a>|awk
-F! '{print $3}'</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;"><span
class="Apple-style-span" style="border-collapse:
separate; border-spacing: 0px;">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;"><span class="Apple-style-span"
style="border-collapse: separate;
border-spacing: 0px;">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;"><span
class="Apple-style-span"
style="border-collapse: separate;
border-spacing: 0px;">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;"><span
class="Apple-style-span"
style="border-collapse: separate;
border-spacing: 0px;">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space;
-webkit-line-break:
after-white-space;"><span
class="Apple-style-span"
style="border-collapse: separate;
border-spacing: 0px;">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space;
-webkit-line-break:
after-white-space;"><span
class="Apple-style-span"
style="border-collapse:
separate; border-spacing: 0px;">
<div style="word-wrap:
break-word; -webkit-nbsp-mode:
space; -webkit-line-break:
after-white-space;">
<p><span
style="background-color:
rgba(255, 255, 255, 0);"><b>WARNING</b>:
This email has not been
encrypted. You are
strongly recommended to
enable PGP or S/MIME
encryption at your end.
For instructions, see <a
moz-do-not-send="true"
href="http://jere.my/l/8m"
title="https://luxsci.com/blog/installing-smime-and-pgp-encryption-certificates-into-major-email-clients.html"
rel="nofollow external">http://jere.my/l/8m</a>.</span></p>
</div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>