Re:Elastic and Amazon reach agreement on trademark infringem...
by deepsun on Wednesday February 16, 2022 @05:30PM
(#30366708)
Sometimes fixing upstream is hard / not possible, when maintainers don't want to accept others' proposals/vision, or are cautious to change architecture with breaking changes.
[ Parent
| on HN ]
Re:Elastic and Amazon reach agreement on trademark infringem...
by DelightOne on Wednesday February 16, 2022 @05:37PM
(#30366800)
So they don't release the result as OSS because upstream wouldn't have included it?
Re:Elastic and Amazon reach agreement on trademark infringem...
by pjgalbraith on Wednesday February 16, 2022 @06:24PM
(#30367256)
I don't know much about this particular case. However generally speaking that is not true. They would just need to make the fork public. Whether the maintainer accepted the changes upstream is irrelevant.
Re:Elastic and Amazon reach agreement on trademark infringem...
by heavyset_go on Wednesday February 16, 2022 @06:53PM
(#30367558)
Unless they actually tried to upstream it, this point doesn't really matter. From what I can see, they never actually tried or intended to upstream their changes, so this is irrelevant. They didn't even release the fork's source, let alone try to upstream it.