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: Lars Kurth <lars.kurth@citrix.com>, committers@xenproject.org
Subject: [PATCH v2 0/3] Significant changes to Xen Project Governance (governance.html)
Date: Mon, 12 Sep 2016 17:20:09 +0100	[thread overview]
Message-ID: <1473697212-3245-1-git-send-email-lars.kurth@citrix.com> (raw)

I made some significant proposed changes to governance.html based on a number 
of issues that were raised in a number of surveys last year, and via other 
means, as well as in the recent discussions related to governance.html changes 
(the issue of too many committers in XAPI and XAPI being able to hijack the 
entire project).

In any case, the changes are expressed in three patches governance.pandoc,
which is the pandoc source for governance.html:

- Code motion changes to make real patches easier to read
  No content has been changed
  An index was added
  Fixed some minor typos and formatting issues

- Added comment sections to highlight problem areas
  The intention here is to highlight the issues to be addressed
    
- Significant changes to decision making; some new roles; minor changes
  Introduces governance changes
  Adds some new roles
  Minor formatting changes, such as missing anchors, wrong 
  Deletes addressed open issues in comments 
  Add additional comments to raise questions or provide background info

The intention is to show you my thought processes behind the proposal
and to prompt questions.

The patch series is based on git://xenbits.xen.org/people/larsk/governance.git
You can see the diff's easily in http://xenbits.xen.org/gitweb/?p=people/larsk/governance.git;a=shortlog;h=refs/heads/2016-overhaul

Open Issues to be fixed 
- Fix up tables as these don't render properly as html
  Also see http://rapporter.github.io/pander/pandoc_table.html
  
---
Changes since v1
- Agreed and changed counting schemes for lazy consensus/votinh
- Added Community Decisions with Funding and Legal Implications
- Clarified AB role in
- Removed comments where superceded by decisions
- Adapted sections with dependencies

-- 
2.5.4 (Apple Git-61)


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

             reply	other threads:[~2016-09-12 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 16:20 Lars Kurth [this message]
2016-09-12 16:20 ` [PATCH v2 1/3] Code motion changes to make real patches easier to read Lars Kurth
2016-09-12 16:20 ` [PATCH v2 2/3] Added comment sections to highight problem areas Lars Kurth
2016-09-12 16:20 ` [PATCH v2 3/3] Significant changes to decision making; some new roles and minor changes Lars Kurth
2016-09-13 16:46   ` George Dunlap
2016-09-13 16:57     ` Lars Kurth
2016-09-19 14:01       ` Ian Jackson
2016-09-19 14:46         ` Lars Kurth
2016-09-19 15:36           ` Ian Jackson
2016-09-20 17:01   ` Ian Jackson
2016-09-20 18:53     ` Lars Kurth

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=1473697212-3245-1-git-send-email-lars.kurth@citrix.com \
    --to=lars.kurth@citrix.com \
    --cc=committers@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).