From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atlmailgw1.ami.com (atlmailgw1.ami.com [63.147.10.40]) by mx.groups.io with SMTP id smtpd.web11.7776.1581694182259823979 for ; Fri, 14 Feb 2020 07:29:42 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: ami.com, ip: 63.147.10.40, mailfrom: felixp@ami.com) X-AuditID: ac1060b2-111ff70000001a2a-d9-5e46bce469ec Received: from atlms2.us.megatrends.com (atlms2.us.megatrends.com [172.16.96.152]) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by atlmailgw1.ami.com (Symantec Messaging Gateway) with SMTP id 23.87.06698.5ECB64E5; Fri, 14 Feb 2020 10:29:41 -0500 (EST) Received: from ATLMS1.us.megatrends.com ([fe80::8c55:daf0:ef05:5605]) by atlms2.us.megatrends.com ([fe80::29dc:a91e:ea0c:cdeb%12]) with mapi id 14.03.0468.000; Fri, 14 Feb 2020 10:29:39 -0500 From: "Felix Polyudov" To: "rfc@edk2.groups.io" , "'leif@nuviainc.com'" , "devel@edk2.groups.io" Subject: Re: [edk2-rfc] [RFC] code-first process for UEFI-forum specifications Thread-Topic: [edk2-rfc] [RFC] code-first process for UEFI-forum specifications Thread-Index: AQHVz7Lo8xkkEE5sBEGhAv8gAPESIKga7vrQ Date: Fri, 14 Feb 2020 15:29:38 +0000 Message-ID: <9333E191E0D52B4999CE63A99BA663A003FFBE929A@atlms1.us.megatrends.com> References: <20200120165852.GU15141@bivouac.eciton.net> In-Reply-To: <20200120165852.GU15141@bivouac.eciton.net> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.99.93] MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpileLIzCtJLcpLzFFi42JZI5AwQ/fpHrc4g3sXJSzaJ8xms9jR8JTN 4uzjt0wOzB7bv19g9HjVP50lgCmqgdEmMS8vvySxJFUhJbU42VYpoCizLDG5UkkhM8VWyVBJ oSAnMTk1NzWvxFYpsaAgNS9FyY5LAQPYAJVl5imk5iXnp2TmpdsqeQb761pYmFrqGirZhWSk KmTmpeUX5SaWZObnKSTn55UAVaemAEUVEro5M46v1CtYxlVx9tsj5gbGRRxdjJwcEgImEl19 p1i7GLk4hAR2MUk8u/yNCcI5zCjRdPsLI0gVm4CqxPHVzSwgCRGBTkaJxU9ms4AkhAUCJKZN 62brYuQASgRKnN3mDBIWETCS6Nq4ghEkzALUe3hyOkiYF6jiZ8dZsJFCAuYSXzqWsYHYnAIW Ehc3rGIHsRkFxCS+n1rDBGIzC4hL3HoynwniUAGJJXvOM0PYohIvH/9jhbAVJLa872SHqNeR WLD7ExuErS2xbOFrZoi9ghInZz5hmcAoMgvJ2FlIWmYhaZmFpGUBI8sqRqHEkpzcxMyc9HJD vcTcTL3k/NxNjJAEsGkHY8tF80OMTByMhxglOJiVRHgPK7rFCfGmJFZWpRblxxeV5qQWH2J0 AobDRGYpblCcACM53tjAQEoUxjE0MTMxNzI3tDQxNzZWEuddueZbjJBAOjCxZKemFqQWwQxh 4uCUamCcEXXC/YF+5U+/7CWGa23DhIr2xX08uu5vdEnVzoin+/q+L+mTEnmbXCTiyJ116rTn 7uDF/gmv5scwnzlla7Au1fntr0fHS28pHgwyLL+41U7jYHHPrYYPt57UfVPxmPv0zoX5ywpv n/69teeFkrr83g12ypOnT8rTO20Tk23+vWhO6qpDvG2nlViKMxINtZiLihMB3htbVhUDAAA= Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Leif, >The process does not in fact change the UEFI bylaws - the change is that th= e >development (of both specification and code) happens in the open. The resul= ting >specification update is then submitted to the appropriate working goup as a= n >Engineering Change Request (ECR), and voted on. For the UEFI Forum, this is= a >change in workflow, not a change in process. I think it would be good to add more details regarding the interaction betwe= en edk2 and UEFI forum. 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 fo= rum. A sponsor has to be identified early in the process. Preferably along with B= uzilla 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 i= terations in the implement --> get feedback --> re-implement cycle. - edk2 effort will be taken into consideration while scheduling future speci= fication releases Please consider the environment before printing this email. The information contained in this message may be confidential and proprietar= y to American Megatrends (AMI). This communication is intended to be read o= nly 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 no= tice that any distribution of this message, in any form, is strictly prohibi= ted. Please promptly notify the sender by reply e-mail or by telephone at 7= 70-246-8600, and then delete or destroy all copies of the transmission.