5 ms·
Pretty sure that license header ended up in the codebase from a clever guy making a PR or it was just a mistake.
by mrbungie 2y ago
Pretty sure that license header ended up in the codebase from a clever guy making a PR or it was just a mistake.
- ilaksh 2y agoOk, I would like to believe that. That's great then thanks.
- mrbungie 2y agoIf it worries you, maybe open an issue? No sane man would allow a weird license that's an API call away from screwing up your own products.
- reasonableklout 2y agoI opened an issue here: https://github.com/huggingface/diffusers/issues/8306 https://github.com/huggingface/diffusers/issues/8306
- pama 2y agoUnfortunately this statement would not offer sufficient legal protection, so the original authors would have to be convinced to give up their previous rights and change the upstream copyright (and huggingface should update their repo license statement). Of course, these days it is typically easy enough to reimplement the code from a paper in plain pytorch, so I’m not sure one needs all this huggingface repo with the extra framework and risk, but to me it doesnt fit the requirement of the OP question.