Software Developers Should Avoid Traumatic Changes
- Drew DeVault tl;dr: Two types of changes in open source software inflict trauma on communities. A change where everyone has to overhaul their code to get it to work again, or a change to get code idiomatic again. Drew shows examples of both of these in the Python community.featured in #163
The Mind Behind Linux (2016 Video)
tl;dr: Fascinating conversation about the inception of Linux and Git, and the man behind them. The initial community involved in Linux was critical. Git was a result of managing Linux's growth. Both projects were to solve Linus' immediate needs.featured in #162
GitHub Arctic Code Vault (Video)
tl;dr: In order to preserve the open source code we are highly dependent on, GitHub has built a vault in the Arctic where all Open Source code will be stored. You can read more about it here.featured in #162
It's The End Of Python 2. Are We Prepared?
- Jeremy Katz tl;dr: There is a burden on maintainers of the 200,000 Python libraries to meet the looming deadline. It's another reason why OS maintainers should be paid for their work.featured in #159
In 2019, Multiple Open Source Companies Changed Course - Is It The Right Move?
- Scott Gilbertson tl;dr: The cloud has created tension amongst open sourced technologies and companies wrapping such technologies into products they sell. This articles debates between changing the open source business model and changing how open source is licensed.featured in #157
The Internet Relies on People Working for Free
tl;dr: Using cURL as an example, we see a fundamental issue with open source projects. cURL was developed by one person. It's used in millions of different devices daily, none of whom pay for it. Click on the link in this tweet it you are paywalled.featured in #154
featured in #152
Software Below The Poverty Line
- André Staltz tl;dr: Open Source projects are severely underfunded. ~$2.5m is the combined amount donated to the top OS projects. When you divide this amount amongst the contributors it's $9K median / $22K average per contributor, which falls well below salary standards.featured in #145
What Comes After “Open Source”
- Steve Klabnik tl;dr: Licensing agreements define both open source and free software, but doesn't capture the essence of why software should be free. Licenses care about distribution and consumption but not production, which is what developers care about. Two potential models are outlined as possible evolutions.featured in #135
The Cloud And Open Source Powder Keg
- Stephen O'Grady tl;dr: Commercial open source vendors are inevitably heading into conflict with cloud companies, as seen in the ongoing chess match between Elastic and Amazon.featured in #133