xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@citrix.com>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: George Dunlap <George.Dunlap@citrix.com>,
	"minios-devel@lists.xenproject.org"
	<minios-devel@lists.xenproject.org>,
	Rich Persaud <persaur@gmail.com>,
	"committers@xenproject.org" <committers@xenproject.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	xen-devel <xen-devel@lists.xenproject.org>,
	"win-pv-devel@lists.xenproject.org"
	<win-pv-devel@lists.xenproject.org>,
	Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Re: [Xen-devel] [RFC] Code of Conduct
Date: Tue, 27 Aug 2019 18:33:00 +0100	[thread overview]
Message-ID: <23909.26956.404750.684802@mariner.uk.xensource.com> (raw)
In-Reply-To: <F76AAD6E-198A-4455-A1DE-EED974DEACA3@citrix.com>

Lars Kurth writes ("Re: [Xen-devel] [RFC] Code of Conduct"):
> I did raise the issue of a cross-project support network, which has not yet been on the agenda. I will be hooked into this process.
> My gut feeling is that we are looking at 6-9 months before all of this is resolved. Maybe longer.

I think this is too long.  We are overdue with this.

> Ultimately, we have 3 options:
> 
>   1.  We wait for the LF and revisit then
>   2.  We go our own way re customization
>   3.  We draft our own customizations and bring it up in one of the LF meetings discussing this
> 
> My gut feeling is to go for c) and I am willing to have a try at customizing the Contributor Covenant along the lines of the previous exercise

I am happy with 2 or 3, but we shouldn't block on LF approval.  Having
input is good.  If later we want to join some cross-community network
and want to update it for that, we can do that.  Updating a document
for something like that is quite easy.  IMO we need to get on with the
really hard work which is adopting a document at all.

I look forward to your Contributor Covenant based draft.

Thanks,
Ian.

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

  reply	other threads:[~2019-08-27 17:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 17:48 [Xen-devel] [RFC] Code of Conduct Lars Kurth
2019-08-15 17:23 ` Rich Persaud
2019-08-15 18:01   ` Lars Kurth
2019-08-15 18:27     ` Rich Persaud
2019-08-15 18:46       ` [Xen-devel] [win-pv-devel] " Lars Kurth
2019-08-15 19:08         ` Rich Persaud
2019-08-15 19:25           ` [Xen-devel] " Lars Kurth
2019-08-16 11:19   ` George Dunlap
2019-08-16 15:49     ` Rich Persaud
2019-08-16 16:20       ` Lars Kurth
2019-08-26 18:03         ` Lars Kurth
2019-08-27 17:33           ` Ian Jackson [this message]
2019-08-27 20:47             ` Lars Kurth
2019-08-28  0:53               ` Stefano Stabellini
2019-08-28  2:02                 ` Lars Kurth
     [not found]             ` <D8EFC0B6-0FFC-4288-86EC-FD0A0BB8C3BF@citrix.com-0>
2019-09-02 15:48               ` Ian Jackson
2019-09-02 18:10                 ` Lars Kurth
     [not found] <AB34D39A-A120-440E-9309-3950E7A465A5@citrix.com-0>
2019-08-12 11:35 ` George Dunlap
2019-08-12 14:27   ` Lars Kurth
2019-08-12 14:35     ` George Dunlap
2019-08-13 14:30       ` 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=23909.26956.404750.684802@mariner.uk.xensource.com \
    --to=ian.jackson@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=committers@xenproject.org \
    --cc=lars.kurth@citrix.com \
    --cc=minios-devel@lists.xenproject.org \
    --cc=mirageos-devel@lists.xenproject.org \
    --cc=persaur@gmail.com \
    --cc=stefano.stabellini@xilinx.com \
    --cc=win-pv-devel@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).