Slashdot Mirror
Free Software, Free Society
What's between the covers Free Software, Free Society is divided into four sections:
- One: The GNU Project and Free Software (10 chapters)
- Two: Copyright, Copyleft, and Patents (6 chapters)
- Three: Freedom, Society and Software (5 chapters)
- Four: The Licenses
The book starts off on a good note. Key to understanding nearly everything in the book is a basic understanding of what source code is. Since Stallman's usual audiences don't need to have this explained, Richard E. Buckman and book editor Joshua Gay provide a three-page introduction ("A Note on Software") which is as good and concise an explanation as I've ever seen of the meaning of "source code," "compiler," "assembler," "machine code" and "operating system." Without quibbling over details that space has made them gloss over, this section is a good mental boot camp for anyone reading the book with no programming knowledge at all.
This note is followed by a topic guide which walks a prospective reader through the contents of the book better than a table of contents can, pointing out what concepts are dealt with in the book's chapters, a sort of micro-index. (And in a book this brief, it helps make up for the lack of a more thorough index.)
Lawrence Lessig's introduction largely repeats what Lessig has said in the past about the openness of software. One paragraph in particular sums up one of my favorite analogies when it comes to Free software, and one which I think translates well to those familiar with other fields, like art and architecture:
"... Law firms have enough incentive to produce great briefs even though the stuff they build can be taken and copied by someone else. The lawyer is a craftsman; his or her product is public. Yet the crafting is not charity. Lawyers get paid; the public doesn't demand such work without price. Instead this economy flourishes, with later work added to the earlier."
Old hat, new hat.
Those familiar with Richard Stallman will no doubt recognize at least some of these essays, or at least their cores, because of the persistence with which Stallman has spread the word of the origins and underlying philosophies of the GNU project and the Free Software Foundation. The first chapters of the book may bore readers who have heard dozens of times the story of Stallman's experiences with the Incompatible Timesharing System (ITS) in the MIT AI lab, the dissolution of the software-sharing society there, and how it directly led to his quest for a complete Free operating system. Stallman is an engaging writer, though, and I found myself enjoying it even though I have heard the story several times before.
The chapter in this section most likely to trouble those set in conventional thinking when it comes to software is Chapter 4, "Why Software Should Not Have Owners."
Despite the title, the book does not consist entirely of essays; it also includes a transcript of Stallman's speech at NYU in May of 2001, which shows how consistent Stallman's speaking is with his writing style. Some people have derided Stallman (and the FSF) as too academic, removed from the realities of normal computer users and the business world which right now implicitly favors non-Free software, so it's interesting to note the context of that speech -- it was a direct, welcome reaction to the prodding of Microsoft Vice President Craig Mundie's speech on the same campus earlier the same month, in which Mundie casually referred to the "viral aspect" of the GPL, and declared that Free software "puts at risk the continued vitality of the independent software sector."
There's also Stallman's short story "The Right to Read" and even (Chapter 10) the text and score of the Free Software Song. 'The Right to Read" may be the part of the book most appropriate for reprinting in tract form to leave around public libraries: this is a story, not quite hypothetical enough, about a future where every time a book is read, it must be unlocked with a password and authorized by those who hold the strings of copyright -- and sharing books is prohibited. Replace "books" with "e-books" and the story becomes less an allegory as a description of current reality.
Just as current are Chapters 12 ("Misinterpreting Copyright -- A Series of Errors") and 16 ("The Danger of Software Patents"). Stallman's arguments here, despite his protests that practicality is secondary to ethical interests, are eminently practical and should be read by everyone whose work touches either copyright or patents. And contrary to disparagement sometimes heaped on the Free software movement, he does not dismiss either of these in toto -- he simply points out forcefully ways in which these protections can be dangerously perverted.
Some of Free Software, Free Society's contents may strike readers (whatever their level of interest) as needlessly pedantic. I'm thinking here specifically of Chapter 21, "Words to Avoid," which lists 14 words and phrases Stallman discourages in the context of Free software as he defines it. On second glance, I think even this chapter is well suited to the book, since the reasoning presented for his objections to each word on this list (a paragraph or two apiece) will be most informative to people not already steeped in the lore and leanings of the Free Software movement. Some of these (I'll tease by saying that the entry for "content" is my favorite) squeeze in some humor as well.
Stallman's philosophy is what drives his attachment to Free software, but this book is not just a collection of harangues -- there's a great deal of practical advice as well.
Chapter 8, "Selling Free Software" is an essay found in earlier form on the GNU website, which in a few hundred words obliterates a persistent myth about Free software -- that it can't be sold or can't make its sellers a profit. Stallman emphasizes the differences that the GPL has on distribution terms, but lays out the terms clearly:
"Except for one special situation*, The GNU General Public License (GNU GPL) has no requirements about how much you can charge for distributing a copy of free software. You can charge nothing, a penny, a dollar, or a billion dollars. It's up to you, and the marketplace, so don't complain to us if nobody wants to pay a billion dollars for a copy."
Helpfully, that older chapter is preceded by one written earlier this year, "Releasing Free Software if You Work at a University." This is a particularly short chapter -- it takes up only two pages -- but the brevity is to Stallman's credit. I would like to see many more case studies beyond the single example presented (a GNU Ada compiler developed at NYU with Air Force funding, with a contract that specified its source code would be donated to the FSF) but these would probably be better in a book with a narrower scope. By not dwelling on unneeded specifics, Stallman has saved space to explain arguments and tactics which may be useful in persuading your school to endorse a Free software license. I also learned in this chapter that "The University of Texas has a policy that, by default, all software developed there is released as free software under the GNU General Public License." (Can anyone tell me more schools where this is true?)
The practical upshot of a philosophical book. Free Software, Free Society is not a book for casual reading, and has no thrills, cliffhangers or suspense -- unless you apply the thoughts within to current, real situations, in which case you can probably find more excitement than you might care for. When Stallman wrote "The Right to Read," no one had yet been arrested for making eBooks accessible or copyable. This book is intentionally didactic and persuasive.
Your library (local or school) should carry a copy of this book because it is distillation of ideas that are philosophically important but by no means abstract. And if the libraries available to you don't carry it, I suggest filling out a book request form -- which you may be able to do right from your computer. (Here are two online examples from Yale and New York City's branch libraries.) Likewise for (as appropriate) your school's computer science department, law school and business school. It would also make a nice gift to your Congressional representatives, since many of them seem to have forgotten that preserving a free society supposed to be their highest aim.
This is a book worth buying, reading, and passing on.
* That exception is when source code is not physically included with binaries; the source code must then be available upon request from the binaries' provider.
You can purchase Free Software, Free Society directly from the GNU Press site. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
..the online or downloadable version of this book?
there is too much of RMS-bashing these days, here on slashdot and on a lot of other places. Sure, whatever his faults, he has contributed significantly to the software community in general. How many people here can say that? It pays to remeber that even the greatest of minds (Edison, Newton, etc) were often on the wrong side; that doesn't detract from their acheivements.
I find Stallman instead to be one of the most persistently, relentlessly reasonable people whose thoughts I've ever encountered. Stallman may be a dogmatist,
Almost by definition, a dogmatist can't be reasonable, since dogma itself, as a tenet, is not subject to reason.
is the book copyrighted? If not, is it under any license agreement? Or can i scan it in, and redistribute it on the internet (in its entirety, with obvious credit that RMS was the author and not me?)
obviously, since the book has physical attributes, i wouldn't believe or suggest that a physical book itself would be free... but i'm curious if he eats his own dog food.
tangental question...
how did it come about that Lessig's eBook was protected to the point of being unusable? Did not he write it? (/Yoda) And did he not have control over how its protections were to be set? I am a devotee of Lessig's ideas (not to the man himself), but this has always bothered and confused me.
guns kill people like spoons make Rosie O'Donnell fat.
Some people say vi zealots are unreasonable. I disagree, I think you should have to press a special sequence of characters before you can edit a document. ;)
Random is the New Order.
The people who believe most in the principles Free Software has to offer are the least likely to receive anything in return for their efforts (well, barring Richard Stallman himself, but even he is poorly compensated in comparison to Bill Gates or Bill Joy). If you're coding for the joy of coding, then it in and of itself is enough compensation, of course, but if Free Software developers were truly paid at the level at which they contribute to society their work would easily exceed everything Microsoft or other commercial developers have to offer.
Try not. Do or do not, there is no try.
-- Dr. Spock, stardate 2822-3.
That's a dogmatic definition of 'dogma.' The word has the same root as 'doctor' (whose medical meaning is quite recent - the sense of 'professor' is much older) and 'doctrine,' which originally referred to teacher and teaching. So a 'dogma' is generally a received teaching, but that does not at all mean (1) that there is no reason behind the teaching, or (2) that the student is not encouraged to reason about it. The same root is in the Greek word dokein one of whose meanings was 'think.' It also shows up as both 'orthodox' and 'paradox.' Also, 'document.'
Basically, a dogmatist is anyone who professes to have a consistent teaching. While famous examples include Philo of Larissa's elaboration on Plato's Academy 4 and the doctrines of the Councils of the Catholic Church, these do not nearly exhaust the senses of the word. Your definition of dogma as not subject to reason sounds like itself a bit of dogma - something you have been taught, but in this case by someone whose reasoning about it is based on perhaps a judgment about the Catholic Church's instances of dogma, rather than an open study of the history of the term.
"with their freedom lost all virtue lose" - Milton
A lot of people get too caught up in his philosophy and overlook the fact that he's a coding god. I liked this article that sheds some light on his coding abilities.
A musician without the RIAA, is like a fish without a bicycle.
RMS is intolerant of perspectives that differ from his own.
I believe you're stretching the meaning of tolerance a little too far here. Tolerance is useful when we are describing the ability of individuals to get along without significantly interacting. It is a stepping stone from hatred to understanding; i.e., if you can't accept or sympathize with homosexuals, you should at least tolerate them since they don't do you any harm.
But RMS gets very angry at people who try to harm his ability to create software by closing off avenues of inquiry through abuse of the idea ownership system. They are harming him, and they are harming his ability to contribute to the software community.
If there were no relationship between what he gets angry about and his contributions to computing, you would be right that the issues are distinct. But they have everything to do with one another.
microsoftword.mp3 - it doesn't care that they're not words...
along with this message...
and on the first page of every chapter is this notice...The same thing has been done with Linux in general (Red Hat)
Actually, I think that you picked a very poor example in that one. Red Hat realizes the value that core developers brought to Linux. A thousand or so of the major contributors -- who did it for love, not for any hope of future profit -- were given rights to buy RHAT stock at the IPO, making them all quite a boodle of cash if they were smart enough about it. Not only that, but Red Hat pays the salaries of people who used to just do linux development because they wanted to, but because Red Hat is able to make money off of it, they feed them as well.
Very rarely do the engineers and scientists and researchers grab the profits from their inventions. But businesses exist for profit, and that's how the world works: they make the money off of things invented by individuals.
Linux/open-source businesses in particular have been fairly conscious about remembering to reward those who worked to bring about that which they're profitting off of. Goodness knows, it's certainly in their best interests to do so.
Congratulations, you have your ideal world, and you didn't have to do any work to achieve it! Your ideal world, in which there is a mix of MIT, BSD licenses, the GPL, and the licenses of Microsoft, Sun, Sony, and so on, is the world we live in now.
The proponents and owners of the "fascist" licenses are now trying to enlist the governments of the world to help them maintain a stranglehold on the market and people's freedoms to use computers to their full potential. The DMCA is a product of your ideal world.
Your freedom (as in, your freedom to think what you want, read what you want, spend your money as you want, work and live where you wish, maintain your privacy as you wish) is becoming inextricably linked to your freedom to control computers and software. Repeat: IF YOU CANNOT CONTROL COMPUTERS AND THE SOFTWARE THEY RUN, YOU WILL LOSE YOUR FREEDOM. Put another way, severe restrictions can and will be put on how you are allowed to live your life.
Your "ideal world" is the vision of a lazy person who thinks (or hopes) that everything will work out for the best. RMS is not such a person, which is perhaps why you do not seem to understand what the FSF is about.
The GPL license puts restrictions on what you can do.
Must we have this discussion again?
The GPL puts restrictions on adding restrictions. The restriction not to add restrictions is a restriction reducing measure. No wishing for more wishes, no freedom to restrict freedom.
Your oversimplified interpretation of the word "free" is laughable. If there are 1 billion people in the world, the GPL guarantees 1 billion people every freedom related to the software in question save one not only for the original work, but for every possible derivative work. A non-GPL license preserves no rights at all relating to derivative works. The only case in which the users end up with less freedom under the GPL is in a case where a piece of software is BSD/MIT licensed, and no one actually creates a closed derived work- in which case no one wanted to exercise that freedom anyway, and therefore no one would actually have been restricted from doing anything anyway. So among all possible users, the freedom granted by the GPL is provably greater than that granted by your precious MIT license.
My ideal world is one where there is a wide mix of software and sofware licenses in use. Some are free, like MIT. Some promote social goals, like GPL. Some are commercial. And some are facist.
Don't they teach you how to spell in troll-school? You can keep your "facist" licenses.
microsoftword.mp3 - it doesn't care that they're not words...
You can check out the source from CVS. Also, most of the essays are already on the GNU philosophy page, and the rest are being put up this week.
We do request that if you download the book rather than buy it, that you make a donation to the Free Software Foundation instead to help offset the cost of producing and formatting the book for publication. Indeed, I am frankly afraid that our meager savannah resources will collapse from the slashdot effect.Sincerely,
Bradley M. Kuhn
Executive Director, Free Software Foundation