All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	"committers@xenproject.org" <committers@xenproject.org>
Subject: Re: [PATCH] Remove ambiguities in the COPYING file; add CONTRIBUTING file
Date: Thu, 11 Aug 2016 11:59:42 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.10.1608111157331.25028@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <D3D21313.2C9E7%lars.kurth@citrix.com>

On Thu, 11 Aug 2016, Lars Kurth wrote:
> On 11/08/2016 01:51, "Stefano Stabellini" <sstabellini@kernel.org> wrote:
> 
> >> +Developer's Certificate of Origin
> >> +---------------------------------
> >> +
> >> +All patches to the Xen Project code base must include the the line
> >                                                          ^ double "the"
> 
> Thanks: will fix. And also fixed in the wiki page where I copied this from.
> 
> 
> >> +GOVERNANCE AND WORKFLOW
> >> +-----------------------
> >> +
> >> +The following documents provide a general overview of governance and
> >> +contribution guidelines for the Xen Project:
> >> + - https://xenproject.org/governance.html
> >> + - https://xenproject.org/help/contribution-guidelines.html
> >
> >It might be worth considering importing the governance as a file in the
> >Xen repository.
> 
> After discussing with a few committers, I think storing this in a git repo
> is a good idea: possibly as markup. It should not be in xen.git though,
> but probably in a new governance.git tree, for which I am maintainer.

That's a good idea. It would make far easier to review changes to it in
the future. I'd suggest markdown, which is actually quite nice to use
and has already been used for a few design docs, including pv calls and
xsplice.


> Let me do a bit of investigation first. In any case, this should be covered
> separately. We can later update this document accordingly.
 
Sure. Thanks for your work on this.

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

  reply	other threads:[~2016-08-11 18:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 11:30 [PATCH] Remove ambiguities in the COPYING file; add CONTRIBUTING file Lars Kurth
2016-08-11  0:51 ` Stefano Stabellini
2016-08-11  9:49   ` George Dunlap
2016-08-11 10:52     ` Lars Kurth
2016-08-11 18:57     ` Stefano Stabellini
2016-08-12  9:15       ` Lars Kurth
2016-08-11 10:39   ` Lars Kurth
2016-08-11 18:59     ` Stefano Stabellini [this message]
2016-08-12  9:13       ` Lars Kurth
2016-08-12 21:45         ` Stefano Stabellini
2016-08-11  9:56 ` George Dunlap
2016-08-11 11:05   ` Lars Kurth
2016-08-11 13:33     ` George Dunlap

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=alpine.DEB.2.10.1608111157331.25028@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=committers@xenproject.org \
    --cc=lars.kurth@citrix.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.