| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Travel for a meeting starting on Monday often requires leaving on Sunday and sometimes on Saturday. I think that many would prefer to have one weekend impacted even if the
impact eats deeper into the weekend rather than having two weekends impacted. Therefore, it is better to move to start earlier having some meetings on Sunday rather than pushing Working Groups to meet on Friday morning.
Pat From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org]
On Behalf Of Jon Rosdahl Thanks John, I appreciate your input and candor. What if we asked the WG to not close their work until Friday? Would it make sense to have a 2 week meeting? I agree that there are lots of alternatives. Some like scrambled eggs while others like sunny side up or Benedict. It is the alternatives that we will discuss, and then decide to follow a plan until we deem it needing to change. And one of the alternatives is no change at all... Cheers,
----------------------------------------------------------------------------- On Fri, Oct 24, 2014 at 9:29 PM, <John_DAmbrosia@dell.com> wrote: Jon, I disagree – this is not fine and not in line with the action item. Personally – plenary weeks are very limited opportunities to get together with colleagues for general
consensus building. But these weeks are so filled that we need to help our members find additional time. Personally, I would throw out that the EC should consider meeting on Sunday in order to give a full
day to the members on Monday. Things are that bad in terms of opportunities for us all to meet. I think asking presenters to characterize their meetings is reasonable. They can describe it as
something that is general or technology specific. For example, as chair of 400G group, my tutorial would be very specific to wireline technologies. I really doubt the 802.11 crowd would care about the technical details of a tutorial. They might care about
the application uses. But as the tutorial creator – I would have a feeling for this. If a meeting were not deemed generic, Paul could decree that the meeting time is available for use. My $0.02 as someone having to deal with this issue. J From:
owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org]
On Behalf Of Jon Rosdahl It has been pointed out to me that there may be some that would like to respond directly to me rather than to the open group. Please send feedback/comments to
jrosdahl@ieee.org Always happy to help,
----------------------------------------------------------------------------- On Fri, Oct 24, 2014 at 1:21 PM, Jon Rosdahl <jrosdahl@ieee.org> wrote: Hello All, I have an action item to start the discussion on the reflector for how can we maximize the time we have allocated for Tutorials. Sometimes we have tutorials that some believe are not for the whole of 802. Sometimes we have tutorials that everyone believes that they are for the whole of 802. Sometimes we have tutorials that some believe are for only one WG. This has caused a bit of angst. Historically, we have had rules that said that during the Plenaries no WG meetings were to be held on Monday or Tuesday to allow for the Tutorials to
be held. Then we has a period where WGs could hold meeting regardless of the Tutorial schedule. Currently we have said that WGs should not hold meetings on Monday evenings, to clear the schedule for Tutorials, and that on Tuesday evenings if we have overflow Tutorials they can be
held in parallel with WG meetings. We all recognize that our time is short and very full. Some WG utilize more time from Monday to Friday than others. Each WG utilizes the amount of time to match what they believe their Members want. How to squeeze more time has lead to this discussion on when a WG could try to gain more time? Comments and suggestions? I will look for your input and try to summarize both sides for discussion in San Antonio. Jon ----------------------------------------------------------------------------- ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
|