mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Aleksey Kuleshov <rndfax@yandex.ru>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] ehci-hcd: remove useless timeout
Date: Fri, 4 Mar 2016 09:58:24 -0800	[thread overview]
Message-ID: <CAHQ1cqFcgVVnQvO6ACpNJx3Czgvdm+-eKyVGMDEYCRsVuFoutA@mail.gmail.com> (raw)
In-Reply-To: <4943131457093089@web17h.yandex.ru>

On Fri, Mar 4, 2016 at 4:04 AM, Aleksey Kuleshov <rndfax@yandex.ru> wrote:
> [quote]
> To improve tracking of who did what, especially with patches that can
> percolate to their final resting place in the kernel through several
> layers of maintainers, we've introduced a "sign-off" procedure on
> patches that are being emailed around.
> [/quote]
>
> So Linux kernel had some problems due to their huge developers/maintainers list
> and they solved them by using "sign-off" procedure.
> Do Barebox have that burden of "patches that can
> percolate to their final resting place in the kernel through several
> layers of maintainers"?
>
> Also in chapter 11 there are rules which are pure bureaucratic.
> Bureaucracy is a thing of a large projects.
> Is Barebox such as big as Linux that it must have these rules too?
>

IANAL, but AFAIU those "rules which are pure bureaucratic" are a legal
framework that originated in Linux kernel and was borrowed by many
projects, Barebox among them. So to answer your question: it has
nothing to do with the size of the project, copyright and associated
laws in various shapes or forms applies to everyone. Can it be done in
a better, less verbose, more convenient form by smaller projects?
Maybe or maybe not, but I don't think the question can be answered
without performing proper legal analysis(done by law professionals, of
course) which is very costly, time consuming, etc.

> Solving inexisting problems doesn't make life easier but complicates it.
>

That's very much a truism, so you won't find much opposition to that.
The devil, as usual, is in the details of how you define what
constitutes a non-existing problem. This may sound rude and I
apologize for not coming up with a way of better delivery, but I,
personally, think that even if we were to assume that the whole SOB
mechanism is  most egregious and ridiculous legal cargo-cult,
necessity to type  "git commit -s" as  opposed "git commit -s" when
you are commiting changes is a non-existing problem.

Andrey

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2016-03-04 17:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 12:48 Aleksey Kuleshov
2016-03-04  7:11 ` Sascha Hauer
2016-03-04 10:42   ` Aleksey Kuleshov
2016-03-04 11:59     ` Antony Pavlov
2016-03-04 12:04       ` Aleksey Kuleshov
2016-03-04 13:59         ` Antony Pavlov
2016-03-04 15:03           ` Aleksey Kuleshov
2016-03-04 17:58         ` Andrey Smirnov [this message]
2016-03-04 20:47           ` Aleksey Kuleshov
2016-03-04 22:57             ` Andrey Smirnov
2016-03-05  0:04               ` Aleksey Kuleshov
2016-03-05  9:15                 ` Antony Pavlov
2016-03-05  9:27                   ` Aleksey Kuleshov

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=CAHQ1cqFcgVVnQvO6ACpNJx3Czgvdm+-eKyVGMDEYCRsVuFoutA@mail.gmail.com \
    --to=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=rndfax@yandex.ru \
    /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