[lkml]   [2002]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ReiserFS Bug Fixes 3 of 6 (Please apply all 6)
Larry McVoy wrote:

>>Another model you might consider, one which would probably make you more
>>money, make us happier, and better avoid "freeloaders", would be to make
>>bitkeeper free for use with free software only. This would be rather
>>similar to what I use for reiserfs, which is free for use with free
>>operating systems only, and available for a fee for all others. It
>>allows you to "do unto others as they would do unto you" (The Reiser
>>Rule ;-) ).
>We are dealing with various commercial organizations who play games
>with the checkin comments so that they can use BK for free and not give
>up any information. Technically, it's a violation of the license if
>they do that, but proving that they are doing it just isn't worth it.
>What I'm tempted to do is to figure out a reasonable way to force free
>uses to make their changes publically available.

This would be good to do.

> More like sourceforge,
>if you use their service, anyone can get at your source. The problem
>is that we can't force all the changes out into the open immediately,
>people may have good reasons to hide (security changes, for example),
>along with bad reasons (they're freeloaders).
Better this inconvenience than hiding the source code....

>Allowing free use of BK with free software only doesn't solve anything.
>We have lots of people doing that and still hiding their changes
>behind empty (or "fixed") checkin comments. It's only the commercial
>organizations who are a problem. I'd really like to force those changes
>out in the open if they aren't going to pay. The whole point of the
>openlogging stuff was to get people to work out in the open.
Umm, I usually use "comment" as my comment for anything not a bugfix,
but it has nothing to do with your license and fear of people reading
it, it is purely that my comments go into the source code unless it is a
bugfix (bugfixes should have user emails attached to them, etc.).

>I've thought a bit about some sort of answer which addresses this and
>I'm curious to see what people would think if the rule were that your
>changes had to show up on a public server within a given time period
>(a month? 2 months? 3 months?). In other words, factor in a reasonable
>ability to work in privacy but make it be limited enough that it only
>works for truly free software.
I'd be happy.

>My definition of free software is anything where the source is publically
>available. It's sometimes called "Open Source". Open source software
>where you can't get at the source is lame.
Call it accessible source, this is my term which allows for pay for use
software whose source code is available for all to read. If you want to
require the software to be free as well, then call it free and
accessible source. (But please don't forbid it from being pay for use
as well as free like reiserfs is.....)

I believe that the antitrust laws should be interpreted as requiring
software source code to be accessible for any software for which there
might be a market for improvements to it. This of course assumes that
the government has any intention of enforcing the anti-trust laws....
which the current administration surely does not.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.063 / U:14.368 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site