User:Ncrfgs/free-knowledge-requires-free-software-and-free-file-formats.html

From Wikipedia, the free encyclopedia

edit ./
edit ../
edit copyrigh.html
edit copyrigh.it.html
edit free-knowledge-requires-free-software-and-free-file-formats.html
edit free-knowledge-requires-free-software-and-free-file-formats.it.html
edit hrunk
edit introduction-opensource.html
edit introduction-opensource.it.html
edit linux-gnu-freedom.html
edit linux-gnu-freedom.it.html
edit shouldbefree.html
edit shouldbefree.it.html
http://logosfoundation.org/copyleft/copyrigh.html
http://blog.jimmywales.com/index.php/archives/2004/10/21/free-knowledge-requires-free-software-and-free-file-formats/
http://www.slackbook.org/html/introduction-opensource.html
http://www.gnu.org/philosophy/linux-gnu-freedom.html
http://www.gnu.org/philosophy/shouldbefree.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">

<head profile="http://gmpg.org/xfn/11"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Jimmy Wales » Blog Archive » Free Knowledge requires Free Software and Free File Formats</title>

<meta name="generator" content="WordPress 1.5.2" />

<link rel="stylesheet" href="http://blog.jimmywales.com/wp-content/themes/default/style.css" type="text/css" media="screen" />

<link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://blog.jimmywales.com/index.php/feed/" /> <link rel="alternate" type="text/xml" title="RSS .92" href="http://blog.jimmywales.com/index.php/feed/rss/" /> <link rel="alternate" type="application/atom+xml" title="Atom 0.3" href="http://blog.jimmywales.com/index.php/feed/atom/" /> <link rel="pingback" href="http://blog.jimmywales.com/xmlrpc.php" />

<style type="text/css" media="screen"> /* To accomodate differing install paths of WordPress, images are referred only here, and not in the wp-layout.css file. If you prefer to use only CSS for colors and what not, then go right ahead and delete the following lines, and the image files. */

body { background: url("http://blog.jimmywales.com/wp-content/themes/default/images/kubrickbgcolor.jpg"); } #page { background: url("http://blog.jimmywales.com/wp-content/themes/default/images/kubrickbgwide.jpg") repeat-y top; border: none; } #header { background: url("http://blog.jimmywales.com/wp-content/themes/default/images/kubrickheader.jpg") no-repeat bottom center; } #footer { background: url("http://blog.jimmywales.com/wp-content/themes/default/images/kubrickfooter.jpg") no-repeat bottom; border: none;}

/* Because the template is slightly different, size-wise, with images, this needs to be set here If you don't want to use the template's images, you can also delete the following two lines. */

#header { margin: 0 !important; margin: 0 0 0 1px; padding: 1px; height: 198px; width: 758px; } #headerimg { margin: 7px 9px 0; height: 192px; width: 740px; }

/* To ease the insertion of a personal header image, I have done it in such a way, that you simply drop in an image called 'personalheader.jpg' into your /images/ directory. Dimensions should be at least 760px x 200px. Anything above that will get cropped off of the image. */ /* #headerimg { background: url('http://blog.jimmywales.com/wp-content/themes/default/images/personalheader.jpg') no-repeat top;} */ </style>

<link rel='archives' title='November 2005' href='http://blog.jimmywales.com/index.php/archives/2005/11/' /> <link rel='archives' title='September 2005' href='http://blog.jimmywales.com/index.php/archives/2005/09/' /> <link rel='archives' title='April 2005' href='http://blog.jimmywales.com/index.php/archives/2005/04/' /> <link rel='archives' title='February 2005' href='http://blog.jimmywales.com/index.php/archives/2005/02/' /> <link rel='archives' title='January 2005' href='http://blog.jimmywales.com/index.php/archives/2005/01/' />

<link rel='archives' title='November 2004' href='http://blog.jimmywales.com/index.php/archives/2004/11/' /> <link rel='archives' title='October 2004' href='http://blog.jimmywales.com/index.php/archives/2004/10/' />


<style type='text/css'> .hilite { color: #fff; background-color: #f93; } </style> </head> <body>




<a href="http://blog.jimmywales.com/index.php/archives/2004/10/21/free-knowledge-requires-free-software-and-free-file-formats/" rel="bookmark" title="Permanent Link: Free Knowledge requires Free Software and Free File Formats">Free Knowledge requires Free Software and Free File Formats</a>

People sometimes ask me why I’m so adamant that Wikipedia must always use free software, even when in some cases it might be the case that proprietary software might be more convenient or better suited for some particular need that we have.

After all, the argument goes, our primary mission is to produce free knowledge, not to promote free software, and whlie we might prefer free software on practical grounds (since it is generally best of breed for webserving applications), we should not be sticklers about it.

I believe this argument is seriously mistaken, and not on merely practical grounds, but on grounds of principle. Free knowledge requires free software. It is a conceptual error to think about our mission as being somehow separate from that.

What is free knowledge? What is a free encyclopedia? The essence is something that anyone who understands free software can immediately grasp. A free encylopedia, or any other free knowledge, can be freely read, without getting permission from anyone. Free knowledge can be freely shared with others. Free knowledge can be adapted to your own needs. And your adapted versions can be freely shared with others.

We produce a massive website filled with an astounding variety of knowledge. If we were to produce this website using proprietary software, we would place potentially insurmountable obstacles in front of those who would like to take our knowledge and do the same thing that we are doing. If you need to get permission from a proprietary software vendor in order to create your own copy of our works, then you are not really free.

For the case of proprietary file formats, the situation is even worse. It could be argued, though not persuasively I think, that as long as Wikimedia content can be loaded into some existing free software easily enough, then our internal use of proprietary software is not so bad. For proprietary formats, even this seductive fallacy does not apply. If we offer information in a proprietary or patent-encumbered format, then we are not just violating our own commitment to freedom, we are forcing others who want to use our allegedly free knowledge to themselves use proprietary software.

Finally, we should never forget as a community that we are the vanguard of a knowledge revolution that will transform the world. We are the leading edge innovators and leaders of what is becoming a global movement to free knowledge from proprietary constraints. 100 years from now, the idea of a proprietary textbook or encyclopedia will sound as quaint and remote as we now think of the use of leeches in medical science.

Through our work, every single person on the planet will have easy low cost access to free knowledge to empower them to do whatever it is that they want to do. And my point here is that this is not some idle fantasy, but something that we are already accomplishing. We have become one of the largest websites in the world using a model of love and co-operation that is still almost completely unknown to the wider world. But we are becoming known, and we will be known, for both our principles and achievements — because it is the principles that make the achievements possible.

Toward that end, it should be a strong point of pride to us that the Wikimedia Foundation always uses free software on all computers that we own, and that we always put forward our best effort to ensure that our free knowledge really _is_ free, in that people are not forced to use proprietary software in order to read, modify, and redistribute it as they see fit.







Leave a Reply


<form action="http://blog.jimmywales.com/wp-comments-post.php" method="post" id="commentform">


<input type="text" name="author" id="author" value="" size="22" tabindex="1" /> <label for="author">Name (required)</label>

<input type="text" name="email" id="email" value="" size="22" tabindex="2" /> <label for="email">Mail (will not be published) (required)</label>

<input type="text" name="url" id="url" value="" size="22" tabindex="3" /> <label for="url">Website</label>


<textarea name="comment" id="comment" cols="100%" rows="10" tabindex="4"></textarea>

<input name="submit" type="submit" id="submit" tabindex="5" value="Submit Comment" /> <input type="hidden" name="comment_post_ID" value="10" />

</form>






</body> </html>