Decide on a license

[notslang]

I'm thinking of using the GPL 3.0 (http://www.gnu.org/licenses/gpl-3.0.txt) (strong copyleft). Does anyone else have an opinion on this?

[nightpool]

Sounds fine. You want to implement?

[notslang]

Sure... i'll add it. However, I don't really want to add it to the top of all files (just one LICENSE file). It seems redundant and pretty annoying. Is there any way to get around this?

[nightpool]

No. You have to have a short license block at the top of all licensed files. You need to release each individual file, as every file is protected separately under copyright. It'll be something like this

Copyright 2012 CORE Robotics 2062

This file is part of the CORE Scouting Database System.

The CORE Scouting Database System 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.

The CORE Scouting Database System 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 the CORE Scouting Database System.  If not, see <http://www.gnu.org/licenses/>.

[notslang]

most of the answers here say it's fine to just put one in the project http://stackoverflow.com/questions/845895/putting-license-in-each-code-file

but i haven't found one from a definitive, legal, source

On Tue, Dec 4, 2012 at 8:47 AM, Evan notifications@github.com wrote:

. You have to have a short license block at the top of all licensed files. You need to release each individual file, as every file is protected separately under copyright. It'll be something like this

[nightpool]

My information and template comes from the FSF, which writes GPL. Also, we would be putting the license just once in the project; the thing that goes in each file is called the license notice, and is there so people can find the license easily.

On Tue, Dec 4, 2012 at 8:55 AM, Sean Lang notifications@github.com wrote:

most of the answers here say it's fine to just put one in the project http://stackoverflow.com/questions/845895/putting-license-in-each-code-file

but i haven't found one from a definitive, legal, source

On Tue, Dec 4, 2012 at 8:47 AM, Evan notifications@github.com wrote:

. You have to have a short license block at the top of all licensed files. You need to release each individual file, as every file is protected separately under copyright. It'll be something like this

— Reply to this email directly or view it on GitHubhttps://github.com/2062/CORE-Scouting-Server/issues/3#issuecomment-10999840.

[notslang]

yeah, i know that it would just require a short header... it's just kinda annoying

On Tue, Dec 4, 2012 at 9:28 AM, Evan notifications@github.com wrote:

My information and template comes from the FSF, which writes GPL. Also, we would be putting the license just once in the project; the thing that goes in each file is called the license notice, and is there so people can find the license easily.

On Tue, Dec 4, 2012 at 8:55 AM, Sean Lang notifications@github.com wrote:

most of the answers here say it's fine to just put one in the project

http://stackoverflow.com/questions/845895/putting-license-in-each-code-file

but i haven't found one from a definitive, legal, source

On Tue, Dec 4, 2012 at 8:47 AM, Evan notifications@github.com wrote:

. You have to have a short license block at the top of all licensed files. You need to release each individual file, as every file is protected separately under copyright. It'll be something like this

— Reply to this email directly or view it on GitHub< https://github.com/2062/CORE-Scouting-Server/issues/3#issuecomment-10999840>.

— Reply to this email directly or view it on GitHubhttps://github.com/2062/CORE-Scouting-Server/issues/3#issuecomment-11001175.