Geoff, I do not believe any bad precedent is being set. If a topic is deemed to be newsworthy, then I will be supportive of a press release. I can also speak with my alliance hat on – the two organizations are separate – and I do not believe we can move forward with the precedent of “leave the other stuff to our alliance colleagues.” What happens if such an organization chooses not to do a press release? There is no co-ordination between the different groups – though I can say I have seen efforts to extend professional courtesies and be informative. Furthermore, how any alliance chooses to act is not the interest of this group, but the interest of its membership. I will continue to be supportive of PRs for newsworthy items. I can say from the questions I saw to the webinar I gave on this topic the week of the interim meeting that there is interest in this topic. Regards, John D’Ambrosia From: owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org] On Behalf Of Geoff Thompson
Sent: Thursday, May 28, 2015 6:21 PM
To: Law, David; STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] +++ 10-day EC Email Ballot +++ IEEE P802.3bz 2.5/5GBASE-T project update press release I was the one who spoke to David against this release. Although my stance has softened after discussion, I still think we ought to have some criteria for 802 press releases and that we should not do one whenever a project group leader thinks he has done something significant. In that vein, this sets a bad precedent. I believe that 802 Press Releases should be limited to 802 level events like PAR approval, approval and/or publication of the standard (and maybe even going to Sponsor Ballot). I would prefer to leave the other stuff to our alliance colleagues. On Thursday, May 28, 2015 2:52 PM, "Law, David" <dlaw@HP.COM> wrote: All,
I would like to now proceed to the EC electronic ballot on the attached updated draft IEEE P802.3bz 2.5/5GBASE-T project update press release I circulated on Friday 22nd May for comment. I've also attached a diff to the draft I circulated then, my thanks to those that provided comments. The most significant change is the addition of a quote from Adrian Stephens.
One of the comments I received during the draft review was that it is unusual for us to issue a press release at a step other that a process step (PAR approval, Working Group ballot, etc.). In this particular case I believe it is justified based on the substantial interest in this activity from industry, and the activity making significant progress, as well as one of the primary application of this IEEE 802.3 project the support of IEEE 802.11, providing the opportunity to demonstrate cross IEEE 802 collaboration.
Paul has delegated the conduct of the EC electronic ballot on the following motion to me. To ensure this release is issued as soon as practical I'm announcing the possibility of an 'early close' to this ballot (see below).
Best regards,
David
Motion
======
The EC supports the IEEE P802.3bz 2.5/5GBASE-T project update press release, to be released with editorial changes as deemed necessary.
Move: David Law
Second: John D'Ambrosia
Start of ballot: Friday 29th May
Close of ballot: Sunday 7th June, 11:59PM AOE
Early close: As required in subclause 4.1.2 'Voting rules' of the IEEE 802 LAN/MAN Standards Committee (LMSC) Operations Manual, this is notice that, to ensure the release is provided in a timely manner, this ballot may close early once sufficient responses are received to clearly decide a matter.
Sufficient responses to clearly decide this matter will be based on the required majority for a motion under subclause 7.1.1 'Actions requiring approval by a majority vote' item (h), 'Other motions brought to the floor by members (when deemed in order by the Sponsor Chair)' of the IEEE 802 LAN/MAN Standards Committee (LMSC) Policies and Procedures.
----------
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. |