[NCSG-PC] Fw: Re: [Ccwg-auctionproceeds] [Ext] Re: Proposed text: role of the community

Thu Jul 25 15:50:50 EEST 2019

Excellent proposal from Elliot Noss; I hope that our representative on this working group may extend support for his proposal. Thanks!

Ayden

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, 25 July 2019 09:16, Elliot Noss <enoss at tucows.com> wrote:

> I would like to suggest a reworking and renaming of the constitution of the Advisory Board.
>
> First the name. An “advisory board” suggests advice. This group is a decision-making board. It should be named appropriately. At ICANN, “Advisory Committee” = recommend to the board. This is not the nature of the task here.
>
> I am not religious about the specific name, but the name should clearly connote its responsibilities. I will suggest “Grants Committee” and make lots of room for feedback.
>
> Second, 2 persons per SO/AC for Advisory Board would mean to me:
>
> - 2x GNSO
> - 2x ccNSO
> - 2x GAC
> - 2x ALAC
> - 2x SSAC
> - 2x RSSAC
>
> This seems egalitarian at the highest level but inappropriate to the task. I would like to suggest two alterations. First, there is no need for SSAC or RSSAC to be involved here. I respect both groups and think their work is important in relation to the core mission (some of my best friends are……). They are also appointed and, most importantly, are specific subject matter experts by design and that subject matter is not related to the task. Of course some projects will have a technical element but there are technical skills throughout the community sufficient to cover this AND many members of those two committees are also members of other parts of the community and will be able to scratch their philanthropic itch.
>
> Next, I strongly feel that the GNSO should have 4-6 seats. The two most important reasons are that it is a GNSO program that has generated the excess funds and the GNSO has essentially grown into two separate groups that are more about balancing each other than they are one cohesive group as the rest of the groups are. Of course there are different positions in each group, but the GNSO uniquely has two VERY different personalities in the CPH and NCPH.
>
> I suggest the following:
>
> - 6x GNSO
> - 2x ccNSO
> - 2x GAC
> - 2x ALAC
>
> This is a good group size as well. 10-12 is the right dynamic for a group like this.
>
> I would close here by noting a strong precedent for fitting the constitution of a community group to its context. During the original ICANN restructuring, we (Tucows) created the position that the ALAC should have a disproportionate representation on the nomcom. The original document is here (it is a fascinating historical read for ICANN history fans in any event and at the time was sometimes mistakenly linked to as the actual document produced by then-ICANN CEO Stuart Lynn):
>
> http://www.byte.org/heathrow/heathrow-declaration-v0r0d5-032502.html
>
> The context was that the nomcom was replacing the public vote and that ALAC was intended to best represent users interests. This was hotly debated at the time but we prevailed and this has remained an important and influential part of the ICANN structure.
>
> The same concept of context applies here.
>
> Thanks.
>
> EN
>
>> On Jul 24, 2019, at 10:50 AM, Emily Barabas <emily.barabas at icann.org> wrote:
>>
>> Hi Elliot,
>>
>> Here you go: https://docs.google.com/document/d/11dusiYnVTZhb_OvwZTvgKf_-5lF9NuzTAq6uV0fwYis/edit#heading=h.gjdgxs
>>
>> Kind regards,
>> Emily
>>
>> From: Elliot Noss <enoss at tucows.com>
>> Date: Wednesday, 24 July 2019 at 16:45
>> To: Emily Barabas <emily.barabas at icann.org>
>> Cc: "ccwg-auctionproceeds at icann.org" <ccwg-auctionproceeds at icann.org>
>> Subject: [Ext] Re: [Ccwg-auctionproceeds] Proposed text: role of the community
>>
>> Could we please put this in a google doc for easier commenting? Or is it ok if I do (I would need all the email addresses in order to share)? If I have missed some reason we can’t do that, apologies in advance. Thanks.
>>
>> EN
>>
>>> On Jul 23, 2019, at 12:45 PM, Emily Barabas <emily.barabas at icann.org> wrote:
>>>
>>> Dear CCWG members,
>>>
>>> A small group of volunteers comprised of Erika Mann and Alan Greenberg volunteered to draft a proposal for the CCWG regarding the role of the ICANN community to include in the Final Report. Please find attached their proposal for your review and feedback.
>>>
>>> This input, along with all other input received over the last few weeks, will be incorporated into a revised draft Final Report that will be used as a basis for discussion on our 31 July call.
>>>
>>> Kind regards,
>>> Emily
>>>
>>> Emily Barabas | Policy Manager
>>> ICANN | Internet Corporation for Assigned Names and Numbers
>>> Email: emily.barabas at icann.org | Phone: +31 (0)6 84507976
>>>
>>> <Advisory_Board-2019-07-17-v02-clean.docx>_______________________________________________
>>> Ccwg-auctionproceeds mailing listCcwg-auctionproceeds at icann.org
>>> https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds
>>> _______________________________________________
>>> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy ([https://www.icann.org/privacy/policy [icann.org]](https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=jk7n-M4s2YmuuENS1pzszm3xggx3GT11xtLzPPXzQ7U&s=uw-Jm3Omao4saa47gUnB3Ta9s3jp_fpoAioaV_ptu88&e=)) and the website Terms of Service ([https://www.icann.org/privacy/tos [icann.org]](https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=jk7n-M4s2YmuuENS1pzszm3xggx3GT11xtLzPPXzQ7U&s=CwJSnW1MBVgn6NIK-hamL97R6LprjDb4F_UsseGJD80&e=)). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190725/4365be8c/attachment.htm>