Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot manual: author list
Date: Tue, 27 May 2014 21:36:40 +0200	[thread overview]
Message-ID: <20140527193640.GE3503@free.fr> (raw)
In-Reply-To: <CAAXf6LXSqbJAjOi-YvEdPvcC=-XZE+6Z1Y-d2BRWEhMXu6ufFw@mail.gmail.com>

Thomas, All,

On 2014-05-27 21:22 +0200, Thomas De Schampheleire spake thusly:
> Currently, the Buildroot manual contains the following in the introduction:
> 
> "Buildroot usage and documentation by Thomas Petazzoni. Contributions
> from Karsten Kruse, Ned Ludd, Martin Herren and others."
[--SNIP--]
> My feeling is that the current listing of authors is not correct
> towards all these other people. There are at least three alternatives
> to do something about this:
> 
> a. replace the author reference in buildroot by a reference to 'the
> Buildroot developers' and let interested people look up the real list
> in git.
> 
> b. expand the list with some of the major contributors to the manual,
> based on the shortlogs above
> 
> c. add an appendix with a generated list (shortlog) of authors, which
> is then complete and up-to-date.
> 
> 
> I'm leaning more to a. or b. than to c.
> The advantage of a. over b. is that there is no discussion about whose
> name should be in the list (where to draw the line), while b. has the
> advantage of giving more explicit credit.

As I suggested on IRC: what about a.+c.? Just change the introduction to:

    Buildroot manual by the Buildroot developers, see xref:credits[].

and add the appendix 'credits' at the end of the manual?

Otherwise, I'd go for just a.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-05-27 19:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 19:22 [Buildroot] Buildroot manual: author list Thomas De Schampheleire
2014-05-27 19:36 ` Yann E. MORIN [this message]
2014-05-27 19:40   ` Thomas De Schampheleire
2014-05-27 19:45   ` Peter Korsgaard
2014-05-27 19:52     ` Yann E. MORIN
2014-05-28  5:27     ` Arnout Vandecappelle
2014-05-28  6:04 ` Thomas Petazzoni

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=20140527193640.GE3503@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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