mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Larry McVoy <lm@work.bitmover.com>,
	Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>,
	linux-kernel@vger.kernel.org
Subject: Re: [OFF TOPIC] BK license change
Date: Fri, 26 Apr 2002 04:22:43 +0000	[thread overview]
Message-ID: <20020426042242.A294@toy.ucw.cz> (raw)
In-Reply-To: <20020421095715.A10525@work.bitmover.com> <20020422143527.K18800@work.bitmover.com> <20020425150158.A88@toy.ucw.cz> <878z79fpzv.fsf@CERT.Uni-Stuttgart.DE> <20020427133442.A31314@work.bitmover.com>

Hi!

> > > Oh and btw how can you change licence retroactively? Those "abusers" have
> > > right to continue to use old versions under old licences...
> > 
> > BK licenses become invalid as soon as a new BK version is released
> > which contains bug fixes or behaves differently in any way.
> 
> The license says that you have to upgrade if your version will not pass
> the current regressions.  In other words, if we have fixed a problem,
> written a test case for it, shipped the fixed version and the test case,
> then yes, you need to upgrade.  If it was important enough that we wrote
> a test case for it, it's probably something you'll end up hitting sooner
> or later.
...
> The free users get an expensive product for free, but they have to
> give back by helping shake out the bugs from the current release.

...and ability to change license under their backs any time you want comes
as nice bonus, eh?

> It's really just an optimization problem.  What we've done is to optimize
> for the most that we can do for the most people.  I'm well aware that

Its really you with very nice ability to blackmail anyone using BK. "We
don't like you, so we are changing licence under your back. Either pay 000,
or you have just lost access to your revision histories." [Oh and oone 
promissed it can not be .000.000 per seat in next version.]

> In short: go build a better answer, and until you do it, how about 
> easing off on the "BK is evil corporate software" mantra a bit?  It's

BK *is* evil corporate software, with unique trapdoor capabilities, and
with unique ability to take away rights from user any time it wants.
								Pavel
PS: No need to reply, but I just could not stand "you have no rights because
we can change licence anytime" and "we are not evil" in one mail.
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2002-04-29 16:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 16:57 Larry McVoy
2002-04-21 12:12 ` Daniel Phillips
2002-04-21 16:29 ` Greg KH
2002-04-22  7:33 ` Simon Fowler
2002-04-22 21:35 ` Larry McVoy
2002-04-21 22:14   ` Daniel Phillips
2002-04-22 22:29     ` Andreas Dilger
2002-04-21 22:52       ` Daniel Phillips
2002-04-22 23:12         ` Doug Ledford
2002-04-21 23:34           ` Daniel Phillips
2002-04-22 22:22   ` Jeff Garzik
2002-04-22 22:52     ` Larry McVoy
2002-04-25 15:01   ` Pavel Machek
2002-04-27  9:30     ` Florian Weimer
2002-04-27 13:45       ` Mr. James W. Laferriere
2002-04-27 20:34       ` Larry McVoy
2002-04-26  4:22         ` Pavel Machek [this message]
2002-04-29 19:34           ` Rik van Riel
2002-04-29 19:45             ` Larry McVoy
2002-04-30  5:36               ` Pavel Janík
2002-04-27 18:13 Christoph Lameter
2002-04-27 18:25 ` Russell King
2002-04-27 18:30 ` Alexander Viro
2002-04-27 21:50   ` Martin Dalecki
2002-04-28 16:55     ` Richard Gooch

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=20020426042242.A294@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=Weimer@CERT.Uni-Stuttgart.DE \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.bitmover.com \
    /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

all inboxes | Powered by JetHome®