socioboard / Socioboard-5.0

Socioboard is world's first and open source Social Technology Enabler. Socioboard Core is our flagship product.
http://www.socioboard.org
Other
1.17k stars 365 forks source link

Missing GPL-3.0-or-later license headers #247

Open TechnologyClassroom opened 3 years ago

TechnologyClassroom commented 3 years ago

I see the GPLv3 LICENSE file was added in https://github.com/socioboard/Socioboard-5.0/pull/245 and there is a bit more to do with this issue. The https://socioboard.org/license/ page says, "The GPLv3 (or later) from the Free Software Foundation is the license that the Socioboard software is under its text follows." The -or-later part of GPL-3.0-or-later is not specified in the git repo of this project.

To complete the "(or later)" portion of the license specification, typically this is done by adding the license header information according to the instructions in the last section How to Apply These Terms to Your New Programs of the license to the README.md file and any additional files that have code in them throughout the project: https://www.gnu.org/licenses/gpl-3.0.html#howto

The README license header would look something like this:

License
=======

    Socioboard - Social Technology Enabler
    Copyright (C) 2014-2021 Socioboard.org

    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 <https://www.gnu.org/licenses/>.

The license headers for each source file would have the same body text and follow the comment syntax of the language they are written in.

Adding the license headers to the README file is the easiest lowest hanging fruit part of this issue. Adding the license headers to all of the code files is more tedious. I would be interested in helping out with this tedious task if you would like my help with it. My last PR in the licensing area sat vacant for 2 years and then was closed so I will hold off on helping unless you want me to help out with this.

sureshbabu1995 commented 3 years ago

Hi, sorry for the inconvenience of your old PR closing, we closed all as a part to recreate new flow,

now we're a little busy setting up the servers and some other works,

Please check with it, if you would like to help us here we always welcome you, we'll be reviewing your PR and we'll merge it if everything is fine.

socioboard commented 3 years ago

Hi @TechnologyClassroom Please Check now, If need any modification please Give the Updates or Give a PR with the updates, I'll be reviewing and update you

TechnologyClassroom commented 3 years ago

That is not what I suggested to do at all. I made a different issue as that is completely different.