Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] Plenary organization



Colleagues-

An alternate suggestion to David's as put forth below.

I would suggest that We keep the Monday EC as it is for two reasons:
  - Many of our North American attendees travel on Monday morning.
    David's proposal (and that of others) would force (or at least
    heavily nudge) a much larger chunk of our rank and file to
    travel on the weekend. While this may seem like no big deal to
    those of use (a) who are officers and/or (b) come from overseas,
    it is significant to many new participants who have not yet
    committed themselves to working with us and, in particular,
    those who have young families. These are participants who
    will vote with their feet.

  - My experience over the last 25 years has shown that the quality
    of EC meetings is significantly handicapped by the late evening
    format. That time slot has, in my strong opinion, demonstrated
    a lower level of EC performance, diligence and collegiality.
    Thus I think it would be a bad idea for the EC to go to an
    evening time slot. (I say this in spite of my personal metabolism
    which gives me an early morning handicap.)

I would offer an alternate to get more meeting time. That would be to eliminate the Monday tutorials and have initial TF meetings on Monday evening. Tuesday evening would be tutorials and the Wednesday Social would remain.

I believe that this set-up would provide the following advantages:
  - Lowest burn-out factor for the largest number of people
- The evening TF day at the front of the week when folks are relatively fresh. - Lowest disturbance to room allocations/catering and thus to ou hotel contracts.
  - At least 3 hours of additional TF time.

I look forward to our discussions on this topic in Dallas.

Best regards,

Geoff Thompson

At 10:02 AM 10/20/2008 , David Law wrote:
>Hi Steve,
>
>What is proposed here would give the WGs approximately 1.5 hours extra
>daytime meeting time Monday - allowing the WG to start at 10:30AM - and
>two extra evenings - eliminate Tuesday tutorial and the Wednesday social -
>which is a start.
>
>I however still think we should consider [1] moving the Opening EC to
>Sunday evening to allow a full day of WG meetings Monday and/or [2] moving
>the closing EC to allow a half day of WG meetings Friday morning. Allowing
>WGs to meet Friday morning would also make Thursday evening available for
>WG meetings - and I would suggest that might be a better approach rather
>than eliminating the Tuesday tutorial or the social.
>
>I do realize that what I suggest places a greater burden on all-ready
>overworked EC members, but I believe we should do everything possible to
>allow the WGs the maximum time to do work.
>
>Best regards,
>  David
>
>***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@ieee.org>
>wrote on 18/10/2008 13:56:42:
>
> -----Original Message-----
> From: ***** IEEE 802 Executive Committee List ***** [mailto:
> STDS-802-SEC@ieee.org] On Behalf Of Shellhammer, Steve
> Sent: Friday, October 17, 2008 11:01 PM
> To: STDS-802-SEC@LISTSERV.IEEE.ORG
> Subject: Re: [802SEC] Plenary organization
>
> All,
>
>         I am NOT in favor of the following,
>
> 1.      Moving Monday EC meeting to Sunday
> 2.      Moving Friday meeting to Thursday night
>
>         However, I agree with some other ideas,
>
> 1.      Eliminate the 802 plenary and shorten the Monday EC meeting.
> Get everything done by 10 AM so the WG's can start by 10:30 AM.
>
> 2.      Eliminate the social.
>
> 3.      Go from one night for Tutorials.  Alternatively, make a
> deadline of 35 days before the meeting to commit to tutorials.  That
> way if we only have one night worth of tutorials we can give Tuesday
> to the WGs.  They would know 35 days in advance and could plan
> accordingly.  They could get their agendas out 30 days in advance.
>
> Regards,
> Steve

----------
This email is sent from the 802 Executive Committee email reflector.  This list is maintained by Listserv.