public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] ebuild copyright attribution?
@ 2004-01-07 16:13 Chris Bainbridge
  2004-01-07 16:36 ` Jon Portnoy
  0 siblings, 1 reply; 7+ messages in thread
From: Chris Bainbridge @ 2004-01-07 16:13 UTC (permalink / raw
  To: Gentoo Dev

Daniel Robbins said in August:

"I've been trying to get people to keep their names in the copyright line for
over a year, but no one has really started doing it. To my knowledge, it is
better to have multiple official copyright holders for GPL code than just a
single copyright holder. I would like all our ebuilds to have a copyright
like this:

# Copyright 2003 Gentoo Technologies, Joe User, and others (see cvs
# changelog.) Distributed under the GPL version 2.

I don't see why this would be a problem for anyone, and makes a lot more
sense than what we are doing now."

Since then I've submitted all my ebuilds with dual copyright lines, but never 
once been accepted as that. I've been told that the automated tools don't 
like a different line, and that "Seemant says "dual copyrights" are only 
accepted for special circumstances, e.g. when you're employed to do the work 
by an external entitity". 

On another note, it would be nice to see ebuilds accepted if there are no bug 
reports after a while.. I have ebuilds for new packages still sitting in 
bugzilla after half a year.


--
gentoo-dev@gentoo.org mailing list


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2004-01-08 16:56 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-07 16:13 [gentoo-dev] ebuild copyright attribution? Chris Bainbridge
2004-01-07 16:36 ` Jon Portnoy
2004-01-08 10:37   ` Thomas de Grenier de Latour
2004-01-08 14:41     ` John Nilsson
2004-01-08 15:59     ` Jon Portnoy
2004-01-08 16:36       ` Thomas de Grenier de Latour
2004-01-08 10:41   ` Alexander Futasz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox