[NCSG-PC] EPDP team composition

[Rafik Dammak]

Hi Stephanie,

I think there is simple distinction. PC confirm NCSG policy positions,
letters and public comments, make the appointments  for representing NCSG
in WGs and committees, and as chair I ensure that is done. However, NCSG
chair liaises with other groups: SG/C, SO/AC etc, communicate with them and
for staff the SG chair is the point of contact and is added to all relevant
leadership mailing lists.
for EPDP case, it would have be awkward if I communicated the appointment
as I am vice chair of the EPDP team and GNSO council liaison :)

Best,

Rafik

Le ven. 20 déc. 2019 à 23:07, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> a écrit :

> I think it is worth a try to get more alternates, given the likelihood of
> more intense meetings.  I will send the notification re Stefan forthwith;
> many thanks for volunteering Stefan!
>
> Thanks for clarifying who should send it Rafik, I find these things rather
> confusing, between the role of the PC Chair and the NCSG Chair.  I presume
> the rationale here is that this was an SG appointment, given the structured
> nature of the EPDP.
>
> cheers Steph
> On 2019-12-20 01:34, Rafik Dammak wrote:
>
> thanks,
> so we can elevate Stefan from alternate to representative and send a note
> to GNSO secretariat. the communication should come from NCSG chair.
> for adding an alternate, I believe we should identify if there is any
> potential candidate. I am wondering if call for candidate will produce a
> sufficient pool of candidates who can step up .
>
> Best,
>
> Rafik
>
> Le mer. 18 déc. 2019 à 22:42, Tatiana Tropina <tatiana.tropina at gmail.com>
> a écrit :
>
>> all,
>> I think if Stefan is ready to step in, we can issue a call for an
>> alternate to join the team. We already did it before when we were replacing
>> Collin.
>> Cheers,
>> Tanya
>>
>> On Wed, 18 Dec 2019 at 14:37, Rafik Dammak <rafik.dammak at gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> thanks for the comments. I guess one first step is to confirm Stefan
>>> willingness and commitment to be rep for the rest of phase 2.
>>> there is also the suggestion if we need to replace the alternate or not.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> Le mer. 18 déc. 2019 à 17:13, Tatiana Tropina <tatiana.tropina at gmail.com>
>>> a écrit :
>>>
>>>>
>>>> To follow up with Dave’s comment: unfortunately, now I have no
>>>> bandwidth to be a full member. Legal committee is the only thing I could
>>>> fully commit to...
>>>> It’s hard — I’d say, nearly impossible — for us to find someone to
>>>> replace Farzaneh with her knowledge and dedication, and we have a big void
>>>> here. However, Stefan is very committed to EPDP and he is fully engaged. So
>>>> my plea to PC would be to appoint him.
>>>> Cheers,
>>>> Tanya
>>>>
>>>> On Wed 18. Dec 2019 at 05:52, Stephanie Perrin <
>>>> stephanie at digitaldiscretion.ca> wrote:
>>>>
>>>>> I am all for having Stefan as full member
>>>>> Steph
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> > On Dec 17, 2019, at 22:56, David Cake <dave at davecake.net> wrote:
>>>>> >
>>>>> > If we can’t make Tatiana step up to full member, I agree that
>>>>> Stefan would be a good choice to replace Farzaneh.
>>>>> >
>>>>> > David
>>>>> >
>>>>> >> On 17 Dec 2019, at 3:23 pm, Rafik Dammak <rafik.dammak at gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> hi all,
>>>>> >>
>>>>> >> as you know, Farzaneh resigned from all her NCSG positions which
>>>>> includes being representative to EPDP team. It is not a situation I wished
>>>>> to deal with but as PC we have to act on this as we appointed her
>>>>> previously.
>>>>> >>
>>>>> >> We should discuss how we shall proceed knowing the current
>>>>> situation/progress for EPDP phase 2 (working toward initial report) and if
>>>>> we need to either convert a an (willing) alternate to be representative
>>>>> and/or issuing a call for candidates.
>>>>> >> any thoughts or suggestions?
>>>>> >>
>>>>> >> Best,
>>>>> >>
>>>>> >> Rafik
>>>>> >> _______________________________________________
>>>>> >> NCSG-PC mailing list
>>>>> >> NCSG-PC at lists.ncsg.is
>>>>> >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>> >
>>>>> > _______________________________________________
>>>>> > NCSG-PC mailing list
>>>>> > NCSG-PC at lists.ncsg.is
>>>>> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>
> _______________________________________________
> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20191220/7588e14c/attachment.htm>