Bonum Certa Men Certa

The GitHubification of Free Software

Article by Thomas Grzybowski



3 rabbits caged



Summary: "The optimal solution to the ongoing GitHubification of Free Software would be the creation of a successfully competitive software development repository specialized to the Free Software community."

GitHub is proprietary software and a manifestation of surveillance capitalism right smack-dab on the face of it. But that is the very least of the problem here. GitHub is an existential problem for Free Software - a crisis that is almost completely obscured from our notice.



GitHub is a major part of Microsoft’s future, and it is not speculation to note that GitHub undermines Free Software. Microsoft is a company which has dedicated itself to ending the Free Software movement – a company which has formally banned the use of the GPL from any of its internal software. If anyone dismisses that GitHub can be an existential problem, see this example pointing to our future: https://www.gnu.org/software/fribidi/ . Here one thinks one is going to a GNU site, but is in fact being directed to Microsoft.



This observation is far from an isolated fact. Free Software advocate figosdev has painstakingly analyzed a vast array of GNU/Linux software packages and compiled volumes of information showing that GNU is becoming dependent upon GitHub in its development processes.

http://techrights.org/2020/05/03/gnuhub-pt-1/

http://techrights.org/2020/05/05/gnuhub-pt-2/

http://techrights.org/2020/05/08/gnuhub-pt-3/



There is a long list of concerning facts documented in the above references, but in essence they add-up to show a strong and growing dependence of GNU “Free” software development upon GitHub: Perhaps most notably (being a basic GNU software development tool), GNU Bison has moved to GitHub, with Bison using GitHub for its development platform. The GNU repository is only a mirror. This is extremely problematic, and again not an isolated fact.

How did this situation come about? A major part of this "trap" is what is called the “Network Effect”. As each additional project-piece of software becomes embedded in GitHub, the "benefit" for each and all such projects increases - and the social cost of avoiding the site also increases. Already a GitHub presence is "expected". And Microsoft has greased the slide by actually paying some project-leads to host their projects there.



In regards to the actual migrations onto GitHub, it can be a four-step process, each step seemingly trivial relative to the previous:

  1. Use of GitHub’s social interfaces for bug tracking.


  2. Use of GitHub as a mirror as a backup site, and “presence” for people’s convenience.


  3. Use of GitHub for development (seeing as most of the bug tracking and pulls happen there).


  4. GitHub becomes the canonical source site.




This is all pretty straightforward, above-board, and not a mystery. But, as we have seen documented above, the migration process is extensive and yet there has been little notice paid to the intrusion of this conduct into Free Software development. Let us be clear: Free Software and GNU are becoming dependent upon Microsoft.

Microsoft dependency is an existential crisis for Free Software. First of all, the source code and other content itself physically resides on Microsoft’s servers. These materials are then fully under their control and open to easy and extensive analysis for technical and strategic information. Surveillance activities involve the real names, locations and associations of people working with GitHub. And there are yet other real and potential benefits to Microsoft emerging from having the source code under their control:



  1. Censorship, and the implicit threat thereof.

  2. Blackmail - the implicit or explicit threat of loss of service or censorship.

  3. Manipulatively granting some projects preferential treatment, payment, or services.

  4. Behavior manipulation and opinion modification – through GitHub payments, site messaging, and marketing.

  5. Outright (direct) monetization of use.



What can be done about this situation? Here things become even more problematic. Earlier in the history of GNU, Free Software was widely perceived to be incommensurate with the activities of companies such as Microsoft. (Microsoft’s aggressively monopolistic and proprietary practices at the time being exceedingly well documented.) In fact, Free Software can be seen largely as a reaction to these behaviors. Psychologically there was a good degree of oppositional motivation: programmers could see matters as being one of “Us vs Them” when thinking about Microsoft, and the Free Software movement was able to progress. But now that Microsoft “Loves Linux”, etc., this motivation becomes weak, diluted, undirected. When “Them” (the non-Free Software forces) are a large part of “Us”, the situation changes markedly, and what needs to be done to advance our freedoms becomes extremely difficult.

So, What To Do? One, I think, would be for any Free Software organization worth the name to require appropriately licensed software to be hosted on the home server or other vetted open-source, Free Software server for development. Proprietary services would be out of the question, as they are non-Free with users having no knowledge of what is going on behind the scenes.

An immediate step is for any important project which is being developed on GitHub to be encouraged to move off of that platform. If the project in question does not have a mirror, it should be mirrored elsewhere, ideally with the permission of the project manager, but not necessarily. This is indeed what Free Software is all about. In this way, if GitHub censors any project it will still remain immediately accessible to users. This mirroring also bleeds-off just a little of Microsoft’s implicit denial-of-service threat they hold over their client projects. Each of us should pick a project we wish to mirror and maintain that mirror!

The optimal solution to the ongoing GitHubification of Free Software would be the creation of a successfully competitive software development repository specialized to the Free Software community. Such a site (or set of distributed sites) could well be a successful replacement to GitHub because it would not be subject to the limitations, compromises, and contradictions inherent to a private proprietary entity run for profit. The effort needed to achieve such a success may be seen as prohibitive – but, as we have seen above, it is necessary.

Comments

Recent Techrights' Posts

Open Source Initiative (OSI) Privacy Fiasco in Detail: The OSI Does Not Respect Anybody's Privacy
The surveillance mafia that bans dissent or key people (even co-founders) with dissenting views
The LLM Bubble is About to Implode, Gimmicks and Financial Shell Games Cannot Prevent That, Only Delay It
To inflate the bubble MElon is now doing the classic trick of buying from oneself for a fictional value
 
LLM Slop Piggybacking News About GNU/Linux and Distorting It
new examples
Links 31/03/2025: Press and Democracy Under Further Attacks in the US, Attitudes Towards Slop Sour
Links for the day
Gemini Links 31/03/2025: More X-Filesposting and Dreaming in Emacs
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, March 30, 2025
IRC logs for Sunday, March 30, 2025
Links 30/03/2025: Security Breaches, Crackdowns on Dissent/Rival Politicians
Links for the day
Gemini Links 30/03/2025: London Soundtrack Festival, Superbloom, gmiCAPTCHA
Links for the day
Phasing Out Vista 10 in Nations Where ~90% of Windows Users Still Rely on It
Recipe for another Microsoft disaster
The Cost of Pursuing the Much-Needed Reform/Shield Against Strategic Lawsuits Against Public Participation (SLAPPs)
“It is curious that physical courage should be so common in the world and moral courage so rare.”
Links 30/03/2025: Contagious Ideas, Signal Leak, and Squashing Lousy Patents
Links for the day
Links 30/03/2025: "Quantum Randomness" and "F-1 Visa Revoked" in US
Links for the day
Gemini Links 30/03/2025: US as a Threat, Returning to the WWW
Links for the day
Links 30/03/2025: Judge Blocks Dismantling Of VOA, Turkey Arrested Many Journalists
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, March 29, 2025
IRC logs for Saturday, March 29, 2025
Judges Would Never Rule for Men Who Strangle Women or Against Women Who Merely Wrote Articles About Abuse They Had Received From Men
We don't intend to do "trial by media", so we won't be disclosing claims and defences until it's over
Windows is an Unnatural Disaster, It is Also Avoidable
there's a wide window of opportunity opening
Gemini Links 29/03/2025: Less YouTube and More Station
Links for the day
In Some Countries, Such as Thailand, Firefox is Already Measured at Less Than 2% (One Day Firefox Will Get Blocked, Not Only Lack Support)
Web consolidation around Chrom-isms will doom the Web as we know it
Killing the News With Spam and Slop Benefits Those Whose Desire is an Uninformed Population
adoption of Free software depends indirectly on political activities/activism
Links 29/03/2025: Trademarks Battles, Fires Destroy More Than 3,000 South Korean Homes
Links for the day
Open Source Initiative (OSI) Privacy Fiasco in Detail: An Introduction
Perhaps tomorrow or perhaps next week we'll share more information about what happened and what was reported to the California Privacy Protection Agency
Links 29/03/2025: More Crackdowns on Science, "Hey Hi" Slopping is Flopping
Links for the day
IBM's BS (Bait, Switch) Regarding Ways to Stay Onboard
PIPs, RTOs, and forced relocations are just an illusion of choice (or ability to recover)
Costa Rica Almost Bankrupt Because of Microsoft
the incidents in Costa Rica are Windows incidents
Gemini Links 29/03/2025: Art of Looking, Wireguard, EMacs
Links for the day
Links 29/03/2025: Attacks on Social Security and War Updates
Links for the day
Banned evidence: Ars Technica forums censored email predicting DebConf23 death, Abraham Raji & Debian cover-up
Reprinted with permission from Daniel Pocock
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, March 28, 2025
IRC logs for Friday, March 28, 2025