[Internal-cg] Primitive notes on scheduling meetings
mnuduma
mnuduma at yahoo.com
Fri Jul 18 15:19:19 UTC 2014
+1
CG may wish to consider running a 1hour workshop at IGF on day 0. In that case, we schedule our Sept meeting a day before IGF, plus IGF day 0.
Mary Uduma
Sent from Samsung tablet
-------- Original message --------
From: Adiel Akplogan <adiel at afrinic.net>
Date: 18/07/2014 15:52 (GMT+00:00)
To: Alissa Cooper <alissa at cooperw.in>
Cc: internal-cg at icann.org
Subject: Re: [Internal-cg] Primitive notes on scheduling meetings
I’m supportive of a monthly teleconference, 2 more f2f meeting this year (2014) and 2 in 2015. I will rather go for IGF and ICANN as potential venues for these meetings in 2014 for two reasons:
1. They both gather a broder participation than say RIR or IETF meetings.
2. They both officially run for less than 5 days so we can be away for less if we add additional day for our own meetings.
- a.
On Jul 18, 2014, at 18:45 PM, Alissa Cooper <alissa at cooperw.in> wrote:
> I’m assuming all the calls will be translated, so I hope so.
>
> Alissa
>
> On 7/18/14, 3:39 PM, "joseph alhadeff" <joseph.alhadeff at oracle.com> wrote:
>
>> If we have something like a .5 day meeting would it warrant all the overhead of translation etc? Is there such a thing as an informal meeting?
>>
>> Joe
>> On 7/18/2014 10:34 AM, Alissa Cooper wrote:
>>> Couple of thoughts:
>>>
>>> I think we can meet for less than two days in the future. Like 1.5, 1, or .5 days, depending on where we are in the process. For example, I think it would be useful to meet at IGF, but given that there are only six weeks between now and then and some people might be on holiday in August, a shorter meeting with a narrow focus on specific action items I don’t think we should always assume 2 days.
>>>
>>> I think we should plan the f2f meetings for the rest of this calendar year, but perhaps not further than that to give us some flexibility to figure out if we need to keep meeting f2f.
>>>
>>> If we want to have two more f2f meetings this year, I think a short one coincident with the IGF and a longer one coincident with the IETF are appropriately spaced for that. If we want to have one, I think a longer one coincident with ICANN51 (or the IETF, but that might be less convenient) would be appropriate time-wise.
>>>
>>> I think we should find a slot (or maybe two alternating slots to share the time zone pain) for a bi-weekly 1-hour conference call and reserve that slot starting two weeks from now and going for the duration of our work together. We can always cancel any particular week if we don’t need a call, but at least we’ll have them slotted in our calendars if we need them.
>>>
>>> Alissa
>>>
>>> On 7/18/14, 3:11 PM, "Wu Kuo-Wei" <kuoweiwu at gmail.com> wrote:
>>>
>>>> The regular ICANN meeting finish on Thursday. So we can have CG meeting from Friday and Saturday.
>>>>
>>>> :-)
>>>>
>>>> Kuo Wu
>>>>
>>>> Wu Kuo-Wei <kuoweiwu at gmail.com> 於 2014/7/18 22:09 寫道：
>>>>
>>>>> Patrik,
>>>>>
>>>>> Well, after the meeting. I am free for two days.
>>>>>
>>>>> :-)
>>>>>
>>>>> Kuo Wu
>>>>>
>>>>> Patrik Fältström <paf at frobbit.se> 於 2014/7/18 21:56 寫道：
>>>>>
>>>>>> Question from me to you Kuo-Wei is whether you can free two days of ICANN meeting in LA for CG work? As chair of SSAC I say that would be difficult if not the CG meeting is adjacent to already scheduled meetings. Not during the meeting.
>>>>>>
>>>>>> Patrik
>>>>>>
>>>>>> On 18 jul 2014, at 15:42, Wu Kuo-Wei <kuoweiwu at gmail.com> wrote:
>>>>>>
>>>>>>> Here is the data for us to recognize (but not necessary condition). There are 24 people joining ICANN meeting regularly, and 7~8 joining IETF meeting. So my comment will be: (please see the following)
>>>>>>>
>>>>>>> WUKnoben <wolf-ulrich.knoben at t-online.de> 於 2014/7/18 21:26 寫道：
>>>>>>>
>>>>>>>> see my comments in red
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Best regards
>>>>>>>>
>>>>>>>> Wolf-Ulrich
>>>>>>>>
>>>>>>>>
>>>>>>>> From: Milton L Mueller
>>>>>>>> Sent: Friday, July 18, 2014 1:42 PM
>>>>>>>> To: internal-cg at icann.org
>>>>>>>> Subject: [Internal-cg] Primitive notes on scheduling meetings
>>>>>>>>
>>>>>>>> Colleagues:
>>>>>>>> Refer to this message as the framework for our discussion of meetings.
>>>>>>>> Also refer to Russ’s “Timeline Discussion” document, as meetings need to be coordinated with our deadlines and expectations of milestones.
>>>>>>>>
>>>>>>>> 3 types of meetings:
>>>>>>>> - Face to face (F2F)
>>>>>>>> - Conference calls
>>>>>>>> - Email List traffic
>>>>>>>>
>>>>>>>> Proposal:
>>>>>>>> 1. Rely on list traffic remainder of July & August: fix 1 call for end of August
>>>>>>>> - charter and call for proposals should be finalized via email and list
>>>>>>>
>>>>>>> Open
>>>>>>>
>>>>>>>>
>>>>>>>> 2. Decision: Next f2f: Istanbul IGF or ICANN LA? or Both? or in connection with any IETF meeting?
>>>>>>>
>>>>>>> ICANN LA meeting.
>>>>>>>
>>>>>>>>
>>>>>>>> F2F - Istanbul IGF Sept X - to publicize and promote work of the CG
>>>>>>>> CG could make a presentation to a plenary session
>>>>>>>>
>>>>>>>> Or, F2F in ICANN meeting in LA
>>>>>>>>
>>>>>>>> Or, F2F in September (IGF) and October (ICANN)
>>>>>>>>
>>>>>>>> 3. Conf calls November, December, January, February: set calls in advance for at least every 4 weeks also beyond Feb 15
>>>>>>>
>>>>>>> Open
>>>>>>>
>>>>>>>>
>>>>>>>> 4. Receipt of proposals by beginning of March 2015?
>>>>>>>>
>>>>>>>> F2F in Dallas, TX near or during IETF 92, Mar 22-27
>>>>>>>> Or, F2F in APNIC 39 in Japan 24 Feb - 6 March 2015
>>>>>>>
>>>>>>> Prefer APNIC 39 in Japan
>>>>>>>
>>>>>>>>
>>>>>>>> 5. Conf call in April
>>>>>>>
>>>>>>> Open
>>>>>>>
>>>>>>>>
>>>>>>>> 6. F2F in May 2015 at a location TBA
>>>>>>>
>>>>>>> ICANN 52 Marrekech meeting?
>>>>>>>
>>>>>>>>
>>>>>>>> 7. Conf calls in June, July
>>>>>>>>
>>>>>>>> 8. Reminders + action lists for every call/meeting
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Internal-cg mailing list
>>>>>>>> Internal-cg at icann.org
>>>>>>>> https://mm.icann.org/mailman/listinfo/internal-cg
>>>>>>>> _______________________________________________
>>>>>>>> Internal-cg mailing list
>>>>>>>> Internal-cg at icann.org
>>>>>>>> https://mm.icann.org/mailman/listinfo/internal-cg
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Internal-cg mailing list
>>>>>>> Internal-cg at icann.org
>>>>>>> https://mm.icann.org/mailman/listinfo/internal-cg
>>>>>
>>>>
>>>> _______________________________________________ Internal-cg mailing list Internal-cg at icann.org https://mm.icann.org/mailman/listinfo/internal-cg
>>>
>>>
>>> _______________________________________________
>>> Internal-cg mailing list
>>>
>>> Internal-cg at icann.orghttps://mm.icann.org/mailman/listinfo/internal-cg
>>
>> _______________________________________________ Internal-cg mailing list Internal-cg at icann.org https://mm.icann.org/mailman/listinfo/internal-cg
> _______________________________________________
> Internal-cg mailing list
> Internal-cg at icann.org
> https://mm.icann.org/mailman/listinfo/internal-cg
_______________________________________________
Internal-cg mailing list
Internal-cg at icann.org
https://mm.icann.org/mailman/listinfo/internal-cg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/internal-cg/attachments/20140718/cc9823a0/attachment.html>
More information about the Internal-cg
mailing list