From: simon@himi.org (Simon Fowler)
To: linux-kernel@vger.kernel.org
Cc: Larry McVoy <lm@work.bitmover.com>
Subject: Re: [OFF TOPIC] BK license change
Date: Mon, 22 Apr 2002 17:33:44 +1000 [thread overview]
Message-ID: <20020422073344.GA7376@himi.org> (raw)
In-Reply-To: <20020421095715.A10525@work.bitmover.com>
[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]
On Sun, Apr 21, 2002 at 09:57:15AM -0700, Larry McVoy wrote:
> Well, now seems like a great time to discuss this. Ha.
>
> It's come to our attention that commercial companies are abusing BK under
> the openlogging rules. To avoid paying for the product, they either put
> in no comments or obscure comments. That is a violation of the license,
> but good luck proving that they are doing it on purpose.
>
> The real issue is that we know from past history that companies make
> changes to GPLed software and then delay access to those changes as
> long as they can (the GPL allows for a "reasonable" amount of lag,
> whatever that is).
>
> The intent of the openlogging requirement was to allow people to work
> out in the open on free software, at no charge. The intent was never
> to allow people to work on free software without giving their changes
> back. I'm not commenting on people's rights to hide their changes,
> they can do whatever they want, but I *am* saying that we don't have
> support closed use for free.
>
> I'm considering a change to the BKL which says that N days after a
> changeset is made, that changeset (and its ancestory) must be available
> on a public bk server. In other words, put a hard limit on how long
> you may hide.
>
> The time period has to be long enough to cover security fixes, DaveM
> raised that issue. I'm thinking 90 days.
>
> Note: public server is not limited to bkbits.net. Any public server is
> fine, so long as it is stable, well known, and available ~95% of the time.
>
Does 'public server' imply that the server is running bkd for
anonymous access? I have several small projects under bk that I keep
in repositories that are accesible to people with an account on my
server, but not to anyone else - would this be a license violation?
(I have no problem with openlogging - it just encourages me to make
/intelligent/ checkin comments, or some approximation thereof)
I'd prefer not to have to run bkd on my server if I don't /have/ to.
Minimising the number of services available to be cracked, and all
that . . .
Simon Fowler
--
PGP public key Id 0x144A991C, or ftp://bg77.anu.edu.au/pub/himi/himi.asc
(crappy) Homepage: http://bg77.anu.edu.au
doe #237 (see http://www.lemuria.org/DeCSS)
My DeCSS mirror: ftp://bg77.anu.edu.au/pub/mirrors/css/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-04-22 7:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 16:57 [OFF TOPIC] BK license change Larry McVoy
2002-04-21 12:12 ` Daniel Phillips
2002-04-21 16:29 ` Greg KH
2002-04-22 7:33 ` Simon Fowler [this message]
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
2002-04-29 19:34 ` Rik van Riel
2002-04-29 19:45 ` Larry McVoy
2002-04-30 5:36 ` Pavel Janík
-- strict thread matches above, loose matches on Subject: below --
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=20020422073344.GA7376@himi.org \
--to=simon@himi.org \
--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