<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Agree completely! The forms are a horror and limit input on key
issues. <br>
</p>
<div class="moz-cite-prefix">On 2/13/2024 6:34 PM, Stephanie E
Perrin wrote:<br>
</div>
<blockquote type="cite"
cite="mid:38567718-f7ab-4efa-9601-ac5fde60fdbb@mail.utoronto.ca">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>I agree that one size cannot fit all, but the general info
about NCSG must be there and the website needs to be updated
with new comments. I think we have fallen away from a standard
format partly because ICANN staff have been experimenting with
new formats themselves....e.g. these wretched google forms that
only accept so many words in a box,, forms that preclude you
commenting on material that they do not include in their form.
In these cases, we need to return to a standard prose document
that compiles all our responses to the questions that were not
asked, ones we wish to raise.</p>
<p>I am very sorry to disappoint Judith and Remmie but this thing
deserved a lot more of our attention.<br>
</p>
<p>cheers Stephanie<br>
</p>
<div class="moz-cite-prefix">On 2024-02-13 1:12 p.m., Akinremi
Peter Taiwo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGK4d08QCed68QVpBen7WeWef5bK7o6+Pbm2wLK8bq+mhsV7Og@mail.gmail.com">
<div dir="auto">Thanks Tomslin for the reminder and the
suggestion for creating a template for public comments.
<div dir="auto"><br>
</div>
<div dir="auto">We can collate the existing templates, review
and make necessary changes to meet immediate needs.
However, I am afraid it won't possible to have a one size
fit all template. </div>
<div dir="auto"><br>
</div>
<div dir="auto">I would say in addition to the review public
comment template we should constantly organise public
comment writing training. </div>
<div dir="auto"><br>
</div>
<div dir="auto">This will ensure readiness of the community as
we can't demand skills that we dont know exit. </div>
<div dir="auto"><br>
</div>
<div dir="auto">My 2cent.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Peter.</div>
<div dir="auto">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, 11 Feb 2024, 7:27 pm
Tomslin Samme-Nlar, <<a
href="mailto:mesumbeslin@gmail.com" moz-do-not-send="true"
class="moz-txt-link-freetext">mesumbeslin@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>Dear policy members,</div>
<div><br>
</div>
<div>I want to take the opportunity to officially welcome
the new members to the 2024 Policy Committee. If like
most, it's been a while since you read the NCSG charter,
I want to use this opportunity to remind all of us what
the roles and responsibility of the Policy Committee is.</div>
<div>
<p><strong><i>2.5 The Policy Committee</i></strong></p>
<p><i>The NCSG Policy Committee is responsible for:</i></p>
<ol>
<li><i>Discussion and development of substantive
policies and statements issued in the name of the
NCSG. This activity will require coordination with
the membership and the Constituencies;</i></li>
<li><i>Organize policy initiatives on behalf of NCSG
membership, including PDP initiatives from the
membership;</i></li>
<li><i>Provide policy research and guidance to NCSG
representatives on the GNSO Council;</i></li>
<li><i>Keep membership informed of GNSO Council
activities;</i></li>
<li><i>Organize, appoint where appropriate, and track
NCSG participation in GNSO and other pertinent
Working Groups.</i></li>
<li><i>Organization and oversight of NCSG
participation in any GNSO Council-related tasks,
whether mandated by Bylaws, Council Procedures or
Council decisions.</i></li>
<li><i>Document methods and procedures used for
decision-making. Such documentation is subject to
review by the NCSG‑EC.</i></li>
</ol>
</div>
<div>There have been many suggestions over the years with
regards to updating or improving some aspects of our
methods & procedures, and I believe <a
class="gmail_plusreply"
id="m_-1448599550791731690plusReplyChip-1"
href="mailto:julf@julf.com" target="_blank"
rel="noreferrer" moz-do-not-send="true">@Johan
Helsingius</a> also have some suggestions but the one
I wanted to bring to your immediate attention is a
possible template for public comments.</div>
<div><br>
</div>
<div><b><u>PUBLIC COMMENT TEMPLATE</u></b><br>
</div>
<div>In the past (as far as I can recollect), we've simply
used past comments as a template for new comments,
though not explicit. Considering that different
submitted comments have different structures, newcommers
have expressed frustration and how quick it is to work
out how we expect penholders to structure comments. With
that in mind, I thought I'd solicit your views on a
proposal to create a public comment template and if
agreeable, I'd like to have a few people volunteer to
build such a template for PC endorsement.</div>
<div><br>
</div>
<div>Please respond with your thoughts and suggestions.<br>
</div>
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div>Warmly,<br>
</div>
Tomslin
<div><span
style="color:rgb(0,0,0);font-size:12.8px"></span></div>
<div><span
style="color:rgb(0,0,0);font-size:12.8px"><br>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank"
rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:NCSG-PC@lists.ncsg.is" moz-do-not-send="true">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext"
href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc"
moz-do-not-send="true">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
</body>
</html>