<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Oops I left out a tools point.<div><br></div><div>NCUCers are relentless Skypers. It’d make sense to share addresses (I’m billdrake) and for you to be added to some of the relevant chats. We can also do an EC chat as needed. We can also consider using other platforms for discussions, to taste…if you’re into Google tools or something else.</div><div><br></div><div>BD</div><div><br></div><div><br><div><div>On Dec 20, 2013, at 6:42 PM, William Drake <<a href="mailto:william.drake@uzh.ch">william.drake@uzh.ch</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi</div><div><br></div><div>So congratulations again to our newly elected EC members. The election produced a great result, and I’m hopeful that we’ll be able to take some good strides forward in building NCUC’s capacity to serve as a platform for civil society participation in the GNSO and ICANN. </div><div><font face="Palatino-Roman"><br></font></div><div><font face="Palatino-Roman">I have many loose ends to catch up on after a month of heavy travel, one of which is helping to get us booted up. In the next few days you’ll probably be barraged with messages from on various points—apologies in advance, including for the length of this message, which you might want to save for reference.</font></div><div><font face="Palatino-Roman"><br></font></div><div><font face="Palatino-Roman">There are a few basics I want to put on your radar at the outset, particularly regarding tech stuff.</font></div><div><font face="Palatino-Roman"><br></font></div><div><font face="Palatino-Roman"><br></font></div><div><font face="Palatino-Roman"><b>Working Methods:</b> </font><span style="font-family: Palatino-Roman;">There’s little on WM in our outdated bylaws,</span><font face="Palatino-Roman"> so it’s up to us how we proceed. We can discuss this online and F2F in Singapore, but for now: </font><span style="font-family: Palatino-Roman;">historically, the EC’s have tended to work in an informal manner, with chairs circulating proposals or action items to the list and if nobody objects within a certain time frame they move forward with assumed consensus, or at least rough c, often without clearly documenting that xyz was decided on this date by these people etc. </span><span style="font-family: Palatino-Roman;">Whether and how much to stick to or depart from this tradition was a subject of debate in the last EC. There was agreement that we could </span><span style="font-family: Palatino-Roman;"> </span><font face="Palatino-Roman">improve the documentation of decisions, and some folks wanted to do this by having more meetings and even voting on some items. But it also proved difficult to organize meetings sometimes, and many decisions were time pressured and needed action...Bottom line: I don’t like “silence is consensus” much, it doesn’t make for good governance or transparent decisions, so when one of us makes a proposal or a decision has to be taken, PLEASE try to respond either way within whatever time frame is suggested. If it turns out this isn’t working and we have to get more formal about it and start scheduling regular meetings and even voting we can, but as everyone’s busy let’s try to make asynchronous, informal, but "all hands on deck” work, and let’s document better, whether we do it at each step along the way or accumulate decisions and do a monthly listing, etc. TBD</font></div><div><span style="font-family: Palatino-Roman;"><br></span></div><div><span style="font-family: Palatino-Roman;"><br></span></div><div><b style="font-family: Palatino-Roman;">Appointments: </b><font face="Palatino-Roman"> This is our first task, as these really should get done in the next two weeks, holidays notwithstanding. I’ll write separately about this to the members list and copy the EC, but please a) think about whether there are people you’d suggest for the open slots and b) be prepared to help agree a list when we’re ready (appointments are the kind of thing we should do with all EC members involved).</font></div><div><font face="Palatino-Roman"><br></font></div><div><font face="Palatino-Roman"><br></font></div><div><div><font face="Palatino-Roman"><b>Listservs: </b></font><font face="Palatino-Roman">You are obviously </font><span style="font-family: Palatino-Roman;">subscribed </span><span style="font-family: Palatino-Roman;">to the EC listserv. </span> The EC list’s archive is <a href="http://lists.ncuc.org/pipermail/ncuc-ec/">http://lists.ncuc.org/pipermail/ncuc-ec/</a> There are other lists in addition to this and the members list, e.g. for the teams we set up last year. You can of course join any, and indeed hopefully volunteer to serve as team coordinators (will send another message about all this). <span style="font-family: Palatino-Roman;">NCUC lists are all at </span><a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo">http://lists.ncuc.org/cgi-bin/mailman/listinfo</a>. </div><div><br></div><div><font face="Palatino-Roman"><br></font></div><div><b>NCUC Website:</b> If you’ve not, please do look through <a href="http://www.ncuc.org/">www.ncuc.org</a>. The website was rebuilt last Spring by volunteers and is incomplete in terms of content. One of the things we really should do this year is bring this up to code, in collaboration with members of the e-team <a href="http://lists.ncuc.org/cgi-bin/mailman/roster/e-team">http://lists.ncuc.org/cgi-bin/mailman/roster/e-team</a>. With Roy’s archive initiative we’ll have additional incentive to focus on this.</div><div><br></div><div><br></div><div><b>GNSO</b> <b>Website: </b>If you are newish to planet ICANN and you’ve not had a chance, it’d be good to poke around the GNSO site, <a href="http://gnso.icann.org/en/index.htm">http://gnso.icann.org/en/index.htm</a>. NCUC exists for the GNSO, so over time it’d be good to get familiar with this complex institutional environment and the procedural/substantive issues. </div><div><br></div><div><br></div><div><b>Confluence</b> <b>Website: </b>There’s an ICANN community website that’s used for meeting planning etc. Since we have our own website we’ve not been using the space staff set up for us, <a href="https://community.icann.org/display/gnsononcomuserconst/NCUC-Home">https://community.icann.org/display/gnsononcomuserconst/NCUC-Home</a>, but we do use the Council spaces for meetings etc. (there’s some helpful stuff on <a href="https://community.icann.org/display/gnsocounres/General">https://community.icann.org/display/gnsocounres/General</a>), and for NCUC Constituency Day agendas, e.g. <a href="https://community.icann.org/display/gnsocouncilmeetings/NCUC+Buenos+Aires+Meeting+2013-11-19">https://community.icann.org/display/gnsocouncilmeetings/NCUC+Buenos+Aires+Meeting+2013-11-19</a>. In addition, Robin’s put stuff in the NCSG space. Probably At Large makes the most use of it, as they have staff to do stuff; other sorts of initiatives also go to Confluence, like the preparation for the Sao Paulo IG meeting next April (we have a Cross Community WG) <a href="https://community.icann.org/pages/viewpage.action?spaceKey=CPMMB&title=ICANN+Community+Preparation+for+the+Multistakeholder+Meeting+in+Brazil+Home">https://community.icann.org/pages/viewpage.action?spaceKey=CPMMB&title=ICANN+Community+Preparation+for+the+Multistakeholder+Meeting+in+Brazil+Home</a> Anyway, it’s worth knowing the Confluence space, and setting up an account if you don’t have one. One reason to do so is you can have a personal page where others in the community can find you, which we no longer have on our website since we gave up the Ning. </div><div><br></div><div><br></div><div><b>Adobe Connect:</b> NCUC has a web room we can use for meetings, both EC and with the broader membership, <a href="https://icann.adobeconnect.com/ncuc/">https://icann.adobeconnect.com/ncuc/</a> No software installation needed. One can log into meetings as Guest but then the moderator has to approve you, or you can get your own account. </div><div><br></div><div><br></div><div><span style="font-family: Palatino-Roman;"><b>Relevant Staff: </b>Glen de Saint Géry is the wonderful ICANN staffer who helps us and other GNSOers with admin stuff.</span><font face="Palatino-Roman"> If you want accounts on ICANN platforms or similar stuff, she’s the person you ask, <</font><a href="mailto:Glen@icann.org">Glen@icann.org</a>>. Nathalie Peregrine helps her <<a href="mailto:nathalie.peregrine@icann.org">nathalie.peregrine@icann.org</a>>. Rob Hoggarth is the professional staff person who’s our wrangler. I’ll be referring to these folks and others in mail so worth getting to know the cast of characters, including the policy staff for GNSO. <a href="http://www.icann.org/en/about/staff">http://www.icann.org/en/about/staff</a></div><div><b><br></b></div><div><br></div><div><b>Your Pictures:</b> <span style="font-family: Palatino-Roman;">Tapani posted pix of you all at </span><font face="Palatino-Roman"> </font><a href="http://www.ncuc.org/governance/executive-committee/" style="font-family: Palatino-Roman;">http://www.ncuc.org/governance/executive-committee/</a><span style="font-family: Palatino-Roman;"> On the assumption that these are ok with you all (please advise if not) I gave that link to Glen. </span><font face="Palatino-Roman"> She will ask ICANN’s webmaster to swap them into the outdated GNSO page about us at </font><a href="http://gnso.icann.org/en/about/stakeholders-constituencies/ncsg/ncuc">http://gnso.icann.org/en/about/stakeholders-constituencies/ncsg/ncuc</a> </div><div><span style="font-family: Palatino-Roman;"><br></span></div><div><font face="Palatino-Roman">Ok, enough for one message :-(</font></div></div><div><br></div>Bill<div><br></div><div><br><div apple-content-edited="true">
<div style="font-family: Palatino; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="font-family: Palatino; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="font-family: Palatino; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">**********************************************************<br>William J. Drake<br>International Fellow & Lecturer<br> Media Change & Innovation Division, IPMZ<br> University of Zurich, Switzerland<br>Chair, Noncommercial Users Constituency, <br> ICANN, <a href="http://www.ncuc.org/">www.ncuc.org</a><br><a href="mailto:william.drake@uzh.ch">william.drake@uzh.ch</a> (w), <a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a> (h),<br> <a href="http://www.williamdrake.org/">www.williamdrake.org</a><br>***********************************************************</div></div></div>
</div>
<br></div></div></blockquote></div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Palatino; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Palatino; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Palatino; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Palatino; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">**********************************************************<br>William J. Drake<br>International Fellow & Lecturer<br> Media Change & Innovation Division, IPMZ<br> University of Zurich, Switzerland<br>Chair, Noncommercial Users Constituency, <br> ICANN, <a href="http://www.ncuc.org">www.ncuc.org</a><br><a href="mailto:william.drake@uzh.ch">william.drake@uzh.ch</a> (w), <a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a> (h),<br> <a href="http://www.williamdrake.org">www.williamdrake.org</a><br>***********************************************************</div></div></div></div>
</div>
<br></div></body></html>