Open Source Timeline: Who Pays When the Licenses Change
Archi4 min read
Contents
- Who Feels Open Source Shocks First
- 1991: Linux appears on a mailing list
- 1998: Netscape opens Navigator
- 2004: Firefox 1.0 reaches regular users
- 2008: Android Open Source Project starts shipping
- 2011: Hudson becomes Jenkins
- 2014: Heartbleed hits OpenSSL
- 2021: Log4Shell lands in Log4j
- 2023: HashiCorp changes Terraform's license
- 2024: Redis changes license, Valkey forks
- 2024: xz utils backdoor is caught
Who Feels Open Source Shocks First#
Open source news usually arrives as a license notice, a security advisory, or a fork announcement. The people who absorb the impact are rarely in the headline. This timeline tracks a few turning points by asking one question: who had to change work habits first?
1991: Linux appears on a mailing list#
Linus Torvalds describes a hobby kernel for 386 machines. The first affected group is narrow: university labs, hobbyists with spare hardware, and a handful of compiler writers. Bank sysadmins and hospital IT staff do not notice. That gap set a pattern. Early open source risk fell on people with time to tinker, not on teams with payroll systems to keep online.
1998: Netscape opens Navigator#
Netscape releases browser source code, and the web development crowd gets a new pile of code to inspect. The most affected people are webmasters who must support competing rendering engines. Ordinary users see little at first. Developers see a long, messy build process. The episode also pulls legal teams into open source, because every contributor license becomes a procurement question.
2004: Firefox 1.0 reaches regular users#
Mozilla ships Firefox 1.0. The affected group widens beyond developers. Windows users get a browser that is not welded to the operating system. Help desks get calls about extensions, bookmarks, and plugins. Web designers get another target for testing. The quiet winners are people on old machines who can keep browsing after Internet Explorer stops fitting their needs.
2008: Android Open Source Project starts shipping#
Phone makers and app developers feel this one first. Carriers inherit a patch queue. Consumers get devices that may stop receiving updates in 18 to 24 months. The least consulted group is the person holding the phone. The most exposed group is the small repair shop or app studio that must support whatever version a customer brings through the door.
2011: Hudson becomes Jenkins#
A dispute over project control splits Hudson into Jenkins. The people most affected are build engineers and release managers. A CI server is not glamorous, but it sits between source code and shipped software. When plugin APIs drift, small teams with one overworked build admin feel it before large firms with dedicated platform staff.
2014: Heartbleed hits OpenSSL#
A missing bounds check in OpenSSL's heartbeat extension exposes memory to remote readers. Server operators, VPN users, and embedded device owners are the first to react. Small website teams with no security staff must patch, rotate keys, and explain the risk to customers. The maintainers behind OpenSSL also become a story, because a library used by a huge share of the web had very thin funding. The people most affected were not the ones who wrote the bug report. They were the ones who had to rebuild trust in a certificate.
2021: Log4Shell lands in Log4j#
A lookup feature in Log4j 2 allows remote code execution. Java backend teams, Minecraft server operators, and internal IT groups spend days tracing dependencies. Enterprises with software bills of materials move faster. Small shops that inherited a Java app from a contractor move slower. The maintainers are a small volunteer group. They absorb the pressure while thousands of downstream users discover they cannot name the libraries inside their own products.
2023: HashiCorp changes Terraform's license#
HashiCorp moves Terraform from MPL to BSL. Platform engineers, consultancies, and small cloud shops are the most affected. The OpenTofu fork gives them a path, but not an instant one. Procurement teams must recheck terms, and vendors must decide whether to wrap the new license or support the fork. The people with the least slack are the two-person infrastructure teams that run production on Terraform and cannot pause delivery to read a license brief.
2024: Redis changes license, Valkey forks#
Redis moves away from BSD. Application teams running self-hosted caches, managed service providers, and cloud resellers feel the shift. Binaries do not break overnight. Upgrade paths do. A small SaaS company may stay on an old release for a year while lawyers and platform leads argue. The fork gives the community a banner, but the immediate work lands on the engineer who has to test a replacement on a Friday.
2024: xz utils backdoor is caught#
A backdoor is found in xz utils before it reaches most production systems. Linux distribution maintainers, early testers, and embedded vendors are the most affected. Andres Freund, a software engineer, spots the anomaly while debugging unrelated performance issues. Most Linux users never run the affected code. The people who did unpaid audit work absorb the stress. The event also exposes a hard truth: the projects most exposed to attack are often maintained by one person with a mailbox full of patches.
More articles