[PC-NCSG] NCSG-PC Work for 2015

[Rafik Dammak]

Hi Avri,

yes the idea to have a topic-call, we did one for IANA stewardship and was
helpful for our comment to the CCWg proposal. I think we can an
accountability call after frankfurt meeting and just before singapore

Rafik

2015-01-20 9:17 GMT+09:00 Avri Doria <avri at acm.org>:

>  Hi,
>
> Amr, glad to see you on the job.
>
> I would also like to suggest that we schedule at least one monthly call
> for the membership on one or another of the massive policy efforts that are
> going on.  Rafik and I talked about doing this but never got very far.  I
> think we did 1.
>
> avri
>
>
> On 19-Jan-15 15:58, Rafik Dammak wrote:
>
> Hi Amr,
>
>  thanks for these proposal,
> regarding PC meeting in Singapore, I may suggest 1 hour for the motions
> (if there are some substantive) and having 1 hour for strategy/planning for
> this year
>
>  Rafik
>
> 2015-01-19 23:47 GMT+09:00 Amr Elsadr <aelsadr at egyptig.org>:
>
>> Hi all,
>>
>>  I know I?ve had a really late start to kicking my new duties off for
>> the PC this year. This must have been a disappointment and a pain to most
>> of you. Been busy these past couple of weeks, but promise to do everything
>> I can to make up for it over the course of this year.
>>
>>  I wanted to start off by sharing some thoughts with you on how I see
>> what I need to do to make the PC perform its function more efficiently, and
>> would be grateful for feedback from all of you. These are my ideas on what
>> I should do, but I some tasks may have slipped my mind:
>>
>>  1. Keeping a close eye on open public comment periods; with
>> announcements (+ reminders) to the PC list to determine which issues are
>> important to our membership, and identifying who would take the lead on
>> each open issue. There are obviously some open issues on the table right
>> now, especially in the aftermath of the NCPH intercessional in DC, that I
>> will try to address in separate emails.
>>
>>  2. Sync that with a schedule on getting comments drafted and approved
>> by the committee. I don?t see a reason to change the current consensus
>> building approach we now use. Silence = consent, unless there are thoughts
>> to the contrary.
>>
>>  3. Following up with NCSG members in various GNSO WGs/CWGs. This is
>> important from a PC perspective to prep comments when asked similar to
>> public comment periods. This does not mean I personally plan to update the
>> NCSG wiki space on ongoing PDPs, but at least make sure there is some
>> initiative for NCSG to submit comments when comments are asked for by the
>> different working groups.
>>
>>  4. Asking councillors to take lead on prepping short briefs of motions
>> before council to be delivered to the general membership prior to every
>> monthly NCSG policy call. I know this is more council work than it is PC
>> stuff, but all the councillors are on the PC. Apart from raising awareness
>> on various GNSO policy recommendations amongst the NCSG membership, I?m
>> hoping this will also help inform councillors who are not as up to speed on
>> all of the motions on the meetings? agendas.
>>
>>  5. I will obviously need to help set agendas for the PC meetings that
>> take place at the ICANN public meetings; the first being next month in
>> Singapore.
>>
>>  6. I would like at least one alternate chair to pick up the slack
>> when/if necessary.
>>
>>  Those are what I?ve come up with. Feedback from all of you would be
>> highly appreciated.
>>
>>  Thanks.
>>
>>  Amr
>>
>> _______________________________________________
>> PC-NCSG mailing list
>> PC-NCSG at ipjustice.org
>> http://mailman.ipjustice.org/listinfo/pc-ncsg
>>
>>
>
>
> _______________________________________________
> PC-NCSG mailing listPC-NCSG at ipjustice.orghttp://mailman.ipjustice.org/listinfo/pc-ncsg
>
>
>
> _______________________________________________
> PC-NCSG mailing list
> PC-NCSG at ipjustice.org
> http://mailman.ipjustice.org/listinfo/pc-ncsg
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ipjustice.org/pipermail/pc-ncsg/attachments/20150120/5cccd8ad/attachment.html>