public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Sean Brogan <sean.brogan@microsoft.com>,
	"abner.chang@hpe.com" <abner.chang@hpe.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Ni, Ray" <ray.ni@intel.com>,
	"Wang, Nickle (HPS SW)" <nickle.wang@hpe.com>
Subject: Re: [edk2-devel] edk2 repo for RedfishPkg
Date: Mon, 20 Apr 2020 17:25:20 +0000	[thread overview]
Message-ID: <CY4PR21MB07430AD7FEC67F84E21ED2D6EFD40@CY4PR21MB0743.namprd21.prod.outlook.com> (raw)
In-Reply-To: <MW2PR2101MB0924E52AE4887380775BA935E1D40@MW2PR2101MB0924.namprd21.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]

Agreed. I’d like to see edk2 Core, edk2 Optional, and edk2 Platform. I think that’s an appropriate division that helps address some of the placement and dependency concerns a number of us (not just MS 😊) have identified.

- Bret
________________________________
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Sean via groups.io <sean.brogan=microsoft.com@groups.io>
Sent: Monday, April 20, 2020 10:20:48 AM
To: devel@edk2.groups.io <devel@edk2.groups.io>; abner.chang@hpe.com <abner.chang@hpe.com>
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Ni, Ray <ray.ni@intel.com>; Wang, Nickle (HPS SW) <nickle.wang@hpe.com>
Subject: [EXTERNAL] Re: [edk2-devel] edk2 repo for RedfishPkg


I support somewhere other than edk2 core.



I would offer a third option to think about; create a new tianocore repo.  For optional features or features that don’t have broad community adoption it would allow for those downstream consumers to easily pick and chose their consumption.  It also helps avoid “core” features becoming entangled or dependent on an optional features.  Current UiApp would be another great example.



Just my opinion.



Thanks

Sean





From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Abner Chang via groups.io
Sent: Monday, April 20, 2020 8:08 AM
To: 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: [EXTERNAL] [edk2-devel] edk2 repo for RedfishPkg



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: 4365 bytes --]

  reply	other threads:[~2020-04-20 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 17:20 [edk2-devel] edk2 repo for RedfishPkg Sean
2020-04-20 17:25 ` Bret Barkelew [this message]
2020-04-21  9:50   ` Ni, Ray

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=CY4PR21MB07430AD7FEC67F84E21ED2D6EFD40@CY4PR21MB0743.namprd21.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