public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>, Laszlo Ersek <lersek@redhat.com>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: [PATCH 2/2] [staging/EdkRepo-Manifest]: Add EdkRepo manifest XML
Date: Tue, 11 Jun 2019 17:04:48 -0700	[thread overview]
Message-ID: <20190612000448.20432-3-nathaniel.l.desimone@intel.com> (raw)
In-Reply-To: <20190612000448.20432-1-nathaniel.l.desimone@intel.com>

Signed-off-by: Nate DeSimone <nathaniel.l.desimone@intel.com>
Cc: Andrew Fish <afish@apple.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
---
 Maintainers.txt | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
 README.md       | 32 ++++++++++++++++++++++++++++++++
 2 files changed, 82 insertions(+)
 create mode 100644 Maintainers.txt
 create mode 100644 README.md

diff --git a/Maintainers.txt b/Maintainers.txt
new file mode 100644
index 0000000000..de4817f6ee
--- /dev/null
+++ b/Maintainers.txt
@@ -0,0 +1,50 @@
+EDK II Maintainers
+==================
+
+This file provides information about the primary maintainers for
+EdkRepo.
+
+In general, you should not privately email the maintainer. You should
+email the edk2-devel list, but you can also Cc the maintainer.
+
+Descriptions of section entries:
+
+  L: Mailing list that is relevant to this area (default is edk2-devel)
+     Patches and questions should be sent to the email list.
+  M: Cc address for patches and questions (ie, the package maintainer)
+  R: Package Reviewer: Cc address for patches and questions. Reviewers help
+     maintainers review code, but don't have push access. A designated Package
+     Reviewer is reasonably familiar with the Package (or some modules
+     thereof), and/or provides testing or regression testing for the Package
+     (or some modules thereof), in certain platforms and environments.
+  W: Web-page with status/info
+  T: SCM tree type and location.  Type is one of: git, svn.
+  S: Status, one of the following:
+     Supported:  Someone is actually paid to look after this.
+     Maintained: Someone actually looks after it.
+     Odd Fixes:  It has a maintainer but they don't have time to do
+                 much other than throw the odd patch in. See below.
+     Orphan:     No current maintainer [but maybe you could take the
+                 role as you write your new code].
+     Obsolete:   Old code. Something tagged obsolete generally means
+                 it has been replaced by a better system and you
+                 should be using that.
+
+EDK II
+------
+W: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II
+L: https://edk2.groups.io/g/devel/
+T: git - https://github.com/tianocore/edk2-staging.git
+
+Responsible Disclosure, Reporting Security Issues
+-------------------------------------------------
+W: https://github.com/tianocore/tianocore.github.io/wiki/Security
+
+EDK II Packages:
+----------------
+
+EdkRepo Manifest
+W: https://github.com/tianocore/edk2-staging/tree/EdkRepo-Manifest
+M: Nate DeSimone <nathaniel.l.desimone@intel.com>
+M: Ashley DeSimone <ashley.e.desimone@intel.com>
+R: Puja Pandya <puja.pandya@intel.com>
diff --git a/README.md b/README.md
new file mode 100644
index 0000000000..2145696afb
--- /dev/null
+++ b/README.md
@@ -0,0 +1,32 @@
+This branch is for integrating the EdkRepo tool manifest XML in to EDK2
+
+# Introduction
+
+EdkRepo is the multi-repository tool for EDK II firmware development. This branch contains an initial set of example manifest files which can be used to try EdkRepo.
+
+# Timeline
+| Time | Event |
+|:----:|:-----:|
+| WW 24 2019 | Initial commit of EdkRepo manifest XML files. |
+|...|...|
+
+# Branch Owners
+- Ashley DeSimone <ashley.e.desimone@intel.com>
+- Nate DeSimone <nathaniel.l.desimone@intel.com>
+
+# Integration
+EdkRepo could live in several places:
+1. edk2-platforms
+2. edk2-pytool-library
+3. The edk2-toolenv repository proposed by Sean (assuming approval of Sean’s RFC)
+4. A new, separate repository created for EdkRepo
+
+This is a topic that requires community discussion to decide what the final location should be.
+
+# Known Issues
+| Issue | Status |
+|:-----:|:------:|
+|...|...|
+
+# Related Links
+- https://github.com/tianocore/edk2-staging/tree/EdkRepo
-- 
2.16.2.windows.1


  parent reply	other threads:[~2019-06-12  0:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  0:04 [PATCH 0/2] EdkRepo - The Multi-Repository Tool for EDK II Nate DeSimone
2019-06-12  0:04 ` [PATCH 1/2] [staging/EdkRepo]: Add EdkRepo - The Multi-Repo Tool Nate DeSimone
2019-06-12  0:04 ` Nate DeSimone [this message]
2019-06-12  7:54 ` [PATCH 0/2] EdkRepo - The Multi-Repository Tool for EDK II Laszlo Ersek
2019-06-12 15:41   ` [edk2-devel] " Nate DeSimone
2019-06-14 21:39 ` Michael D Kinney

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=20190612000448.20432-3-nathaniel.l.desimone@intel.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