All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Piotr Dałek" <branch@predictor.org.pl>
To: ceph-devel@vger.kernel.org
Subject: Re: updating the documentation
Date: Wed, 12 Jul 2017 21:22:46 +0200	[thread overview]
Message-ID: <20170712192246.GA10000@mailware> (raw)
In-Reply-To: <CA+2bHPaRDo=HLpui_4jcMXcFCzgR6UsmetpX7B6t2L-160oV=A@mail.gmail.com>

On Wed, Jul 12, 2017 at 11:37:32AM -0700, Patrick Donnelly wrote:
> On Wed, Jul 12, 2017 at 11:29 AM, Sage Weil <sweil@redhat.com> wrote:
> > In the meantime, we can also avoid making the problem worse by requiring
> > that all pull requests include any relevant documentation updates.  This
> > means (1) helping educate contributors that doc updates are needed, (2)
> > helping maintainers and reviewers remember that doc updates are part of
> > the merge criteria (it will likely take a bit of time before this is
> > second nature), and (3) generally inducing developers to become aware of
> > the documentation that exists so that they know what needs to be updated
> > when they make a change.
> 
> There was a joke to add a bot which automatically fails PRs for no
> documentation but I think there is an way to make that work in a
> reasonable way. Perhaps the bot could simply comment on all PRs
> touching src/ that documentation is required and where to look, and
> then fails a doc check. A developer must comment on the PR to say it
> passes documentation requirements before the bot changes the check to
> pass.

For sure it could fail if a PR changes config_opts.h and doesn't carry any
doc update -- lack of docs for config options is probably the most common
and most annoying issue among Ceph users.

-- 
Piotr Dałek
branch@predictor.org.pl
http://blog.predictor.org.pl

  reply	other threads:[~2017-07-12 19:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 18:29 updating the documentation Sage Weil
2017-07-12 18:37 ` Patrick Donnelly
2017-07-12 19:22   ` Piotr Dałek [this message]
2017-07-12 19:28   ` Sage Weil
2017-07-18 13:51     ` John Spray
2017-07-18 20:03       ` [ceph-users] " Gregory Farnum
2017-07-18 21:14         ` John Spray
2017-07-18  4:59 ` Dan Mick
  -- strict thread matches above, loose matches on Subject: below --
2007-04-01 12:07 Updating " Stuart Axon

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=20170712192246.GA10000@mailware \
    --to=branch@predictor.org.pl \
    --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 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.