From: "Abner Chang" <abner.chang@hpe.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Wang, Nickle (HPS SW)" <nickle.wang@hpe.com>
Subject: edk2 repo for RedfishPkg
Date: Mon, 20 Apr 2020 15:07:47 +0000 [thread overview]
Message-ID: <TU4PR8401MB0429FE8C0E73F74593280C6DFFD40@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
Hi edk2 community members,
Per to the short discussion with Mike and Ray, we would like to know your opinions regard to which edk2 repo to accommodate RedfishPkg, edk2/RedfshPkg or edk2-platforms/Features/RedfishPkg?
The current direction of edk2 open source is going to reduce the size and some features were moved to edk2-platform already (e.g. edk2-platforms/Features/Intel).
Although RedfishPkg is a FW core feature however not all of systems require this. For example, most of client systems don't need Redfish for the out of band management so far, maybe later.
My current idea is put RedfishPkg under edk2-platforms/Features, however I am also fine with having this package to under edk2 repo.
What is your opinion? edk2 or edk2-platforms?
Thanks
Abner
[-- Attachment #2: Type: text/html, Size: 2920 bytes --]
reply other threads:[~2020-04-20 15:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=TU4PR8401MB0429FE8C0E73F74593280C6DFFD40@TU4PR8401MB0429.NAMPRD84.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