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] Changes in the Buildroot autobuilders
Date: Mon, 17 Jun 2013 19:54:07 +0200	[thread overview]
Message-ID: <20130617175407.GA3202@free.fr> (raw)
In-Reply-To: <CAEBucnCWYyj23_RyLtP3p-B6zmBYiYOA4LiODMEdxEr7x4D+xw@mail.gmail.com>

Spenser, All,

On 2013-06-17 11:20 -0500, Spenser Gilliland spake thusly:
> Are we sure we want to add more variables to the .mk files.  One of
> Buildroot's main differentiators is the cleanliness of these files in
> comparison to other packaging methods.
> 
> As an alternative, this information could be pulled from the git log
> and anyone who has made a change to the package directory in the past
> would be subscribed to errors.

No, I am not in favour of this solution.

Being a 'maintainer' should be voluntary, opt-in, and explicit.

If I send an update or fix to a package does not mean I am committed to
maintain that package in the long-run. This change can be just a typo or
something minor, and might not express my interest in the wellfare of
that package.

However, if I am really interested in a package (eg. those I've
submitted, or others that are important to me), then I want to express
this intent to maintain it explicitly.

Now, I understand that adding yet more to the .mk can be seen as clutter.

The alternative to a expressing maintainership in the source would be to
have the autobuilder website offer a way to subscribe/unsubscribe to
certain conditions (eg. package, arch...). I think this is a bit
overkill, and delicate to handle.

So, there are three possibilities:

  - per-package _MAINTAINER variable in each .mk
  - global MAINTAINERS a bit like the Linux kernel
  - subscription from the autobuilder website

My preference goes to the first, but I think the second is good too.
I'd expect the third to be complex and too overkill for this, unless
Thomas (which is responsible for the autobulders ;-) ) thinks he can
handle this, of course.

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:[~2013-06-17 17:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 16:00 [Buildroot] Changes in the Buildroot autobuilders Thomas Petazzoni
2013-06-16 17:03 ` Yann E. MORIN
2013-06-16 17:18   ` Thomas Petazzoni
2013-06-16 17:25     ` Yann E. MORIN
2013-06-16 18:05       ` Thomas Petazzoni
2013-06-17  7:45         ` Maxime Ripard
2013-06-17  7:49           ` Thomas Petazzoni
2013-06-17 16:20             ` Spenser Gilliland
2013-06-17 17:54               ` Yann E. MORIN [this message]
2013-06-17 18:07                 ` ANDY KENNEDY
2013-06-17 20:09                   ` Mischa Jonker
2013-06-18  7:12                     ` Thomas Petazzoni
2013-06-17 20:39                 ` Spenser Gilliland
2013-06-18  6:21                 ` Arnout Vandecappelle
2013-06-18  7:16                   ` Thomas Petazzoni
2013-06-18 16:46                     ` Yann E. MORIN
2013-06-17  6:25       ` Arnout Vandecappelle

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=20130617175407.GA3202@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