From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mx.groups.io with SMTP id smtpd.web11.8598.1575605498671542960 for ; Thu, 05 Dec 2019 20:11:38 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 134.134.136.20, mailfrom: brian.richardson@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Dec 2019 20:11:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,282,1571727600"; d="scan'208,217";a="236901055" Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by fmsmga004.fm.intel.com with ESMTP; 05 Dec 2019 20:11:37 -0800 Received: from orsmsx115.amr.corp.intel.com (10.22.240.11) by ORSMSX103.amr.corp.intel.com (10.22.225.130) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 5 Dec 2019 20:11:37 -0800 Received: from orsmsx114.amr.corp.intel.com ([169.254.8.67]) by ORSMSX115.amr.corp.intel.com ([169.254.4.121]) with mapi id 14.03.0439.000; Thu, 5 Dec 2019 20:11:37 -0800 From: "Brian Richardson" To: "devel@edk2.groups.io" Subject: TianoCore Community Meeting Minutes 12/05/2019 Thread-Topic: TianoCore Community Meeting Minutes 12/05/2019 Thread-Index: AdWr6wUEsfHRv8/tSo6u3+NUndhczA== Date: Fri, 6 Dec 2019 04:11:37 +0000 Message-ID: <80AC2BAA3152784F98F581129E5CF5AFCAF9CD09@ORSMSX114.amr.corp.intel.com> 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.139] MIME-Version: 1.0 Return-Path: brian.richardson@intel.com Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_80AC2BAA3152784F98F581129E5CF5AFCAF9CD09ORSMSX114amrcor_" --_000_80AC2BAA3152784F98F581129E5CF5AFCAF9CD09ORSMSX114amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable (note: merged meeting minutes from both sessions) Topics: * Stable Tag * CI * FOSDEM * Groups.io issues w/ patches * 2020 Q1 Planning * HBFA & Unit Testing * Code First Stable Tag 201911 has been released. Thanks to everyone who contributed. Sm= all delay on release due to github administration issues, may need to creat= e another admin level for release engineers. CI data now displayed on main page for edk2 github repo. FOSDEM - Feb 1-2, 2020 in Brussels * Submissions to open source firmware track from Intel & Linaro * Acceptance notices should be sent on Dec 8 Groups.io issues w/ patches * Seeing issues with large patch sets (over 40 items). Mike Kinney i= nvestigating. This has been observed by multiple users, so it is likely a g= roups.io "feature". Gitconfig can batch large e-mail patch sets with delays= as a workaround. Red Hat will experiment on configuration. * Lazlo has seen inconsistencies with names used e-mail, which cause= s problems with commit history. Switching computers or environments can cau= se problems in gitconfig. Possible issues with Outlook/Exchange server (see= n with some e-mails sent from intel.com). * Goal is to update best practices for gitconfig, including Python h= elper script. * Change in domain should be considered a different author. Requires= additional review to make sure this is the same person. * Note: Issues this like have motivated the conversation for changin= g workflow from e-mail patches. Need to revisit new workflow & resolve in c= ommunity. 2020 Q1 Planning * Rush of patches ahead of soft freeze date. Need to be proactive fo= r each stable tag release & avoid this problem. * Developers should be focused on large/high-risk changes first, the= n move to lower priority/complexity issues. Reduces risk & thrash. * Metrics for bugs & features: size of patch set, algorithmic comple= xity, value with changes to critical code (even if changes are small, are r= isks justified versus benefits?). Measure as part of bug scrub, can push to= next stable tag if deadlines cannot be met. * Mike is investigating Bugzilla fields that can help manage this pr= ocess (existing or new additions). * Is there measurement criteria when moving code from edk2-staging t= o edk2 main repo? This is the responsibility of the staging branch owner. M= ay need to spell this out as part of the exit criteria when staging code is= elevated to master edk2 repo (testing APIs? How many platforms were used f= or validation?) * New protocols? Ok to add new EDK II APIs. If they impact UEFI spec= updates, that is related to the code first initiative (different discussio= n, see below). * How is security mapped to risk assessment? Need to make sure this = is covered. HBFA & Unit Testing * Brent @ Microsoft has sent a proposal to add HBFA to CI process fo= r unit testing (with examples). * Goal: Simplify process to add new unit tests & related APIs. Initi= al focus at library level. Module level has challenges in host environment = (mocked interfaces can be complicated, shouldn't be more complex than the a= ctual test). Infrastructure should take burden of complexity of test cases = (instead of developer). * Framework should support multiple frameworks under the test direct= ory. Staring with HBFA, but not assuming a single framework. * Stewards will review current proposal & provide feedback. Feedback= is encouraged from the community on the edk2 rfc list. Code First - still work in progress * Accessibility - Andrew @ Apple working on text-to-speech & related= audio protocols in emulator. * Leif @ Linaro still working on code first proposal. Will send to e= dk2 rfc list when ready. * Naming conventions will clearly identify pre-spec & post-spec work= . Brian will be on vacation on Jan 2, 2020 (next scheduled community meeting)= . Will find different meeting owner for that date. Thanks ... br --_000_80AC2BAA3152784F98F581129E5CF5AFCAF9CD09ORSMSX114amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

(note: merged meeting minutes from both sessions)

 

Topics:

·        Stable Tag

·        CI

·        FOSDEM

·        Groups.io issues w/ patches

·        2020 Q1 Planning

·        HBFA & Unit Testing

·        Code First

 

Stable Tag 201911 has been released. Thanks to everyone who contrib= uted. Small delay on release due to github administration issues, may need = to create another admin level for release engineers.

 

CI data now displayed on main page for edk2 github repo.=

 

FOSDEM - Feb 1-2, 2020 in Brussels

·        Submissions to open source firmware track from Intel & = Linaro

·        Acceptance notices should be sent on Dec 8

 

Groups.io issues w/ patches

·        Seeing issues with large patch sets (over 40 items). Mike K= inney investigating. This has been observed by multiple users, so it is lik= ely a groups.io "feature". Gitconfig can batch large e-mail patch sets with delays as a workaround. Red Hat will experime= nt on configuration.

·        Lazlo has seen inconsistencies with names used e-mail, whic= h causes problems with commit history. Switching computers or environments = can cause problems in gitconfig. Possible issues with Outlook/Exchange server (seen with some e-mails sent from intel.com).=

·        Goal is to update best practices for gitconfig, including P= ython helper script.

·        Change in domain should be considered a different author. R= equires additional review to make sure this is the same person.<= /span>

·        Note: Issues this like have motivated the conversation for = changing workflow from e-mail patches. Need to revisit new workflow & r= esolve in community.

 

2020 Q1 Planning

·        Rush of patches ahead of soft freeze date. Need to be proac= tive for each stable tag release & avoid this problem.

·        Developers should be focused on large/high-risk changes fir= st, then move to lower priority/complexity issues. Reduces risk & thras= h.

·        Metrics for bugs & features: size of patch set, algorit= hmic complexity, value with changes to critical code (even if changes are s= mall, are risks justified versus benefits?). Measure as part of bug scrub, can push to next stable tag if deadlines cannot be m= et.

·        Mike is investigating Bugzilla fields that can help manage = this process (existing or new additions).

·        Is there measurement criteria when moving code from edk2-st= aging to edk2 main repo? This is the responsibility of the staging branch o= wner. May need to spell this out as part of the exit criteria when staging code is elevated to master edk2 repo (testi= ng APIs? How many platforms were used for validation?)

·        New protocols? Ok to add new EDK II APIs. If they impact UE= FI spec updates, that is related to the code first initiative (different di= scussion, see below).

·        How is security mapped to risk assessment? Need to make sur= e this is covered.

 

HBFA & Unit Testing

·        Brent @ Microsoft has sent a proposal to add HBFA to CI pro= cess for unit testing (with examples).

·        Goal: Simplify process to add new unit tests & related = APIs. Initial focus at library level. Module level has challenges in host e= nvironment (mocked interfaces can be complicated, shouldn't be more complex than the actual test). Infrastructure should tak= e burden of complexity of test cases (instead of developer).

·        Framework should support multiple frameworks under the test= directory. Staring with HBFA, but not assuming a single framework.

·        Stewards will review current proposal & provide feedbac= k. Feedback is encouraged from the community on the edk2 rfc list.

 

Code First - still work in progress

·        Accessibility - Andrew @ Apple working on text-to-speech &a= mp; related audio protocols in emulator.

·        Leif @ Linaro still working on code first proposal. Will se= nd to edk2 rfc list when ready.

·        Naming conventions will clearly identify pre-spec & pos= t-spec work.

 

Brian will be on vacation on Jan 2, 2020 (next scheduled community = meeting). Will find different meeting owner for that date.

 

Thanks … br

 

--_000_80AC2BAA3152784F98F581129E5CF5AFCAF9CD09ORSMSX114amrcor_--