Freie und Open Source Software (FOSS) (OSP): Unterschied zwischen den Versionen
Anna (Diskussion | Beiträge) K (→frei versus offen: links) |
Anna (Diskussion | Beiträge) K (→frei versus offen: add text) |
||
| Zeile 42: | Zeile 42: | ||
= frei versus offen = | = frei versus offen = | ||
| + | |||
| + | [http://www.unix.org/what_is_unix/history_timeline.html Geschichte UNIX] | ||
[http://www.faqs.org/docs/artu/ch02s01.html Origins and History of Unix, 1969-1995] | [http://www.faqs.org/docs/artu/ch02s01.html Origins and History of Unix, 1969-1995] | ||
| − | [ | + | "In 1985 Intel shipped the first 386 chip, capable of addressing 4 gigabytes of memory with a flat address space. The clumsy segment addressing of the 8086 and 286 became immediately obsolete. This was big news, because it meant that for the first time, a microprocessor in the dominant Intel family had the capability to run Unix without painful compromises. The handwriting was on the wall for Sun and the other workstation makers. They failed to see it. |
| + | |||
| + | 1985 was also the year that Richard Stallman issued the GNU manifesto [Stallman] and launched the Free Software Foundation. Very few people took him or his GNU project seriously, a judgment that turned out to be seriously mistaken. In an unrelated development of the same year, the originators of the X window system released it as source code without royalties, restrictions, or license code. As a direct result of this decision, it became a safe neutral area for collaboration between Unix vendors, and defeated proprietary contenders to become Unix's graphics engine." | ||
| + | |||
| + | ... | ||
| + | |||
| + | "In 1986 Larry Wall, previously the inventor of patch(1), began work on Perl, which would become the first and most widely used of the open-source scripting languages. In early 1987 the first version of the GNU C compiler appeared, and by the end of 1987 the core of the GNU toolset was falling into place: editor, compiler, debugger, and other basic development tools. Meanwhile, the X windowing system was beginning to show up on relatively inexpensive workstations. Together, these would provide the armature for the open-source Unix developments of the 1990s. | ||
| + | |||
| + | 1986 was also the year that PC technology broke free of IBM's grip. IBM, still trying to preserve a price-vs.-power curve across its product line that would favor its high-margin mainframe business, rejected the 386 for most of its new line of PS/2 computers in favor of the weaker 286. The PS/2 series, designed around a proprietary bus architecture to lock out clonemakers, became a colossally expensive failure.[17] Compaq, the most aggressive of the clonemakers, trumped IBM's move by releasing the first 386 machine. Even with a clock speed of a mere 16 MHz, the 386 made a tolerable Unix machine. It was the first PC of which that could be said. | ||
| + | |||
| + | It was beginning to be possible to imagine that Stallman's GNU project might mate with 386 machines to produce Unix workstations almost an order of magnitude less costly than anyone was offering. Curiously, no one seems to have actually got this far in their thinking. Most Unix programmers, coming from the minicomputer and workstation worlds, continued to disdain cheap 80x86 machines in favor of more elegant 68000-based designs. And, though a lot of programmers contributed to the GNU project, among Unix people it tended to be considered a quixotic gesture that was unlikely to have near-term practical consequences." | ||
[http://www.gnu.org/ Das GNU Projekt] | [http://www.gnu.org/ Das GNU Projekt] | ||
Version vom 14. November 2008, 09:56 Uhr
Inhaltsverzeichnis
Akademie, Kloster, Handwerk
Pekka Himanen
The Hacker Ethic and the Spirit of the Information Age
Die Fußnoten zu Platon (OSP)
Kooperationsmodelle (OSP)
Richard Sennett
The Craftsman Sennett: Handwerk
Julian Bell. New York Review of Books 55/16
At the same time, Sennett in his mid-sixties—now, by his own description, one of the "elderly" — is attentive to immediate contemporary concerns. Early in his argument's trajectory, the ongoing debates over Wikipedia fall within its penumbra. Is the wildfire expansion of that nonprofit reference Web site a trend to celebrate, or does it show that knowledge acquisition is succumbing to "part anarchy, part mob rule"? Does the incessant shuttle of volunteers' entries and editorial alterations amount to nothing more than an "online multiplayer irreality game," as a onetime editor of the Encyclopædia Britannica has alleged?
Sennett notes that Wikipedia has problems with the quality of its input, but the drift of his thinking comes to the Web site's support. For in principle, at least, it is an "open source" project, one that encourages its users to act as its codevelopers and that publically reveals, rather than conceals, the constant evolution of its content. As with the Linux operating system for computers, the trailblazer for "open source" models in software development, Wikipedia trusts to the good sense and goodwill of interested parties at large. The kernel of the Linux code "can be employed and adapted by anyone; people donate time to improve it."
That is the type of institutional model that Sennett, who inclines to some form of socialism, tends to favor. The foil he sets against it in this context is the Microsoft Corporation, with its secretive, proprietary approach to product development. By contrast, those engaged in "open source" projects such as Wikipedia put considerations of ownership behind them. Their signatures are not on display. Concentrating on the identification of problems and the exploration of fresh possibilities, their online chat is terse and content-packed. A "blunt impersonality turns people outward."
And in such a light Sennett, with a characteristically bold sweep of the hand, associates these networkers with the nameless potters, smiths, and weavers that Hesiod celebrated in archaic Greece, when he composed a hymn to their master god Hephaestus. "Open source" participants form a community of craftsmen to whom the ancient appellation demioergoi [literally, "public producers"] can be applied. It is focused on achieving quality, on doing good work, which is the craftsman's primordial mark of identity.
For Sennett, then, the "craftsman" across the ages has been a person who knows how to do "good work." What is good work? Answers to that question are what he constantly tries to find on his book's rarely beaten and sometimes rugged track of argument. He wishes to close in on a certain quality of activity, rather than on the particular social role that his chosen title might seem to denote.
Paul B. Schmidt, Berlin OSC 15 (2008)
Wie der Wirtschaftsethiker Ulrich Thielemann (Süddeutsche Zeitung, 29.2.08) sagt: „Nicht das Geldverdienen sollte die Hand führen, sondern der Wille, gute Arbeit zu verrichten“, verfolgt der amerikanische Soziologe Sennett die These, dass ein zentrales menschliches Bestreben sei, „seine Arbeit um ihrer selbst willen gut zu machen“. Das ist nun durchaus nicht immer ganz einfach, und eine Quelle der Unzufriedenheit kann das Fehlen dieser Möglichkeit auch bei hohem Einkommen sein. So berichtet Sennett von zahlreichen Linux-Programmierern, die es leid waren, für weitaus mehr Geld mittelmäßige Programme für eine größere Softwarefirma zu schreiben, die ihre Produkte beim Verbraucher testet. Sie entschieden sich, lieber auf Teile ihres Gehalts zu verzichten, aber die Chance zu haben, gute Arbeit zu machen, unter anderem dadurch, dass sie in der open-source-community mit anderen Programmierern kooperieren konnten, statt überwiegend in Konkurrenz zu anderen Leuten ihres Fachs zu stehen.
Auch an anderer Stelle waren solche Firmen im Vorteil, die z.B. bei der Entwicklung neuer Produkte auf Kooperation statt auf Konkurrenz setzten, denn ihre Produkte waren besser oder die Entwicklung verlief schneller. Gute Arbeit entsteht auch dadurch, dass die Entscheider alle wichtigen Informationen erhalten. Wenn in einem Unternehmen die Beschäftigten zwar Freundlichkeit und Teamarbeit simulieren, aber dabei wichtige Informationen zurückhalten, gerät es in Nachteil zu einem solchen, in dem bei allem Respekt vor dem Vorgesetzten in aller Deutlichkeit Kritik vorgetragen und auch gestritten wird, wie dies Sennett von einer Reihe japanischer Unternehmen darstellt.
Perlentaucher | The Guardian, Review | Kostis Velonis
frei versus offen
Origins and History of Unix, 1969-1995
"In 1985 Intel shipped the first 386 chip, capable of addressing 4 gigabytes of memory with a flat address space. The clumsy segment addressing of the 8086 and 286 became immediately obsolete. This was big news, because it meant that for the first time, a microprocessor in the dominant Intel family had the capability to run Unix without painful compromises. The handwriting was on the wall for Sun and the other workstation makers. They failed to see it.
1985 was also the year that Richard Stallman issued the GNU manifesto [Stallman] and launched the Free Software Foundation. Very few people took him or his GNU project seriously, a judgment that turned out to be seriously mistaken. In an unrelated development of the same year, the originators of the X window system released it as source code without royalties, restrictions, or license code. As a direct result of this decision, it became a safe neutral area for collaboration between Unix vendors, and defeated proprietary contenders to become Unix's graphics engine."
...
"In 1986 Larry Wall, previously the inventor of patch(1), began work on Perl, which would become the first and most widely used of the open-source scripting languages. In early 1987 the first version of the GNU C compiler appeared, and by the end of 1987 the core of the GNU toolset was falling into place: editor, compiler, debugger, and other basic development tools. Meanwhile, the X windowing system was beginning to show up on relatively inexpensive workstations. Together, these would provide the armature for the open-source Unix developments of the 1990s.
1986 was also the year that PC technology broke free of IBM's grip. IBM, still trying to preserve a price-vs.-power curve across its product line that would favor its high-margin mainframe business, rejected the 386 for most of its new line of PS/2 computers in favor of the weaker 286. The PS/2 series, designed around a proprietary bus architecture to lock out clonemakers, became a colossally expensive failure.[17] Compaq, the most aggressive of the clonemakers, trumped IBM's move by releasing the first 386 machine. Even with a clock speed of a mere 16 MHz, the 386 made a tolerable Unix machine. It was the first PC of which that could be said.
It was beginning to be possible to imagine that Stallman's GNU project might mate with 386 machines to produce Unix workstations almost an order of magnitude less costly than anyone was offering. Curiously, no one seems to have actually got this far in their thinking. Most Unix programmers, coming from the minicomputer and workstation worlds, continued to disdain cheap 80x86 machines in favor of more elegant 68000-based designs. And, though a lot of programmers contributed to the GNU project, among Unix people it tended to be considered a quixotic gesture that was unlikely to have near-term practical consequences."
Freiheit, Richard Stallman
"Free software" is a matter of liberty, not price. To understand the concept, you should think of "free" as in "free speech," not as in "free beer."
Free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software:
- The freedom to run the program, for any purpose (freedom 0).
- The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
- The freedom to redistribute copies so you can help your neighbor (freedom 2).
- The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.
A program is free software if users have all of these freedoms. Thus, you should be free to redistribute copies, either with or without modifications, either gratis or charging a fee for distribution, to anyone anywhere. Being free to do these things means (among other things) that you do not have to ask or pay for permission.
...
However, certain kinds of rules about the manner of distributing free software are acceptable, when they don't conflict with the central freedoms. For example, copyleft (very simply stated) is the rule that when redistributing the program, you cannot add restrictions to deny other people the central freedoms. This rule does not conflict with the central freedoms; rather it protects them.
You may have paid money to get copies of free software, or you may have obtained copies at no charge. But regardless of how you got your copies, you always have the freedom to copy and change the software, even to sell copies.
"Free software" does not mean "non-commercial." A free program must be available for commercial use, commercial development, and commercial distribution. Commercial development of free software is no longer unusual; such free commercial software is very important.
...
Another group has started using the term "open source" to mean something close (but not identical) to "free software." We prefer the term "free software" because, once you have heard that it refers to freedom rather than price, it calls to mind freedom. The word "open" never refers to freedom.
Categories of Free and Non-Free Software
Copylefted software
Copylefted software is free software whose distribution terms ensure that all copies of all versions are free software. This means, for instance, that copyleft licenses generally disallow others to add additional requirements to the software (though a limited set of safe added requirements can be allowed) and require making source code available. Some copyleft licenses, such as GPL version 3, block other means of turning software proprietary.
In the GNU Project, we copyleft almost all the software we write, because our goal is to give every user the freedoms implied by the term “free software.” See Copylefted for more explanation of how copyleft works and why we use it.
Copyleft is a general concept; to actually copyleft a program, you need to use a specific set of distribution terms. There are many possible ways to write copyleft distribution terms, so in principle there can be many copyleft free software licenses. However, in actual practice nearly all copylefted software uses the GNU General Public License. Two different copyleft licenses are usually “incompatible”, which means it is illegal to merge the code using one license with the code using the other license; therefore, it is good for the community if people use a single copyleft license.
Non-copylefted free software
Non-copylefted free software comes from the author with permission to redistribute and modify, and also to add additional restrictions to it.
If a program is free but not copylefted, then some copies or modified versions may not be free at all. A software company can compile the program, with or without modifications, and distribute the executable file as a proprietary software product.
The X Window System illustrates this. The X Consortium releases X11 with distribution terms that make it non-copylefted free software. If you wish, you can get a copy which has those distribution terms and is free. However, there are non-free versions as well, and there are popular workstations and PC graphics boards for which non-free versions are the only ones that work. If you are using this hardware, X11 is not free software for you. The developers of X11 even made X11 non-free for a while.
____
Now, you might wonder why I don't just duck the issue and avoid all this grief. When SIGLINUX invited me to speak, I could simply have said “No, sorry” and the matter would have ended there. Why didn't I do that? I'm willing to take the risk of being abused personally in order to have a chance of correcting the error that undercuts the GNU Project's efforts.
Calling this variant of the GNU system “Linux” plays into the hands of people who choose their software based only on technical advantage, not caring whether it respects their freedom. There are people like Barr, that want their software “free from ideology” and criticize anyone that says freedom matters. There are people like Torvalds that will pressure our community into use of a non-free program, and challenge anyone who complains to provide a (technically) better program immediately or shut up. There are people who say that technical decisions should not be “politicized” by consideration of their social consequences.
In the 70s, computer users lost the freedoms to redistribute and change software because they didn't value their freedom. Computer users regained these freedoms in the 80s and 90s because a group of idealists, the GNU Project, believed that freedom is what makes a program better, and were willing to work for what we believed in.
Getrennte Wege 1997
aus: Glyn Moody: Rebel Code S. 165ff
An important catalyst for these changes was the appearance of Eric Raymond's essay The Cathedral and the Bazaar, which he had finished in January 1997. "One of the first people I bounced the paper off was Erik Troan," Raymond explains. "He was a key developer at Red Hat, and a good friend of mine.
...
The conference took place in San Jose, California, on 20 August 1997. Larry Wall made his first idiosyncratic keynote, which bore the punning and yet descriptive title of `Perl Culture,' and Raymond read The Cathedral and the Bazaar. This time, Raymond notes, there was a subtle difference to the response he received from that of the audience in Germany. "In the intervening couple of months," he explains, "the paper had spread through the culture so rapidly that at the Perl conference there was already a sense of celebration that hadn't been present in Bavaria, where it had nonetheless been received with "wild enthusiasm," as he re-calls.
...
O'Reilly decided to organize another meeting. "Late in the fall [of 1997] I started organizing a meeting for the spring, which was really this summit, which we called the Freeware Summit. Where I thought, gosh, let me just see if I can get the heads of these various well-known projects ... together and meet." Those heads included Linus, Larry Wall, Brian Behlendorf, Eric Allman, Paul Vixie and Eric Raymond. Originally planned as a meeting for hackers who were based on the West Coast of the United States, it was later broadened to be more inclusive. Although not the only gap in the line-up—there was no representative from the free BSD variants, for example—the key name conspicuous by its absence was that of Richard Stallman.
"RMS was not invited," Raymond explains. "I argued that he should be, and lost the argument. Tim O'Reilly and the other co-organizers thought he would disrupt the effort to achieve a consensus from which we could go forward." The exclusion turned out to be symbolic. As well as allowing the others to meet and swap experiences, the Freeware Summit signaled a key shift within that world and made explicit a tension that is still unresolved.
It all centered on the word "free" in "free software." For Stallman, freedom is absolutely central to everything he does, and so there could be no question of choosing anything else. But even his admirers have trouble with the word, if not the idea. For example, Bruce Perens has described the GNU GPL as "one of the revolutionary documents of our century" But he acknowledges, "The word `free' is somewhat intimidating to business in that they think they can't make money if it's free. English has this problem that most of the time when we say `free' we mean without cost, and the way that Richard Stallman applies `free' to `free software' it means `with liberty.' So he was talking about rights not price; that didn't really come over."
A couple of months before the Freeware Summit, Raymond began looking for a new name that would be less ambiguous than the existing "free software." The trigger for this search was Netscape's announcement in January 1998 that it was releasing the source code for its Communicator browser suite (discussed in Chapter 11). In the wake of this move, Raymond saw that the free software community had a unique opportunity to exploit the media interest it had generated.
After visiting Netscape at its headquarters in Mountain View, California, Raymond convened a meeting at the offices of the GNU/Linux hard-ware company VA Research, at that time also located in Mountain View, on 3 February 1998. "I put forward the proposition that we needed a new label that was less threatening to the mainstream," he remembers, "and we brainstormed it and we came up with `open source."'
Those taking part included Raymond; Larry Augustin, the CEO of VA Research; John "maddog" Hall, who was there by telephone for part of the meeting; Sam Ockman, from the Silicon Valley Linux User Group; and Christine Peterson, president of Foresight Institute. Raymond ex-plains, "The Foresight Institute [is] a bunch of thinkers who are concerned about nanotechnology," building machines on a molecular scale, "trying to bring it into existence, and trying to control it so that we use it properly." It was Peterson, he says, "who actually came up with the term `open source."'
One of the main items of business for the Freeware Summit organized by O'Reilly, which took place on 7 April 1998, in Palo Alto, was to find an alternative to the name "free software" that all the leaders present were happy to rally behind. Suggestions included not only the newly coined "open source," but also "freeware," "sourceware," and "freed software." After some discussion, a vote was held, and "open source" won.
...
The Open Source Definition lays down nine criteria that the distribution license of software must meet to be called "open source." The first three — the ability to distribute the software freely, the availability of the source code, and the right to create derived works through modifications — enshrine the basic characteristics that lie at the heart of the new software methodology. The other criteria spell out ancillary requirements; for example, they ensure that the license does not discriminate against persons or groups or fields of endeavor (such as business), and they close loopholes that might otherwise be exploited.
In a press release issued before the Freeware Summit, the software projects it embraced were called "freeware"; after the summit, another press release called them "open source" ("sourceware" was also mentioned). The reason given for the shift is significant: "While this type of software has often been called 'freeware' or 'free software' in the past, the developers agreed that commercial development of the software is part of the picture, and that the terms `open source' or `sourceware' best describe the development method they support."
That is, the meeting represented a conscious attempt to make comprehensible and acceptable to software companies what had hitherto been something of a fragmented and fringe activity. This was an important repositioning. The leaders present at the Freeware Summit had agreed that to drive the uptake of their software further they needed to adopt a more business-friendly approach—including an easily remembered and understood name. In other words, a brand.
Richard Stallman has always viewed this shift with alarm. "The open source movement is Eric Raymond's attempt to redirect the free software movement away from a focus on freedom," he says. "He does not agree that freedom to share software is an ethical/social issue. So he decided to try to replace the term 'free software' with another term, one that would in no way call to mind that way of framing the issue. "In the GNU Project," Stallman emphasizes, "we want to talk about freedom, so we continue to describe our software as 'free software'; we do not use the term 'open source.' Raymond hopes that using the term 'open source' will convince existing software companies to release useful programs as free software. This is useful when you can do it, but what our community needs most is to be full of users who value their freedom and will not easily let it go."
There was little that Stallman could do to prevent the others from carrying out what amounted to a rebranding exercise. The marketing aspect of the summit had been one of the key considerations even while it was being planned. "As we thought about it," O'Reilly recalls, "we said, gosh, this is also a great PR opportunity — we're a company that has learned to work the PR angles on things. So part of the agenda for the summit was hey, just to meet and find out what we had in common. And the second agenda was really to make a statement of some kind about this was a movement, that all these different programs had something in common."
At the end of the summit, a press conference was held. Nothing could symbolize better the new approach than this phalanx of top hackers facing the press for all the world like the board of some conventional corporation. O'Reilly recalls that "the basic message was, you guys [in the press] are talking about 'are you going to beat Microsoft?' — and I said, look at these [open source] guys. Every one of them has dominant market share, with no money, nothing but the power of their ideas, and this new model. And I went down the list and said look, here's Apache, here's Sendmail, all these programs that are the market leader. I said, so tell me this isn't a winning model.""
"Perhaps in the end the open-source culture will triumph not because cooperation is morally right or software ``hoarding is morally wrong (assuming you believe the latter, which neither Linus nor I do), but simply because the closed-source world cannot win an evolutionary arms race with open-source communities that can put orders of magnitude more skilled time into a problem."
Linus Torvalds: LINUXs History
Linus Torvalds: The Origins of Linux
zurück zu Open Source Philosophie (Vorlesung Hrachovec, Winter 2008)
