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

Small license issues #382

Open
rrooij opened this Issue Jul 3, 2015 · 3 comments

Comments

Projects
None yet
4 participants
@rrooij

rrooij commented Jul 3, 2015

First of all, I think it is great that this software is licensed AGPLv3+. It is an awesome project and we really need a free as in freedom search engine, which also contains server code available to the users.

There are however some small license issues. Those are not major problems, but it would be nice to have them solved.

  1. The software doesn't include a full copy of the license. A full copy of the license can be retrieved here:
    https://www.gnu.org/licenses/agpl-3.0.txt
  2. The full source code of the minified JS scripts aren't available in the repositories. As far as I know, it should be according to the AGPLv3+ license.

This is what I could find so far. I'm not an expert in licensing issues, so feel free to correct me.

And thanks for the awesome software!

@asciimoo

This comment has been minimized.

Show comment
Hide comment
@asciimoo

asciimoo Jul 4, 2015

Owner

Thanks, the first note fixed. I'm not sure about the second one, could you please point out which section of the AGPLv3+ describes it?

Owner

asciimoo commented Jul 4, 2015

Thanks, the first note fixed. I'm not sure about the second one, could you please point out which section of the AGPLv3+ describes it?

@rrooij

This comment has been minimized.

Show comment
Hide comment
@rrooij

rrooij Jul 5, 2015

@asciimoo Cool!

I'm also not sure about the second one. It'd be of help if someone from GNU could help. I interpreted this way because of section 6, however, I'm no expert on this matter.

rrooij commented Jul 5, 2015

@asciimoo Cool!

I'm also not sure about the second one. It'd be of help if someone from GNU could help. I interpreted this way because of section 6, however, I'm no expert on this matter.

@vyp

This comment has been minimized.

Show comment
Hide comment
@vyp

vyp Jul 23, 2015

IANAL so I could very well be wrong, but it's my understanding that free software in general has to distribute the source code in form the author originally writes it in. Meaning minified code does not fulfill that (even if it can be unminified).

But looking at the JS scripts, all the minified ones seem to be third party libraries (and all the ones that are searx specific seem to be unminified). If this is correct and the minified third party scripts are unmodified from the original ones, then I think it should be okay if there are just links to the original source code libraries themselves. But I'm not even sure if that is needed by the license, just it would probably clarify things/solve this issue.

That can still be a pita though, so maybe it's worth looking into something like bower if that really is an issue for the license.

vyp commented Jul 23, 2015

IANAL so I could very well be wrong, but it's my understanding that free software in general has to distribute the source code in form the author originally writes it in. Meaning minified code does not fulfill that (even if it can be unminified).

But looking at the JS scripts, all the minified ones seem to be third party libraries (and all the ones that are searx specific seem to be unminified). If this is correct and the minified third party scripts are unmodified from the original ones, then I think it should be okay if there are just links to the original source code libraries themselves. But I'm not even sure if that is needed by the license, just it would probably clarify things/solve this issue.

That can still be a pita though, so maybe it's worth looking into something like bower if that really is an issue for the license.

ston3o pushed a commit to ston3o/searx that referenced this issue Jul 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment