toggle quoted messageShow quoted text
I had, perhaps excessively, been waiting for more feedback.
I promised Mike yesterday that I will rework based on feedback and
send out next week at the latest. If people have no further comments
then, we can adopt the process and start using it.
On Wed, Mar 11, 2020 at 15:52:07 +0000, Samer El-Haj-Mahmoud wrote:
Has there been any progress on this "code-first process" proposal? Any timeline on when we should expect it to be launched?
From: email@example.com <firstname.lastname@example.org> On Behalf Of Felix Polyudov via Groups.Io
Sent: Friday, February 14, 2020 10:30 AM
To: email@example.com; 'leif@...' <leif@...>; firstname.lastname@example.org
Subject: Re: [edk2-devel] [edk2-rfc] [RFC] code-first process for UEFI-forum specifications
The process does not in fact change the UEFI bylaws - the change isI think it would be good to add more details regarding the interaction between edk2 and UEFI forum.
that the development (of both specification and code) happens in the
open. The resulting specification update is then submitted to the
appropriate working goup as an Engineering Change Request (ECR), and
voted on. For the UEFI Forum, this is a change in workflow, not a change in process.
Here is what I suggest:
Each specification update Bugzilla ticket must have a sponsor. A sponsor is a person or a company that will be presenting change request to the UEFI forum.
A sponsor has to be identified early in the process. Preferably along with Buzilla ticket creation.
It is sponsor's responsibility to officially submit ECR to the UEFI forum by creating a mantis ticket with a Bugzilla link.
There are two reasons to create mantis ticket early in the process:
- Creation of the ticket exposes the effort to the UEFI forum thus enabling early feedback from the members(via Bugzilla), which may reduce number of iterations in the
implement --> get feedback --> re-implement cycle.
- edk2 effort will be taken into consideration while scheduling future specification releases
Please consider the environment before printing this email.
The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.