Re:How the .NET Foundation kerfuffle became a brouhaha
by robmen on Friday October 08, 2021 @03:41AM
(#28796698)
Important to note, this extra layer was added without discussing it would be done before or after. The lack of communication eroded trust.
Re:How the .NET Foundation kerfuffle became a brouhaha
by still_grokking on Friday October 08, 2021 @01:55AM
(#28796150)
But if you gave away copyright you don't own the project any more. And if you don't own it, you don't own it…
The new owner can do further on how he pleases.
Sad in this case(es) but from a legal standpoint it's very likely like that, I guess (INAL).
Re:How the .NET Foundation kerfuffle became a brouhaha
by oaiey on Friday October 08, 2021 @02:22AM
(#28796282)
Yeah, but a stupid owner does what they did as nuclear options, a smart owner has the power but never use them but convinces people and let them work loosely as long as this is possible.
This is a cooperate thinking applied to a foundation. Is a recipe for failure.
Re:How the .NET Foundation kerfuffle became a brouhaha
by robmen on Friday October 08, 2021 @03:46AM
(#28796729)
The copyright applies to the source code the copyright is written on. Lawyers then argue who owns the "project" (GitHub organization/repository). For example, the copyright is not applied to the issues in the issue tracker.
But the argument is about whether the .NET Foundation could do such a thing. The argument is whether they should. And, the .NET Foundation chooses that they should take over the projects, project maintainers can make different decisions themselves.
None of this has been decided yet.
What's being done here is changes to how the project is managed. Basically inserting an upper management over the heads of existing maintainers. AFAIK, this right was not given (or at least the maintainers did not intend to give) to the umbrella org.