<story><title>How the .NET Foundation kerfuffle became a brouhaha</title><url>https://robmensching.com/blog/posts/2021/10/6/how-the-.net-foundation-kerfuffle-became-a-brouhaha/</url></story><parent_chain><item><author>Permit</author><text>Many projects joined the .NET Foundation after it was created. It didn&amp;#x27;t really do anything for them (I think they basically sponsor meetups), but it wasn&amp;#x27;t harming anyone either.&lt;p&gt;The .NET Foundation asked for owner access on the author&amp;#x27;s repository (for a CLA bot). The author declined and a workaround was organized.&lt;p&gt;Years later the .NET Foundation asked for &amp;quot;owner access&amp;quot; on the author&amp;#x27;s repository (to allow them enforce Code of Conduct across all repositories). The author declined.&lt;p&gt;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 (temporarily, it was later revoked after the CLA bot was set up, thanks &amp;#x2F;u&amp;#x2F;ethbr0 for the correction).&lt;p&gt;Some time later the author realized that the project had now been silently moved to GitHub Enterprise (likely in the short window @dnfadmin had owner access). 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.&lt;p&gt;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: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;reactiveui&amp;#x2F;splat&amp;#x2F;pull&amp;#x2F;778&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;reactiveui&amp;#x2F;splat&amp;#x2F;pull&amp;#x2F;778&lt;/a&gt;). The change itself seems innocuous, but the approach bothered people.&lt;p&gt;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 especially like for their projects not to have their ownership changed silently.&lt;p&gt;Edit: For the record, I do not believe this is part of some embrace, extend, extinguish plan on behalf of Microsoft. I think these accusations actually cheapen what has happened here. I suspect this was more of a &amp;quot;can we make this process easier and more convenient for the .NET Foundation&amp;quot;-type thing.&lt;p&gt;The people involved with this will have to do some soul searching. The .NET Foundation should operate in service of its member projects, not the other way around.</text></item><item><author>zippergz</author><text>I&amp;#x27;m not trying to be lazy (ok maybe a little bit), but can someone please provide like a 3-4 sentence summary of what happened? Everything I&amp;#x27;ve seen on this either assumes you already know, or is very long and rambly, or both.</text></item></parent_chain><comment><author>moksly</author><text>I think this is on point. We once had an issue with open street maps, that caused our routing system to not be capable of directing citizens and employees to the second biggest municipality in our country because a one way street had the wrong direction marked in OSM by mistake.&lt;p&gt;This had a huge impact on us. With thousands of employees and citizens calling our IT support staff of 5 people every day.&lt;p&gt;When I used our OSM official “City off X” account to fix it, I was an utter idiot and submitted both a real life picture I took myself as well as a Google maps and a krak maps (Danish map service) screenshots. I didn’t know this wasn’t legal, because I was an idiot, but it resulted in our fix getting reversed and a week long discussion with the OSM community members about fixing the damn street.&lt;p&gt;We made the street one way. But we couldn’t fix it in an OSS map service because the community wouldn’t let us because we made a stupid mistake.&lt;p&gt;We’ve now switched our services to Krak. But I can promise you that if we had, had the admin power to force our chance through during those days, we wouldn’t have given any regards to the OSS community.&lt;p&gt;If an popular tool wasn’t working within the .Net framework CLA I imagine the process would be somewhat similar inside Microsoft.&lt;p&gt;It’s just one of those things where the OSS community processes and Enterprise process of “get this fixed right now, at any cost by any means, ignoring every standard we may have, just get it fixed, now. Then make sure it never happens again.” that happens every now and then when the beast awakens, clashes. I’m not sure how you can avoid it, as Enterprise will never want to comply with OSS processes when it’s in a hurry.</text></comment>
<story><title>How the .NET Foundation kerfuffle became a brouhaha</title><url>https://robmensching.com/blog/posts/2021/10/6/how-the-.net-foundation-kerfuffle-became-a-brouhaha/</url></story><parent_chain><item><author>Permit</author><text>Many projects joined the .NET Foundation after it was created. It didn&amp;#x27;t really do anything for them (I think they basically sponsor meetups), but it wasn&amp;#x27;t harming anyone either.&lt;p&gt;The .NET Foundation asked for owner access on the author&amp;#x27;s repository (for a CLA bot). The author declined and a workaround was organized.&lt;p&gt;Years later the .NET Foundation asked for &amp;quot;owner access&amp;quot; on the author&amp;#x27;s repository (to allow them enforce Code of Conduct across all repositories). The author declined.&lt;p&gt;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 (temporarily, it was later revoked after the CLA bot was set up, thanks &amp;#x2F;u&amp;#x2F;ethbr0 for the correction).&lt;p&gt;Some time later the author realized that the project had now been silently moved to GitHub Enterprise (likely in the short window @dnfadmin had owner access). 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.&lt;p&gt;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: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;reactiveui&amp;#x2F;splat&amp;#x2F;pull&amp;#x2F;778&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;reactiveui&amp;#x2F;splat&amp;#x2F;pull&amp;#x2F;778&lt;/a&gt;). The change itself seems innocuous, but the approach bothered people.&lt;p&gt;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 especially like for their projects not to have their ownership changed silently.&lt;p&gt;Edit: For the record, I do not believe this is part of some embrace, extend, extinguish plan on behalf of Microsoft. I think these accusations actually cheapen what has happened here. I suspect this was more of a &amp;quot;can we make this process easier and more convenient for the .NET Foundation&amp;quot;-type thing.&lt;p&gt;The people involved with this will have to do some soul searching. The .NET Foundation should operate in service of its member projects, not the other way around.</text></item><item><author>zippergz</author><text>I&amp;#x27;m not trying to be lazy (ok maybe a little bit), but can someone please provide like a 3-4 sentence summary of what happened? Everything I&amp;#x27;ve seen on this either assumes you already know, or is very long and rambly, or both.</text></item></parent_chain><comment><author>plorkyeran</author><text>&amp;gt; I suspect this was more of a &amp;quot;can we make this process easier and more convenient for the .NET Foundation&amp;quot;-type thing.&lt;p&gt;I suspect there was also just a different picture on what the .NET Foundation even meant inside and outside of MS. It&amp;#x27;s different people working on it inside MS than the ones who originally set things up, and the new people may not have even seen their actions as trying to take control of anything because they were under the impression that everyone considered them in charge already.</text></comment>