ACP, One of the Oldest Open Source Apps 102
Esther Schindler writes "The Airline Control Program (ACP), introduced by IBM around 1967, predated the term 'open source' by decades. But you may be surprised by how much of its development resembles the FOSS movement today. The ITWorld.com article An Abbreviated History of ACP, One of the Oldest Open Source Applications describes what made it special."
Anonymous Coward (Score:3, Insightful)
This was how it was back in the days, and that is why RMS started GNU and FSF, to keep it that way.
Re:It's not open source. (Score:5, Insightful)
I think you are confusing Open Source with Free Software.
Re:It's not open source. (Score:5, Insightful)
What you're looking for is GNU/Freedom.
Re:It's not open source. (Score:1, Insightful)
http://opensource.org/docs/osd [opensource.org]
There's quite a few more requirements than just having the code be available.
Re:It's not open source. (Score:4, Insightful)
So says OSI, but they haven't actually managed to establish legal control over the term 'open source', so at best, the definition is contested, at worst, there are multiple meanings.
Re:It's not open source. (Score:3, Insightful)
http://opensource.org/docs/osd [opensource.org]
There's quite a few more requirements than just having the code be available.
Yes, and those requirements go beyond open source; it's more a definition of free software than open source. While many peopel view open source and free as one and the same I think it's worthwhile to differentiate between the two.
BSD, for example, is an open source project with a license that differs from the above in allowing for proprietary use as well.
Re:It's not open source. (Score:5, Insightful)
What the hell is wrong with moderators today? This is not insightful or informative... loufoque make a perfectly valid point. ACP may resemble open source, but it is not open source.
Claiming that the definition of open source does not include redistribution rights is revisionist, if not totally absurd.
Re:It's not open source. (Score:3, Insightful)
Non-advertise clause BSD meets those terms perfectly - http://opensource.org/licenses/bsd-license.php [opensource.org]. You can allow *more* things, you just can't allow *less*.
Those people did essentially come up with the term "open source", using their definition seems reasonable. Of course they couldn't trade mark it since it's a descriptive term.
"Free software" clearly means "software without cost" but using that definition in a discussion about "open source" and "free software" licenses is retarded.
Re:Definition 1, Definition 2, etc. (Score:5, Insightful)
"speciality coffee" isn't a specifically crafted term of art invented by a particular organization.
"Open Source" is.
Re:Ummm, Spacewar!? (Score:5, Insightful)
> but it was rare to have a mechanism in place to submit changes anywhere or pass updates to
> all the users (remember - no internet, few modems, source mostly passed on 7 or 9 track tape reels).
Actually both existed. Spacewar! was distributed primarily in paper-tape form, patches were contributed with paper, scissors and tape.
No, really.
Maury
Re:Anonymous Coward (Score:5, Insightful)
RMS was angered when a printer manufacturer wouldn't supply the source code to the printer driver, IIRC.
And what most people miss about this story is not just that the manufacturer wouldn't provide the driver. It was that they refused to provide the driver so that rms could modify it so that MIT could use the hardware in the way that they pleased after paying for it.
The device was a shiny new laser printer. rms wanted to add a feature to the driver - notifying someone when (not if) the printer jammed so that print jobs wouldn't get backed up when the printer jammed without having to have someone babysit the printer. The printer maker (I believe it was Xerox, but I could be wrong on this part) didn't want to give up the source because they were afraid that it contained trade secrets because they were the only game in town for laser printing.
The refusal of source code for drivers goes on today, mainly from wireless manufacturers (with the added point that they feel they might be liable if someone violates an FCC reg because they tweaked the driver) and the video card makers.