From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot manual: author list
Date: Wed, 28 May 2014 07:27:02 +0200 [thread overview]
Message-ID: <538573A6.6080503@mind.be> (raw)
In-Reply-To: <871tvfdmyx.fsf@dell.be.48ers.dk>
On 27/05/14 21:45, Peter Korsgaard wrote:
>>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>
> Hi,
>
> >> 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?
>
> I would also suggest we go for a (unless any of the people explictly
> listed would disagree). We don't list authorship anywhere else (E.G. in
> the .mk files) in Buildroot, and it sounds like a pain to maintain such
> a list and decide what a 'major contribution' is.
I agree with this. If we want to list contributors, it's more relevant to do
that for the entire codebase than just for the manual.
On a side note however: Karsten Kruse, Ned Ludd, Martin Herren are *not* in the
shortlog of buildroot.html!
Regards,
Arnout
>
> Thomas (Petazzoni), what do you say?
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-05-28 5:27 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
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 [this message]
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=538573A6.6080503@mind.be \
--to=arnout@mind.be \
--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 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.