Main Menu
SourceForge.net
TT100
 
 
Public license with attribution clause

As you are aware TenderSystem OS is released under the TenderSystem Public License (TPL), which is an adapted version of the Mozilla Public License, with an attribution clause. This license was conceived by SugarCRM, after vTiger forked their code base and released it as vTiger CRM, which is explained in an article, Code Theft or Liberalisation, that I wrote in December 2004.

The vTiger fork was not for technical reasons, which is one of the strengths of open source software, but rather a business strategy, in effect “leeching” of the hype created by SugarCRM and the work they have done. SugarCRM then added an attribution clause (SPL v1.1.3) to prevent this from happening again in the future. During the mudslinging that ensued SugarCRM were criticised for the way they handled the situation and not for license changes, as it was understandable why they were implemented.

At that stage we were busy evaluating the various open source licenses to release the TenderSystem code base, and saw the genius behind this model, especially for a web user interface application, that created a win-win scenario for developers and the community at large.

When TenderSystem was released under the TPL it was not submitted to OSI for certification, as there is pressure to decrease the number of approved licenses, even though it adheres to the definitions of open source. OSI will also most probably not certify project specific licenses, as the MPL states that the words “Mozilla” and “Netscape” may not be used for a derivative licenses, thereby creating a new license even though no other wording is altered.

Since then many projects were launched under this license and some existing projects even changed to this license due to the good fit for web based applications, as is the GPL for embedded applications. Lately some critics have come to the fore saying that the license is a form of badgeware and that it encumbers the spirit of open source.

Fortunately Mitch Radcliffe from Socialtext, a projects that also release under an adapted license, has submitted a General Attribution Provision (GAP), to be attached to OSI approved licenses that make provision for it, for approval to to the OSI board. The general provision is a very clever idea, as it will not affect the OSI license proliferation problems, and hopefully a formal response of their views will be released shortly.

If this is approved it will allow these projects to embrace other licenses, such as the GPL or LGPL, will most probably be TenderSystem’s choice, instead of just the MPL as is the current scenario.

Nicholas Goodman commented on the GAP provision on his blog to also provide limited Trademark and logo rights to prevent projects from circumventing the license through Trademark usage. The problem that this might cause is that a Trademark has to be protected to remain valid, which was the cause behind the Debian/Firefox debacle, and might be better to insert a complete Trademark Usage Policy, or version, in the license.

Rick Moen blogged wrote an article at Linux Gazette that members of the OSI mailing list found an obstacle with OSI’s definition #10, namely “License Must Be Technology-Neutral”, in that sometimes a user interface is not present, such as when running a daemon. This should not be a problem by rewording the GAP to a “reasonable attribution”, the term coined in Nicholas Goodman’s blog, in that adherence to attribution is only required when a user interface is present.

Which ever way it turns out I look forward to the outcome of the process and sure that there are going to be some interesting comments to this post.

[UPDATE: Socialtext have withdrawn the GAP for OSI board revision and will submit a new license in the future.]

5 Comments

  1. Comment by Christiaan:

    UPDATE: Alfresco has changed from the adapted MPL + attribution to GPL (version 2 only) with an additional “FLOSS exemption” that allows other OS applications to include the software, without having to release their own code under the GPL.

    The article can be found at http://news.com.com/Open-source+Alfresco+shifts+to+GPL/2100-7344_3-6161579.html.

    This is a very good move but TenderSystem is going to wait for GPL v3 to be finalised before considering a move.

  2. Comment by Christiaan:

    Rick Moen has submitted an email that I sent him to the OSI discussion list that can be found at http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:12566:200703:hnoknjoeceofapianmhk.

    You can also read up on my responses to this discussion at:

    http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:12573:200703:hnoknjoeceofapianmhk
    http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:12587:200703:hnoknjoeceofapianmhk

    To sum up the discussion Rick said that he thinks that the TPL contravenised OSI definitions #3 (allowing derivative works) and #6 (requiring business reuse) and OSD #10 (technology neutral).

    As stated in my response definition #3 and #6 are explicitly permitted in the license and the only issue could be if TenderSystem is used in a headless environment that it would infringe #10. TenderSystem is however a web based application and will therefore not be used in such an environment.Another way to overcome this would be to change the license wording to state that Annexure B only has to be adhered to if reasonably possible.

    Our preference however would be to release under a Tier 1 OSI approved license and are therefore waiting for the GPL3 / LGPL3 to be finalised before adopting a new license.

    We are also not interested in releasing under an intermediate license that just has to be changed in the future.

    Should you not agree with the above please let me know so that we can discuss.

  3. Comment by Christiaan:

    Ross Mayfield from Socialtext has sent new license to the OSI discussion mailing list that can be found at http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:12605:200703:ddflneepifdnbhkgfeln.

    This is an adapted version of the MPL with an exhibit B annexure that makes provision for attribution, based on the Adaptive Public License, and a network use provision based on the Affero license.

  4. Comment by Christiaan:

    GPLv3 draft 3 was released this week and it looks like it will not cover the SAAS / ASP loophole. It does however mention that Affero v2 will be compatible with GPLv3 so I presume that will be the license to look at.

    Affero v2 is not released yet, most probably just GPLv3 with distribution altered to incorporate usage, which should be completed a month after GPLv3’s release.

    http://www.affero.org: Affero’s software project was created to facilitate funding for Free Software and Open Source projects and to facilitate more effective dialogue among groups.

  5. Comment by Christiaan:

    There is a very interesting article at InfoWorld [http://weblog.infoworld.com/openresource/archives/2007/04/web_20_and_the.html] stating the problems that ASP software developers are experiencing and that a new license must be developed to overcome this problem.

Leave a comment

Login
Username:

Password:


Lost Password?

Register now!

Copyright ValueCard (Pty) Ltd ValueCard (Pty) Ltd
All rights reserved
Disclaimer
Privacy Policy
Sitemap