SA Bugzilla – Bug 3128
Should AUTHOR be the project now?
Last modified: 2004-03-12 12:29:49 UTC
I understand that CPAN does allow projects to be authors, so perhaps we should change the ownership of the CPAN module to be the SpamAssassin project. The same question applies for the RPM package since it is not particular to any distribution. I believe Debian requires a Debian Developer, so that should probably remain owned by Duncan, although maybe we should own our own .deb package and Duncan can continue owning the official Debian package -- that is Debian's prerogative anyway.
Subject: Re: New: Should AUTHOR be the project now? On Fri, Mar 05, 2004 at 08:29:20PM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote: > I understand that CPAN does allow projects to be authors, so perhaps we should > change the ownership of the CPAN module to be the SpamAssassin project. +1 > The same question applies for the RPM package since it is not particular to > any distribution. I believe Debian requires a Debian Developer, so that should Sure. I happen to just build the RPMs on my machine, which means it's signed and such with my GPG key. It'd be pretty trivial to do it with the release key instead.
+1 to both. (Even though it may mean less goodies via Amazon ;)
Or should it be "Apache Software Foundation"? As far as Debian goes, I'm just the Maintainer. The "author" information goes in /usr/share/doc/spamassassin/copyright: Upstream Authors: Justin Mason <jm@jmason.org>, Craig Hughes <craig@hughes-family.org> Daniel Quinlan <quinlan@pathname.com> Theo van Dinter <felicity@kluge.net> and others For 3.0.0 I'm going to have to rewrite this file to update with the new license, etc, and I'll be happy to add the rest of the committers or ASF or SpamAssassin Project, whatever. (I don't know why I didn't originally include all the committers) I don't see any benefit of SpamAssassin providing it's own .deb, but I'd be interested in your reasoning.
Subject: Re: Should AUTHOR be the project now? > For 3.0.0 I'm going to have to rewrite this file to update with the > new license, etc, and I'll be happy to add the rest of the committers > or ASF or SpamAssassin Project, whatever. (I don't know why I didn't > originally include all the committers) Yeah, we can (and I think should) probably just list the project as a whole rather than individual authors. > I don't see any benefit of SpamAssassin providing it's own .deb, but > I'd be interested in your reasoning. It might be convenient for people running woody. I've been using the SpamAssassin 2.63 package from backports.org. We could just link to that, I suppose. Daniel
fixed in Makefile.PL closing as FIXED