Permalink
Browse files

RM packages with missing or incompatible license.

Packages on MELPA must be compatible with GNU GPLv3 and preferably
should have a license which will avoid issues in the future (GPLv3+).

Until the problems are fixed we can no longer distribute them.
  • Loading branch information...
milkypostman committed Aug 18, 2017
1 parent 3c8683e commit c3366117f3399660509f62849a88dc8be56a1fef
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.

This file was deleted.

Oops, something went wrong.

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.
View

This file was deleted.

Oops, something went wrong.

18 comments on commit c336611

@vyp

This comment has been minimized.

Show comment
Hide comment
@vyp

vyp Aug 18, 2017

Contributor

🎉🎉

Contributor

vyp replied Aug 18, 2017

🎉🎉

@purcell

This comment has been minimized.

Show comment
Hide comment
@purcell
Member

purcell replied Aug 18, 2017

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Aug 18, 2017

Member

I have restored 6 packages already, and I will continue to do so as more of the removed packages are being released under a GPLv3 compatible license. I will do that in batches, so there will be delays.

Some of the removed and re-added packages were re-licensed after they were removed (or shortly before).

But a few of the removed packages actually already were GPLv3-compatible. However these packages specify the license in a way that is not easily detectable by tools and/or they don't do so in the library, which is problematic because an Elpa package does only contain the library, not the README or LICENSE. If your package is one of those, then please put the actual license or permission statement in the library header.

For GPLv3+:

;; This file 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, or (at your option)
;; any later version.

;; This file 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/>.

For MIT:

;; Permission is hereby granted, free of charge, to any person
;; obtaining a copy of this software and associated documentation
;; files (the "Software"), to deal in the Software without
;; restriction, including without limitation the rights to use, copy,
;; modify, merge, publish, distribute, sublicense, and/or sell copies
;; of the Software, and to permit persons to whom the Software is
;; furnished to do so, subject to the following conditions:

;; The above copyright notice and this permission notice shall be
;; included in all copies or substantial portions of the Software.

;; THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
;; EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
;; MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
;; NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
;; BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
;; ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
;; CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
;; SOFTWARE.

In both cases you should also add a line

;; Copyright (c) YEAR  COPYRIGHT HOLDER

If you don't want to add the permission statement or license to library headers because you find that to be too noisy, then please add a header keyword instead.

For GPLv3+ one of:

;; License: GNU General Public License version 3, or (at your option) any later version
;; License: GNU General Public License version 3, or any later version
;; License: GNU GPL version 3, or (at your option) any later version
;; License: GPL version 3, or (at your option) any later version
;; License: GPL version 3, or any later version
;; License: GPL v3, or (at your option) any later version
;; License: GPL v3, or any later version
;; License: GPL-3+

For MIT:

;; License: MIT
Member

tarsius replied Aug 18, 2017

I have restored 6 packages already, and I will continue to do so as more of the removed packages are being released under a GPLv3 compatible license. I will do that in batches, so there will be delays.

Some of the removed and re-added packages were re-licensed after they were removed (or shortly before).

But a few of the removed packages actually already were GPLv3-compatible. However these packages specify the license in a way that is not easily detectable by tools and/or they don't do so in the library, which is problematic because an Elpa package does only contain the library, not the README or LICENSE. If your package is one of those, then please put the actual license or permission statement in the library header.

For GPLv3+:

;; This file 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, or (at your option)
;; any later version.

;; This file 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/>.

For MIT:

;; Permission is hereby granted, free of charge, to any person
;; obtaining a copy of this software and associated documentation
;; files (the "Software"), to deal in the Software without
;; restriction, including without limitation the rights to use, copy,
;; modify, merge, publish, distribute, sublicense, and/or sell copies
;; of the Software, and to permit persons to whom the Software is
;; furnished to do so, subject to the following conditions:

;; The above copyright notice and this permission notice shall be
;; included in all copies or substantial portions of the Software.

;; THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
;; EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
;; MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
;; NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
;; BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
;; ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
;; CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
;; SOFTWARE.

In both cases you should also add a line

;; Copyright (c) YEAR  COPYRIGHT HOLDER

If you don't want to add the permission statement or license to library headers because you find that to be too noisy, then please add a header keyword instead.

For GPLv3+ one of:

;; License: GNU General Public License version 3, or (at your option) any later version
;; License: GNU General Public License version 3, or any later version
;; License: GNU GPL version 3, or (at your option) any later version
;; License: GPL version 3, or (at your option) any later version
;; License: GPL version 3, or any later version
;; License: GPL v3, or (at your option) any later version
;; License: GPL v3, or any later version
;; License: GPL-3+

For MIT:

;; License: MIT
@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Aug 18, 2017

Member

Pinging the associated authors

Could you please also ping those affected by cf92ce1.

Member

tarsius replied Aug 18, 2017

Pinging the associated authors

Could you please also ping those affected by cf92ce1.

@timvisher

This comment has been minimized.

Show comment
Hide comment
@timvisher

timvisher Aug 18, 2017

Contributor

My packages should be good now iiuc. Let me know if there's more I need to do.

Contributor

timvisher replied Aug 18, 2017

My packages should be good now iiuc. Let me know if there's more I need to do.

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Aug 18, 2017

Member

Thanks @timvisher! Looks good.

Member

tarsius replied Aug 18, 2017

Thanks @timvisher! Looks good.

@swflint

This comment has been minimized.

Show comment
Hide comment
@swflint

swflint Aug 18, 2017

Contributor

And pushover.el is up-to-spec!

Contributor

swflint replied Aug 18, 2017

And pushover.el is up-to-spec!

@quodlibetor

This comment has been minimized.

Show comment
Hide comment
@quodlibetor

quodlibetor Aug 19, 2017

Contributor

py-gnitset is also correct

Contributor

quodlibetor replied Aug 19, 2017

py-gnitset is also correct

@xahlee

This comment has been minimized.

Show comment
Hide comment
@xahlee

xahlee Aug 21, 2017

Contributor

is it possible to use just a GPLv3 license? Thanks.

Contributor

xahlee replied Aug 21, 2017

is it possible to use just a GPLv3 license? Thanks.

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Aug 21, 2017

Member

is it possible to use just a GPLv3 license? Thanks.

Yes, those are the preferred licensing terms. So I am not quite sure why you are asking that - please rephrase if this isn't the answer you were looking for. Please follow the instructions in c336611#commitcomment-23721000 to make sure you specify those licensing terms in a way that is guaranteed to be detectable by tools.

Member

tarsius replied Aug 21, 2017

is it possible to use just a GPLv3 license? Thanks.

Yes, those are the preferred licensing terms. So I am not quite sure why you are asking that - please rephrase if this isn't the answer you were looking for. Please follow the instructions in c336611#commitcomment-23721000 to make sure you specify those licensing terms in a way that is guaranteed to be detectable by tools.

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Aug 21, 2017

Member

Oh! GPLv3 and only v3, not GPLv3 or later. Sorry I overlooked that. Your question makes much more sense now that I have realized that ;-)

Yes, that is also good. Just drop the , or (at your option) any later version part.

Member

tarsius replied Aug 21, 2017

Oh! GPLv3 and only v3, not GPLv3 or later. Sorry I overlooked that. Your question makes much more sense now that I have realized that ;-)

Yes, that is also good. Just drop the , or (at your option) any later version part.

@xahlee

This comment has been minimized.

Show comment
Hide comment
@xahlee

xahlee Aug 21, 2017

Contributor

@tarsius thanks! I changed them. Let me know if there's issues.

Contributor

xahlee replied Aug 21, 2017

@tarsius thanks! I changed them. Let me know if there's issues.

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Aug 21, 2017

Member

@swflint, @quodlibetor, @xahlee Thanks a lot!

I am currently doing an Emacsmirror update run, which takes a few hours. When that is done I will re-add your package(s) to Melpa.

Member

tarsius replied Aug 21, 2017

@swflint, @quodlibetor, @xahlee Thanks a lot!

I am currently doing an Emacsmirror update run, which takes a few hours. When that is done I will re-add your package(s) to Melpa.

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Aug 22, 2017

Member

@swflint could you please add a license to i3wm?

Member

tarsius replied Aug 22, 2017

@swflint could you please add a license to i3wm?

@swflint

This comment has been minimized.

Show comment
Hide comment
@swflint

swflint Aug 22, 2017

Contributor

@tarsius Done.

Contributor

swflint replied Aug 22, 2017

@tarsius Done.

@kostajh

This comment has been minimized.

Show comment
Hide comment
@kostajh

kostajh Aug 22, 2017

Contributor

@tarsius kostajh/harvest.el is up-to-date now

Contributor

kostajh replied Aug 22, 2017

@tarsius kostajh/harvest.el is up-to-date now

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius
Member

tarsius replied Aug 23, 2017

@swflint @kostajh Thanks!

@aurelienbottazini

This comment has been minimized.

Show comment
Hide comment
Please sign in to comment.