How the .NET Foundation kerfuffle became a brouhaha

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • Home

    This is the landing repository for the .NET foundation efforts. Start here! (by dotnet-foundation)

  • As I have no idea about .NET development, I don't really understand the relation between these projects and .NET Foundation.

    Is .NET foundation paying them money? Or what is the relationship between the projects and Microsoft/.NET Foundation?

    Reading the "apology" on github, it seems that .NET Foundation/Microsoft thinks those projects are essentially theirs, and they are free to put them under their enterprise account to "simplify billing"

    https://github.com/dotnet-foundation/Home/discussions/39

    But reading this article, and the one below, the maintainers think otherwise?

    https://www.glennwatson.net/posts/dnf-problems-solutions

    There are also some notes about copyright that I don't understand. Who owns the copyright? Microsoft or the maintainers?

  • splat

    Makes things cross-platform

  • Many projects joined the .NET Foundation after it was created. It didn't really do anything, but it wasn't harming anyone either.

    The .NET Foundation asked for owner access on a repository (for their CLA bot). The author declined and a workaround was organized.

    Years later the .NET Foundation asked for owner access on a repository (to allow them enforce Code of Conduct across all repositories. The author declined.

    The CLA bot stopped working. The author was told it would work if he gave it owner access. The author was annoyed because they previously had a workaround. They gave in and gave @dnfadmin owner access.

    The author woke up and realized that the project had now been silently moved to GitHub Enterprise. The author states that projects in GitHub Enterprise can be entirely controlled by the owner of the account (the .NET Foundation). This transfer happened silently.

    Independently, this happened to another project (who had coincidentally had an issue with a Microsoft employee and former contributor force a pull-request into their project: https://github.com/reactiveui/splat/pull/778).

    People are upset because of how tone-deaf all of this is. They would like the .NET Foundation to stop trying to gain complete control over the member projects. They would like Microsoft employees to not force pull requests into their projects.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts