There was another rule you did not know seemingly. Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity.[1]
> The only source quoted on the water issue is an EE professor from a school in California, who I am guessing is not a subject matter expert on water in Washington state.
Replication is not the same as reproduction; I can replicate an API without violating someone's license or copyright (which I would by reproducing their work).
Developers are permitted to learn from open source code with restrictive copyrights, and apply those lessons to developing other software which does not comply with the copyright of their 'example'.
As an aside, I do believe that LLM trainers are ignoring and violating many licenses, but open-source software is not a clear example of a violation.
Depends on how you define "learn": usually, a company wanting to rebuild and publish something under a different license prohibits their developers from having ever looked at original code, to avoid the risk of copying over exact snippets out of their memory accidentally.
Copyright protects only arbitrarily non-trivial parts of the original being reproduced, but that means that you have to be careful with learning from copyrighted material. Programming books will have direct clauses allowing snippet reuse, but not for teaching purposes.
> Sure, but developers are permitted to learn from open source code with restrictive copyrights, and apply those lessons to developing other software which does not comply with the copyright of their 'example'.
This was a different argument. And there is no contradiction to separate LLMs and people.
> As an aside, I do believe that LLM trainers are ignoring and violating many licenses, but open-source software is not a clear example of a violation.
Ahhhh yes that's one that lawyers might have fun with. MIT says:
> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
My personal thought on that: it's going to be almost guaranteed that, if an LLM is producing stuff it clearly derived from a certain piece of code XYZ, it will also be capable of producing the correct answer to the question "what's the license for XYZ?" And lawyers will successfully argue that this counts as "included".
> My personal thought on that: it's going to be almost guaranteed that, if an LLM is producing stuff it clearly derived from a certain piece of code XYZ, it will also be capable of producing the correct answer to the question "what's the license for XYZ?" And lawyers will successfully argue that this counts as "included".
The MIT license terms are not say the name the license if asked. They are The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
And this would be improbable for many reasons I think.
Their open source software depended on or derived from your package. They included your copyright notice with software they distributed. Someone contributed code. Someone reported a bug. Someone requested a feature. Someone mentioned it at a conference. I could continue.
[1] https://news.ycombinator.com/newsguidelines.html