<div>Hi Sam,<br></div><div><div><br></div><div>Thanks for raising awareness of these past conversations and for sharing your experience at a top of the pyramid of the NPOC Policy Committee. Regarding this comment:<br></div></div><div><br></div><blockquote style="padding: 0px 0px 0px 1rem; margin: 0px; border-left: 4px solid rgb(229, 229, 229); color: rgb(34, 34, 34); font-family: Arial, "Helvetica Neue", Helvetica, sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; line-height: 23.1px; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="protonmail_quote" type="cite"><div class="moz-cite-prefix"><div>It is not that we cannot make a list of potential deliverables, it is just that there is no consensus on what those should be, and no working from that to the work agenda for the Policy Committees. As Policy Committee Chair I got (gently, or not) beaten around the head and shoulders when I put suggestions on the table.<span class="Apple-converted-space"> </span><br></div></div></blockquote><div><br></div><div>For the benefit of those of us (like myself) who have not been members of the NCSG for very long, could you please fill us in on what these proposed deliverables were?<br></div><div><br></div><div>I'm very curious as to how we can fairly evaluate the work of the NCSG's Policy Committee. What are the indicators of success or failure we can use and which reflect the values of concern to our membership? (I ask this question rhetorically, it is something which demands input and reflection from all of us.)<br></div><div><br></div><div>Many thanks,<br></div><div><br></div><div class="protonmail_signature_block"><div>Ayden Férdeline<br></div><div><a href="http://www.linkedin.com/in/ferdeline" title="http://www.linkedin.com/in/ferdeline">linkedin.com/in/ferdeline</a><br></div><div><br></div></div><blockquote type="cite" class="protonmail_quote"><div>-------- Original Message --------<br></div><div>Subject: NCSG Policy Committee - Chair, etc.<br></div><div>Local Time: August 19, 2016 5:17 PM<br></div><div>UTC Time: August 19, 2016 4:17 PM<br></div><div>From: lanfran@YORKU.CA<br></div><div>To: NCSG-DISCUSS@LISTSERV.SYR.EDU<br></div><div><br></div><div><br></div><div class="moz-cite-prefix"><div>All,<br></div><div><br></div><div>This is a follow up to Avri's comments. I hate changing the
subject line on a thread but I have done it here because I think
there is an issue residing behind Avri's comment <i>"..the reason
the monthly</i><i><br>
</i><i>meetings
have not worked is because the PC members, especially the
council
members, do not make participating a priority - no knock against
the
current members, over the years, the members never have."<br>
<br>
</i>My comments are based on serving (badly) as Chair of the NPOC
Policy Committee. Despite what is written in Charters, etc. there
is no clear understanding of what the Policy Committees at this
level should actually be doing in terms of deliverables. It is not
that we cannot make a list of potential deliverables, it is just
that there is no consensus on what those should be, and no working
from that to the work agenda for the Policy Committees. As Policy
Committee Chair I got (gently, or not) beaten around the head and
shoulders when I put suggestions on the table. Most of the
criticism said simply, to use Stephanie Perrin's term, "recruit
more worker bees for PDPs & WGs". Even some proposed
strategies to deliver that outcome were trounced, although I see
that ICANN itself is now trying some of them. </div><div><br></div><div>This is not to criticize people, or offer excuses, it is just to
underscore the need for a discussion here. I will not presume what
the NCSG Policy Committee should focus on in terms of
deliverables, but I do think that a healthy discussion of what
that might be is needed. <br></div><div><br></div><div>Sam L, NPOC/csih<br></div></div></blockquote><div><br></div>