paul and all,<br><br><div class="gmail_quote">On Sat, Apr 27, 2013 at 12:12 PM, Paul Wilson <span dir="ltr"><<a href="mailto:pwilson@apnic.net" target="_blank">pwilson@apnic.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Kilnam.<br>
<br>
I suggest that for the time being we consider the MSG and "program committee" to be one and the same, under the name "MSG".<br></blockquote><div><br>agree with your proposal with reservation.<br>expect msg to discuss on this matter during msg/general assembly during seoul aprigf.<br>
<br>assume you are msg chair and also program committee chair now.<br><br>chon<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
My reason is that for both groups, a demonstrated multistakeholder approach must be taken, ensuring balance and diversity of participation. This is not trivial to implement, and our operating principles have still not been well tested. We don't have a great track record in the past, so we really do have to fix this and demonstrate both the commitment and the implementation.<br>
<br>
It will be much easier to achieve the required approach if we are dealing with a single group/list. If we have 2 lists, I think the job gets quite a bit harder.<br>
<br>
I do agree in principle that we could split the MSG from the Program group in future, if this is generally felt to be necessary.<br>
<br>
Paul.<br>
<div><div class="h5"><br>
<br>
<br>
<br>
On 27/04/2013, at 12:01 PM, kilnam chon <<a href="mailto:chonkn@gmail.com">chonkn@gmail.com</a>> wrote:<br>
<br>
> here is the proposal for APrIGF group and committee with their mailing lists (and website);<br>
><br>
> 1. MSG<br>
> " to support and ensure the proper conduct of the organizational work of the annual Asia Pacific Regional IGF,....................."<br>
><br>
> remark: to select a site for annual APrIGF<br>
> to approve the proposal of annual APrIGF<br>
> to oversee the org work of annual APrIGF<br>
> (more)<br>
><br>
> 2. "Program Committee"<br>
> to be in charge of the program of the annual APrIGF<br>
><br>
> remark: this committee may be/may not be identical to MSG with<br>
> respect its membership.<br>
><br>
> need to decide how to form PC. i recommend MSG to<br>
> decide how to form PC including its chair.<br>
><br>
> 3. domain name for APrIGF<br>
> we should use either <a href="http://rigf.asia" target="_blank">rigf.asia</a>, OR <a href="http://aprigf.asia" target="_blank">aprigf.asia</a>, but not both to avoid<br>
> confusion. we even have <a href="http://ap.rigf.asia" target="_blank">ap.rigf.asia</a>!<br>
><br>
> we have many <a href="http://xxxx.rigf.asia" target="_blank">xxxx.rigf.asia</a>(2012.rigf, <a href="mailto:msg@rigf.asia">msg@rigf.asia</a> proposal,..)<br>
> as well as <a href="http://xxx.aprigf.asia" target="_blank">xxx.aprigf.asia</a>(<a href="http://www.aprigf.asia" target="_blank">www.aprigf.asia</a>,...) now.<br>
><br>
> if we could not decide which one to decide, we should delete<br>
> the domain name, <a href="mailto:msg@rigf.asia">msg@rigf.asia</a> from the APrIGF OP.<br>
><br>
> chon<br>
><br>
><br>
><br>
><br>
><br>
</div></div>> <APrIGF_DraftOP_Rev_0426.docx>_______________________________________________<br>
> Rigf_program mailing list<br>
> <a href="mailto:Rigf_program@ap.rigf.asia">Rigf_program@ap.rigf.asia</a><br>
> <a href="https://mailman.dotasia.org/mailman/listinfo/rigf_program" target="_blank">https://mailman.dotasia.org/mailman/listinfo/rigf_program</a><br>
<br>
</blockquote></div><br>