On Sat, Aug 21, 2010 at 14:44:08 (CEST), Arnout Engelen wrote:

> On Fri, Aug 20, 2010 at 02:57:57PM +0200, Alessio Treglia wrote:
>> I've been doing some work on the package, license information seems
>> missing in the sources.
>> Plus, no license is provided with the original tarball.
> Right - the README does contain a copyright line, states it's GPL and links to
> gnu.org, but copyright information is not in every file and the GPL text is 
> not
> included.
> Can/should we include copyright information in each file, or do we need 
> upstream to take care of this? Unless you beat me to it I'll prepare a patch 
> somewhere next week to add copyright/license information to each source file
> and send it to upstream.

The GPL contains at the end of the license text suggestion how to apply
it to your work properly. I'm including a copy of that for your

            How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper mail.

  If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:

    <program>  Copyright (C) <year>  <name of author>
    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".

  You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see

> As for not including the GPL license text, is that a problem?

Yes, because we are effectively redistributing your work. It must be
absolutely clear for any party, including the people that are interested
in redistributing work from us (think sidux, ubuntu or other derivative
distributions) what the exact redistribution terms are. Otherewise there
is a considerable risk that the archive admistrators decide to not
include your work in the archive.

Reinhard Tartler, KeyID 945348A4

pkg-multimedia-maintainers mailing list

Reply via email to