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 Anonymous Coward on Monday February 08 2016, @11:35PM
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.
Allow me:
ssh soylentnews.org
mkdir git && cd git
git init --bare .
touch git-export-daemon-ok
git update-server-info
mv hooks/post-update.sample hooks/post-update
This is how you create a fresh bare repository on your server that be cloned over HTTP. Just use SSH to push to it, or to log in and pull to it. The Git daemon hook will then run update-server-info after each push automatically which prepares the repository for pulling via HTTP.
If you have a fucking web server there's really no reason not to install Git (even bullshit shared hosting like 1&1 has Git installed). You can even make the /git/ directory a git.soylentnews.org sub-domain, for easier migration to another server if it ever needs to be run on its own hardware.
Instructions for how to set this up with an existing repo is equally simple. You clone the repository (optionally as bare), and configure it as above. Or create a bare repo as above, and then
git push --mirror ssh://yourserver/git/repo-dir
For private repositories it's only slightly more complex: Just get a (free) SSL cert, enable HTTPs, and use HTTP-AUTH to password protect the git directory (SSL ensures the logins HTTP usually sends in the clear isn't seen by MITMs). On windows workstations you'll install CURL, *nix already has it. Then configure CURL with the machine / username / password to match the repo, that way you never have to enter the login data when you pull from the HTTP source. If your remote repo is not bare, then you'll want to keep it checked out on a branch that you're not pushing to. A "stable" branch, for example. Then when you want to make a new stable release, log in and merge stable branch with the newest branch you want to publish. Gitorious is shit, IMO, but it's a project that handles this shit for newbies.
Seriously, there is ZERO reason to use Github if you have a webserver, even a shared web-server. In fact, I won't do webdev without git installed on the server. It makes updating and rolling back files so much nicer. To move to production I simply merge the production-config atop the latest working development branch, then cloning the resulting image to production servers.
I swear, people who use Git don't even know how to use Git thanks to brain rot crutches like Github (a centralized single-point-of-failure data silo that doesn't need to exist). Submodules make my life a breeze. They're like repositories within repositories -- Git's answer to SVN "vendor branches".
Meh, filthy normals abound. Plebs gonna pleb. Pearls before swine, and all that.
(Score: 0) by Anonymous Coward on Tuesday February 09 2016, @01:30AM
Ok it wasnt just me then.
GitHub was basically christened as the central point. This is a natural way to work in a group with a lot of people. To have one place that is sane and 'always works'. However, GitHub should act better than this. They can quickly find themselves irrelevant exactly because of the way git is made and works. You can quickly go from where the cool kids hang out to that place where 'the weirdos' hangout. Ask Collabnet and Sourceforge how well it worked out when they decided to lock up the code. That is a minor issue compared to being a bully.
(Score: 0) by Anonymous Coward on Tuesday February 09 2016, @06:08AM
Meh, filthy normals abound.
A "filthy normal" is someone who is sexually or romantically attracted to real people.
(Score: 0) by Anonymous Coward on Tuesday February 09 2016, @03:58PM
NORMIES GET OUT REEEEEEEEEEEEEEE [youtube.com]
(Score: 0) by Anonymous Coward on Tuesday February 09 2016, @07:48AM
You had me until you said "Submodules make my life a breeze."
Nobody uses them for any length of time and honestly says this.
(Score: 0) by Anonymous Coward on Tuesday February 09 2016, @03:55PM
GIT IS DISTRIBUTED VERSION CONTROL
No no no! You've got it all wrong! Git is centralized distributed version control!