How the .NET Foundation kerfuffle became a brouhaha

Re:How the .NET Foundation kerfuffle became a brouhaha by Brian_K_White on Friday October 08, 2021 @01:18AM (#28795993)

You willingly gave me the key to your garage so that I can mow your lawn with your lawnmower.

I used the key to steal your car.

[ Parent | on HN ]

Re:How the .NET Foundation kerfuffle became a brouhaha by robmen on Friday October 08, 2021 @03:48AM (#28796738)

Then you and I would probably no longer be friends.

[ Parent | on HN ]

Re:How the .NET Foundation kerfuffle became a brouhaha by jgilias on Friday October 08, 2021 @02:26AM (#28796307)

They signed over Copyright.

Isn't a better analogy that they willingly gifted away their garage with everything in it under a _promise_ that they can still use the car?

Honestly, to me the only way out seems to exercise the licensee rights and fork.

[ Parent | on HN ]

Re:How the .NET Foundation kerfuffle became a brouhaha by iudqnolq on Friday October 08, 2021 @03:53AM (#28796761)

Nitpick, but in general a verbal promise in exchange for something of value would be considered a legally binding contract in the US.

[ Parent | on HN ]

Re:How the .NET Foundation kerfuffle became a brouhaha by jgilias on Friday October 08, 2021 @06:46AM (#28797755)

I think not just US, also Switzerland among other places. But either way, Copyright was signed over, and that has real implications. Although, in this case I gather that initially the Copyright owner for the given project was Microsoft, then some other foundation, and now .NET foundation. So, it's not like the maintenaners signed over anything they had, really. As sad as it is, legally it has never been theirs. Good thing the license protects some freedoms.

[ Parent | on HN ]

Re:How the .NET Foundation kerfuffle became a brouhaha by robmen on Friday October 08, 2021 @03:49AM (#28796744)

Forking is still one way this may resolve. The .NET Foundation can decide to provide other options.

[ Parent | on HN ]