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:52:20 +0200 [thread overview]
Message-ID: <20140527195220.GF3503@free.fr> (raw)
In-Reply-To: <871tvfdmyx.fsf@dell.be.48ers.dk>
Peter, All,
On 2014-05-27 21:45 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> >> 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.
Oh, we'd maintain the same way we maintain the list of packages: with a
little bit of scripting and a make target in docs/manual/manual.mk.
But I'm fine with just a., too. I just misunderstood Thomas DS'
c-suggestion.
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-05-27 19:52 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 [this message]
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=20140527195220.GF3503@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