Re: [802SEC] Opening Plenary Meeting Changes and New Member Introduction Meeting reminder

["Rigsbee, Everett O" <everett.o.rigsbee@BOEING.COM>]

Pat,  It is one thing to say that we are thinking about making some changes.  It's another to go ahead and make them without telling people what is going to happen and giving them a chance to provide feedback before it happens.  We have no basis on which to judge that our customers will think these changes are an improvement.  They may just decide the Opening Plenary is just another meeting to be avoided.  I know how much we (SEC) hate it when the IEEE decides to make changes without asking us first if that is an improvement or not.  Don't you think our attendees deserve the same respect ???  

Thanx,  Buzz
Dr. Everett O. (Buzz) Rigsbee
Boeing IT - SSG
PO Box 3707, M/S: 7M-FM
Seattle, WA  98124-2207
(425) 865-2443    Fx: (425) 865-6721
Cell: (425) 417-1022
everett.o.rigsbee@boeing.com



-----Original Message-----
From: Pat Thaler [mailto:pthaler@BROADCOM.COM] 
Sent: Monday, February 13, 2006 10:37 AM
To: STDS-802-SEC@listserv.ieee.org
Subject: Re: [802SEC] Opening Plenary Meeting Changes and New Member Introduction Meeting reminder


Buzz,

Actually, I think that Paul did inform people at the last opening plenary that changes were being planned for the format. I don't think a test run in a tutorial slot would get adequate attendance to be a successful test. By evening, people have other things to do - they will make time for a technical tutorial but very few have been willing to skip dinner and human networking time for process discussions lately. 

Regards,
Pat

-----Original Message-----
From: Rigsbee, Everett O [mailto:everett.o.rigsbee@BOEING.COM] 
Sent: Friday, February 10, 2006 11:43 AM
To: STDS-802-SEC@listserv.ieee.org
Subject: Re: [802SEC] Opening Plenary Meeting Changes and New Member Introduction Meeting reminder

Hi Bob,  I'm not at all concerned that we can't create a viable alternative process if it is warranted.  I am just concerned that we try doing it this time without fair warning, so that we have folks showing up expecting the same-old Plan A and instead they get subjected to Plan B.  I see no reason why we can't try out the "new & improved" format in a tutorial slot and have an extra half hour to take comments and suggestions on what (from our attendees point of view) is goodness and what is unnecessary or of limited value/appeal.  I just think it is better to ask our customers up front if it is broken and how they would prefer we go about fixing it.  It OK to have a straw-horse for the alternative but let's not presume to know what our customers really want.  Maybe they'd prefer to kill the entire Opening Plenary and go straight to the WG sessions, or maybe they'd like something we haven't even thought of yet.  

Maybe for most of our guys, "It's not broke, so don't go trying to fix
it !!!"   Quien sabe !!!     :-)   

Thanx,  Buzz
Dr. Everett O. (Buzz) Rigsbee
Boeing IT - SSG
PO Box 3707, M/S: 7M-FM
Seattle, WA  98124-2207
(425) 865-2443    Fx: (425) 865-6721
Cell: (425) 417-1022
everett.o.rigsbee@boeing.com



-----Original Message-----
From: Grow, Bob [mailto:bob.grow@INTEL.COM]
Sent: Thursday, February 09, 2006 6:47 PM
To: STDS-802-SEC@listserv.ieee.org
Subject: Re: [802SEC] Opening Plenary Meeting Changes and New Member Introduction Meeting reminder


Paul:

I agree with the intent of the change, I think Buzz's desire to know what will be worked on would be met with comprehensive slides on major benchmarks expected to be addressed during the plenary week.  To me, these are:

SG status
    Proposed new study items (aka CFIs)
    Planned transfer of WG to EC or another WG
    Age of SG
    Termination of SG
PAR actions (new, modified, extension and withdrawl)
Project status
    Current status (stage of draft development, current draft, ballot
status)
    Schedule for next major benchmark (down select, WG ballot, Sponsor ballot, RevCom submittal) Any actions on Std, RP, Guide
    Reaffirmation (plan, success/failure)
    Withdrawl (administrative/ballot)   
Change of WG/TAG status (hibernation, reactiviation)

The opening report describes what is expected to be covered and the closing report covers what actually was accomplished.

I would facitously observe in contradiction to Buzz that if someone can't find my slide set with notice (we could include a paragraph in the registration receipt as well as prior notice via reflectors) and with the www.ieee802.org URL presented at the opening plenary with explanation of detail available via that URL, then I'm not sure they have passed the IQ test for someone I want participating in my WG. ;-)

I may choose to also include some of the fluff that Mike objects to in my opening slide set where it doesn't burn (minutes X ~600 plenary
attendees) of resource, but I would make a similar IQ test observation that given a pointer to the 802.3 web page if I posted the fluff boilerplate and they can't find it ...  We certainly haven't failed to meet the requirements for openness.

--Bob

--Bob

-----Original Message-----
From: Paul Nikolich [mailto:paul.nikolich@ATT.NET] 
Sent: Thursday, February 09, 2006 8:12 AM
To: STDS-802-SEC@listserv.ieee.org
Subject: [802SEC] Opening Plenary Meeting Changes and New Member Introduction Meeting reminder

Dear EC members,

I will organize and run the opening plenary meeting differently in March than we have had in the past.  

I will not have each WG/TAG chair present their status update slides. Rather, you must send them to me and Bob O'Hara 1 week prior to the opening plenary meeting (27 Feb), whereupon Bob will put your slide decks on the website for participants to review.

My goal is to make the opening plenary meeting more informative and interactive.  The meeting will be organized as follows: 
- opening remarks (by me and EC members as appropriate) 15min, 
- Q&A with entire EC 15min, 
- presentation by someone from Staff or EC on a specific topic (this time by Michael Lindsay) 15min,
- Q&A on the presentation 15min,
- closing remarks 1min.

I would like you to send me any major items you believe are deserve special mention during the opening remarks.

A more detailed draft agenda I have in my mind at the moment follows. Suggestions on improvements are welcome.

1) Opening Remarks: 15 minutes
The unusual boilerplate stuff--Financial Report, Patent Policy, Membership Policy, general announcements (election notice, tutorials, new 
PARs, any major items EC members would like me to highlight, etc.) (Nikolich, Sherman, Thaler, Rigsbee, Hawkins, O'Hara)

2) Q&A with EC members (Nikolich moderates): 15 minutes

3) presentation: 15 minutes
Michael Linday (SA attorney) The dos and don'ts of IEEE SA 802 
Standards Development
a)  imperative principles: due process, openness, consensus, balance, 
right of appeal
b) code of ethics: safety, avoid conflict of interest, honesty, reject 
bribery, technical focus by qualified experts, be open to and provide honest 
criticism, fair treatment for all, avoid injuring others reputations, assist 
colleagues in professional development
c) intellectual property: essential IP and LOA; copyright policy, trademark 
usage
d) indemnification policy

4) Q&A based on presentation: 14 minutes (Nikolich moderates) 
I will also announce the location/time for further discussion on this topic if there is sufficient interest.  If we have an empty tutorial slot we'll put 
it there.

5) Closing remarks, notices: 1 minute. (Nikolich)

Hopefully this will make for a much more valuable utilization of the time we get to address the entire 802 assembly in one room.

Also, please remember that Pat Thaler is organizing a 'new member introduction' meeting to be held Monday morning--please let your groups know about this new feature.  Pat--please send a note to the EC reflector with the topics you plan to have covered during this meeting. Pat will have a Vice Chair present (David Law has volunteered this time) and it will be good to have a representative from each WG/TAG present to help field questions specific to that group--so please ask your group if a knowledgable member would be willing and available to participate in this meeting.

Regards,

--Paul

----------
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.

----------
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.

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