Re: BK kernel workflow

Larry McVoy
2004-10-31T17:48:39Z

On Sun, Oct 31, 2004 at 12:05:53AM +0100, Alan Cox wrote:
> On Sul, 2004-10-31 at 00:46, Larry McVoy wrote:
> > a lot of people think that then lets fix that. By the way, with all
> > due respect, Andrea & Roman are not "reasonable" people in this context.
> > Let's find some reasonable people who are not BK users and make sure they
> > are comfortable with what is going on. Alan Cox, Al Viro, who else?
> > I don't really care if it is non-BK users, BK users, or a combination,
> > I just care that there is some sanity in the discussion.
> >
> > Is there any need for this or is this a non-issue?
>
> Seems a total non issue to me. If you did utterly evil things then your
> statements archived in email so far would be more than sufficient.

Cool. But I'd like to clarify something someone else said, for the record.

> > I think you could make a compelling argument that the linux
> > kernel history
> > metadata is *not* covered under the GPL, and hence can be
> > restricted by licensing.

> That's an interesting argument. I think you could argue that a BK
> repository is an aggregation of metadata and the kernel source, and
> therefore only the kernel source needs to be distributed. IANAL, this
> question has now gotten into territory in which I don't feel comfortable
> offering an opinion.

There are really three distinct chunks of information in BK:
- the source code under management
- the metadata created by users, i.e., checkin comments. We also
consider user names, dates, and timestamps to be created by users
even though BK itself does that for you.
- the metadata created by BK

The license and ownership of kernel source code managed by BK has nothing
to do with BK nor the BK license.

There is a question as to whether the metadata created by the users
is GPLed. It's not because it falls under the separate works part
of the GPL. If that metadata were GPLed then your user name in an
inode is GPLed if you were putting a GPLed file into a filesystem.
That's a boundary you aren't going to be able to cross no matter how
hard you try (note: you can start arguing about this and I'll ignore
you, we've been over this).

Just to make our position clear, consider this a formal declaration that
we make no claims of ownership of user created metadata, as defined above,
and impose no restrictions on its use. I suspect that this declaration
isn't needed, you ought to have rights to your own name and checkin
comments, but let's make sure that there is no confusion about that.

There is the question of metadata created by BK. That's also not GPLed
for the same reasons. This metadata is more like the block pointers in
a file system. While you may use BK, if you have a license, to dig out
your data and the user created metadata, you aren't entitled to expose the
internal BK metadata. That falls under the reverse engineering clause,
non-compete clause, etc. I realize you don't like this if you are trying
to create a competing product but that's the way things are.

Please respect that just as we are respecting your rights to your data.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com