public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sumit Semwal <sumit.semwal@linaro.org>,
	linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linaro-mm-sig@lists.linaro.org, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net
Subject: Re: [RFC 3/4] Documentation: move dma-buf documentation to rst
Date: Thu, 11 Aug 2016 14:47:26 +0300	[thread overview]
Message-ID: <87twerv86p.fsf@intel.com> (raw)
In-Reply-To: <1470912480-32304-4-git-send-email-sumit.semwal@linaro.org>

On Thu, 11 Aug 2016, Sumit Semwal <sumit.semwal@linaro.org> wrote:
> diff --git a/Documentation/dma-buf/guide.rst b/Documentation/dma-buf/guide.rst
> new file mode 100644
> index 000000000000..fd3534fdccb3
> --- /dev/null
> +++ b/Documentation/dma-buf/guide.rst
> @@ -0,0 +1,503 @@
> +
> +.. _dma-buf-guide:
> +
> +============================
> +DMA Buffer Sharing API Guide
> +============================
> +
> +Sumit Semwal - sumit.semwal@linaro.org, sumits@kernel.org

Please use the format

:author: Sumit Semwal <sumit.semwal@linaro.org>

---

While on this subject, please excuse me for hijacking the thread a bit.

Personally, I believe it would be better to leave out authorship notes
from documentation and source files in collaborative projects. Of
course, it is only fair that people who deserve credit get the
credit. Listing the authors in the file is often the natural thing to
do, and superficially seems fair.

However, when do you add more names to the list? When has someone
contributed enough to warrant that? Is it fair that the original authors
keep getting the credit for the contributions of others? After a while,
perhaps there is next to nothing left of the original contributions, but
the bar is really high for removing anyone from the authors. Listing the
authors gives the impression this is *their* file, while everyone should
feel welcome to contribute, and everyone who contributes should feel
ownership.

IMHO we would be better off using just the git history for the credits.


BR,
Jani.


PS. I am no saint here, I've got a couple of authors lines myself. I
promise not to add more. I certainly won't chastise anyone for adding
theirs.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2016-08-11 11:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 10:47 [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Sumit Semwal
2016-08-11 10:47 ` [RFC 1/4] dma-buf/fence: kerneldoc: remove unused struct members Sumit Semwal
2016-08-11 10:47 ` [RFC 2/4] dma-buf/fence: kerneldoc: remove spurious section header Sumit Semwal
2016-08-12  8:44   ` Daniel Vetter
2016-08-11 10:47 ` [RFC 3/4] Documentation: move dma-buf documentation to rst Sumit Semwal
2016-08-11 11:47   ` Jani Nikula [this message]
2016-08-11 12:31     ` Sumit Semwal
2016-08-11 11:58   ` Markus Heiser
2016-08-11 12:12     ` Markus Heiser
2016-08-11 12:49     ` Sumit Semwal
2016-08-11 10:48 ` [RFC 4/4] Documentation/sphinx: link dma-buf rsts Sumit Semwal
2016-08-11 14:36 ` [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Jonathan Corbet
2016-08-12  6:35   ` Sumit Semwal
2016-08-12  8:38     ` Daniel Vetter

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=87twerv86p.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sumit.semwal@linaro.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