xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: xen-api@lists.xenproject.org, win-pv-devel@lists.xenproject.org,
	committers@xenproject.org, mirageos-devel@lists.xenproject.org,
	Lars Kurth <lars.kurth@citrix.com>
Subject: [PATCH v3 2/4] Added document containing governance related todo list
Date: Fri, 23 Sep 2016 19:55:27 +0100	[thread overview]
Message-ID: <1474656929-3528-3-git-send-email-lars.kurth__15960.2005187937$1474656993$gmane$org@citrix.com> (raw)
In-Reply-To: <1474656929-3528-1-git-send-email-lars.kurth@citrix.com>

Contains items that at some point need to be addressed.
The items do not directly affect governance.pandoc

Signed-off-by: Lars Kurth <lars.kurth@citrix.com>
---
 governance.todo | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 governance.todo

diff --git a/governance.todo b/governance.todo
new file mode 100644
index 0000000..81e068c
--- /dev/null
+++ b/governance.todo
@@ -0,0 +1,23 @@
+This document contains some governance related TODO items that at some point 
+need to be addressed. The items do not directly affect governance.pandoc
+
+### Maintainers
+
+CONSISTENCY ISSUES that probably ought to be cleaned up at some point
+- The xen.git MAINTAINERS file does not list our release managers and 
+  stable branch maintainers
+- We do have a number of repos without MAINTAINERS files, e.g. mini-os.git, 
+  osstest.git
+- For projects with many repositories (e.g. XAPI and Mirage OS), using MAINTAINERS 
+  files is not very practical. XAPI seems to sometimes use MAINTAINERS and README 
+  files at other times. We may need a more central place to state roles.
+
+### Project Leadership Team and Project Lead
+
+CONSISTENCY ISSUES that probably ought to be cleaned up at some point
+- XAPI and Mirage OS ought to decide who their leadership team is 
+  (I made some assumptions for now)
+
+### Per Sub-Project Governance Specialisation 
+
+- XAPI, WinPV and MirageOS need to provide this information, if they deviate
\ No newline at end of file
-- 
2.5.4 (Apple Git-61)


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-09-23 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1474656929-3528-1-git-send-email-lars.kurth@citrix.com>
2016-09-23 18:55 ` [PATCH v3 1/4] Code motion changes to make real patches easier to read Lars Kurth
2016-09-23 18:55 ` Lars Kurth [this message]
2016-09-23 18:55 ` [PATCH v3 3/4] Significant changes to decision making; some new roles and minor changes Lars Kurth
2016-09-23 18:55 ` [PATCH v3 4/4] Addressed comments on quorum and security team members Lars Kurth
     [not found] ` <1474656929-3528-5-git-send-email-lars.kurth@citrix.com>
2016-10-03 16:27   ` Ian Jackson
2016-10-04  9:49     ` Lars Kurth
     [not found]     ` <D4194734.2EC04%lars.kurth@citrix.com>
2016-10-04  9:52       ` Ian Jackson
     [not found] ` <1474656929-3528-2-git-send-email-lars.kurth@citrix.com>
2016-10-14 20:12   ` [PATCH v3 1/4] Code motion changes to make real patches easier to read Konrad Rzeszutek Wilk
     [not found] ` <1474656929-3528-3-git-send-email-lars.kurth@citrix.com>
2016-10-14 20:13   ` [PATCH v3 2/4] Added document containing governance related todo list Konrad Rzeszutek Wilk
     [not found] ` <1474656929-3528-4-git-send-email-lars.kurth@citrix.com>
2016-10-14 20:30   ` [PATCH v3 3/4] Significant changes to decision making; some new roles and minor changes Konrad Rzeszutek Wilk

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-all 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='1474656929-3528-3-git-send-email-lars.kurth__15960.2005187937$1474656993$gmane$org@citrix.com' \
    --to=lars.kurth@citrix.com \
    --cc=committers@xenproject.org \
    --cc=mirageos-devel@lists.xenproject.org \
    --cc=win-pv-devel@lists.xenproject.org \
    --cc=xen-api@lists.xenproject.org \
    --cc=xen-devel@lists.xenproject.org \
    /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;
as well as URLs for NNTP newsgroup(s).