Slashdot Mirror

holmesfsf writes "Creeped out by the Lower Merion School District's remote monitoring of students? Check out the Free Software Foundation's response to the laptop spying scandal and help build a wiki listing of school districts that provide students with laptops, so that the FSF can campaign against mandatory, proprietary laptops."

jamesswift writes "The FSF have written an open letter to Google urging them to free the VP8 codec with an irrevocable royalty-free licence: 'With its purchase of the On2 video compression technology company having been completed on Wednesday February 16, 2010, Google now has the opportunity to make free video formats the standard, freeing the web from both Flash and the proprietary H.264 codec.'" Also from the letter: "The world would have a new free format unencumbered by software patents. Viewers, video creators, free software developers, hardware makers -- everyone -- would have another way to distribute video without patents, fees, and restrictions. The free video format Ogg Theora was already at least as good for web video (see a comparison) as its nonfree competitor H.264, and we never did agree with your objections to using it. But since you made the decision to purchase VP8, presumably you're confident it can meet even those objections, and using it on YouTube is a no-brainer."

ndogg writes "It's no secret that Stallman doesn't like Mono. Miguel, however, has been pretty quiet about those criticisms, until now. It seems he'll no longer be quiet. He's responded strongly to an article by Stallman that criticizes Codeplex about its aims due to its origin at Microsoft. Miguel says Stallman is fearmongering, and is missing an opportunity by his criticism."

An anonymous reader writes "The Free Software Foundation's Holmes Wilson is just back from Berlin, where he participated in the Ogg Theora book sprint put on by FLOSS Manuals. Here is a broad look at Ogg Theora and how it fits into the push for free formats: where we're winning, what works, and what could be improved."

twitter writes "There's been a lot of fuss about mono lately. After SCO and MS suing over FAT patents, you would think avoiding anything MS would be a matter of common sense. RMS now steps into the fray to warn against a serious mistake: 'Debian's decision to include Mono in the default installation, for the sake of Tomboy which is an application written in C#, leads the community in a risky direction. It is dangerous to depend on C#, so we need to discourage its use. .... This is not to say that implementing C# is a bad thing. ... [writing and using applications in mono] is taking a gratuitous risk.'" Update: 06/27 20:22 GMT by T : Read on below for one Mono-eschewing attempt at getting the (excellent) Tomboy's functionality, via a similar program called Gnote. Update: 06/27 21:07 GMT by T: On the other side of the coin, reader im_thatoneguy writes "Jo Shields, a Mono Developer, has published an article on 'Why Mono Doesn't Suck,' why it is not a threat to FOSS, why it is desirable to developers and why it should be included in Ubuntu by default." LastGuyonEarth writes "Gnote was started on April 2009 by Gnome developer Hubert Figuiere, known also for his work on Abiword. The goal of Gnote is to provide a Free Software implementation of Tomboy that doesn't rely on Mono. The ultimate goal is to replace Tomboy in an effort to make Gnome and GNU/Linux distributions non-dependant on Novell's implementation of Microsoft's .NET platform. For our testing purposes, I installed Gnote 0.5.1 on Ubuntu Jaunty through a personal PPA, but I would love to see it officially packaged in the near future."

Saint Aardvark writes "The Free Software Foundation has announced that they've settled their lawsuit with Cisco (reported earlier here). In the announcement, they say that Cisco has agreed to appoint a Free Software Director for Linksys, who will report periodically to the FSF; to notify Linksys customers of their rights; and to make a monetary donation to the FSF. An accompanying blog entry explains further: 'Whenever we talk about the work we do to handle violations, we say over and over again that getting compliance with the licenses is always our top priority. The reason this is so important is not only because it provides a goal for us to reach, but also because it gives us a clear guide to choosing our tactics. This is the first time we've had to go to court over a license violation.'"

Saint Aardvark writes "The Free Software Foundation has announced that they've settled their lawsuit with Cisco (reported earlier here). In the announcement, they say that Cisco has agreed to appoint a Free Software Director for Linksys, who will report periodically to the FSF; to notify Linksys customers of their rights; and to make a monetary donation to the FSF. An accompanying blog entry explains further: 'Whenever we talk about the work we do to handle violations, we say over and over again that getting compliance with the licenses is always our top priority. The reason this is so important is not only because it provides a goal for us to reach, but also because it gives us a clear guide to choosing our tactics. This is the first time we've had to go to court over a license violation.'"

David Vuorio writes "The Open Graphics Project aims to develop a fully open-source graphics card; all specs, designs, and source code are released under Free licenses. Right now, FPGAs (large-scale reprogrammable chips) are used to build a development platform called OGD1. They've just completed an alpha version of legacy VGA emulation, apparently not an easy feat. This YouTube clip shows Gentoo booting up in text mode, with OGD1 acting as the primary display. The Linux Fund is receiving donations, so that ten OGD1 boards can be bought (at cost) for developers. Also, the FSF shows their interest by asking volunteers to help with the OGP wiki."

Brett Smith writes "This morning the Free Software Foundation filed suit against Cisco for violations of the GPL and LGPL. There's a blog post with background about the case. The full complaint is available too." The short version, as excerpted by reader byolinux, is that "in the course of distributing various products under the Linksys brand Cisco has violated the licenses of many programs on which the FSF holds copyright, including GCC, binutils, and the GNU C Library. In doing so, Cisco has denied its users their right to share and modify the software."

Brett Smith writes "This morning the Free Software Foundation filed suit against Cisco for violations of the GPL and LGPL. There's a blog post with background about the case. The full complaint is available too." The short version, as excerpted by reader byolinux, is that "in the course of distributing various products under the Linksys brand Cisco has violated the licenses of many programs on which the FSF holds copyright, including GCC, binutils, and the GNU C Library. In doing so, Cisco has denied its users their right to share and modify the software."

Brett Smith writes "This morning the Free Software Foundation filed suit against Cisco for violations of the GPL and LGPL. There's a blog post with background about the case. The full complaint is available too." The short version, as excerpted by reader byolinux, is that "in the course of distributing various products under the Linksys brand Cisco has violated the licenses of many programs on which the FSF holds copyright, including GCC, binutils, and the GNU C Library. In doing so, Cisco has denied its users their right to share and modify the software."

Brett Smith writes "This morning the Free Software Foundation filed suit against Cisco for violations of the GPL and LGPL. There's a blog post with background about the case. The full complaint is available too." The short version, as excerpted by reader byolinux, is that "in the course of distributing various products under the Linksys brand Cisco has violated the licenses of many programs on which the FSF holds copyright, including GCC, binutils, and the GNU C Library. In doing so, Cisco has denied its users their right to share and modify the software."

David Gerard writes "Version 1.3 of the GNU Free Documentation License is out (FAQ). This license is little-used, except on the #8 site in the world: Wikipedia. And this version includes special provisions to re-license wiki-based content from GFDL to the much simpler Creative Commons Attribution-ShareAlike license 3.0, as requested by the Wikimedia Foundation. Wikipedia plans to hold a public consultation process to decide whether and how to migrate to CC-BY-SA. The discussion is already running hot and heavy."

Bennett Haselton contributes the following essay on the consequences of license choice as it applies to sites based on user contributions; read on below for more of his big idea for making Knol a more useful resource. "Google Knol should allow its writers to publish under a Creative Commons Share Alike license. The preceding sentence may not mean much to you, but if you've ever wanted to cite a Wikipedia article as a source, or simply read a Wikipedia article with some assurance that someone wasn't pulling your leg with some creative editing, or if you've wanted to contribute to Wikipedia but couldn't afford the time unless you received some modest compensation for it, then the addition of this one simple feature to Knol might make all the difference." (More below.)

I've been suggesting for some time that Wikipedia, or some fork of Wikipedia, should allow users to "sign off" on a version of an article, and then lock that article against future edits until the signer had approved them. The signing off would allow people to cite a Wikipedia article as a source that had been vetted by at least one person (with confidence in the source depending on that person's credentials). The signer's identity (and sometimes, their credentials) could be confirmed using several methods, such as verifying an .edu e-mail address. Users could still submit edits, but they would have to be approved by the article verifier. Different users could sign off on different versions of the same article, and readers would still have the option of viewing the latest version of an article, with all of its unmoderated edits (which is what you're looking at on Wikipedia most of the time).

Knol, which allows users to submit articles on any topic they want, has incorporated all of the above features (adding, for example, the ability to verify authors' real names using credit cards), and gone one step further by allowing users to place AdSense ads in their articles. However, there's one stumbling block to Knol incorporating all of Wikipedia's content and blessing it with the verification of credentialed experts: Currently, although you have to dig a bit deep to find this out, Knol's Terms of Service do not allow content to be copied from Wikipedia.

Content on Wikipedia is published under the GNU Free Documentation License -- when you click any of the "edit" links in a Wikipedia article and begin typing in new content, you're agreeing to submit your content under the terms of the GFDL. When you publish on Knol, on the other hand, your options are to publish under a Creative Commons Attribution 3.0 License (CC-BY), a Creative Commons Attribution-Noncommercial 3.0 License (CC-BY-NC), or a traditional "All Rights Reserved" copyright model. Both the GFDL and the Creative Commons Attribution licenses are popular with content creators who want to give content altruistically "to the world" -- these licenses all allow content to be redistributed freely without modification. The main difference is in the rights that they grant to people who want to create derivative works (modifying or expanding on the original work).

The GFDL is intended as a "viral" license -- if you take a work that is published under the GFDL, and publish a derivative work created from that, your derivative work must also be published under the terms of the GFDL -- that is, also allowing other users to redistribute your work freely and create derivative works from it as well. If a site mirrors Wikipedia articles without including the terms of the GFDL, Wikipedia encourages users to send notifications to those sites pointing out that they're violating Wikipedia's copyright, and if necessary to escalate the matter to their Web hosting provider for noncompliance. You can mirror Wikipedia all you want, and even put put ads all over your mirror site, but you cannot change the terms.

Creative Commons Attribution (CC-BY) licenses, on the other hand, allow users to create derivative works and publish them under almost any terms they want, including an "All rights reserved" model, provided that they give attribution to the author of the original work. If Susan publishes an article under CC-BY, you can create a derivative work by expanding on her article, and -- assuming your contributions are substantial enough to be copyrightable in themselves -- you can prohibit other users from redistributing your article or creating derivative works from it, something that would not be possible if Susan had published her article under the GFDL. (Obviously, you cannot prohibit others from redistributing Susan's article or creating their own derivative works from it, but you can restrict these rights as applied to your own derivative work.)

Russell Potter, a Professor of English at Rhode Island College and a Citizendium contributor who explained this difference to me, points out that CC-BY licenses are more friendly to academics who want to reuse content in a published book or in a conference presentation. "Say an academic (me) contributes a long article on London's Crystal Palace," he wrote. "Others edit it in modest ways, but the article is still about 90% my own work. Perhaps I want to give a paper at a conference based on this entry, or use large bits of it in a book I'm writing. GFDL would have made either impossible." (Impossible, that is, unless the book publisher released the book under the GFDL, but most book publishing companies are reluctant to do that.)

And therein lies the logical incompatibility between the GFDL and the CC-BY publishing options currently allowed by Knol. If you copy GFDL-licensed content from Wikipedia, you are agreeing that for any copies or derivative works that you create, you will not only permit other users to remix them, but that you will require those other users to agree to the same terms for the remixed works that they publish. If you published such content on Knol under the CC-BY option, you would be granting the reader permission to incorporate the work into their own derivative work which they could then publish under an All Rights Reserved license. And the GFDL doesn't allow you to grant that permission to the reader. Section 5.5 of Knol's Terms of Service explicitly states that GFDL content cannot be re-published under a CC-BY license, and Mike Linksvayer makes this point on the Creative Commons blog as well. Some authors have begun copying Wikipedia content to Knol anyway, and even though that particular article included a link to the GFDL, users have pointed out in the comments that it's still a TOS violation anyway. Google appears to be lax about policing these violations for now, but in the right-hand column, the links to "Similar Content on the Web" show that Google can trivially detect if content is copied from other sites, and may be planning to remove such content or demote it in search results if it's copied from a site like Wikipedia that doesn't allow copying under Knol's terms.

However, the Creative Commons family of licenses also includes the Creative Commons Attribution-Share Alike License (CC-BY-SA), which is written in the same spirit as the GFDL -- if a work is released under CC-BY-SA, any published derivative works created from that work must also be released under the same license. In fact the Free Software Foundation, which writes new versions of the GFDL, announced in December 2007 their intention to make the next version of the GFDL explicitly compatible with CC-BY-SA, so that any work published under the GFDL can be incorporated into a work published under CC-BY-SA, and vice versa. This new version of the GFDL has not been released yet, but the FSF replied by e-mail to say they're working on it.

(Perhaps you might be wondering, as I did, how already-existing content on Wikipedia can be said to be "licensed" under a new version of the GFDL when it comes out. How can past Wikipedia contributors have agreed to a future version of the license that didn't exist yet? The answer is that when you submit edits on Wikipedia, you're agreeing to submit your edits under the "GNU Free Documentation License, Version 1.2 or any later version", and it's the "or any later version" that means contributors are deemed to have agreed to the next version of the GFDL, which will presumably be CC-BY-SA-compatible.)

If Google Knol adds the ability to publish under a Creative Commons Attribution-Share Alike license, and the FSF releases a new version of the GFDL that is compatible with this license, then I think we will finally see what I hoped for in February 2008 -- a "gold rush" of users copying content from Wikipedia to Knol, where it can be verified by credentialed users and protected against vandalism. Some users' verifications will be more valuable than others -- a physics article verified by a physics professor is more trustworthy than the same article verified by an anonymous user, and even an article about The X-Files may be more trustworthy when it's verified by a physics professor, not because it's the professor's area of expertise, but because a professor with a valued reputation would be less likely to sign their name to unverified garbage.

Will Knol add the Share Alike option? Perhaps they may be nervous about what would happen if they allowed unlimited copying from Wikipedia, especially with financial incentives. At the moment, Knol seems to be downplaying the fact that you can make money from writing articles, even as everyone else buzzes about it. On their front page, under "Learn More", Knol lists the reasons you should contribute: "Visibility - We value and promote authorship. Great content will be visible on any search engine. Community - You can connect with other experts in your area of interest to share and grow knowledge," etc. Really? That's all? AdSense isn't mentioned in the FAQ, and only briefly at the end of a posting about "Knol bugs and workarounds". And officially the site never mentions Wikipedia at all, except in the knols about it.

But many of the articles on Wikipedia -- especially the kind of articles that academics would be willing to sign their names to -- would probably enhance the Knol site, not drag it down. Wikipedia founder Jimmy Wales correctly predicted that Knol would generate a lot of articles about Viagra. If Knol can tolerate that garbage (and under their own policies, there is little grounds for removing those articles, unless the authors lifted the content from some other site), they should welcome the addition of articles about stochiometry, Shakespeare, and Serbia, even if they were copied from Wikipedia and then vetted by a university professor or journalist. (None of those topics have their own Knol yet, although there was room for Knols about Simon Cowell, Superman, and sex addiction.)

After all, the incentives that AdSense creates for Knol writers are roughly the same as the incentives for Web publishers in general -- you can try to turn a quick buck, or you can invest in your site's reputation for the long run -- and while there is a new "made-for-AdSense" site born every minute, few would disagree that the rise of AdSense has been good for content on the Web in general.

While copying from Wikipedia to Knol is against the rules right now, there's no reason in principle to be against creating a Wikipedia sub-fork on Knol, if Google allows Knol writers to select the Creative Commons Attribution-Share Alike publishing option. One user, responding to the unauthorized use of Wikipedia articles, posted in the Knol users' group on Google Groups: "What I REALLY want to see Google do is crack down on these clowns who are copying and pasting articles from Wikipedia." I say, just change the rules and send in the clowns.

Slashdot welcomes original submissions; many thanks to Bennett for this one.

In this recent Slashdot post kernel hacker Harald Welte was characterized as "VIA's open source representative," but that is just one of many irons he has in the fire, as a glance at his Wikipedia bio will show. You can obviously ask Harald about many interesting things besides VIA's open source strategy — and before you ask about VIA, you ought to read the last few entries on his blog, at least one of which mentions VIA questions he can't answer. But VIA aside, there's plenty to ask Harald about. For example, he won an award from the FSF earlier this year for his work on gpl-violations.org. In any case, Harald is a powerful force for GNU/Linux and Free Software, and we appreciate him taking time out of his undoubtedly hectic schedule to answer your questions. (Usual Slashdot interview rules apply.)

Virgil Tibbs writes "The GNU operating system is turning 25 this year, and the Free Software Foundation has kicked off its month-long celebration of the anniversary by releasing 'Happy Birthday to GNU,' a short film featuring the English humorist, actor, novelist and filmmaker Stephen Fry. In the five-minute film, Fry compares the free software operating system to 'good science' and contrasts it with the 'kind of tyranny' imposed by the proprietary software produced by companies like Microsoft and Apple that it replaces. He encourages people to use free GNU/Linux distributions like gNewSense and free software generally, for freedom's sake."

mjasay writes "At OSCON this year, MySQL's Brian Aker made this bold statement: 'Microsoft is irrelevant ... We're more worried about Apple.' The Free Software Foundation appears to have caught the hint, and has turned its attention to all-things-Apple with a 'denial of service' attack on the Apple Genius Bars. The idea is to completely book all Genius Bars and then ask the 'geniuses,' over and over again, a few questions about Apple's proprietary ways (while, apparently, real customers with support issues are left to flounder). Lost in this anti-Apple fervor, however, is the Free Software Foundation's complete and conscious failure to protect the web. Richard Stallman has long felt that software that doesn't sit on his desktop doesn't affect his freedom, but isn't the opposite true? Why is the FSF focused on Apple when the bigger concern should be Google, Yahoo!, Amazon, and other web players, a point made by Tim O'Reilly recently at OSCON?" Defective by Design is just one of many FSF projects, remember; it hardly seems fair to say that the FSF has been ignoring the implications of software as a service.

mako writes "The FSF just announced the results of a meeting it held on software freedom and network services. They are hailing the launch of a new group called Autonomo.us to follow up on these issues and the publication of the Franklin Street Statement on Freedom and Network Services which lays out a set of recommendations and guidelines for protecting freedom for software as a service." Update 22:07 GMT by SM: Corrected language incorrectly crediting FSF with creating Autonomo.us.

Apro+im points out a NYTimes report which states that Microsoft and the OLPC project have officially agreed to put Windows XP on the XO laptop. While Microsoft has been working toward this for some time, analysts began to think a deal was more likely after Walter Bender resigned from the project and was replaced by Charles Kane. Former OLPC security developer Ivan Krstic had a lot to say about Windows on the XO as well. From the Times: "Windows will add a bit to the price of the machines, about $3, the licensing fee Microsoft charges to some developing nations under a program called Unlimited Potential. For those nations that want dual-boot models, running both Windows and Linux, the extra hardware required will add another $7 or so to the cost of the machines, Mr. Negroponte said. The project's agreement with Microsoft involves no payment by the software giant, and Microsoft will not join One Laptop Per Child's board. 'We've stayed very pure,' Mr. Negroponte said.

The author of ATSC capture and edit tool has announced that he is attempting to revoke the licensing of his product under the GPL General Public License. Unfortunately it appears that the GPL does not allow this particular action. Of course in this heyday of lawyers and trigger happy litigators who can tell. What successes have others had in trying to take something they once operated under the GPL and make it private? And the more pressing question, why?

sla291 writes "Jimmy Wales made an announcement yesterday night at a Wikipedia party in San Francisco : Creative Commons, Wikimedia and the FSF just agreed to make the current Wikipedia license compatible with Creative Commons (CC BY-SA). As Jimbo puts it, 'This is the party to celebrate the liberation of Wikipedia'."

mako writes "The Free Software Foundation has released the Affero General Public license version 3. The license is essentially the GPLv3 with an added clause that requires that source code be distributed to users that interact with the application over a network. The license effectively extends copyright to Web applications. The new AGPL will have important effects for companies that, under the GPL, have no obligation to distribute changes to users on the Web. This release adds the license to the stable of official FSF licenses and is compatible with the GPLv3."

NewYorkCountryLawyer writes "In what has been termed the ''RIAA's worst nightmare', the Free Software Foundation has announced that it is coming to the aid of the victims of RIAA lawsuits, by establishing an Expert Witness Defense Fund to assist defendants in RIAA cases. The purpose of the fund is 'to help provide computer expert witnesses to combat RIAA's ongoing lawsuits, and to defend against the RIAA's attempt to redefine copyright law.' The funds will be used to pay fees and/or expenses of technical expert witnesses, forensic examiners, and other technical consultants assisting individuals named as defendants in non-commercial, peer-to-peer file sharing cases brought by the RIAA, EMI, SONY BMG, Vivendi Universal, and Warner Bros. Records, and their affiliated companies, such as Interscope, Arista, UMG, Fonovisa, Motown, Atlantic, Priority, and others."

GeekyBodhi writes "Brett Smith, the licensing compliance engineer at FSF's Free Software Licensing and Compliance Lab held a public question and answer session in an IRC meeting last night. At the meeting Smith addressed questions regarding various sections of GPLv3 (Linux.com shares a corporate overlord with Slashdot) including Section 7 (additional rights), and Section 11 (patents and patent protection), and explained how the incompatibility between GPLv2 and GPLv3 doesn't rule out any interaction between differently licensed programs."

mjasay writes "Groklaw notes that the Free Software Foundation has decried Microsoft's attempts to distance itself from its obligations to abide by GPL Version 3 (press release here). Citing Microsoft's earlier declaration that they are not bound by GPLv3, the Free Software Foundation declared, 'Microsoft cannot by any act of anticipatory repudiation divest itself of its obligation to respect others' copyrights.' The press release implies that the Free Software Foundation may sue Microsoft over the issue."

A GNU Dawn writes "The GPL v3 has just been released. Among other things, the released version grandfathers in the Novell deal so that Microsoft's SLES coupons will undermine their patent threats, replaces references to the Magnusson-Moss Warranty Act with more specific language, and clarifies that using BitTorrent to convey a GPLed work is not a breach of the license (it might be one, technically, in GPLv2). The GPL FAQ has been updated to cover the new changes." Commentary is available over at Linux.com (which is owned, along with Slashdot, by Sourceforge).

Joe Blakesley writes "Today, the Free Software Foundation announced that version 3 of the GNU General Public License will be released on Friday, June 29 at noon (EDT). Live video footage of the GPL's unveiling by Richard M. Stallman will be available as a stream on the FSF's website."

cyclop writes "I am coding a data analysis application in my laboratory that I would like to release as free (as in freedom) software. Moreover I am going to begin a small OSS game that will be based, in part, on GPLv2 libraries. Problem is: in both cases, I'd like to be able to exchange code both with GPLv2 and (future) GPLv3 projects. I have no particular passions about either license — only thing is I don't want BSD-style 'do anything you want' licensing but a copyleft license. I know that GPLv2 and GPLv3 are not compatible. What can I do? Double licensing? Is there a compatible-with-both license? Adding exceptions? What do you think is the best way to address the GPLv2-to-GPLv3 transition without ending up on one or the other side of the barricade?"

chessweb writes "Here is a rather enlightening article by Richard Stallman on the reasons for moving to GPLv3 that puts the previous TiVo post into the right context." From the article: "One major danger that GPLv3 will block is tivoization. Tivoization means computers (called 'appliances') contain GPL-covered software that you can't change, because the appliance shuts down if it detects modified software... The manufacturers of these computers take advantage of the freedom that free software provides, but they don't let you do likewise... GPLv3 ensures you are free to remove the handcuffs. It doesn't forbid DRM, or any kind of feature. It places no limits on the substantive functionality you can add to a program, or remove from it. Rather, it makes sure that you are just as free to remove nasty features as the distributor of your copy was to add them."

An anonymous reader writes "Eben Moglen, general counsel and board member of the FSF and chairman of the SFLC, has announced on his blog that he will be resigning from his leadership position with the FSF now that GPLv3 draft 3 is out the door. "

An anonymous reader writes "Eben Moglen, general counsel and board member of the FSF and chairman of the SFLC, has announced on his blog that he will be resigning from his leadership position with the FSF now that GPLv3 draft 3 is out the door. "

DefectiveByDesign writes "Remember how AMD said they'd make use of ATI's GPU technology to make better technology? Well, not all change is progress. InfoWorld's Tom Yager reports that AMD plans to block access to the framebuffer in hardware to help enforce DRM schemes, such as allowing more restricted playback of Sony Blu-Ray disks. They can pry my Print Screen key from my cold, dead fingers."

H4x0r Jim Duggan writes "A transcript is now online of a talk Richard Stallman gave in Brussels earlier this week about the discussion draft 3 of GPLv3. Among other things, he explained how it will address the Novell-MS deal, from Novell's point of view and from Microsoft's, and he explained how the tivoisation clause was narrowed to make it more acceptable in the hope that it will be used by more people. After the talk he also gave an interview, and yesterday, draft 2 of LGPLv3 was released."

Novus Ordo Seclorum writes "According to CNet, Linus Torvalds is 'pretty pleased' with the current GPL v3 draft. He said, 'Unlike the earlier drafts, it at least seems to not sully the good name of the GPL any more.' After his earlier criticism, some had questioned whether such controversies would lead to rifts in the community, especially if the kernel ended up under a different license than the GNU tools. But with the latest revisions, Linus will entertain moving the kernel over to the GPL v3."

Novus Ordo Seclorum writes "According to CNet, Linus Torvalds is 'pretty pleased' with the current GPL v3 draft. He said, 'Unlike the earlier drafts, it at least seems to not sully the good name of the GPL any more.' After his earlier criticism, some had questioned whether such controversies would lead to rifts in the community, especially if the kernel ended up under a different license than the GNU tools. But with the latest revisions, Linus will entertain moving the kernel over to the GPL v3."

johnsu01 writes "The Free Software Foundation has announced publication of the third discussion draft of the GNU General Public License Version 3. Because quite a few changes have been made since the previous draft and important new issues have surfaced, the drafting process has been extended and revised to encourage more feedback. The most significant changes in this draft include refinements in the "tivoization" provisions to eliminate unwanted side effects, revision of the patent provisions to prevent end-runs around the license, and further steps toward compatibility with other free software licenses. The FSF has also explicitly asked the community whether the new patent provisions should apply retroactively to the Microsoft-Novell deal."

johnsu01 writes "The Free Software Foundation has announced publication of the third discussion draft of the GNU General Public License Version 3. Because quite a few changes have been made since the previous draft and important new issues have surfaced, the drafting process has been extended and revised to encourage more feedback. The most significant changes in this draft include refinements in the "tivoization" provisions to eliminate unwanted side effects, revision of the patent provisions to prevent end-runs around the license, and further steps toward compatibility with other free software licenses. The FSF has also explicitly asked the community whether the new patent provisions should apply retroactively to the Microsoft-Novell deal."

johnsu01 writes "The Free Software Foundation has announced publication of the third discussion draft of the GNU General Public License Version 3. Because quite a few changes have been made since the previous draft and important new issues have surfaced, the drafting process has been extended and revised to encourage more feedback. The most significant changes in this draft include refinements in the "tivoization" provisions to eliminate unwanted side effects, revision of the patent provisions to prevent end-runs around the license, and further steps toward compatibility with other free software licenses. The FSF has also explicitly asked the community whether the new patent provisions should apply retroactively to the Microsoft-Novell deal."

johnsu01 writes "The Free Software Foundation has announced publication of the third discussion draft of the GNU General Public License Version 3. Because quite a few changes have been made since the previous draft and important new issues have surfaced, the drafting process has been extended and revised to encourage more feedback. The most significant changes in this draft include refinements in the "tivoization" provisions to eliminate unwanted side effects, revision of the patent provisions to prevent end-runs around the license, and further steps toward compatibility with other free software licenses. The FSF has also explicitly asked the community whether the new patent provisions should apply retroactively to the Microsoft-Novell deal."

johnsu01 writes "The Free Software Foundation has announced publication of the third discussion draft of the GNU General Public License Version 3. Because quite a few changes have been made since the previous draft and important new issues have surfaced, the drafting process has been extended and revised to encourage more feedback. The most significant changes in this draft include refinements in the "tivoization" provisions to eliminate unwanted side effects, revision of the patent provisions to prevent end-runs around the license, and further steps toward compatibility with other free software licenses. The FSF has also explicitly asked the community whether the new patent provisions should apply retroactively to the Microsoft-Novell deal."

johnsu01 writes "The Free Software Foundation has announced publication of the third discussion draft of the GNU General Public License Version 3. Because quite a few changes have been made since the previous draft and important new issues have surfaced, the drafting process has been extended and revised to encourage more feedback. The most significant changes in this draft include refinements in the "tivoization" provisions to eliminate unwanted side effects, revision of the patent provisions to prevent end-runs around the license, and further steps toward compatibility with other free software licenses. The FSF has also explicitly asked the community whether the new patent provisions should apply retroactively to the Microsoft-Novell deal."

An anonymous reader wonders: "I am working as an independent developer for a client I have a long relationship with, and of whom I used to be an employee. I've made informal contracts in the past for development work, but this job is much more significant. Also, the client has gone to court over software development in the past; he was in the right to do so, but I need to cover myself. The product will be released under the (L)GPL and copyrighted by me, and the client will also be agreeing to open the license and give me the copyright on some code I previously developed. I plan to consult a lawyer, but I just want a little more direction before I start investing hours. Are there any resources I should know about, beyond what the FSF has to offer?"

shadowmage13 writes "Hollywood privately admits that DRM is not really about piracy. From the article: 'In a nutshell: DRM's sole purpose is to maximize revenues by minimizing your rights so that they can sell them back to you... Like all lies, there comes a point when the gig is up; the ruse is busted. For the movie studios, it's the moment they have to admit that it's not the piracy that worries them, but business models which don't squeeze every last cent out of customers.' You can take action on Digital Restrictions Management at DefectiveByDesign of the Free Software Foundation, Digital Freedom, and the Electronic Frontier Foundation."

FrankNFurter writes to note the launch yesterday of the FSF's BadVista campaign against Microsoft's new operating system. BadVista's aim is to inform users about the alleged harms inflicted by Vista on the user and about free software alternatives. Quoting program administrator John Sullivan: "Vista is an upsell masquerading as an upgrade. It is an overall regression when you look at the most important aspect of owning and using a computer: your control over what it does. Obviously MS Windows is already proprietary and very restrictive, and well worth rejecting. But the new 'features' in Vista are a Trojan Horse to smuggle in even more restrictions. We'll be focusing attention on detailing how they work, how to resist them, and why people should care."

j00bar writes "After Linus Torvalds' impassioned critiques of the second draft of GPLv3 and the community process the FSF has organized, Newsforge's Bruce Byfield discovered in conversations with the members of the GPLv3 committees that the committee members disagree; they believe not only has the FSF been responsive to the committees' feedback but also that the second draft includes some modifications in response to Torvalds' earlier criticisms." NewsForge and Slashdot are both owned by OSTG.

thppft! writes "The second discussion draft of the GNU General Public License version 3 was released, along with the first discussion draft of the GNU Lesser General Public License. Along with the text for the licenses , the GPLv3 website also includes an introduction by Eben Moglen along with markup changes to the rationale and the GPL itself."

thppft! writes "The second discussion draft of the GNU General Public License version 3 was released, along with the first discussion draft of the GNU Lesser General Public License. Along with the text for the licenses , the GPLv3 website also includes an introduction by Eben Moglen along with markup changes to the rationale and the GPL itself."

thppft! writes "The second discussion draft of the GNU General Public License version 3 was released, along with the first discussion draft of the GNU Lesser General Public License. Along with the text for the licenses , the GPLv3 website also includes an introduction by Eben Moglen along with markup changes to the rationale and the GPL itself."

thppft! writes "The second discussion draft of the GNU General Public License version 3 was released, along with the first discussion draft of the GNU Lesser General Public License. Along with the text for the licenses , the GPLv3 website also includes an introduction by Eben Moglen along with markup changes to the rationale and the GPL itself."

thppft! writes "The second discussion draft of the GNU General Public License version 3 was released, along with the first discussion draft of the GNU Lesser General Public License. Along with the text for the licenses , the GPLv3 website also includes an introduction by Eben Moglen along with markup changes to the rationale and the GPL itself."