[NCUC-DISCUSS] [Announcement] PC NCSG NCUC rep.
Stephanie Perrin
stephanie.perrin at mail.utoronto.ca
Thu Jun 28 19:44:13 CEST 2018
I do agree that the remedy is improved communication, so lets work on
that. And congrats Claudio, looking forward to further collaboration.
Stephanie Perrin
On 2018-06-28 10:42, Cláudio Lucena wrote:
> Thank you all and I hope to be able to finish this replacement period
> with the necessary contributions. It is a first time experience from
> me, I'm available and I'd be more than happy to hear and consider all
> your thoughts, comments, concerns and suggestions so we can channel
> them appropriately.
>
> I share Dorothy's, Collin's and Stephanie's concerns about the
> importance of a consolidated policy approach whenever possible,
> considering that the interests of these constituencies are more often
> than not aligned, but I also think with the correct approach,
> communication and commitment we can turn this challenge into a
> valuable opportunity for wider engagement.
>
> Thank you all once again.
> Best,
> Cláudio
>
> --
> Cláudio S. de Lucena Neto
>
> cid:image001.png at 01D03AE9.ED675EB0
>
> http://www.fd.lisboa.ucp.pt/site/resources/design/fdlogo-researchcenter.jpg
>
>
> Visiting Research Fellow
>
> The Center for Cyber, Law and Policy, University of Haifa, Israel
>
> **
>
> PhD Candidate, Research Centre for the Future of Law
>
> Católica Global School of Law, Universidade Católica Portuguesa
>
> *
>
> Researcher, Fundação para a Ciência e a Tecnologia
>
> Ministério da Ciência, Tecnologia e Ensino Superior de Portugal
>
> *
>
> Professor of Law, Center for Legal Studies
>
> Paraíba State University (UEPB), Brazil
>
>
> LinkedIn: https://br.linkedin.com/pub/cláudio-lucena/22/7a8/822
> <https://br.linkedin.com/pub/cl%C3%A1udio-lucena/22/7a8/822>
>
>
> Universidade Estadual da Paraíba
>
> www.uepb.edu.br
> <https://br.linkedin.com/pub/cl%C3%A1udio-lucena/22/7a8/822>
>
> Centro de Ciências Jurídicas - Campus I
>
> Departamento de Direito Privado
>
> Rua Coronel Salvino de Figueiredo, 157
>
> CEP 58.400-253
>
> Campina Grande - PB - Brasil
>
> Fone/Fax: *55 83 3310 9753
>
>
> CONFIDENTIALITY NOTICE
>
> This message, as well as any attached document, may contain
> information that is confidential and privileged and is intended only
> for the use of the addressee named above. If you are not the intended
> recipient, you are hereby notified that any disclosure, copying or
> distribution of this email or attached documents, or taking any action
> in reliance on the contents of this message or its attachments is
> strictly prohibited and may be unlawful. Please contact the sender if
> you believe you have received this email by mistake.
>
>
>
> Em qui, 28 de jun de 2018 às 08:31, Joan katambi <joanhopek at gmail.com
> <mailto:joanhopek at gmail.com>> escreveu:
>
> Congs' Claudio
>
> Joan
>
> On Thu, Jun 28, 2018 at 1:42 PM, Rafik Dammak
> <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>> wrote:
>
> Hi,
>
> For background, the concept of policy committee (PC) was
> already in the older bylaws and it was not an addition to the
> new bylaws. The amendments in last bylaws were to update it
> and solve the inconsistencies. The PC was inactive de facto
> for years since the GNSO restructuring as we moved policy
> discussion and coordination at NCSG level. I think that will
> continue.
>
> I can understand that many may have concerns or find issues
> about NCUC PC or Vice-Chair but there was some rationale for
> them. For example, Vice-chair position is not an unusual one
> and it is there to ensure that someone can fill the chair
> tasks in case of any problem in accordance with what the
> bylaws state.
>
> The bylaws or charter are constitutional documents, they give
> guidance and principles but don't into go into the specifics
> and details. The bylaws or charter cannot envision all cases
> and scenarios but leave implementation to the
> operating procedures which are there to make things clear and
> outline how things functions.
>
> Best,
>
> Rafik
>
>
>
> Le jeu. 28 juin 2018 à 14:13, Arsène Tungali
> <arsenebaguma at gmail.com <mailto:arsenebaguma at gmail.com>> a écrit :
>
> This whole discussion would have happened by the time the
> NCUC charter was being discussed and before it being
> adopted by us here and then by a Board resolution.
>
> I am sure many of us (including myself) didn’t carefully
> read the draft charter, we would have noted issues like
> PCs or Vice Chair roles. I hope next time we take time to
> read these types of documents during consultation (or
> public comment) stage.
>
> The NCUC chair is simply doing her job, implementing our
> agreed upon charter.
>
> Though i agree that we should only have one PC at SG level
> (with reps from Constituencies) but i am inclined to see
> how this opportunity will be used by our members at
> constituency level, an opportunity to engage in policy
> work. Then we can judge its effectiveness and act
> accordingly. I urge those who took the Policy Writing
> course to consider populating these PCs and use the gained
> knowledge there as well.
>
> Thanks,
> Arsene
> -----------------
> Arsène Tungali,
> about.me/ArseneTungali <http://about.me/ArseneTungali>
> +243 993810967
> GPG: 523644A0
> Goma, Democratic Republic of Congo
>
> Sent from my iPhone (excuse typos)
>
> On Jun 28, 2018, at 4:15 AM, Benjamin Akinmoyeje
> <benakin at gmail.com <mailto:benakin at gmail.com>> wrote:
>
>> Congratulations Claudio as new PC NCSG NCUC representative.
>>
>>
>> As per the Policy Committe for NPOC, my suggestion will
>> be to let the committee be as long as they can make 10
>> members, this another opportunities for engagement of
>> members as long as their work can consolidate other
>> committees work.
>>
>>
>> Regards,
>> Benjamin
>>
>> On Thu, Jun 28, 2018 at 12:02 AM, Tomslin Samme-Nlar
>> <mesumbeslin at gmail.com <mailto:mesumbeslin at gmail.com>> wrote:
>>
>> I completely agree with the arguments put forth for
>> joint effort and collective action. Nevertheless, it
>> might be beneficial to know the rationale behind the
>> introduction of constituency-level PCs in the new bylaws.
>>
>> Cheers,
>> Tomslin
>>
>> On Thu., 28 Jun. 2018, 08:30 Collin Kurre,
>> <collin at article19.org <mailto:collin at article19.org>>
>> wrote:
>>
>> Hello everyone,
>>
>> I support the suggestion that we consolidate
>> policy committees.
>>
>> Rather than splitting into smaller factions,
>> which I believe would further silo conversations
>> and diminish our potential collective impact,
>> non-commercial stakeholders should seek to
>> coordinate more effectively in order to effect
>> positive change through joint action.
>>
>> Best regards,
>> Collin Kurre
>>
>> On Jun 27, 2018, at 12:05, Stephanie Perrin
>> <stephanie.perrin at mail.utoronto.ca
>> <mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
>>
>>> May I humbly suggest that this proliferation of
>>> policy committees (now we have 3) should be
>>> re-examined if it does not result in coordinated
>>> input on the policy input for GNSO council and
>>> comments. I am not sure we have enough forward
>>> motion at the NCSG level, and cross
>>> communication is not great Lets try to ensure
>>> that all PC members are in copy on all
>>> activities, so that we do not unnecessarily
>>> duplicate each others research, discussion, and
>>> outreach.
>>>
>>> On 2018-06-27 10:10, Renata Aquino Ribeiro wrote:
>>>> Dear members
>>>>
>>>> The EC has concluded the deliberation for PC NCSG NCUC representative.
>>>> The term is until after the election of the new EC (after October) as
>>>> this representative will be a replacement.
>>>>
>>>> The selected was Claudio Lucena. Votes received from AP, EU and LAC EC.
>>>>
>>>> We would like to thank all candidates who participated on the process
>>>> and remind you that there are many different ways of participating
>>>> with NCUC.
>>>>
>>>> Per implementation of our bylaws, we will soon build the Policy
>>>> Committee NCUC and we hope you keep interested as this group has to
>>>> have 10 participants.
>>>>
>>>> Thank you
>>>>
>>>> Renata
>>>> _______________________________________________
>>>> Ncuc-discuss mailing list
>>>> Ncuc-discuss at lists.ncuc.org <mailto:Ncuc-discuss at lists.ncuc.org>
>>>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>> _______________________________________________
>>> Ncuc-discuss mailing list
>>> Ncuc-discuss at lists.ncuc.org
>>> <mailto:Ncuc-discuss at lists.ncuc.org>
>>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>> _______________________________________________
>> Ncuc-discuss mailing list
>> Ncuc-discuss at lists.ncuc.org
>> <mailto:Ncuc-discuss at lists.ncuc.org>
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>
>>
>> _______________________________________________
>> Ncuc-discuss mailing list
>> Ncuc-discuss at lists.ncuc.org
>> <mailto:Ncuc-discuss at lists.ncuc.org>
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>
>>
>> _______________________________________________
>> Ncuc-discuss mailing list
>> Ncuc-discuss at lists.ncuc.org
>> <mailto:Ncuc-discuss at lists.ncuc.org>
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> <mailto:Ncuc-discuss at lists.ncuc.org>
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>
>
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org <mailto:Ncuc-discuss at lists.ncuc.org>
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>
>
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org <mailto:Ncuc-discuss at lists.ncuc.org>
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>
>
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20180628/d8ae5ab8/attachment.html>
More information about the Ncuc-discuss
mailing list