We do appreciate your work on nesting. I know it has been useful to many in the community here.
I was asking about where the code comes from, because your plugin doesn’t seem to actually be open source. I recalled mentioning svgnest in that same discussion with you many years ago, so I just wondered when seeing this discussion the other day about the connection, if any, and a search here for those terms showed that opennest error messages do include some references to svgnest and deepnest files (Tutorial for OpenNest - #2 by diff-arch).
Whether it was written from scratch or if it is a mix of original work and bits of other people’s code, or a rewrite and modification, or even if it had been a direct port, that’s all good as long as the licenses allow it, I just personally think it’s also good practise to always properly acknowledge the contributions of the original authors whenever using their code.
For a permissive license like MIT, there isn’t a requirement to also make the new work open-source, but I believe you are still legally required to include in the distribution the original author’s copyright and license statement somewhere end users can see it if you use ‘substantial portions’.
I’m sure many users don’t care about where all the code comes from or how it is credited if it does what they want, but I think it can actually help foster a respectful environment, encourage other developers and push the development forward to be clear about it, and doing so for any portions which are borrowed doesn’t devalue all the other original work that goes into it at all.