From: bjorn@mork.no (Bjørn Mork)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel contributions from organisations and individual privacy
Date: Sat, 13 Jun 2015 17:40:19 +0200 [thread overview]
Message-ID: <87381vmxb0.fsf@nemi.mork.no> (raw)
In-Reply-To: <4E5779AD88B2F040B8A7E83ECF544D1A603600@SJCPEX01CL03.citrite.net> (Jeff Haran's message of "Fri, 12 Jun 2015 23:29:51 +0000")
Jeff Haran <Jeff.Haran@citrix.com> writes:
> What is the downside to a large company for violating GPL?
Losing all rights to the software in question forever is probably the
largest downside. If we talk about the Linux kernel (as I assume we do
in this forum) then I have a hard time believing any company can survive
that. Note that loosing the rights to use the Linux kernel will not
only affect the products your company produce, but also your rights to
*use* any Linux based product. The legal department would also end up
with a limited selection of phones they could legally use.
So, I'd say the downside is infinite.
Why do companies still risk this? For little or no gain whatsoever? Or
even negative gain, since we all know that you get many times back for
every contribution you make to open source.
I guess it is the result of tech staff and legal staff not talking
together. The legal staff will hopefully have some understanding of the
GPL, and know that violating it leaves them without any rights to the
software in question. But they will probably assume that those rights
are for sale, or that it is possible to buy the rights to an equivalent
software product. The technical staff will know that this is impossible,
but they are probably not aware of the finer details of the GPL. So
there you go: Noone understand the full consequences.
Bj?rn
next prev parent reply other threads:[~2015-06-13 15:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 9:19 Kernel contributions from organisations and individual privacy Chris Packham
2015-06-11 4:58 ` Jason Ball
2015-06-11 5:10 ` Chris Packham
2015-06-11 5:19 ` Ruben Safir
2015-06-11 14:28 ` Greg KH
2015-06-11 14:41 ` Ruben Safir
2015-06-11 15:38 ` Greg KH
2015-06-11 16:39 ` Ruben Safir
2015-06-11 17:54 ` Greg KH
2015-06-11 17:57 ` Greg KH
2015-06-11 23:26 ` Ruben Safir
2015-06-11 23:37 ` Rik van Riel
2015-06-11 23:55 ` Ruben Safir
2015-06-12 0:13 ` Jeff Haran
2015-06-12 1:28 ` Rik van Riel
2015-06-12 23:29 ` Jeff Haran
2015-06-13 15:40 ` Bjørn Mork [this message]
2015-06-13 19:08 ` Ruben Safir
2015-06-15 23:08 ` Jeff Haran
2015-06-15 23:55 ` Rik van Riel
2015-06-16 16:23 ` Jeff Haran
2015-06-13 16:23 ` Rik van Riel
2015-06-14 21:18 ` Valdis.Kletnieks at vt.edu
[not found] ` <B424B28F-AB7E-4972-95BB-FF91D85D0FED@gmail.com>
2015-06-14 23:29 ` Valdis.Kletnieks at vt.edu
[not found] ` <557E0FF7.1000607@gmail.com>
2015-06-15 2:08 ` Valdis.Kletnieks at vt.edu
2015-06-12 0:52 ` Greg KH
2015-06-12 3:31 ` Valdis.Kletnieks at vt.edu
2015-06-12 4:39 ` Ruben Safir
2015-06-12 7:18 ` Valdis.Kletnieks at vt.edu
2015-06-11 13:13 ` Rik van Riel
2015-06-11 14:27 ` Greg KH
2015-06-11 14:25 ` Greg KH
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=87381vmxb0.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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.