8 ms·
FSF Wastes Away Another "High Priority" Project
- rosser 14y agoThis surprises anyone? As far as the FSF (or at least Stallman, which for all practical purposes is the same thing) is concerned, LibreCAD and FreeCAD are in the wrong here — for using one of the FSF's own licenses. Stallman is a zealot, and this is what zealots do.
- benatkin 14y agoWell the FSF purports to be an organization that advances the cause of free software, so it's worth calling them on their bullshit. Not everyone thinks of them as a zealot organization even though it's headed by a zealot. Perhaps they should. Also I think this issue might be fixable if there's enough outcry about it. And they really are in a tough situation because of this.
- jlarocco 14y agoIt's been well known for a long time that the FSF is only interested in advancing their own idea of "free software." At this time it's the GPLv3 flavor of free software. For people who don't agree with the FSF's idea of "free software" or don't want the politics that goes along with the GPL and FSF, there's always the BSD license. Though it really wouldn't help in this case, since the library in question belongs to the FSF.
- benatkin 14y agoThe need for open source tools that interact with dwg resonates strongly with me. I hope they can rewrite it, and I hope they choose BSD (or MIT) rather than GPLv2.
- gknoy 14y agoExactly: The solution seems to be (unfortunately) to let LibreDWG languish, and write a new library which is GPL2, or some other license. Sounds painful, since the people who want to use it are those who until now have not been (I assume) the ones writing the library.
- cube13 14y agoTo be fair, it looks like the FSF is letting LibreDWG languish anyway. There hasn't been a master commit in 2 years, and the last activity in the repository was in February 2012. I'd assume that a "high priority" project would have a lot more activity than that, especially because there hasn't been a binary release yet( http://www.gnu.org/software/libredwg/ http://www.gnu.org/software/libredwg/ ).
- tedks 14y agoThe FSF hasn't had developers for GNU projects on staff in decades, if I remember correctly. They aren't letting it languish, they're actively trying to give it exposure and find new hackers for it -- that's the point of it being a high priority project as far as I can tell.
- tjaerv 14y agoAnd for those fed up with copyright as a whole: http://unlicense.org http://unlicense.org
- gillianseed 14y agoWhat bullshit? This is about a company (Ribbonsoft) which released their code under a modified GPLv2 licence which removed the 'or later clause', thus making it a 'new' licence which is incompatible with any other GPL licences except GPLv2. FSF has since created GPLv3, under which all their code is now released, for all GPLv2 licenced code out there which is using the FSF's original GPLv2 licence there is no problem since it has the 'or later' clause. The problem here is that Ribbonsoft removed the (or later) clause and thus making it incompatible with future GPL versions. And what is this 'tough situation' they are in?
- dllthomas 14y ago> [T]his is what zealots do. This, and rebelling against the Roman occupation of the Holy Land.
- jlarocco 14y agoI'm not so sure FSF is trying to say they're in the wrong for using GPLv2. In my mind, it's similar to Apple or Microsoft not releasing a new version of iTunes or Office for one of their old operating systems. They're not saying anybody is "in the wrong," but it's the old version and people should upgrade. I have a hard time blaming FSF for wanting other projects to upgrade to GPLv3 instead of downgrading their own project to GPLv2. It could almost be said that it's the whole point of the GPL. And, like you said, this should be a surprise to absolutely nobody.
- RexRollman 14y agoI completely disagree. The FSF has every right to not re-license the software.
- sigzero 14y agoI don't think anyone is arguing that they don't have the right. I think people are arguing that it is a douche move on their part.
- RexRollman 14y agoTo me, the douche move is whining about it when they decided against allowing it.
- gillianseed 14y agoWhy is it a 'douche move'? If the original licencors Ribbonsoft had not released the code under a modified GPLv2 licence where they explicitly removed the 'or later' clause then there would have been no problem.
- gillianseed 14y agoIt's not one of 'FSF's own licences', it's a modified GPLv2 licence where the 'or later' clause has been removed so that it is GPLv2 ONLY, thus making it a NEW licence. No GPL licences crafted by FSF has this limitation.
- mbetter 14y ago> but the FSF/Richard Stallman doesn't the DWG library on the earlier version of their own open-source license. I think they an important word.
- akoumjian 14y agoWhy are they bound to GPLv2? It was my understanding that original authors had the ability to relicense as GPLv3.
- rosser 14y agoNot if other dependencies are GPLv2 only, which is what TFA suggests.
- liljimmytables 14y ago> LibreCAD is GPLv2 licensed since it came out of code from the QCad Community Edition product from Ribbonsoft. It's bound to GPLv2. The GPL has an upgrade clause. > This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. Why doesn't this apply?
- kryptiskt 14y agoThere are projects with or without the upgrade clause, the former is sometimes referred to as GPLv2+. Linux, for example, lacks that clause.
- JoshTriplett 14y agoThe line you quoted doesn't appear in the terms of the license; projects can use that language to apply GPLv2 or any later version, but they don't have to do so. Many projects explicitly use version 2 only, most famously the Linux kernel.
- muuh-gnu 14y agoSo it is effectively their fault for preventing the licence of their project from _ever_ being updated, even in the case where some future legal loophole makes exploiting GPLv2 code possible. It is short sighted essentially freezing the legal status of a project forever, and it is even more idiotic to blame the FSF for being incompatible with projects that voluntarily cut off forward-compatibility by removing the "or any later" clause.
- mlinksva 14y agoIf freezing legal status of a project forever is short-sighted, the ability to opt-out of upward compatibility in GPLv2 is a tragedy, as is the same in GPLv3. If there ever is a GPLv4, hopefully it will be purely GPLv4+ with no option for GPLv4-only.
- benatkin 14y agoWhen did the FSF change it from GPLv2 to GPLv3? It should be possible to go back to that version and fork it. Or is it applied retroactively?
- jamesjporter 14y agoI believe license changes can be applied retroactively to all versions with the permission of all the copyright holders; I would assume this is what was done.
- muuh-gnu 14y agoOnly if you still get it directly from the copyright holder. If you get it from someone else, and that someone got their copy under the terms of GPLv2, they still can distribute it under v2.
- tzs 14y agoThat is an unsettled question. According to the license itself, you cannot sublicense GPLv2 code. When you distribute a copy of third party GPLv2 code to someone, their license is coming from the copyright owner directly, not via sublicensing through you. If the copyright holder is no longer issuing licenses, it is not at all clear what would happen. The analysis gets complicated and speculative at this point. There are quite a few plausible theories, but it is going to take a few actual cases followed by appeals for any clarity to start developing in this area.
- rquirk 14y agoThe initial checkin to git on savannah is 2009, with a GPL v3 licence. But if you go to the original sourceforge svn repo, it started out GPL v2. I think you could fork a version from prior to revision 21 from sourceforge and it would be GPLv2+.
- deleted 14y ago[deleted]
- abraininavat 14y agoCould someone tell me, is the FSF actually relevant anymore? If so, how?
- h2s 14y agoThere is always the need for somebody to stand up as the opposing side to those who seek to build their business on abusive practices such as vendor lock-in or DRM. The FSF is that voice, and it's a more important role than ever. For example, the FSF has long warned of the dangers of DRM, and in recent years these warnings have proved themselves prescient now that we have things like Amazon remotely wiping Kindles on a whim and deleting objectionable books. More recently, the FSF has begun making a lot of noise about the dangers of SecureBoot. Will the wider developer community disregard these warnings as the ravings of irrelevant zealots? Based on past observations, I certainly hope not.
- snambi 14y agoCannot imagine the world without FSF. Thank god for FSF and RMS.
- RexRollman 14y agoHere hear.
- lifeguard 14y agoKids today have no idea what the web and Internet were like in the 90s. The GPL is vital to our freedoms.
- pnathan 14y agoBeyond having an uncannily correct track record, the FSF also does not move its goalposts, thusly denying the possibility of corporate interests gaslighting libre software.
- lucian1900 14y agoWhy the fuck would a library not use the LibraryGPL? It's the same stupidity as readline.
- cygx 14y agoIt's GNU policy - see http://www.gnu.org/licenses/why-not-lgpl.en.html http://www.gnu.org/licenses/why-not-lgpl.en.html
- viraptor 14y agoThe irony here is really hard to miss: "By releasing libraries that are limited to free software only, we can help each other's free software packages outdo the proprietary alternatives."
- cygx 14y agoYou have to get into the GNU mindset here: If you consider non-free software immoral and your ultimate goal is to outlaw it, providing libraries which can be used by proprietary software makes you guilty of aiding and abetting.
- dllthomas 14y agoLGPL as "Library GPL" is deprecated - the v3.0 version is called the "Lesser GPL". It's intended to be appropriate for some libraries, but was never intended to be used for all. See the link in my neighbor comment for more details.
- lucian1900 14y agoThe renaming was entirely political. If the author wants their library to actually be used, it should be LGPL. GPL-ing a library almost always makes it pointless.
- dllthomas 14y ago> The renaming was entirely political. Well sure; the FSF is essentially a political organization. I'm not sure what point you're making here. The renaming was a statement that the organization believes the license is not always what is most appropriate for libraries. This is entirely relevant to the original point, which was a refutation of the notion that the FSF is dumb for not using the clearly-appropriate-because-they-named-it-that "Library GPL". > If the author wants their library to actually be used, it should be LGPL. If the author wants their code to be used as broadly as possible, it should be public domain. If the author, maybe, has some concerns other than just how broadly the code is used, then some more restrictive license may be appropriate - BSD, LGPL, or GPL, depending on your particular goals. > GPL-ing a library almost always makes it pointless. If your only goal is broad adoption, then this is certainly the case. Somehow, I think the FSF has goals other than broad adoption of their software. Even so, it is certainly the case that releasing your library under the GPL will mean that many projects will avoid it. Whether this trade-off is worthwhile depends not only on the weight you place on various goals, but also on the nature of the library: something that adds huge amounts of value relative to alternatives, and relative to proprietary libraries that might serve as other parts of a final application, will be a lot more likely to change the license of prospective projects than something that is easily replaced or displaces other things of more value. This is actually more-or-less the FSF's position, per my understanding, on libraries: "we encourage GPL but do what makes sense." This was their reasoning on readline, and that definitely drove some GPLing of software before workalike alternatives surfaced. This was presumably their reasoning here. This is not to say that the reasoning is necessarily correct.
- meaty 14y agoAt the risk of starting a flame war, this is why all my shit is BSD licensed. Like the software, the license isn't a pain in the arse either.
- _ak 14y agoSame here. I only use software licenses where I can understand every single word. My personal preference is MIT, but 2-clause BSD or ISC would be equally fine.
- verand 14y agoBut not 3-clause BSD? I figure the reasoning behind the third clause is to cover the situation where you write FooLib and someone uses it, advertising, "The Crazy Super Cool App is the craziest and supercoolest app of them all because FooLib makes it so crazy and supercool!" If the CSCA turns out to be a stinking pile, you don't get the stigma.
- lifeguard 14y agoAre you saying you selected your software for the BSD lic, or just that the stuff you like happens to be BSD lic?
- meaty 14y agoBoth.
- anonymouz 14y agoAnyone surprised by the fact that the FSF puts its principles about the purity of free software licenses before pragmatism hasn't been paying much attention. The GPLv3 is the flagship license of the FSF and they think it fixes some issues with the GPLv2, so it's hardly surprising that they will refuse to relicense their high priority projects under the older license. "But you'll gain more users" has never been a reason for the FSF to compromise on their principles. One may equally well ask why LibreCAD insists on GPLv2 (without upgrade clause), and does not switch to GPLv3 if they want to use GPLv3 libraries.
- glesica 14y agoLibreCAD doesn't hold the copyright, so they can't change the license. The copyright is held by a private company with no particular incentive to make the Free product better, especially since the paid product wouldn't be able to use the LibreDWG code.
- millerc 14y agoYou seem to forget the primary reason why the GPL came to be, the principle that caused RMS to rewrite EMACS as an open source product in the first place: if a piece of software is closed, or in this case "not open enough", they want it rewritten under a new license. This story only seems to be a case of political pressure to do so, regardless of the effort a rewrite may cause. In this regards, FSF is clearly putting the value of the license above the value of the software itself. This is why I can't endorse the GPL: it is mainly motivated and designed to deny authority over software ownership, not for actual openness. If somebody really want to open up a piece of software, Public Domain is the way to go.
- glesica 14y agoThis comment is basically nonsense. Not saying I agree or disagree, it just makes no sense as a response to my comment. I was making a factual correction. The GP suggested that LibreCAD change their license. I pointed out that doing so is not possible and not likely to become possible. That is all.
- darkarmani 14y agoIt looks like this was brought up on the mail-list Feb. 2012: http://lists.gnu.org/archive/html/libredwg/2012-02/msg00000.html http://lists.gnu.org/archive/html/libredwg/2012-02/msg00000....
- doctorpangloss 14y agoWhy not provide a way for users to download the library separately and execute it as a binary blob? That way, if there's a license violation, it is the responsibility of the user. Kind of like libdvdcss and Handbrake? On the other hand, it seems odd to me that the kind of person who would be hung up by licenses is interested in using free software. Why not just buy AutoCad at this point? I guess that's sort of the FSF's biggest mistake. They act like there are no alternatives. Though they seem to understand that with LGPL: This is why we used the Lesser GPL for the GNU C library. After all, there are plenty of other C libraries; using the GPL for ours would have driven proprietary software developers to use another—no problem for them, only for us.
- fluidcruft 14y agoYour answers are found in the saga of the readline wars (where every imaginable method to run around the GPL and make it meaningless has been tried). Broadly speaking the rule of thumb is that if something makes use of internal knowledge of GPL code implementation or function (i.e. unique data structures/objects/functions that are not considered "standard"), it's considered a derivative work (this is also how the Linux kernel approaches GPL vs non-GPL drivers, too). If all it were to take was to adapt and repackage a GPL project as a dynamically loaded library, the GPL would be meaningless. In my mind, the really hairy area is where certain projects seem to be allowed to define "public" APIs that surrender GPL protection and allow use of closed binary libraries (i.e. the Linux kernel's public driver interface or Octave's MEX interface). Or what happens when the BSD folks just copy your API and re-implement everything (undermining the uniqueness of the GPL software's internals)? Don't bring this up to the FSF though, they suddenly switch from being eloquent to pretending to be dense.
- tomjen3 14y agoWhat I never really understood was why nobody ever cloned readline? Clisp was open sourced because they used readline, but they already had a completely working common lisp system with everything -- how hard can it be to write a readline library?
- st3fan 14y agoIt is open source. If a project does not move forward then commit code to it.
- gwern 14y ago> The Free Software Foundation was contacted about making LibreDWG GPLv2+ instead (since the FSF is the copyright holder), but the FSF/Richard Stallman doesn't the DWG library on the earlier version of their own open-source license. Doesn't the what?
- chebucto 14y agoRMS's comments in a recent Slashdot interview are worth noting: http://features.slashdot.org/story/13/01/06/163248/richard-stallman-answers-your-questions?sdsrc=popbyskid http://features.slashdot.org/story/13/01/06/163248/richard-s... "What project is using the wrong license? by gQuigs ... RMS: If I could magically change one program to GPLv3, it would be Linux. ... Another program that is important to convert is LibreCAD. This is more than a fantasy: the developers of LibreCAD are working on replacing the old GPLv2-only code that they included, so as to switch to GPLv3-or-later. Would you like to help?"
- nicholassmith 14y agoOpen source software is fantastic, I've made code public and free to use, I build on open source, I've committed to open source and done crazy bug hunts. I love open source. I cannot stand the GPL, it's an absolute unworkable nightmare. It's set out to achieve something fantastic and it's been ruined, it's so heavy handed that in the real world it's now meaning developers will avoid it rather than deal with it as there's so many gotchas like this.
- matt2000 14y agoI have a hard time describing any license that limits your rights as one promoting freedom. I never understood why the FSF wasn't more behind the BSD style licenses.
- tspiteri 14y agoThe FSF is more about giving users rights to change the code than about giving developers rights to use libraries. With BSD-style licenses, developers can limit the users' rights to change the code, which is not in line with the FSF's line.
- drcube 14y agoIs the US Constitution "restrictive" because it limits the right of our president to become a dictator? Would a constitution that said essentially "Those in power can do whatever they want" make us more free?
- deleted 14y ago[deleted]
- jstalin 14y agoHelpful comparison of open source licenses, for those interested: https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses https://en.wikipedia.org/wiki/Comparison_of_free_and_open-so... I personally prefer the UNLICENSE: http://unlicense.org/ http://unlicense.org/
- mikegerwitz 14y agohttp://www.gnu.org/licenses/rms-why-gplv3.html http://www.gnu.org/licenses/rms-why-gplv3.html
- mikegerwitz 14y agoI ended up preparing a more extensive commentary, which may be found here: http://mikegerwitz.com/thoughts/2013/01/Re-FSF-Wastes-Away-Another-High-Priority-Project.html http://mikegerwitz.com/thoughts/2013/01/Re-FSF-Wastes-Away-A...
- lifeguard 14y agoThat phoronix missive was the stupidest post I have read in a long time.
- snogglethorpe 14y agoPhoronix is like that....