CEPH filesystem development
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Welcome message to new contributors
Date: Sun, 01 Jun 2014 11:45:01 +0200	[thread overview]
Message-ID: <538AF61D.3010304@dachary.org> (raw)

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

Hi Ceph,

TL;DR: I volunteer to install a bot that posts a welcome message to the first pull request of a new contributor. Unless someone else already has something ready ;-)

As a new contributor you are supposed to go thru https://github.com/ceph/ceph/blob/master/SubmittingPatches and prepare the patch accordingly. But it's a long read if you're going to fix a typo. You're probably going to forget to add the Signed-off-by: in the comment, which is the only thing you really need to comply to in this case.

The bot would listen to the pull request queue and send a welcome message to new contributors (i.e. no previous Author: commit or Signed-off-by with this name). And a gentle reminder that Signed-off-by: is required if it is missing. 

Here is a gerrit example of such a message, in the context of OpenStack:

https://review.openstack.org/#/c/94195/

Welcome, new contributor!		May 19 3:44 PM

Patch Set 1:

Thank you for your first contribution to OpenStack.

Your patch will now be tested automatically by OpenStack testing frameworks
and once the automatic tests pass, it will be reviewed by other friendly
developers. They will give you feedback and may require you to refine it.

People seldom get their patch approved on the first try, so don't be
concerned if requested to make corrections. Feel free to modify your patch
and resubmit a new change-set.

Patches usually take 3 to 7 days to be reviewed so be patient and be
available on IRC to ask and answer questions about your work. The more you
participate in the community the more rewarding it is for you. You may also
notice that the more you get to know people and get to be known, the faster
your patches will be reviewed and eventually approved. Get to know others
and become known by doing code reviews: anybody can do it, and it's a
great way to learn the code base.

Thanks again for supporting OpenStack, we look forward to working with you.

IRC: https://wiki.openstack.org/wiki/IRC
Workflow: https://wiki.openstack.org/wiki/Gerrit_Workflow

Cheers
-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

             reply	other threads:[~2014-06-01  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01  9:45 Loic Dachary [this message]
2014-06-02 12:36 ` Welcome message to new contributors Sage Weil
2014-06-10 21:29 ` Loic Dachary

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=538AF61D.3010304@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.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