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

conflicting license statements #817

Open
onlyjob opened this issue Apr 16, 2015 · 7 comments
Open

conflicting license statements #817

onlyjob opened this issue Apr 16, 2015 · 7 comments

Comments

@onlyjob
Copy link
Contributor

onlyjob commented Apr 16, 2015

I've noticed that some files have conflicting license statements. For instance the header of file scripts/ZoneMinder/lib/ZoneMinder/Trigger/Channel.pm claims GPL-2+ but in the end of the same file I found the following statement:

This library is free software; you can redistribute it and/or modify
it under the same terms as Perl itself, either Perl version 5.8.3 or,
at your option, any later version of Perl 5 you may have available.

Please clarify whether such .pm files are double-licensed or if only one particular license applies.

All .pm files in scripts/ZoneMinder/lib/ZoneMinder/Trigger are affected, some in scripts/ZoneMinder/lib/ZoneMinder/Control as well as all *.pm and *.pm.in in scripts/ZoneMinder/lib/ZoneMinder.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@knight-of-ni
Copy link
Member

@kylejohnson can you get a hold of Phil and see what he thinks about this one?

@web2wire
Copy link

I'm happy to put everything on the same licence, probably GPL3 nowadays. I suspect the perl ones just had whatever I found in similar modules from elsewhere.

@onlyjob
Copy link
Contributor Author

onlyjob commented May 10, 2015

So at the moment some Perl components (modules and scripts where Perl license is mentioned) are dual-licensed but we can upgrade to GPL-3+ (version 3 or above), right?

Since everything is already under GPL-2+ I suppose it already includes GPL-3+...

If everyone agrees we can just drop Perl license statements or (in case we choose to preserve dual-licensing) move them towards the beginning of files...

@SteveGilvarry SteveGilvarry self-assigned this Mar 18, 2017
@SteveGilvarry
Copy link
Member

Review and fix all licenses

@stale
Copy link

stale bot commented Jun 15, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added stale and removed stale labels Jun 15, 2018
@stale
Copy link

stale bot commented Aug 15, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Oct 14, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 14, 2018
@ZoneMinder ZoneMinder deleted a comment from 996b Oct 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment