Bug #53012 for Mail-ListDetector: Missing Copyright Information

Wed Dec 23 14:25:40 2009 frequency [...] cpan.org - Ticket created

Subject:

Missing Copyright Information

Hi: While packaging your module for Debian, I noticed that it doesn't seem to mention copyright or license information. In Debian we need copyright/license information for all of the packages we upload. Could you give us (replying to this bug report is fine): years of copyright, copyright holders' names, copyright holders' e-mail addresses. Unfortunately without this information we cannot upload it. This is more than just a Debian issue. I'm not a lawyer, but it's my understanding that both copyright and licensing information is vital for the continued success of open source software. Copyright is what allows you to assert a license, and a license is what ensures open source remains open source, and that users can make use of your software. A great article discussing some of this is "What is Copyleft?" by Richard Stallman: http://www.gnu.org/copyleft/ Thanks for releasing your work to the CPAN. I apologize in advance for the noise, as I understand that the last thing most authors want to deal with is legal administrivia like this. I do hope, however, that you could (in your continued generosity) help us with this request. Please also consider adding these statements to your code/package README, since we must distribute some evidence of copyright information if it is not in the source package itself. Cheers, Jonathan Yu On behalf of the Debian Perl Team

Wed Jun 30 10:27:50 2010 MSTEVENS [...] cpan.org - Correspondence added

I'm not sure if it's enough for debian, but I've made the licensing much more explicit in the README file.

Wed Jun 30 10:27:51 2010 The RT System itself - Status changed from 'new' to 'open'

Wed Jun 30 10:28:11 2010 MSTEVENS [...] cpan.org - Correspondence added

Changes made in the new 1.03 release.

Thu Jul 01 15:43:11 2010 JAWNSY [...] cpan.org - Correspondence added

Hi Michael, Sorry, I haven't had much time for my packaging work these days... I just took a look at the latest sources and notice there is still no copyright statement. We need something explicit like: Copyright 2009-2010, Michael Stevens <email@example.com> If you just leave a note here with the proper copyright statement and update it in your version control system, that's sufficient for us. We don't need you to release another version of your package. Cheers, Jonathan

Sun Jul 11 17:44:09 2010 MSTEVENS [...] cpan.org - Correspondence added

On Thu Jul 01 15:43:11 2010, JAWNSY wrote: Show quoted text

> Hi Michael, > > Sorry, I haven't had much time for my packaging work these days... I > just took a look at the latest sources and notice there is still no > copyright statement. We need something explicit like: > > Copyright 2009-2010, Michael Stevens <email@example.com> > > If you just leave a note here with the proper copyright statement and > update it in your version control system, that's sufficient for us. We > don't need you to release another version of your package.

How's this? http://github.com/mstevens/Mail--ListDetector/commit/6d796766b4860dd319f6f828382cb91d6d1d03bd Inevitably a little vague but should be accurate.

Mon Jul 19 22:43:27 2010 JAWNSY [...] cpan.org - Correspondence added

To whom this may concern: This package was recently accepted into Debian unstable. Thanks again for your contribution to CPAN, and thanks for your commitment to open source. I'm marking this bug as resolved now, as the next release will carry a copyright notice which is satisfactory to the Debian Free Software Guidelines. Cheers, Jonathan On Sun Jul 11 17:44:09 2010, MSTEVENS wrote: Show quoted text

> On Thu Jul 01 15:43:11 2010, JAWNSY wrote:

> > Hi Michael, > > > > Sorry, I haven't had much time for my packaging work these days... I > > just took a look at the latest sources and notice there is still no > > copyright statement. We need something explicit like: > > > > Copyright 2009-2010, Michael Stevens <email@example.com> > > > > If you just leave a note here with the proper copyright statement

> and

> > update it in your version control system, that's sufficient for us.

> We

> > don't need you to release another version of your package.

> > How's this? > > http://github.com/mstevens/Mail-- > ListDetector/commit/6d796766b4860dd319f6f828382cb91d6d1d03bd > > Inevitably a little vague but should be accurate.

Mon Jul 19 22:44:31 2010 frequency [...] cpan.org - Status changed from 'open' to 'resolved'