Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-trustees
Navigation:
Lists: gentoo-trustees: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-trustees@g.o
From: Donnie Berkholz <spyderous@g.o>
Subject: Re: copyright stuff
Date: Wed, 13 Jul 2005 04:33:27 -0700
On Tue, 2005-07-12 at 14:58 -0700, Deedra Waters wrote:
> 1. We only worry about copyrighting code that gentoo actually owns,
> mainly catalyst, portage, the installer and things  like that.
> Also any documentation that gentoo has written along with the utilities
> that may have been written for portage etc etc.

That makes sense to me, since the vast majority of ebuilds aren't really
copyrightable anyway.

> 2. it would be a co-ownership basically, meaning thatif i wrote
> documentation or parts of documentation, i would retain the rights to
> those docs, but gentoo owns the entire thing.

I don't understand this. Could you clarify?

> 3. only gentoo would have the ability to sue. This is more a legal
> thing, but basically it's so that if we ever had to go into law to
> defend the copyright, the other person can't force us to drag  all of
> our developers into court.

I'm a little confused about what exactly you're proposing. Is it an
exclusive license, assigning a share of the rights or something else
altogether?

Thanks,
Donnie
Attachment:
signature.asc (This is a digitally signed message part)
Replies:
Re: copyright stuff
-- Deedra Waters
References:
copyright stuff
-- Deedra Waters
Navigation:
Lists: gentoo-trustees: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: copyright stuff
Next by thread:
Re: copyright stuff
Previous by date:
Re: copyright stuff
Next by date:
Re: copyright stuff


Updated Jun 17, 2009

Summary: Archive of the gentoo-trustees mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.