How the .NET Foundation kerfuffle became a brouhaha

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).

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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

I'm pretty sure the copyright is shared, at least that's how I've seen CLA's happen in the past, they grant joint ownership.

[ Parent | on HN ]

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

Some projects are "contribution" (like you describe) and some are "assignment" (.NET Foundation holds the copyright).

[ Parent | on HN ]