Thanks @infratec!
@flashbob, that license only covers the code of libcurl, but the bindings are the work of @infratec so they are Copyright by him, and he's free to keep it proprietary or release it under a license of his choosing (of course, if the license were to conflict with that of libcurl it would make little sense, but legally it doesn't make a difference).flashbob wrote: Thu Jul 25, 2024 2:55 pm You're basically right, but in this case I don't really understand the licensing confusion. The LibCurl library (dll) cannot be licensed again because it is an external open source project and a license already exists.
Copyright is complex topic and has different rules for different types of works. In code projects, every chunk of code contributed by third parties also means that these parties have copy rights over their contributed code (e.g. in a cause for compensation, they will be allotted a share calculated on percentages over the entire code). So much so, that once a project creator has accepted external contributions he might not re-license the project without the consent of every contributor, since they own the decision rights over their code chunks.
Translations also count as Copyright, even though the Copyright of the original text is owned by the original author, the translation rights are owned by the translator. Even pagination and typesetting count as Copyrighted work. When it comes to photographs the laws are quite complex, since it depends on the central subject of the photograph: important building require permission from the architect who designed it, people must sign permissions to reuse, and with photographs of minors it's even more complicated, and these laws vary from country to country (in Italy, permission to reproduce photographs of living people expire after a fixed number of years).
Usually, the main problem when it comes to software licenses is always Germany, which has strict laws, and different ones from the rest of Europe. For example, in Germany public domain is basically impossible to use, because of a famous case where someone scanned public domain material for redistribution but the court ruled that the very act of scanning it made it copyrighted material, and revoked its public domain status — which is why German citizens and residents can't subscribe or contribute to the Gutenberg project, for example. Basically, in Germany it's very hard for a contemporary person do declare his work into the public domain, because any human efforts to operate on that material would make it copyrighted by those who handle it.
And of course, different countries tend to interpret differently the various licenses clauses (what constitutes "derivate work", what is eligible for copyright status, etc.). An example are the recent legal court cases over the use of library headers in proprietary closed-source software, where the offended party claims that using the headers binds to the license terms of the project, and where the other party claims that headers are not code and thus are not subject to the license terms.
Big companies have pools of lawyers who's job is to look into these legal problems, keeping track of international law. But for us Indy developers, the best we can do is stick to well known FOSS licenses and cross fingers — but at least with these licenses you are somewhat backed-up by the FOSS world, since many organizations have interests in seeing these licenses pass the test of real court trials.