SoylentNews is people
SoylentNews
In a stunning example of failure to understand the meaning of the word equality, Github's "social impact team" is now actively discriminating against people based on gender and skin color; white women in particular:
One insider criticized GitHub's "social impact team," which is in charge of figuring out how to use the product to tackle social issues, including diversity within the company itself. It's led by Nicole Sanchez, vice president of social impact, who joined GitHub in May after working as a diversity consultant.
While people inside the company approve of the goal to hire a more diverse workforce, some think the team is contributing to the internal cultural battle.
"They are trying to control culture, interviewing and firing. Scary times at the company without a seasoned leader. While their efforts are admirable it is very hard to even interview people who are 'white' which makes things challenging," this person said.
Sanchez is known for some strong views about diversity. She wrote an article for USA Today shortly before she joined GitHub titled, "More white women does not equal tech diversity."
At one diversity training talk held at a different company and geared toward people of color, she came on a bit stronger with a point that says, "Some of the biggest barriers to progress are white women."
From a site policy standpoint, this really makes me want to argue for finding another host for our rehash repository, enormous pain in the ass though that would be.
(Score: 4, Informative) by mechanicjay on Monday February 08 2016, @09:30PM
From a site policy standpoint, this really makes me want to argue for finding another host for our rehash repository, enormous pain in the ass though that would be.
Seriously, ping me on IRC. I'm running a sizeable GitLab operation for my Department. There's no reason at all we couldn't overload one of the existing linode hosts with a local install of GitLab. The latest version of GitLab even has api calls to import an entire project from GitHub, making things relatively painless.
My VMS box beat up your Windows box.
(Score: 2) by The Mighty Buzzard on Monday February 08 2016, @09:46PM
Nifty. Have to get my case made to the higher-ups first though.
My rights don't end where your fear begins.
(Score: 0) by Anonymous Coward on Tuesday February 09 2016, @06:15AM
Also take a look at Gitblit. It's like a tiny GitHub written in Java. I used it at my last job and it was great.
(Score: 3, Interesting) by jmorris on Tuesday February 09 2016, @01:33AM
The latest version of GitLab even has api calls to import an entire project from GitHub, making things relatively painless.
You know what would be totally awesome? If an import routine could be beefed up to allow easy tracking of a project to make forking as easy as moving.
Picture it. Project gets Entered, CoC adopted. The smart ones simply fork while continuing to track all patches from the original project, perhaps even their bugtracker as well. Begin discussions on a new mailing list but remain subscribed to the old one so they see all issues being debated. But only one way, zero goes back. Think of it as a one way fork due to CoC in exactly the same way as a license conflict can cause. For example OpenOffice.org -> LibreOffice where patches in LibreOffice can't go backward because of GPL not being backward compatible with the BSD license of OO.o. If the original CoC infected branch backports the new fork's changes they surrender because badthinkers are contributing code. Users won't care and will see the fork as having everything the original has (except perhaps the name) and tend to prefer it. Once distros begin pointing at the fork you can put a fork in the infected site.
Eventually the two would diverge to a point where tracking the original changes and bug reports would become more problem than benefit but if the fork were timed to a burst of development from the forking devels the original could be eliminated before it became a problem. A few public examples should suffice to put an end to the CoC scam.
(Score: 2) by AudioGuy on Tuesday February 09 2016, @04:24AM
This has been my position, and I argued for it unsuccessfully, since before we put code on github. I didn't know mechanicjay was using it at that time.
So that is two admins and our most prolific programmer on board. :-)
(Score: 1) by mechanicjay on Tuesday February 09 2016, @09:40AM
Though honestly, if we take the position that we're abandoning GitHub because of their CoC, GitLab is a steaming pile of RoR -- which has it's own issues with CoCs. So, with GitHub, is it the CoC, or the looney tunes shenanigans in general?
My VMS box beat up your Windows box.