[CXX-899] Update documentation of third-party licenses Created: 20/Apr/16 Updated: 21/Jun/16 Resolved: 27/May/16 |
|
| Status: | Closed |
| Project: | C++ Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | legacy-1.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Giulio Paci | Assignee: | David Golden |
| Resolution: | Done | Votes: | 0 |
| Labels: | legacy-cxx | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Despite claiming to be release under Apache 2.0, this project includes code released under several other licenses.
|
| Comments |
| Comment by Githook User [ 27/May/16 ] |
|
Author: {u'username': u'xdg', u'name': u'David Golden', u'email': u'xdg@xdg.me'}Message: This changes compare_numbers.h to the Apache 2 license for consistency All other third-party licenses have been consolidated into top-level |
| Comment by Giulio Paci [ 21/Apr/16 ] |
|
Hi, thank you for your comment. I am not sure how big is the issue about "Public Domain". I live in a country that is probably affected by some of the issues (for example in my country it is not possible to alienate the moral right to claim that you wrote the software in the first place), but I do not know if there are any other issues. Moreover I think it is unlikely that developers publishing code under Public Domain are then going to sue anybody for unlicensed usage of their software (unless they have planned to do so from the beginning, but this seems even more unlikely). Zlib and md5: it is just a matter of you explicitly say which license you are going to use for your changes. I personally tend to release my changes with the same license of the software I am changing (or dual licensing them, especially if I think the original license is too restrictive). |
| Comment by Andrew Morrow (Inactive) [ 20/Apr/16 ] |
|
Thanks for reporting these issues. I'll comment on a few of them here:
The remaining components are not actually used by the driver - only by the tests. In general, the licensing situation for the legacy C++ driver is considerably muddled by its provenance - it derives from the MongoDB server sources. If you have concerns about the above issues, I strongly recommend that you migrate to using the new C++11 driver if at all possible. It should be clear of the sort of issues you have identified above. We may need to add a COPYING file there for MNMLSTC and/or catch, but that should be it. |