Steve, et al,
As you’ve seen on the 802.11be calls, WebEx can capture the list of all those who voted (and whether it is a straw poll or a motion is just a matter of how it is presented on the screen/written in the poll text). And, we’re using a convention of putting “[V}” at the start of our name, for those who claim they are a voting member (not required, but highly useful) of putting everyone’s voting status in their name (as you all can see on the EC now, for those of us who have participated in 802.11be and haven’t changed our names back again). This allows the vote to be confirmed (after the fact) to ensure that only voting members did in fact participate – or “cleanup” the results to show only voting members counts.
Assuming the motion vote isn’t particularly close, and the results are not critical in real-time, it seems adequate to sort these details out after the call.
Mark
From: ***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@LISTSERV.IEEE.ORG> On Behalf Of Steve Shellhammer
Sent: Tuesday, May 5, 2020 11:04 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] July 2020 IEEE 802 Executive Committee election process
Paul, et. al.,
Thanks. I was going to send an email out before the call, but someone called me and took up that time.
I think if we are going to mandate virtual meetings and holding motions I think we need a tool to do real-time voting of voting members on calls.
* Webex/Zoom both provide tools for doing straw polls of everyone on the call
* ePoll allow for offline voting of voting members, but no real-time
However, none of these provide the ability to do real-time voting of voting members. I believe we would need such a tool to hold those virtual meetings.
Regards,
Steve
From: Paul Nikolich <paul.nikolich@att.net <mailto:paul.nikolich@att.net> >
Sent: Tuesday, May 5, 2020 6:53 AM
To: Steve Shellhammer <sshellha@qti.qualcomm.com <mailto:sshellha@qti.qualcomm.com> >; STDS-802-SEC@LISTSERV.IEEE.ORG <mailto:STDS-802-SEC@LISTSERV.IEEE.ORG>
Subject: Re[2]: [802SEC] July 2020 IEEE 802 Executive Committee election process
CAUTION: This email originated from outside of the organization.
Steve,
We'll address that question today during the EC call.
Regards,
--Paul
------ Original Message ------
From: "Steve Shellhammer" <sshellha@qti.qualcomm.com <mailto:sshellha@qti.qualcomm.com> >
To: "Paul Nikolich" <paul.nikolich@att.net <mailto:paul.nikolich@att.net> >; "STDS-802-SEC@LISTSERV.IEEE.ORG <mailto:STDS-802-SEC@LISTSERV.IEEE.ORG> " <STDS-802-SEC@listserv.ieee.org <mailto:STDS-802-SEC@listserv.ieee.org> >
Sent: 5/4/2020 4:34:00 PM
Subject: RE: [802SEC] July 2020 IEEE 802 Executive Committee election process
Paul,
For WG that do not plan to meet that week, I assume a 10-day electronic ballot will work. Correct?
Regards,
Steve
From: ***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@LISTSERV.IEEE.ORG <mailto:STDS-802-SEC@LISTSERV.IEEE.ORG> > On Behalf Of Paul Nikolich
Sent: Monday, May 4, 2020 12:01 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG <mailto:STDS-802-SEC@LISTSERV.IEEE.ORG>
Subject: [802SEC] July 2020 IEEE 802 Executive Committee election process
CAUTION: This email originated from outside of the organization.
Dear EC Members,
Following Roger's recommendation http://ieee802.org/secmail/msg24597.html, I support conducting the July 2020 Plenary Session by electronic means given the exceptional case we cancelled the July 2020 plenary venue.
Assuming we adopt Roger's proposal (or something similar), it is my intention to follow the 802 Executive Committee election process I outlined for the cancelled March 2020 Plenary Session (see below -- except replace "March" with "July") at the July 2020 Plenary Session electronic meetings. I expect the WG/TAG officer election process to be conducted during the WG/TAG electronic meetings held at the July 2020 Plenary Session.
I reserved 20 minutes for discussion of this as agenda item 4.04 at tomorrow's 05 May 2020 IEEE 802 EC web conference. Speak to you tomorrow.
Regards,
--Paul
------ Forwarded Message ------
From: "Paul Nikolich" <paul.nikolich@att.net <mailto:paul.nikolich@att.net> >
To: "STDS-802-SEC@listserv.ieee.org <mailto:STDS-802-SEC@listserv.ieee.org> " <STDS-802-SEC@listserv.ieee.org <mailto:STDS-802-SEC@listserv.ieee.org> >
Sent: 1/30/2020 4:57:32 PM
Subject: Notice of March 2020 IEEE 802 Executive Committee election process
Dear EC members,
Details for the March 2020 IEEE 802 Executive Committee election process is available at https://mentor.ieee.org/802-ec/dcn/20/ec-20-0022-00-00EC-notice-of-march-2020-election-process.pdf. Please circulate this notice to your WG members by 03 February so they have ample time to consider it before the March session.
Per the LMSC P&P sections 3.1 and 4.0 all 802 executive committee members are elected or appointed and confirmed at the first Plenary session of each even numbered year. Therefore election/appointments are scheduled to occur at the upcoming March 2020 Plenary session.
I will stand for re-election as Chair of 802. If I am re-elected, I plan to fill the 802 Appointed Officer positions as follows: first Vice Chair-James Gilb, second Vice-Chair-Roger Marks, Recording Secretary-John D’Ambrosia, Executive Secretary-Jon Rosdahl and Treasurer-George Zimmerman. I also plan to appoint the following individuals to fill the non-voting positions of 802 Member Emeritus Treasurer Advisor-Clint Chaplin, 802 Member Emeritus-Advisor-Geoff Thompson and Hibernating Working Group Chairs: 802.16 Chair-Roger Marks, 802.21 Subir Das, 802.22 Apurva Mody and 802 Ombudsman-Guido Hiertz. All the appointees have agreed to accept the appointments and wish to be confirmed.
If you, or others in you WGs, wish to be considered for the 802 Chair or the appointed positions, please contact me and the Recording Secretary as soon as possible.
All potential EC members--please remember to submit your letter of endorsement and disclosure of affiliation to John D’Ambrosia as soon as possible, but not later than the March 2020 opening EC meeting.
Finally, please carefully review the Disclosure of Affiliation FAQ (standards.ieee.org/faqs/affiliation.html) and the IEEE Standards Board Bylaws, 5.2.1.5 Disclosure of Affiliation* (standards.ieee.org/about/policies/bylaws/sect5.html) to ensure all candidates for 802 leadership positions fully understand this requirement and are in compliance with the policy.
Regards,
Paul Nikolich
Chair, IEEE 802 LAN/MAN Standards Committee
* Please ensure all candidates comply with the IEEE SA 5.2.1.5 Disclosure of affiliation policy:
Every participant in a working group, Standards Association ballot, or other standards development activity shall disclose his or her affiliation(s), which includes employer(s) and any other affiliation(s). An individual is deemed "affiliated" with any individual or entity that has been, or will be, financially or materially supporting that individual's participation in a particular IEEE standards activity. This includes, but is not limited to, his or her employer(s) and any individual or entity that has or will have, either directly or indirectly, requested, paid for, or otherwise sponsored his or her participation. Failure to disclose every such affiliation(s) may result in complete or partial loss of rights to participate in IEEE SA activities. An individual is not excused from compliance with this policy by reason of any claim of a conflicting obligation (whether contractual or otherwise) that prohibits disclosure of affiliation(s).
A person who believes that a participant's disclosure is materially incomplete or incorrect should report that fact to the appropriate Standards Committee(s).
_____
To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC <https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1> &A=1
_____
To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC <https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1> &A=1
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.