From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by mx.groups.io with SMTP id smtpd.web12.6941.1583469146232159569 for ; Thu, 05 Mar 2020 20:32:26 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 192.55.52.151, mailfrom: soumya.k.guptha@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Mar 2020 20:32:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,520,1574150400"; d="scan'208,217";a="244508840" Received: from orsmsx102.amr.corp.intel.com ([10.22.225.129]) by orsmga006.jf.intel.com with ESMTP; 05 Mar 2020 20:32:25 -0800 Received: from orsmsx114.amr.corp.intel.com (10.22.240.10) by ORSMSX102.amr.corp.intel.com (10.22.225.129) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 5 Mar 2020 20:32:25 -0800 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.183]) by ORSMSX114.amr.corp.intel.com ([169.254.8.140]) with mapi id 14.03.0439.000; Thu, 5 Mar 2020 20:32:25 -0800 From: "Soumya Guptha" To: "announce@edk2.groups.io" , "devel@edk2.groups.io" Subject: TianoCore Community Meeting Minutes - March Thread-Topic: TianoCore Community Meeting Minutes - March Thread-Index: AdXzb++JMucHHBgFQy2EmpdvnKe1Xg== Date: Fri, 6 Mar 2020 04:32:24 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [10.22.254.138] MIME-Version: 1.0 Return-Path: soumya.k.guptha@intel.com Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B1D50B8C067F864C836E6827E538E343A1737E1BORSMSX113amrcor_" --_000_B1D50B8C067F864C836E6827E538E343A1737E1BORSMSX113amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable TianoCore Community Meeting Minutes March 5, 2020 Stable Tag Updates: 1. Edk2 stable tag 202002 has been released: https://github.com/tiano= core/edk2/releases/tag/edk2-stable202002 2. Edk2 stable tag 202005 feature planning has started. * Features are listed in: https://github.com/tianocore/tianocore.gith= ub.io/wiki/EDK-II-Release-Planning Community Action: Please send if any feature requests that needs to be adde= d to the upcoming stable tag release. Opens: 1. Sean requested a few features (variable policy, TLS 1.3 etc.) for s= table tag Q2 release. Sean will follow up with Liming on those features to = get them added to Q2 stable tag. 2. Kevin - Need a fix in EDK2. Insyde engineers don't know where to st= art. Documentation is stale or assumes that you understand the open source = project. * Action: We discussed this issue. Kevin to follow the link - https:= //github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process = , this should provide some guidance to the engineers on how to make a fix i= n EDK2. 3. Discussion around Bugzilla - Liming to explore adding more detailed= information on bugzilla wiki page TianoCore Bug Triage - APAC / NAMO Meeting time: * Scheduled currently from 9:00 ~ 9:30 AM PRC time. Even after the US= daylight saving during March, plan is to keep this meeting from 9:00~9:30A= M PRC time. This time is working well and close to TianoCore Design Meeting= , developers can plan their time and attend these two meetings together. Community consensus received on the timeslot. Events: SPRING 2020 UEFI PLUGFEST has been pos= tponed due to the Coronavirus situation. More details are published here - = https://uefi.org/events/upcoming Community issues that were brought up last month on the governance and the = process: 1. RFC: The RFC process seems to get only minimal comments and a lot = gets lost in the noise of the lists. There isn't a good "final" state wher= e all approved RFCs can be seen. The process is entirely driven by the sub= mitter and thus there is little consistency. I wanted to highlight anothe= r project and how they handle this. https://github.com/rust-lang/rfcs As a= casual observer it is very easy to review their RFCs (in flight and approv= ed/rejected) as well as understand how to create and submit one if so desir= ed. The tooling is just git/github so it is familiar to the target audienc= e and has a strong ability to track progress, show history, and be backed u= p like any code project. They also leverage github issue tracker for pre r= fc conversation and discussions. 2. Bugs/Features/Releases: First the bug triage and scrub is not ver= y well attended. I know it is hard to get a ww audience together on a call= but i think part of the goal was to offer a public process and a place to = learn/discuss. Is there a better way that still meets those goals? Second= ly, the number of bugs that get discussed is pretty small and the list of o= pen bugzillas are grower faster than the triage effort. Third, the results= are pretty minimal. Usually a change in owner and a very short comment as= king the owner to look at it is the result of the triage. There is sometim= es good conversation (assuming knowledgeable parties are in attendance) but= this is impractical to capture into the bugzilla while still keeping forwa= rd progress. Finally, as a submitter of a lot of open/unconfirmed bugs it i= s not very easy to understand the owners priorities and when the bug will b= e fixed and merged to master/stable tag. I am happy to contribute effort to= making a new process but want to understand if others are frustrated by th= is as well. Intel Response: We are evaluating the possibility of using git hub for the = code review process. Expect RFCs in the month of March. Regards, Soumya Soumya Guptha Open Source Program Manager, Intel Corporation --_000_B1D50B8C067F864C836E6827E538E343A1737E1BORSMSX113amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

TianoCore Community Meeting Minutes

March 5, 2020

 

Stable Tag Updates:

1.       Edk2 stable tag 202002 has been released: https://github.com/tianocore/edk2/releases/tag/edk2-stable202002

2.       Edk2 stable tag 202005 feature planning has started.

·     =   Features are listed in: https://github.com/tianocore/tianocore.github.io/wiki= /EDK-II-Release-Planning

Community Action:= Please send if any feature requests that needs to be added to the upcom= ing stable tag release.

Opens: <= /o:p>

1. &= nbsp;    Sean reques= ted a few features (variable policy, TLS 1.3 etc.) for stable tag Q2 releas= e. Sean will follow up with Liming on those features to get them added to Q= 2 stable tag.

 

2. &= nbsp;    Kevin ̵= 1; Need a fix in EDK2. Insyde engineers don’t know where to start. Do= cumentation is stale or assumes that you understand the open source project= .

·       Action: We = discussed this issue. Kevin to follow the link  - https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Pr= ocess , this should provide some guidance to the engineers on how to ma= ke a fix in EDK2.

 

3. &= nbsp;    Discussion = around Bugzilla - Liming to explore adding more detailed information on bug= zilla wiki page  

 

TianoCore Bu= g Triage - APAC / NAMO Meeting time:

·     =   Scheduled currently from 9:00 ~ 9:30 AM PRC time. Even afte= r the US daylight saving during March, plan is to keep this meeting from 9:= 00~9:30AM PRC time. This time is working well and close to TianoCore Design Meeting, developers can plan their time= and attend these two meetings together.

Community consens= us received on the timeslot.

 

Events:

<= span style=3D"font-size:10.5pt;font-family:"Arial",sans-serif;col= or:#EB2227;text-transform:uppercase;background:white">SPRING 2020 UEFI PLUG= FEST has been postpo= ned due to the Coronavirus situation. More details are published here - https://uefi.org/events/upcomi= ng

 

Community issues that were brought up last month on the governan= ce and the process:

1.&nbs= p;      RFC:= The RFC process seems to get only minimal comments and a lot gets lost in = the noise of the lists.  There isn't a good "final" state wh= ere all approved RFCs can be seen.  The process is entirely driven by the submitter and thus there is little consistency.&nbs= p;  I wanted to highlight another project and how they handle this.&nb= sp; https://github.com/r= ust-lang/rfcs As a casual observer it is very easy to review their RFCs (in flight an= d approved/rejected) as well as understand how to create and submit one if = so desired.  The tooling is just git/github so it is familiar to the t= arget audience and has a strong ability to track progress, show history, and be backed up like any code project.&n= bsp; They also leverage github issue tracker for pre rfc conversation and d= iscussions.     

2.&nbs= p;      Bugs= /Features/Releases:  First the bug triage and scrub is not very well a= ttended.  I know it is hard to get a ww audience together on a call bu= t i think part of the goal was to offer a public process and a place to learn/discuss.  Is there a better way that sti= ll meets those goals?  Secondly, the number of bugs that get discussed= is pretty small and the list of open bugzillas are grower faster than the = triage effort.  Third, the results are pretty minimal.  Usually a change in owner and a very short comment asking t= he owner to look at it is the result of the triage.  There is sometime= s good conversation (assuming knowledgeable parties are in attendance) but = this is impractical to capture into the bugzilla while still keeping forward progress. Finally, as a submitter of a lo= t of open/unconfirmed bugs it is not very easy to understand the owners pri= orities and when the bug will be fixed and merged to master/stable tag. I a= m happy to contribute effort to making a new process but want to understand if others are frustrated by this as w= ell.  

&= nbsp;

Intel Respons= e: We are evaluating the po= ssibility of using git hub for the code review process. Expect RFCs in the = month of March.

&nbs= p;

Regards,

Soumya

 

Soumya Guptha
Open Source Program Manager, Intel Corporation<= /span>

 

--_000_B1D50B8C067F864C836E6827E538E343A1737E1BORSMSX113amrcor_--