Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: paawan oza <paawan1982@yahoo.com>
To: "Robert Dewar" <dewar@adacore.com>,
	"Martin Schröder" <lionhead@onlinehome.de>
Cc: gdb@sourceware.org
Subject: Re: generic query regarding GPL and licensing terms associated with gdb
Date: Fri, 13 Aug 2010 17:50:00 -0000	[thread overview]
Message-ID: <345075.95668.qm@web112503.mail.gq1.yahoo.com> (raw)
In-Reply-To: <4C657043.3020206@adacore.com>

well, actually my intension was to understand legal, license and employer's 
right point of view.
I remember when I submit a patch for gdb, my employer used to evaluate its 
business sense and value and revenue capabilities.
then considering certain factors, they allow it to go to open source.

so I was confused having so many terms used together such as GPL, redistribute, 
modifying source code etc.
so I came up with the hyphothetical scnerio.

thank you for the inputs as licensing issues are also good to know and their 
legal consequences. : )

Regards,
Oza.



----- Original Message ----
From: Robert Dewar <dewar@adacore.com>
To: Martin Schröder <lionhead@onlinehome.de>
Cc: gdb@sourceware.org
Sent: Fri, August 13, 2010 9:48:11 PM
Subject: Re: generic query regarding GPL and licensing terms associated with gdb

Martin, what you are saying is seriously wrong!

The GPL never automatically forces disclosure of anything.

If you take GPL code, modify it by adding trade secrets,
and then distribute it without giving a GPL license, it
is not the case that somehow you have lost the trade
secrets, or that anyone is free to disclose them. That
is not at all the case.

Yes, it is true that if you grant a GPL license to someone
for the distrtibuted object, then of course there are no ytrade
secrets.

But NO ONE EVER forces you to issue a GPL license.

You most certainly can redistribute without granting
such a license (and if there are trade secrets present,
then indeed you cannot grant a valid GPL license anyway).

Now if you *DO* redistribute in this manner, you have likely
committed a copyright violation, actionable in the usual way.

In response to such a claim of copyright violation, you can
AT YOUR DISCRETION, cure the infringement in the future by
granting a GPL license, but no one forces you to do so,

The GPL NEVER forces you to disclose anything, it simply
says that if you meet certain disclosure and distribution
requirements then you have a license to redistribute, that's
all!






  reply	other threads:[~2010-08-13 17:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13  4:08 paawan oza
2010-08-13  5:04 ` Robert Dewar
2010-08-13  6:16   ` paawan oza
2010-08-13  7:56     ` Martin Schröder
2010-08-13 14:26       ` Robert Dewar
2010-08-13 15:35         ` Martin Schröder
2010-08-13 16:18           ` Robert Dewar
2010-08-13 17:50             ` paawan oza [this message]
2010-08-13 18:15             ` Martin Schröder
2010-08-24 21:13               ` Steffen Dettmer
2010-08-24 21:33                 ` Robert Dewar
2010-08-27 11:38                   ` Steffen DETTMER
2010-08-15 16:40           ` Florian Weimer
2010-08-13 14:24     ` Robert Dewar
2010-08-13 15:50 ` Tom Tromey

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=345075.95668.qm@web112503.mail.gq1.yahoo.com \
    --to=paawan1982@yahoo.com \
    --cc=dewar@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=lionhead@onlinehome.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox