4 ms·

> After reading more closely, it appears both repos are derivative works of pojects that Bumble (aka Badoo) owns. It says so in the README.md. That is how Open

> After reading more closely, it appears both repos are derivative works of pojects that Bumble (aka Badoo) owns. It says so in the README.md. That is how Open Source is supposed to work, I don't understand why everyone is thinking that this is some kind of huge discovery. Since both the MVICore and MVIKotlin repos are Apache 2.0, Badoo could simply pull in any improvements from MVIKotlin in if they wanted. They could ask their ex-employee if there was any interest in Badoo officially maintaining the project. There are about ten other paths I could suggest that go with how OSS projects can and should work. None of them involve sending legal notices to your former employees to "transfer" the repos. All I'm seeing here is that some person at Badoo/Bumble with little knowledge of how OSS works and a lot of lawyer time to throw around has made this move, and lost them a lot of goodwill from potential future employees.

deleted 5y ago
[deleted]
chii 5y ago
> That is how Open Source is supposed to work i dont know if you can claim this - OSS is not supposed to be unsanctioned derivative works of commercial software that is private. The company _could_ make it OSS, but an employee cannot, since they do not actually own the rights to make this decision. Perhaps Bumble was a bit heavy handed, but from the point of view of the law, they are acting within their rights to demand ownership transfer, or removal etc.
- deleted 5y ago
  [deleted]
- pritambaral 5y ago
  > ... commercial software ... Commercial and OSS are orthogonal. > ... that is private It seems to have been released under Apache 2.0: https://github.com/badoo/MVICore/blob/master/LICENSE https://github.com/badoo/MVICore/blob/master/LICENSE > The company _could_ make it OSS They _did_