add GPL? licence and shebangs to the project. about cherrymusic

[tilboerner]

Licenses:

• jQuery: dual GPL and MIT (=X11)
• jPlayer: dual GPL and MIT
• cherryPy: BSD

All of those are equal to or more permissible than GPL, which makes them compatible with GPL. I'd say we go with GPL, because it keeps the thing open and free.

Here's a draft of the file header:

#!/usr/bin/python3
#
# CherryMusic standalone music server
# Copyright (c) 2012 ${author}
#
# licensed under GNU GPL version 3 (or later)
# see http://www.gnu.org/licenses/
#
# http://fomori.org/cherrymusic/
# http://github.com/devsnd/cherrymusic/

I'm not sure in what form and place jPlayer et al. and their licenses must be mentioned.

We should put the full license text into the project root.

Quote from there:

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
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    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' andshow 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".

This is way too long and verbose.