All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] An Open, Transparent Patch Submission Process
Date: Fri, 26 May 2017 19:13:02 +0000	[thread overview]
Message-ID: <1495825980.2678.3.camel@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

Hi all,

We're excited to announce a new patch submission process for SPDK utilizing
GerritHub, a hosted code review service integrated with GitHub. All patches,
even from SPDK maintainers, will now use the new process, which means all code
reviews and discussions are now fully open and transparent to everyone. We
encourage everyone, even if you aren't an expert, to review patches and vote
with a +1 or -1! A quick query for all open patches is here (better queries and
dashboard set up are in the guide at the bottom):

https://review.gerrithub.io/#/q/project:spdk/spdk+status:open

Further, the SPDK continuous integration tests are hooked up to GerritHub, which
means that when you submit a patch a whole battery of tests on a wide range of
systems will be run with results reported directly to the code review. You can
view the current status of the continuous integration system at:

http://ci.spdk.io


A comprehensive guide to the new patch submission process can be found here:

http://www.spdk.io/development

A quick start guide is still in the works.

We're thrilled to open this system up to everyone, giving all community members
access to the same tools the SPDK maintainers have.

Thanks,
The SPDK maintainers

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]

                 reply	other threads:[~2017-05-26 19:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1495825980.2678.3.camel@intel.com \
    --to=spdk@lists.01.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.