5 ms·

> The primary goal was to centralize billing to give member projects access to additional GitHub services. A secondary goal was to ensure the continuity of memb

by RNCTX 5y ago

> The primary goal was to centralize billing to give member projects access to additional GitHub services. A secondary goal was to ensure the continuity of membership projects, using requestable admin access, as just described. Seems like a pretty obvious lie. One of the people in the issues forum post about this pointed out how they had not only failed to give them "more services," but rather taken those "services" away over time. (1) Why is no one else calling the obvious here? Their foundation exec director got mad when someone called bullshit on giving the foundation admin over their repo to enforce "code of conduct." So the foundation exec director set out to get them to add the foundation's account to the admin list on their repos so that they could be taken control of in the middle of the night with no warning. This is what happens when you have self promoting people with a privileged political status in administrative positions. 1. https://github.com/dotnet-foundation/Home/discussions/38#discussioncomment-1439434 https://github.com/dotnet-foundation/Home/discussions/38#dis...

oaiey 5y ago
From a corporate perspective this has very little to do with CoC. It has to do with simplifying their life. CoC enforcement is surely and element on the list, but there are many others. As you noted, no one talks about it. Why? Because that is not the problem. This whole crisis is not because of GitHub Enterprise usage alone. It is because of the absolute lack of communication and the disrespect towards the maintainers. That is so much worse than some CoC enforcement.
- RNCTX 5y ago
  The details don't support that assessment. Chain of events: 1) The CLA library requested by the foundation was reported broken by an admin one of the member project repos. That member project repo had refused to turn over control of said repo to the foundation specifically because of the perceived overreach in authority stemming from the code of conduct policy of said foundation. 2) The exec director, or someone on the foundation's staff, told the person reporting the issue with the CLA library that the solution was to make the foundation account an admin on their repo. 3) When the foundation is made an admin on said repo, the repo is silently transferred to the foundation's account in the middle of the night with no warnings. 4) Then, exec director force-merges a pull in another repo, of the same CLA library. This is all a very useful glimpse into how corporations will use their diversity hires to get rid of people who refuse to give the corporation what it wants without any compensation or resistance.

by RNCTX 5y ago

oaiey 5y ago

From a corporate perspective this has very little to do with CoC. It has to do with simplifying their life. CoC enforcement is surely and element on the list, but there are many others. As you noted, no one talks about it. Why? Because that is not the problem. This whole crisis is not because of GitHub Enterprise usage alone. It is because of the absolute lack of communication and the disrespect towards the maintainers. That is so much worse than some CoC enforcement.

RNCTX 5y ago
The details don't support that assessment. Chain of events: 1) The CLA library requested by the foundation was reported broken by an admin one of the member project repos. That member project repo had refused to turn over control of said repo to the foundation specifically because of the perceived overreach in authority stemming from the code of conduct policy of said foundation. 2) The exec director, or someone on the foundation's staff, told the person reporting the issue with the CLA library that the solution was to make the foundation account an admin on their repo. 3) When the foundation is made an admin on said repo, the repo is silently transferred to the foundation's account in the middle of the night with no warnings. 4) Then, exec director force-merges a pull in another repo, of the same CLA library. This is all a very useful glimpse into how corporations will use their diversity hires to get rid of people who refuse to give the corporation what it wants without any compensation or resistance.