Slashdot Mirror

← Back to Stories (view on slashdot.org)

FSF: New Apache License not GPL-Compatible

Posted by timothy on from the clashing-clauses dept.

__past__ writes "It seems that the XFree86 issue is not the only licensing battle currently fought in the FLOSS world: An update to the FSF's list of Free Software licenses lists the new Apache License, Version 2.0 (which has been discussed on Slashdot before) as not being GPL-compatible, due to a clause related to software patents." (Read on for more.)

__past__ continues "The new version of the Apache license will apply to all Apache projects, including the popular web server and many Java libraries like Xerces and Log4J, and making it easier to integrate Apache- and GNU-licensed code was one of the primary goals for its development. With the new license being GPL-incompatible (just like the older Apache licenses were), it is not possible to distribute programs that use libraries covered by under it and others covered by the GPL.

Apparently, the FSF does not actually consider the patent-related clauses a bad idea, let alone non-free - it is just that they impose a restriction that the GPL does not, and that makes the license automatically incompatible. It might even be that GPL Version 3 will include similar statements or at least allow them, as a message from FSF legal counsel Eben Moglen indicates. Additionally, prominent Apache hacker Roy Fielding claims that it doesn't really matter what the FSF thinks about the matter, because according to the Apache Software Foundation, derived works can just be distributed under the GPL."

11 of 405 comments (clear)

  1. Is anyone else getting worried here? by Ryvar · · Score: 4, Interesting

    Slightly concerned that we'll look back and say "Well, 2004 would've been the year Linux arrived in a big way . . . EXCEPT THAT WE TORE OURSELVES APART AT THE SEAMS."

    I don't mean to panic-monger or scream that the sky is falling without due cause - but this is all starting to get a bit worrying. Open Source has enough problems right now without actively helping its opponents.

    --Ryv

    1. Re:Is anyone else getting worried here? by orasio · · Score: 5, Interesting

      RTFA
      Nobody is fighting here.
      The FSF wrote a letter explaining license incompatibility issues in Apache license 2.0, and they even say its not a bad idea, in the listing of licenses.
      They state that the incompatibility exists, because it does, and they even imply that they might fix it themselves, so what's the problem?
      Anyway, who cares about "Linux" arriving in a big way? What is important is that free software continues to advance, and most of all, continues to be _free_, and license incompatibilities are bad in that they dont allow the cooperation between the ASF and the FSF (and XFree people), who are probably the most important developers of free software.

    2. Re:Is anyone else getting worried here? by Short+Circuit · · Score: 5, Interesting

      I'd like to see a clause in GPL3 that says something like "All patented contributions must be freely licensed for this work and automatically so for any legally derived works."

      Or something like that.

      Hey! Let's start a petition! Petition the FSF to include a statement to that effect in GPL3, and to release GPL3 by the end of the year.

      That'll be something to look forward to. :) I don't have the time to spawn the petition, but if I see it on Slashdot, I'll sign it.

      --
      tasks(723) drafts(105) languages(484) examples(29106)
    3. Re:Is anyone else getting worried here? by __past__ · · Score: 5, Interesting
      Petition the FSF to include a statement to that effect in GPL3, and to release GPL3 by the end of the year.
      I think it is pretty likely that the GPL3 will include something on patents anyway, this actually seems to be one of the two major reasons why people feel an update is neccessary (the other one being the "ASP hole", i.e. the GPL not being prepared for a web application scenario)

      It being released this year seems less likely, AFAIK it is still in pie-in-the-sky mode. Sure, you can petition them about it, but remember that the consequences of a rushed, ill-concieved GPL V.3 would be way worse than that of a delayed one. "Release early, release often" probably doesn't work that well for legal documents.

      --
      Programming can be fun again. Film at 11.
    4. Re:Is anyone else getting worried here? by T-Ranger · · Score: 4, Interesting
      I don't understand the problem here. RMS is old enough to remember when computers were big and centerlized.

      A "computer utility" was the purpose behind the Multics project. Many mainframe hardware manufactures, in addition to small regional based outfits, opearated ASP style businesses as far back as the 1960's. ASPs are nothing new.

      Ive said it before, HTTP+HTML - markup language with forms, client side rendering, few bits going accross the wire, is conceptually exactly the same as IBM 3270 terminals worked. A 1960's time sharing computer company is conceptually exactly the same as a 2004 web bases ASP.

      They should have seen this coming.

  2. Who knows by barenaked · · Score: 4, Interesting

    I believe that you can distribute a program under the GNU General Public License and a seperate Trademark license. That is what AbiSource does with AbiWord. And I don't think it restricts the freedom of the user since it is still allowed to distribute derived works. What does not seem to be compatible with the GPL is trying put any further restrictions on the user by invoking normal copyright law. By trying to use copyright law in the Apache license to restrict the rights of recipient to use an arbitrary word in the use of their derived work doesn't seem to be compatible with the GPL. (That arbitrary word would of course be Apache in this case :) Although if you have a real trademark on that word then clause 4 and 5 could be seen as just stating that the Apache License does not grant someone the right to use the word Apache since it is a trademark. But if that is the case then you could easily take away all confusion by using something like the following instead of clauses 4 and 5: This license does not grant you the right to use any of the trademarks of the Apache Software Foundation. "Apache" is a trademark of the Apache Software Foundation and products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. I think that would make sure that the new Apache License is compatible with the GPL.

  3. No. by Svartalf · · Score: 4, Interesting

    The problem is not one of the GPL being problematic, but rather people not thinking through what they're doing with their licensing. One of the GPL's purposes is to ensure that the code stays available to those that are interested in it as long as they are so interested. Pretty much only the GPL and LGPL do this of all the licenses out there. The other variants do this to some or no degree (MPL and APSL do some of this, but they're not as strong as the GPL is in this regard and the BSD/MIT/Artistic variants tend to not protect you from propritization of the code at all...).

    In the case of the new XFree86 license, it's a stupid play on their part to try to get more recognition (there's other ways to do this, folks- not a single player in the FOSS community is claiming that they're the ones that produced XFree86 at this point in time.) and I'm sure that the Apache license is probably another example of something not being quite thought out in the ramifications department.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  4. Another bump in the road by hoegg · · Score: 4, Interesting

    Many developers have strong convictions about which license they wish to use when releasing their code. However, I think that they'd often rather reuse and extend an existing library that does not use their license of choice than be burdened with re-implementing that functionality within their products or creating a new project with their license-of-choice. These kinds of incompatibilities encourage duplication of effort and discourage collaboration on many projects.

    I often wonder whether this problem could be mitigated or even solved by some creative license language. I'd like to license my software in such a way that it could be reused by projects using any of a majority of the other open source licenses. Also, I'd like to modularize it so that it could take advantage of high quality software released under otherwise incompatible licenses.

  5. Eben Moglen on Apache License, Version 2.0 by hexene · · Score: 4, Interesting
    Eben Moglen has previously stated on behalf of the FSF:

    ... FSF continues to believe that the achievement of compatibility between ASL and GPL would be of enormous benefit to the community of free software developers, allowing merger of valuable code bases currently separated by license incompatibilities. FSF is pleased to note the convergence implied by the ASL 2.0 draft. FSF will make efforts, in the development, discussion, and adoption of GPL 3 to further the process of convergence, by carefully considering the Apache Foundation's approach to the patent defense problem...

    So there is some light at the end of the tunnel.

  6. Who cares? by neurojab · · Score: 4, Interesting


    I, for one, use plenty of non-GPL software in my day to day life. I enjoy GPL software, but I tend to release open source software under more permissive licenses, such as MIT. I also use (and write) a lot of (gasp) closed source software as well.

    For the love of Pete, there are plenty of different software licenses out there. If you don't like the terms of a given license, don't use the software. If apache changes their terms because they think it makes them less likely to be sued, good for them. The GPL isn't the One True License, it's just one of the more restrictive ones that still claims to be "free". News flash: you can run software with virtually any license as long as you agree to the conditions. If some GPL-zealot distribution decides not to include Apache because of this, that's their problem.

  7. It DOES matter! by Eric+Smith · · Score: 4, Interesting
    prominent Apache hacker Roy Fielding claims that it doesn't really matter what the FSF thinks about the matter, because according to the Apache Software Foundation, derived works can just be distributed under the GPL.
    It most certainly does matter.

    If I want to distribute a derived work made partially from Apache software under the Apache license version 2, and partially from Foobarco's software under the GPL version 2, the fact that Roy Fielding (or even the Apache Foudnation) is OK with it does NOT solve the problem. Distributing the derived work under the Apache license terms is a violation of the GPL, and Foobarco would have grounds for action.