From: "Soumya Guptha" <soumya.k.guptha@intel.com>
To: "announce@edk2.groups.io" <announce@edk2.groups.io>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: TianoCore Community Meeting Minutes - 2/4
Date: Fri, 5 Feb 2021 04:12:26 +0000 [thread overview]
Message-ID: <MWHPR1101MB2366BC50F325E320E724816CA7B29@MWHPR1101MB2366.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2141 bytes --]
TianoCore Community Meeting Minutes (APAC/NMO)
February 4, 2021
EVENTS:
No new updates.
STABLE TAG:
edk2-stable202102 - Feature Planning freeze on 2/15
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
STEWARDS DOWNLOAD (Mike Kinney)
* Design meeting - we discussed on Automation & CI system.
* Community Action: Need help from the community on ECC tool (EFI code checker), we have critical issues, need help quickly.
* Kevin - will explore to see if someone has any expertise wrt ECC tool.
* Sean plans to send to the info to the community on the tool to help format the source code. Sean will send it to the mailing list.
Suggests making ECC smaller.
* Addressed all issues related to cmocka.
* Workflow for maintainers: some maintainers like to work on multiple pull requests, causing extra work, process issue. We are investigating on automation. Task is to Evaluate the automation feature and get feedback.
* Bugzilla Feature request - update on NASM compiler version will start now. This is not required by developers until after the Q1 stable tag.
Opens:
1. Nate - Google summer code (sponsored internship program run by google). Need some mentors to mentor the interns. Tianocore open source needs to apply. Application deadline Feb 19th. We need to develop interesting ideas for summer projects. Nate will start an offline thread to discuss ideas for projects. Couple of people have expressed some interest in becoming mentors.
Community Action: If you are interested in either mentoring or have a project idea, please send an email to (nathaniel.l.desimone@intel.com).
1. Sean - code contribution, project management - are we doing anything to improve.
Acknowledgments:
Community Action: Please send Soumya if you like to acknowledge anyone from the community, if anyone helped you close bugs or reviewed code etc..We will post those acknowledgements on the community page.
Soumya Guptha
Firmware Ecosystem Enabling Manager, SFP/IAGS
[-- Attachment #2: Type: text/html, Size: 10142 bytes --]
next reply other threads:[~2021-02-05 4:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 4:12 Soumya Guptha [this message]
2021-02-05 21:26 ` TianoCore Community Meeting Minutes - 2/4 Bret Barkelew
2021-02-05 22:44 ` [edk2-devel] " Michael D Kinney
2021-02-05 23:34 ` mikuback
2021-02-11 17:44 ` Soumya Guptha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR1101MB2366BC50F325E320E724816CA7B29@MWHPR1101MB2366.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox