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.
I'm well aware that there are a vocal set of people who want complete
freedom to do whatever they want; I don't care to hear from them. For
the rest of you, would this change be a net positive?
-- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 23 2002 - 22:00:29 EST