kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: bernd@petrovitsch.priv.at (Bernd Petrovitsch)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [OT] Can a commercial company use software with GPLv2 for free?
Date: Fri, 16 Nov 2012 13:09:52 +0100	[thread overview]
Message-ID: <1353067796.22416.134.camel@thorin> (raw)
In-Reply-To: <CAC-1EbafB3ydJWBcYBGQM1RRyp78AHZxJNhrJg3KNA-=B2DXiQ@mail.gmail.com>

Hi!

On Don, 2012-11-15 at 23:34 +0200, Mohammed Gamal wrote:
[...]
> It also depends on what you mean by 'use'. If it is 'using' the GPLv2

Yes - and "use" can mean a lot in that context: From pure in-house usage
(e.g. a CVS server used for a proprietary product) over providing CVS
repos to the outside (e.g. some hypothetical company which just sells
CVS repo access and support) - with or without patching it - up to
(re-)using sourcecode of it (or the complete sourcecode) in some other
own product.
[ List may not be complete;-) ]

So without exact knowing, what they do with it (and what not) in what
way, one cannot write more specific hints than - basically - "follow the
rules of the license".

GPLv2 is actually short and simple enough to be readable and
understandable by not-lawyers.
There are books providing more explanation and - of course - the
Internet is full of discussions about this .....

[ Full quote deleted ]

	Bernd
-- 
Bernd Petrovitsch                  Email : bernd at petrovitsch.priv.at
                     LUGA : http://www.luga.at

  reply	other threads:[~2012-11-16 12:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 18:10 [OT] Can a commercial company use software with GPLv2 for free? hz hanks
2012-11-15 18:27 ` Bjørn Mork
2012-11-15 21:26 ` Bernd Petrovitsch
2012-11-15 21:34   ` Mohammed Gamal
2012-11-16 12:09     ` Bernd Petrovitsch [this message]
2012-11-16 13:36     ` Greg Freemyer

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=1353067796.22416.134.camel@thorin \
    --to=bernd@petrovitsch.priv.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).