From: Ian Campbell <ian.campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [COVERITY ACCESS] for Lars Kurth
Date: Thu, 1 Oct 2015 10:14:29 +0100 [thread overview]
Message-ID: <1443690869.11707.7.camel@citrix.com> (raw)
In-Reply-To: <20150930151458.GD30549@localhost.localdomain>
On Wed, 2015-09-30 at 11:14 -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 29, 2015 at 11:01:44AM +0100, Lars Kurth wrote:
> > Hi,
> >
> > I agree to the conditions in the XenProject Coverity contribution
> > guidelines [1].
> >
> > I have been community manager for the Xen Project since 2011 and
> > chairman of the Xen Project Advisory Board since 2013.
> >
> > I would like access primarily to be able to write and speak
> > intelligently about Xen and Coverity (more generally quality) in
> > blog postings, conference talks and updates to the advisory board.
> > I may also go and fix the one or other bug. It would be easier to go
> > through the stats and history myself, rather than trying to get
> > some other developer to do it for me.
> >
> > [1] http://xenproject.org/help/contribution-guidelines.html
>
> +1
Strictly speaking the requirements include that the mail "be signed by a
PGP key which is part of the strong set of the PGP web of trust". Which it
was not.
But the spirit of that rule is, quoting the guidelines:
serve to help validate the identity and trustworthiness of the person
since they will be given access to potentially sensitive information.
I think given that Lars is well known to pretty much all of us and
obviously a trustworthy member of the community we can waive that
particular requirement, so although I'm wary of setting a precedent:
+1.
Ian.
prev parent reply other threads:[~2015-10-01 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 10:01 [COVERITY ACCESS] for Lars Kurth Lars Kurth
2015-09-30 15:14 ` Konrad Rzeszutek Wilk
2015-10-01 9:14 ` Ian Campbell [this message]
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=1443690869.11707.7.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth.xen@gmail.com \
--cc=xen-devel@lists.xen.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).