As an open-source foundation, the projects you endorse reflect directly on your values, brand, and public trust. Foundations like Apache have set high standards by being selective about projects they host, especially discouraging those that drift into monetization models that reduce openness — such as paywalling core components or shifting key features behind paid licenses.<p>A current .NET Foundation project, Avalonia, appears to be heading in this direction with its recent move to introduce a paid toolkit called “Accelerate.” - [related thread][1].<p>While some argue this is a necessary evolution for financial sustainability, it’s worth noting that many high-impact FOSS projects — Linux, Debian, Python, PHP, and Laravel to name a few — have managed to thrive with models that build businesses *around* the software, rather than limiting freedom within it.<p>If the .NET Foundation seeks to deepen trust within the wider OSS and POSIX communities, it should reflect on whether hosting open-core projects aligns with its long-term vision. A constructive dialogue with Avalonia’s maintainers could lead to a model that supports sustainability *without compromising on openness* — something many in the .NET open source community deeply value.<p>Open .NET has a bright future, and it’s crucial that decisions today help preserve both the technical and ethical integrity of the ecosystem.<p>It might be time for the .NET Foundation to initiate a conversation with the Avalonia team and consider offering guidance on sustainable, community-aligned models. Open Source .NET carries high hopes for the future — and allowing short-term monetization decisions to dilute core freedoms risks killing the proverbial hen that lays the golden eggs.<p>[1]: https://reddit.com/r/AvaloniaUI/comments/1k1pozw/avalonia_is_getting_less_free_as_in_freedom_and/