All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fix for a build ?
Date: Tue, 04 May 2010 20:44:40 +0200	[thread overview]
Message-ID: <20100504184441.0EB6FB076D3@gemini.denx.de> (raw)
In-Reply-To: <n2m3e45db431005040739m7ff0eb77x712f3e39681f44f8@mail.gmail.com>

Dear Sylvain Lamontagne,

In message <n2m3e45db431005040739m7ff0eb77x712f3e39681f44f8@mail.gmail.com> you wrote:
> 
> Ok, I am now in the seat of someone that could push the idea of
> putting the next platform we develop into the mainline. But other
> MBA/Finance/Manager persons that really take decisions will surely ask
> my department why I would like to give internal informations of our
> product in a way that any of our competitors could get it easily. How
> could I give them an answer that would be aligned with the philosophy
> ?

First, U-Boot is covered by the GPL, so you will have to give the
full sources anyway to any of your customers who asks for it - even
if it's one of your direct competitors.

Second, do you really think there is any intellectual property in a
port of U-Boot that is worth such protection?  If so, you better write
your own proprietary boot loader from scratch.

Third: according to Ohloh (http://www.ohloh.net/p/u-boot) it would
cost you (or your company) some 270+ man-years or $_15,000,000 to
develop something like U-Boot from scratch. You got all this code
completely for free, so it seems only just and equitable that you
return the little you added to the community, too.

> > I did not intend to be rude, but I have to admit that your attitude
> > is not exactly in line how community projects like this work.
> Then I'm sorry, but for me this project sounds like it is directed by
> a bunch of elitist who would not accept someone that don't already
> know how the project work. Criticizing and judging questions asked by
> people that may never have work on or with  something like U-Boot
> before. If you are afraid of getting to much dumb questions then this
> means that the documentation and the FAQ from the U-Boot website could
> be improve in a way that new comers would find easily the informations
> they need.

All the documentation is in a wiki - please feel free to add any
parts you consider missing.


Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
People seldom know what they want until you give them what  they  ask
for.

  reply	other threads:[~2010-05-04 18:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 13:51 [U-Boot] Fix for a build ? Sylvain Lamontagne
2010-05-03 18:52 ` Mike Frysinger
2010-05-03 20:14   ` Sylvain Lamontagne
2010-05-03 20:37     ` Wolfgang Denk
2010-05-03 20:34 ` Wolfgang Denk
2010-05-03 21:44   ` Mike Frysinger
2010-05-03 22:02   ` Sylvain Lamontagne
2010-05-03 23:30     ` Mike Frysinger
2010-05-04  7:56     ` Wolfgang Denk
2010-05-04 14:39       ` Sylvain Lamontagne
2010-05-04 18:44         ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-05-05 10:32 Igor Luri
2010-05-05 15:55 ` Sylvain Lamontagne

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=20100504184441.0EB6FB076D3@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.