Lunduke
News • Science & Tech
Who really coined the term 'Open Source'?
The story you've heard is wrong.
August 10, 2023
post photo preview

Nowadays, “Open Source” is a well understood, widely used concept. Everyone who works within the software development world understands what it means.

But… who coined the term? Who is the first person to actually use the phrase “open source” in reference to software? Let's dive into some of the (sometimes conflicting) statements from multiple people… and what the reality actually looks like.

Was it Eric S Raymond or Bruce Perens? (Who, together, founded the Open Source Initiative in 1998.) Or, perhaps, Richard Stallman? Turns out… not any of those guys. At least not initially.

Let's start with the accepted origin of the term by the Open Source Initiative… and then dig further into the past... and why the Open Source Initiative is very, very wrong.

February 5, 1998 - Christine Peterson

In a recounting of a meeting, held on Feb 5, 1998, Christine Peterson of the Foresight Institute was attending a meeting with the likes of Eric S Raymond and Jon “maddog” Hall.

During that meeting, according to a recounting by Peterson, the topic turned to terminology. What phrase should be used for what we all now understand as “open source”?

A few options were floated – such as “freely distributable”, “cooperatively developed”, and “sourceware”. Christine Peterson recals that she was “the originator of the term ‘open source software’” and “between meetings that week, I was still focused on the need for a better name and came up with the term ‘open source software.’ While not ideal, it struck me as good enough.”

Peterson mentioned the phrase to Todd Anderson, who then mentioned it during the meeting. Peterson allowed the rest of the members of that 1998 meeting to come to their consensus on it.

Eric S Raymond, in response to this, stated the following:

“Chris's account matches my recollections in every respect and reminds me of some details I had forgotten. I fully endorse it.

 

I can add that it was indeed I who explicitly brought up terminology as an issue. I had a clearer initial sense than others there (though they did catch up with me later) that we were in effect planning a marketing and branding campaign. That sense was driving my thinking, and continued to do so for months afterwards. But it was something I didn't talk about much because I knew “marketing” was a bad word to these died-in-the-wool geeks, something they'd need to get used to thinking about gradually. I'd had to struggle with the concept myself before making peace with it.

 

The only other important thing this account leaves out is something Chris didn't know because she couldn't read my mind. The truth is that I spotted “open source” as the winner we were looking for almost immediately, the first or maybe second time it came up, well before I started advocating for it later in the discussion.

 

You see, I too was feeling like it was important not to step on the discussion, better to allow a consensus to develop without me forcing it. But I spotted the useful connection to “open source” as used in intelligence work immediately and was more excited than I let on. It seemed perfect for our propaganda needs - ideologically neutral, easily parsed, just enough connection to a respectable and established term of art. I was very impressed with Chris for inventing it.

 

I actually felt a considerable sense of relief when the other participants gravitated to the term. I would have fought for it over the alternatives on offer, but didn't have to. Bright crowd at that meeting; I was ahead of the curve only because I had put concentrated thought into the problems before I walked in. We all figured out what needed to be done, and we did it.

 

Ever since I was first reminded that “open source” was Chris's coinage I've been careful to credit it to her. She deserves her happy twinge. Maybe I would have come up with the same term or something as good myself, maybe not - it's good that we didn't have to roll those dice.”

But.

Was that really the first time the phrase “open source” was used in reference to software?

Turns out… no.

It, absolutely was not.

Let's go back further.

September 10, 1996 - Caldera

Two years earlier, in 1996, Caldera had acquired a number of assets from Novell. This included DR-DOS, CP/M, and many others originally created by Digital Research (helmed by the late, great Gary Kildall).

On Sep 10, 1996, Caldera released the source code for DR-DOS. The headline for the press release reads as follows:

“CALDERA. ANNOUNCES OPEN SOURCE CODE MODEL FOR DOS”

Going on to say:

“Caldera believes an open source code model benefits the industry in many ways.”

Clearly the phrase “open source” was in common usage (at least among some groups or companies) back in 1996.

But what about… earlier than that?

August 19, 1993 - Jerome (Jerry) Schneider

In a 1993 USENET post (to comp.os.ms-windows.programmer.win32), Jerome Schneider made the following statement:

“Anyone else into “Source Code for NT”? The tools and stuff I'm writing for NT will be released with source. If there are “proprietary” tricks that MS wants to hide, the only way to subvert their hoarding is to post source that illuminates (and I don't mean disclosing stuff obtained by a non-disclosure agreement). Open Source is best for everyone in the long run.

In a posting entirely about the goodness of releasing source code… it is refered to directly as “Open Source” (with capital first letters). Clearly, we're back to at least 1993 as a commonly used term... a term that was felt to be so obvious and common that it didn't need further explanation.

December 4, 1990 - Kent, the man from xanth

In December of 1990 a post was made to two USENET newsgroups (comp.sys.amiga and alt.religion.computers) that contained the following line:

“BSD's open source policy meant that user developed software could be ported among platforms”

The author was… “Kent, the man from xanth”.

Seriously.

But… can we go back… further?

October 10, 1989 - Chris Mc Donald

October. 1989. Another USENET post (this time to comp.virus) contains the following:

“I am struck by the lack of any reference to Virus-L, RISKS Forum and other INTERNET services which have for years provided we users the best available, open source information on the subject of computer viruses.”

That one feels iffy to me. Could have been interpreted a few different ways. So, let's continue digging back through time.

February, 1987 - The NSA

In a 1990 USENET post (to sci.crypt) by Tony Patti (editor of “Cryptosystems Journal”), there is a reference to a February 1987 document, being obtained via the Freedom of Information Act, which contains the following:

“Although software was developed from open source material, the application of that information into the subject software program contains cryptographic capabilities that are controlled under category 13B.”

Tony Patti, who published that snippet, goes on to say:

“My primary concern is that those policies must comply with the U.S. Constitution and thereby allow the free dissemination of open-source/published material – including software (ESPECIALLY FREE SOFTWARE) which is developed directly from published algorithms.”

Now. Internal usage of the phrase “open source” within the NSA might be confirmed as early as 1987.

What this shows, in far more certainty, is a common understanding of the term as early as May 11th of 1990 (the date of the USENET post from Tony Patti).

So. Who coined the term?

The question of “Who coined the phrase Open Source” is still difficult to answer. But we can, fairly definitively, say this much we know:

  • The first known usage of the phrase (in context) by a company would be Caldera in 1996.

  • The first known usage of the phrase (in context) by an individual / journalist would be May of 1990 by Tony Patti.

  • The first known potential usage of the phrase (in context) by a government agency might be the NSA in 1987.

Could there be earlier references than these? It's possible. But, after some exhausting digging, this is as far back as I (and others) seem to be able to go.

One thing is absolutely certain: The term was definitely not created in 1998 by Christine Peterson.

August 9th, 2023 Update

This article was originally published back in November of 2021.

The Open Source Initiative, whose leadership has seen this article, continues -- to the present day -- to push the false story of the term being coined in 1998 by Christine Peterson.

Why?  They know, without a doubt, that the phrase dated back far earlier than 1998.  Yet they cling, almost desperately, to their provably false tale.  How weird is that?

What on Earth could they possibly gain by trying to change history in this way?  It boggles the mind.

Details like this are important.  Getting our history -- the history of Computers -- factually correct is important.  Because we love computers.  And making up false histories about them just makes no sense at all.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
7
What else you may like…
Videos
Podcasts
Posts
Articles
Lunduke Journal Videos Now Subscriber Exclusives

All articles and audio podcasts remain 100% free for everyone.

The Article:
https://lunduke.substack.com/p/lunduke-journal-videos-now-subscriber

00:09:55
Open Source Orgs Pledge Fealty to United Nations

Linux Foundation, GNOME Foundation, others pledge to "support the needs of the United Nations", promote DEl discrimination & RISE.

The article:
https://lunduke.substack.com/p/open-source-orgs-pledge-fealty-to

00:30:10
Counter-Strike 2 Switched to Wayland (for One Day)

After a number of significant issues when running under Wayland, Valve's CS2 is now back to X11 as default. Wayland advocates blame everything but Wayland.

00:13:19
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044
post photo preview

Not at all nerdy, but I saw this on Substack and it gave me a chuckle. Consider it a friendly reminder to always proofread what you write, lol.

post photo preview

Anybody running Omarchy on Framework computers and need help adding hibernation?

post photo preview
post photo preview
Tea App Clone Exposes Driver’s Licenses
Last month the Tea App exposed 60 GB of personal data (including the government ID of users). Now a clone "TeaOnHer" App did the exact same thing. The future is stupid.

Last month, we saw the massive data breach of the “Tea App” — a smartphone app for women to talk about men they don’t like — resulting in over 60 GB of personally identifiable data leaked out to the public. Stuff like selfies and pictures of drivers licenses.

Well, it didn’t take long for a “TeaOnHer” App to appear — with the same basic functionality, except this time for men to talk about women they don’t like.

 

And, of course, the developer of “TeaOnHer” made the same basic mistake that the “Tea App” made: They permanently stored a ton of personal information. Including, once again, divers licenses.

You can already see where this is going.

Driver’s Licenses Everywhere

Almost as soon as the “TeaOnHer” app went live, writers for TechCrunch went looking to see if they could easily access any of that data. Because wouldn’t that be crazy if a copy-cat app made the exact same kind of security mistakes as the app it was copying?

What TechCrunch found was that it took no more than around 10 minutes for them to begin accessing pictures of drivers licenses of user accounts.

 

10 minutes!

With a bunch of the usual suspects of bad security being involved: unprotected file storage (in this case, Amazon), public API documentation, and a lack of secured API calls.

Now, unlike the “Tea App” breach — which resulted in massive archives of personal data published all over the web — it isn’t known if these vulnerabilities actually resulted in significant data archives getting out there in the wild.

But, as the writers at TechCrunch put it, “The bugs were so easy to find that it would be sheer luck if nobody malicious found them before we did.”

There’s a Lesson Here… But it Won’t Be Learned

Sure, this “hack” of the “TeaOnHer” App was easy — as was the hack of the “TeaApp” before it. Both of those systems were comically insecure.

But, the reality is, no complex online system is truly secure.

Have a website or App which stores (and publishes) user data? It can be hacked.

And, if there is sufficient interest in obtaining whatever data is being stored, not only can it be hacked… but it will be hacked.

The HaveIBeenPwned site, alone, has documented close to 15 Billion (with a B) accounts which have not only been breached… but reported and (often) made available in some way.

 

And that 15 Billion is only the breached accounts which we know about.

Anyone who works in IT can tell you that the vast majority of data breaches are never discovered. And the majority of those which are discovered… are never disclosed publicly.

Considering that the current population of the Earth is roughly 8 Billion, it’s safe to assume that every single adult on Earth, with an Internet connection, probably has several breached accounts already.

With the frequency, and size, of such data breaches increasing.

Should these Tea Apps have had better security? You bet your tuchus. From the looks of things neither developer spent any significant time trying to implement even the most basic security precautions.

For Pete’s sake, at least try to slow the hackers down a little.

But the real problem here is not the total lack of security — even “good” security can (and will) be overcome.

No.

The real problem is the type of data being permanently stored, in an Internet accessible way, by these services. If a service is likely to be breached (and any significant service is), a key goal is to limit the amount of data which a hacker can gain access to.

Here are a few good rules of thumb when dealing with data being stored on an Internet accessible server:

  • Do not store any more data, at any given moment, than is 100% necessary.

  • If previously stored data is no longer needed, delete it. Completely. Not “flagged” for deletion. Actually deleted.

  • Whatever data you are storing should be encrypted whenever possible.

  • If sensitive personal data absolutely must be stored, for legal and regulatory reasons, consider physical archives stored in a secure location instead of an Internet connected server.

  • And, of course, don’t use unprotected (or barely protected) “cloud” file storage like the numbskull developers of these “Tea” apps did. That never ends well.

Simple guidelines which, if followed, could significantly reduce the negative impact of inevitable data breaches.

But, of course, few online services — big or small — will follow such guidelines. They will continue expanding the quantity of data they store on increasingly complex systems.

Which means we’ll see more and more data breaches — containing an ever increasing amount of personal data.

Welcome to the future.

The stupid, stupid future.

Read full Article
post photo preview
50% Off Lunduke Journal for August
You save money. The Lunduke Journal gets more subscribers. Win-win.

This last weekend we had a “50% off Subscriptions” sale — and the response was nothing short of phenomenal. Amazing to see so many people supporting truly independent Tech Journalism!

The future looks bright.

You know what? Just for kicks, let’s extend that 50% off… for the entire month of August.

Take your time. Pick the subscription type (below) that makes the most sense for you (there are many, most excellent options).

Note: The 50% off discounts are available via Locals, Substack, & Itch (MP4 Downloads). Monthly subscriptions are also available on X, Patreon, & YouTube, but those platforms do not have the ability to provide these types of discounts.

If you’re ever unsure of where to grab the latest articles, podcasts, and videos from The Lunduke Journal, check out Lunduke.com.

50% Off Yearly or Monthly Subscription:

Available via both Locals and Substack. (This includes full access to all new videos & the community Forum.)

That means $3 / Month. Or $27 / Year (which works out to $2.25 / Month).

Via Lunduke.Locals.com:

Via Lunduke.Substack.com:

Note: You can also grab a Monthly subscription via X, YouTube, or Patreon. There’s no way to offer a discount on those platforms. But those are still good options!

The Famous Lifetime Subscription:

The "World Famous Lunduke Journal Lifetime Subscription" is exactly what it sounds like. Pay once and get full access to The Lunduke Journal. For life.

Now, through the entire month of August… you can snag one at a crazy discount. Normally these are $200… but you can grab one for $100. (You can also pay more if you’d like to donate a little extra.)

The Lifetime Subscription can be obtained via Locals, Substack, or using Bitcoin. All three options work great and are super easy (& all three include full access to both new videos & the community Forum). Scroll down and choose your option.

Note: The Lifetime Subscription only applies to Substack and Locals. Other platforms (such as X, Patreon, & YouTube) do not provide the functionality necessary to create Lifetime Subscriptions.

How to get a Lifetime Subscription via Locals:

  1. Go to Lunduke.Locals.com/support.

  2. Select "Give Once".

  3. Enter "100" (or more) into the amount field.

  4. After checking out, Lunduke will toss you an email once your account is set to full lifetime status. (This usually happens within a few hours.)

How to get a Lifetime Subscription via Substack:

  1. Go to Lunduke.Substack.com/subscribe.

  2. Select the “Lifetime Subscription” option.

  3. After checking out, Lunduke will toss you an email once your account is set to full lifetime status. (This usually happens within a few hours.)

If you would also like full, Lifetime access to Lunduke.Locals.com (which is included):

  1. Make a free account on Lunduke.Locals.com.

  2. Email “bryan at lunduke.com” with the email address you use on both Substack and Locals (can be different email addresses).

  3. Lunduke will toss you an email once your account is set to full lifetime status on Locals.

How to get a Lifetime Subscription with Bitcoin:

You can also obtain a Lifetime Subscription via Bitcoin.

bc1qyjakve8fywm8pz2v99v57yhjj0vzr2vjze6fcq

  • Email "bryan at lunduke.com" with the following information: What time you made the transaction, how much was sent (in Bitcoin), and the email address you use (or plan to use) on Locals.com or Substack.com (or both).

50% Off DRM-Free, MP4 Downloads:

Want to be able to download every show The Lunduke Journal releases (and watch them on whatever device you like)? Yeah. You can do that. For 50% off.

Note: This DRM-Free download option does not include access to the Forum. This option is strictly for downloading the episodes.

No matter which type of subscription you choose, thank you for your support! Every subscription goes directly towards keeping The Lunduke Journal running well into the future.

-Lunduke

Read full Article
post photo preview
Linux Foundation’s New Banned Words: Hung, Pow-wow, & Sanity Check
The Academy of Motion Picture Arts & Sciences, Netflix, Apple, & Intel teamed up with The Linux Foundation to say "don't use HUNG when talking about software."

The Linux Foundation has announced the release of a new “Inclusive Language Guide” — which adds a handful of new words you are not allowed to say.

And it’s even more ridiculous than you might expect.

 

This new “Inclusive Language Guide” is designed to “drive a more diverse, equitable, and inclusive culture” (read: DEI) and to replace “offensive language” with “acceptable language”.

Past iterations of the “Inclusive Language Guide” included “Socially Charged” words such as “Master / Slave”, “Black / White”, and even “Owner”.

This new revision officially adds “Pow-wow” to that list of death-causing words.

 

Of course, any “gendered language” remains firmly off limits. “Manpower”? Can’t say that. And definitely don’t use “gendered” pronouns like “he” or “she”.

Doing so is literally genocide.

 

Which brings us to my favorite new additions (to the “Ableist” and “Violent” language sections of the list).

  • Sanity Check

  • Dummy

  • Hung

That’s right. You can’t use the word “hung” anymore.

 

I deleted 3 different titles for this story containing the word “hung”. They were all very entertaining and very inappropriate. I would like credit for the restraint I am showing right now.

As crazy, insane, and abnormal (see what I did there?) as this list of “bad” words is… what’s even stranger is the group behind it.

This is a joint project between The Linux Foundation and — wait for it — the Academy of Motion Picture Arts & Sciences. Yes. The one that produces the Oscars.

 

The two organizations teamed up to create the Academy Software Foundation.

Which, apparently, ran out of worthwhile things to work on… and, instead, chose to add “hung” to a “don’t use this word in the software industry” list.

That organization also worked with the Alliance for OpenUSDanother Linux Foundation Project — to publish this list.

 

Who, exactly, is responsible for making all of this happen at the Alliance for OpenUSD?

Pixar, Nvidia, Adobe, Autodesk, and Apple.

 

And the leadership over at the Academy Software Foundation includes companies like Netflix, Sony, Adobe, Intel, Microsoft, and Epic Games.

 

Right about now you may be wondering why Epic Games and Amazon is so worried about you using the word “hung”.

I don’t have an answer for you.

It’s weird.


Thanks to all of the subscribers to The Lunduke Journal for making this work possible — without taking a single dime from Big Tech (or running a single ad). Check Lunduke.com for all the ways you can get the articles, podcasts, and videos.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals