From: "Soumya Guptha" <soumya.k.guptha@intel.com>
To: Bret Barkelew <Bret.Barkelew@microsoft.com>,
"announce@edk2.groups.io" <announce@edk2.groups.io>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>
Subject: Re: TianoCore Community Meeting Minutes - 2/4
Date: Thu, 11 Feb 2021 17:44:14 +0000 [thread overview]
Message-ID: <MWHPR1101MB23663B95F4A95BF5F4A9A4D8A78C9@MWHPR1101MB2366.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CY4PR21MB018262ABCACDCCF87A4F5B34EFB29@CY4PR21MB0182.namprd21.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 4088 bytes --]
Great to hear Bret. Thanks.
Folks, this is a reminder. The deadline for submitting our project (Tianocore) proposal to Google summer code is approaching soon (Feb 19th), please do reach out to Nate Desimone if you have any project ideas.
Thanks,
Soumya
From: Bret Barkelew <Bret.Barkelew@microsoft.com>
Sent: Friday, February 5, 2021 1:26 PM
To: Guptha, Soumya K <soumya.k.guptha@intel.com>; announce@edk2.groups.io; devel@edk2.groups.io; Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>
Subject: RE: TianoCore Community Meeting Minutes - 2/4
@Desimone, Nathaniel L<mailto:nathaniel.l.desimone@intel.com>, I'm interested in mentorship for the GSC project. Would like to talk offline about potential projects and past experience.
RE: ECC, we're internally evaluating 'uncrustify' as an option to 1) check for formatting violations and 2) provide a tool to automatically format code prior to submission. There are changes that we've made to the tool to support ECC, but there are some small places that we're coming up short. What would be the appetite to evaluate our progress and discuss possibly adjusting the ECC to be more flexible where we've come up short?
- Bret
From: Soumya Guptha via groups.io<mailto:soumya.k.guptha=intel.com@groups.io>
Sent: Thursday, February 4, 2021 8:12 PM
To: announce@edk2.groups.io<mailto:announce@edk2.groups.io>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [EXTERNAL] Re: [edk2-announce] TianoCore Community Meeting Minutes - 2/4
TianoCore Community Meeting Minutes (APAC/NMO)
February 4, 2021
EVENTS:
No new updates.
STABLE TAG:
edk2-stable202102 - Feature Planning freeze on 2/15
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftianocore%2Ftianocore.github.io%2Fwiki%2FEDK-II-Release-Planning&data=04%7C01%7CBret.Barkelew%40microsoft.com%7Ca97d5c438d514d0859ea08d8c98c43a6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637480951557144463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UA13OI0UuZ2QSboHsE4dZY5J0Az1uL8Boxldw0jdtmU%3D&reserved=0
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<mailto: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: 10106 bytes --]
prev parent reply other threads:[~2021-02-11 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 4:12 TianoCore Community Meeting Minutes - 2/4 Soumya Guptha
2021-02-05 21:26 ` 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 [this message]
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=MWHPR1101MB23663B95F4A95BF5F4A9A4D8A78C9@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