Re: [802SEC] Attendance Credit At LMSC WG Meetings
John,
This is a tough situation. It can be hard to monitor people fairly especially during periods when group size is high or when a group has multiple meetings in parallel. For many of us things have to be somewhat on the honor system. However, there are times when someone flaunts the attendence requirements so obviously that one has to take action.
My first course of action would be 1. It gives the person a chance to respond if he/she doesn't think the observation was accurate and it puts the person on notice to correct their behavior in the future. To delete the credit without telling the person could cause problems. It could appear underhanded. The person affected will find out later when they either lose voting rights or can't gain them. At that point they could validly complain that people's recollections have dimmed making it difficult to contest the action.
Unless we all start wearing those tracking ankle bracelets, it is hard to think of a system that would ensure attendance matched sign-ins without getting in the way of real work so 3 seems impractical. If the problem is people signing in at multiple working groups for the same time period, there was a discussion a while ago of comparing attendance sign-ins and having those with overlapping ones declare one group that they attended for the majority of the period. This would be clerically burdensome and would require more standardization in tracking time between the groups. It also doesn't help with those who may sign in and go someplace besides another meeting.
Many years ago when Don Loughry was chair of 802.3, person X made a practice of moving around the 802 meeting signing in as much as possible to maintain voting rights in a number of working groups. One day Don spotted X standing at the back table signing in, having grabbed the book as it went passed and looking ready to depart as soon as he passed it on. Don interrupted the meeting to ask X if having signed the book he was actually planning on attending some of the meeting. X looked abashed, said of course and sat down. X was a good deal more careful in the future to attend a reasonable part of the meeting rather than sign and dash. I don't know if Don had spoken to him privately at some earlier time or not. If someone continually tries to flaunt the system and private counseling doesn't work, there is nothing like catching them in the act. It also made the point to others that we intended to enforce the attendance rules.
Regards,
Pat
-----Original Message-----
From: owner-stds-802-sec@listserv.ieee.org
[mailto:owner-stds-802-sec@listserv.ieee.org]On Behalf Of John Lemon
Sent: Wednesday, 01 December, 2004 3:56 PM
To: STDS-802-SEC@listserv.ieee.org
Subject: [802SEC] Attendance Credit At LMSC WG Meetings
More experienced ones:
I'm seeking some advice on how to handle a claim of attendance at the most recent plenary meeting. One person managed to sign-in for 75% of the half-day sign-in slots for 802.17. However, said person was not actually in attendance for more than a few minutes for some of those periods.
What would you recommend we do in such a situation?
1. Strike the sign-ins for the periods when the person was in attendance for only a few minutes, and notify them of the action?
2. Strike the sign-ins for the periods when the person was in attendance for only a few minutes, without notifying them of the action?
3. Count this as a learning experience and institute tighter control on the sign-in booklet in the future?
4. Other?
If you chose 3, how would you recommend preventing this abuse in the future?
Tony, I came in to the 802.1 meeting for our joint 802.1/802.17 meeting just as you were finishing saying something about this to the 802.1 participants. I missed most of what you said. Could you repeat it here?
Thanks,
John Lemon
----------
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.