Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please consider changing license for downstream #3

Open
siwinski opened this issue May 23, 2015 · 16 comments
Open

Please consider changing license for downstream #3

siwinski opened this issue May 23, 2015 · 16 comments

Comments

@siwinski
Copy link

I would like to package the Behat stack for Fedora/EPEL but Artistic 1.0 licensed software is not allowed in Fedora/EPEL. Please consider changing this library's license to the newer Artistic 2.0 license or perhaps even the MIT license like most other Behat libraries.

For reference, here are the Fedora software license lists:

From http://www.gnu.org/licenses/license-list.html#ArtisticLicense :

Artistic License 1.0

We cannot say that this is a free software license because it is too vague; some passages are too clever for their own good, and their meaning is not clear. We urge you to avoid using it, except as part of the disjunctive license of Perl.

@stof
Copy link
Member

stof commented May 26, 2015

This library is a port of a Perl library. This is probably why it was released by keeping the same license, as most of the library is just taking the Perl data and converting them to PHP files.

However, I don't know whether Perl is using Artistic 1 or 2. They don't mention the version. Can you tell me whether http://dev.perl.org/licenses/artistic.html is the version 1 or 2 ?

@siwinski
Copy link
Author

That exact link is version 1. Version 2 is at http://www.perlfoundation.org/artistic_license_2_0

One directory up from version 1 (http://dev.perl.org/licenses/) sounds like code can be GPL or Artistic License?

@remicollet -- Any chance you could help decipher the license and determine if this library's license could even be changed?

@remicollet
Copy link

According to github history there is only 2 commiters, so if both agree, updating version should be fine.

@siwinski if you want to be really sure, raise the question on fedora-legal mailing list.

@stof
Copy link
Member

stof commented May 26, 2015

@remicollet this code was extracted from other places though (it was in Behat 2.x itself, and in Doctrine 1 before that). And all the x*.php files contain data maintained in the Perl library (the only difference being converting them from Perl files to PHP files)

@spotrh
Copy link

spotrh commented Jun 3, 2015

The standard "perl license" is Artistic 1.0 or GPL+ (any version of the GPL). Since there are known issues with the Artistic 1.0 license, Fedora chooses GPL+. If you wanted to relicense the work to that dual license, we'd use your work under GPL+ as well.

@siwinski
Copy link
Author

@stof could this library use dual licenses Artistic 1.0 or GPL+ like Perl so it could be packaged for Fedora under GPL+?

@everzet
Copy link
Member

everzet commented Aug 4, 2015

This library is a copy-paste by me. As far as I know (feel free to correct me), you need approval from original authors for a change of license. I'm not them:
https://github.com/Behat/Transliterator/blob/master/src/Behat/Transliterator/Transliterator.php#L20-L22

@everzet
Copy link
Member

everzet commented Aug 4, 2015

Hmm. I just noticed this:
https://github.com/Behat/Transliterator/blob/master/src/Behat/Transliterator/Transliterator.php#L16

According to this line the actual license of the library should be LGPL, not Artistic.

@stof
Copy link
Member

stof commented Aug 4, 2015

@everzet depends which part. The issue is that the code comes from multiple sources originally (LGPL is the part coming from Doctrine 1 whcih was LGPL, while Artistic is the part ported from Perl)

@stof
Copy link
Member

stof commented Aug 4, 2015

and btw, see the comment in the phpdoc a few lines above the one you linked:

the original author names and emails are not known

@stof
Copy link
Member

stof commented Aug 4, 2015

In summary, the licensing of this code base is already a huge mess

@valioDOTch
Copy link

Even more funny: CPAN does not list this as dual-licensed
https://metacpan.org/pod/Text::Unidecode

So probably I'd first ask Sean M. Burke whether he would be willing to dual-license it with LGPL (this is the preferred approach for Perl modules).

Then either consider porting it again from Perl or ask the original authors...

@siwinski
Copy link
Author

Any progress or updates on the licensing of this project?

@remicollet
Copy link

remicollet commented Apr 19, 2016

From: http://cpansearch.perl.org/src/SBURKE/Text-Unidecode-1.27/LICENSE

This module, Text::Unidecode (along with its documentation and its
data tables) is distributed under the same terms as Perl itself.

Which means Gpl+ or Artistic, which is ok for downstream

@siwinski
Copy link
Author

http://search.cpan.org/dist/Text-Unidecode/ defines Text::Unidecode's license as "The Perl 5 License (Artistic 1 & GPL 1)"

Downstream Fedora/EPEL defines Text::Unidecode's (perl-Text-Unidecode) license is "GPL+ or Artistic".

@stof would you accept a pull request changing composer.json license to:

"license": ["GPL-1.0+", "Artistic-1.0"],

and adding a GPL license file?

@nforgeot-norsys
Copy link

nforgeot-norsys commented Feb 9, 2023

Hello, we are having a similar problem to make our application open source.

We use behat/transliterator through behat/behat and gedmo/doctrine-extensions.

The AGPLV3 license selected for publishing our application does not authorize Artistic 1.0.

Is it possible to revise the license ? Artistic 2.0 ? or MIT, like behat/behat since v2.2 during 2011, if the code is extracted from behat/behat ?

Not a simple matter :/

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants