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

Re: [802SEC] Consent agenda guideline



See responses below

On Wed, Jun 8, 2016 at 8:16 AM, John D'Ambrosia <jdambrosia@gmail.com> wrote:

Pat,

See comments below

 

John

 

From: owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org] On Behalf Of Pat Thaler
Sent: Tuesday, June 7, 2016 6:19 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: [802SEC] Consent agenda guideline

 

Here is the current text from the Chair's Guidelines:

 

The following should be considered for inclusion on the consent agenda upon request:

1) First renewal of a Study Group (either ECSG or WGSG)

2) Public statements (e.g., press releases, responses to regulatory bodies, liaison statements, etc.) that have been announced to the EC email reflector made available to the EC members 24 hours in advance of the start of the meeting.

 

JD> it is not uncommon for PRs to get sent to the reflector and then subsequent modifications.  Are you referring to the final version of the PR after comments / modifications have been made, and not the initial PR that gets sent to the reflector for comment?


[pat] "I" wasn't referring to anything.  That is the existing text in the Chair's guidelines. I expect the 24 hours requirement is for the version of the statement that is on the consent agenda (which will be the final if it stays on the consent agenda).

 

3) Presentation of the Tutorial schedule at the opening meeting, only if all presentations have been given to the Recording Secretary according to the guidelines.

4) Other pro-forma information items

5) Meeting minutes from previous meetings if they have been announced to the EC email reflector and distributed 1 week in advance.

 

 

JD> I am assuming this is 1 week in advance of the meeting where it would get considered.  I would like to reduce the 1 week in advance to 72 hours prior to the , which is the Friday before the Opening Meeting on Monay. Or Tuesday if considered on the Friday Closing.


[pat] There are approximately 4 months to prepare the meeting minutes and a month to prepare the teleconference minutes. There are 119 pages of minutes from the March meeting plus whatever will be generated for the June Teleconference (February's teleconference minutes were 14 pages). It would be an excessive burden to review the minutes in 72 hours during the meeting week (and those traveling to the meeting may traveling on Friday giving them even less time.)  The minutes should be available a week before the plenary week so we can review them before getting on the plane. 

 

As currently written it has deadlines for some items but not all. And each item with a deadline has a different deadline. 

Since meeting minutes are often lengthy and should be available well before the meeting, it makes sense for them to have a deadline well before the meeting. "1 week in advance" is a bit vague. I assume 1 week before the opening plenary was intended, not 1 week before the time the consent agenda is to be approved.

 

The deadline of 24 hours in advance that was mentioned on the call appears in 2) which applies to public statements.

 

Items regarding progression of drafts aren't covered by any of the categories. We approved such items on the consent agenda for the call. Since the language above only says "should be considered" and doesn't prohibit other items. 

 

Looking back at minutes from 2015 through now, I can't find any other cases where we had draft progression motions on the consent agenda. 

 

 

So, the first question is, are draft progression motions appropriate for the consent agenda?

I tend to think they are. These motions are often approved with little or no discussion/debate. Where there is a question or controversy, they can always be pulled off the agenda. 

 

Comments?

 

JD> I agree that default should be to start with consent agenda, and people can request to pull if they so desire.

 

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