Re: How to name the license in the spec

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 24, 2020 at 03:51:27PM -0400, Richard Fontana wrote:
On Mon, Aug 24, 2020 at 7:18 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote:

On Mon, Aug 24, 2020 at 6:30 AM Jaroslav Skarvada <jskarvad@xxxxxxxxxx> wrote:
>
>
>
> ----- Original Message -----
> > Am Montag, den 24.08.2020, 03:18 -0400 schrieb Jaroslav Skarvada:
> > > Hi,
> > >
> > > the code contains the following text:
> > >  * <db@xxxxxxxxxxx> wrote this file.  As long as you retain this
> > > notice you
> > >  * can do whatever you want with this code, except you may not
> > >  * license it under any form of the GPL.
> > >  * A postcard or QSL card showing me you appreciate
> > >  * this code would be nice. Diane Bruce va3db
> > >
> > > How to name such license in the spec?
> >
> >
> > Hi,
> >
> > from my POV (not a lawyer) this license does NOT look to be suitable for
> > Fedora. Although the license seems to be compliant with many or most of
> > the statues of opensoure-software, it impairs the user's freedom, and
> > thus is to be considered as a NON-FREE license.
> >
> > Just my thoughts about it…
> >
> > Cheers
> > Björn
> >
>
> Sorry, I don't understand why it can "impairs the user's freedom" if
> it disallows re-licensing under GPL
>

Because it effectively states that you cannot combine it with another
work that would collectively be GPL. You cannot satisfy the terms of
this license and the GPL at the same time in that situation.

This is nonfree software unless the author can be contacted to remove
that clause. If they remove the clause, it's Free Software and can be
included in Fedora.

Ironically, I'm pretty sure such a clause is against the FreeBSD
licensing principles too.

I am going to disagree with my learned friends on this issue. Many
licenses considered acceptable for Fedora are also considered GPLv2
and GPLv3-incompatible for various reasons. In particular there is the
"Original SSLeay License", which was one of the conjuncts in what was
generally known as the OpenSSL license, which tacks on this clause at
the end:

* The licence and distribution terms for any publically [sic]
available version or
* derivative of this code cannot be changed.  i.e. this code cannot simply be
* copied and put under another distribution licence
* [including the GNU Public Licence [sic].]

If that was considered okay, if somewhat unfriendly, then I think the
language pointed out here ought to be okay too.

Back to the original question... what short name do we give this license?

- It has an advertising clause
- It forbids relicensing under any form of the GPL (curious what that means
  for potential derivative works)
- And it has the postcard/QSL card request, sort of like vim's donation
  request

License: BSD with oddities

or

License: Difficult

?

--
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat, Inc. | Boston, MA | EST5EDT
_______________________________________________
legal mailing list -- legal@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to legal-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/legal@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Gnome Users]     [KDE Users]

  Powered by Linux