[CPWG] About Single Subject Meetings

Olivier MJ Crépin-Leblond ocl at gih.com
Thu May 21 22:54:24 UTC 2020


Hello all,

interesting discussion. I guess these additional calls are called CPWG
calls as they are about policy topics that could be addressed in the
CPWG but since they are big topics, they need more time to address than
the amount of weekly time we have in the CPWG. You'll notice the vast
majority of these additional calls are about the Subsequent Procedures.
If you are not interested in the topic of Subsequent Procedures, then by
all means, miss the additional calls. If you are interested in the topic
of Subsequent Procedures but the call is at an unfriendly time, or you
just don't have the time to attend when it is running, then by all means
listen, or even fast forward through the recording of the call later. I
often fast forward through calls I have missed, fast forwarding through
the intro, the blabla, the stuff I already know, and focus on the
important stuff, which means I can review an important 90 minute call in
30 minutes, when I have time.

So why are there so many calls about Subsequent Procedures? Because the
work on Subsequent Procedures will result in a new version of the
Applicant Guidebook for new gTLD applications. This monster of a
document, current version in
https://newgtlds.icann.org/en/applicants/agb is 388 pages in the English
version. 388 pages of very dense instructions for applicants, and rules
and so on. And of course, the new one is likely to be even longer. And
at some point, the new Applicant Guidebook is going to land on our
doorstep and our community is going to be asked to comment on it. And we
are probably going to be asked to do that in a short amount of time. All
we are trying to do in this round, is to educate enough people in our
community with each and every one of the topics that are being
discussed, whilst at the same time, also help Justine in guiding her for
ALAC positions in the Subsequent Procedures working group. So we do not
end up shocked about what we find in the new AGB and we don't end up
smothered by nearly 400 pages covered with dense ink. Death by AGB.
Kindest regards,

Olivier

On 22/05/2020 00:15, Holly Raiche wrote:
> I like the idea of not using the term ‘single issue’ CPWG calls.
>  Let’s call them what they are - calls on XXXXX subject.  And for
> those interested in the topic, attendance is nice but not mandatory.
>  Keep the CPWG calls so that people can have an overview of what is
> going on and then dig deeper into the issue(s) they want to follow.
>  Ed’s right - they are interesting, but they eat into people’s time.
>
> Indeed, at some point, we need to ask ourselves how much of people’s
> volunteer time ICANN can rightly claim, and what can reasonably be
> expected of any one individual. (particularly when a lot of those
> calls are not Sydney-Friendly times)
>
> Holly
>
>> On May 22, 2020, at 7:12 AM, Jonathan Zuck
>> <JZuck at innovatorsnetwork.org <mailto:JZuck at innovatorsnetwork.org>> wrote:
>>
>> I guess I see all of this as a a symptom of just having too much to
>> do. THAT is the real issue. The alternative is to just have a longer
>> call or more than I e cpwg call which seems like even more. Dunno
>>
>> Jonathan Zuck
>> Executive Director
>> Innovators Network Foundation
>> www.InnovatorsNetwork.org <http://www.innovatorsnetwork.org/>
>>
>> ------------------------------------------------------------------------
>> *From:* Eduardo Diaz <eduardodiazrivera at gmail.com
>> <mailto:eduardodiazrivera at gmail.com>>
>> *Sent:* Thursday, May 21, 2020 2:02:25 PM
>> *To:* Jonathan Zuck <JZuck at innovatorsnetwork.org
>> <mailto:JZuck at innovatorsnetwork.org>>
>> *Cc:* CPWG <cpwg at icann.org <mailto:cpwg at icann.org>>
>> *Subject:* Re: [CPWG] About Single Subject Meetings
>>  
>> Exactly my point! 
>>
>> I am interested in being able to collaborate and provide my input in
>> the regular CPWG meeting discussions therefore I feel compelled to
>> participate in these single issue meetings (which by the way are very
>> enlightening) to do so. Otherwise, why I am participating in the CPWG
>> at all?
>>
>> The problem is not the single issue meeting itself is the additional
>> meetings.
>>
>> -ed
>>
>>
>>
>> On Thu, May 21, 2020 at 4:49 PM Jonathan Zuck
>> <JZuck at innovatorsnetwork.org <mailto:JZuck at innovatorsnetwork.org>> wrote:
>>
>>     Actually, the way we've been doing them there's no duplication.
>>     If you miss the single purpose, it's not discussed again on the
>>     CPWG call so it really is up to you. 
>>
>>     Jonathan Zuck
>>     Executive Director
>>     Innovators Network Foundation
>>     www.InnovatorsNetwork.org <http://www.innovatorsnetwork.org/>
>>     ------------------------------------------------------------------------
>>     *From:* Eduardo Diaz <eduardodiazrivera at gmail.com
>>     <mailto:eduardodiazrivera at gmail.com>>
>>     *Sent:* Thursday, May 21, 2020 1:36:24 PM
>>     *To:* Jonathan Zuck <JZuck at innovatorsnetwork.org
>>     <mailto:JZuck at innovatorsnetwork.org>>
>>     *Cc:* CPWG <cpwg at icann.org <mailto:cpwg at icann.org>>
>>     *Subject:* Re: [CPWG] About Single Subject Meetings
>>      
>>     Jonathan:
>>
>>     The thing is that it is expected for all CPWG participants to
>>     also participate in these single issue meetings. How are we
>>     expected to contribute during the regular CPWG meeting
>>     discussions if we do not the issues at hand as well as the folks
>>     that want to dive deeper into the subject.
>>
>>     -ed
>>
>>     On Thu, May 21, 2020 at 3:18 PM Jonathan Zuck
>>     <JZuck at innovatorsnetwork.org
>>     <mailto:JZuck at innovatorsnetwork.org>> wrote:
>>
>>         Thanks Eduardo. I guess I see the single purpose meetings as
>>         a kind of ad hoc subcommittee of only folks that want to dive
>>         deeper into that subject. We need to “keep the lights on,” so
>>         to speak, on the CPWG calls and make sure we’re covering all
>>         that needs discussing on a particular week so we can’t really
>>         just convert them to single purpose as we might start letting
>>         things fall between the cracks. Does that make sense?
>>
>>         Jonathan
>>
>>          
>>
>>          
>>
>>         *From: *CPWG <cpwg-bounces at icann.org
>>         <mailto:cpwg-bounces at icann.org>> on behalf of Eduardo Diaz
>>         <eduardodiazrivera at gmail.com
>>         <mailto:eduardodiazrivera at gmail.com>>
>>         *Date: *Thursday, May 21, 2020 at 12:16 PM
>>         *To: *CPWG <cpwg at icann.org <mailto:cpwg at icann.org>>
>>         *Subject: *[CPWG] About Single Subject Meetings
>>
>>          
>>
>>         I have noticed that, more and more, we are having CPWG single
>>         subject meetings in addition to the weekly CPWG meetings. 
>>
>>          
>>
>>         It is my strong impression that this is causing "meeting
>>         fatigue". As a result, we may start to see a drop in
>>         participation and hence its effectiveness.
>>
>>          
>>
>>         I recommend that instead of having additional meetings, use
>>         the CPWG weekly meetings and convert them into CPWG single
>>         issue meetings when necessary.
>>
>>          
>>
>>         -ed
>>
>>          
>>
>>          
>>
>>         -- 
>>
>>         *NOTICE:* This email may contain information which is
>>         confidential and/or subject to legal privilege, and is
>>         intended for the use of the named addressee only. If you are
>>         not the intended recipient, you must not use, disclose or
>>         copy any part of this email. If you have received this email
>>         by mistake, please notify the sender and delete this message
>>         immediately.
>>
>>
>>
>>     -- 
>>     *NOTICE:* This email may contain information which is
>>     confidential and/or subject to legal privilege, and is intended
>>     for the use of the named addressee only. If you are not the
>>     intended recipient, you must not use, disclose or copy any part
>>     of this email. If you have received this email by mistake, please
>>     notify the sender and delete this message immediately.
>>
>>
>>
>> -- 
>> *NOTICE:* This email may contain information which is confidential
>> and/or subject to legal privilege, and is intended for the use of the
>> named addressee only. If you are not the intended recipient, you must
>> not use, disclose or copy any part of this email. If you have
>> received this email by mistake, please notify the sender and delete
>> this message immediately.
>> _______________________________________________
>> CPWG mailing list
>> CPWG at icann.org <mailto:CPWG at icann.org>
>> https://mm.icann.org/mailman/listinfo/cpwg
>>
>> _______________________________________________
>> 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) and the website Terms of
>> Service (https://www.icann.org/privacy/tos). 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.
>
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> 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) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.

-- 
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cpwg/attachments/20200522/e63f00e4/attachment-0001.html>


More information about the CPWG mailing list