The FLA Gets Some Traction

by Mike Gunderloy - Aug. 25, 2008Comments (3) | Trackback URL

Have you ever heard of the Fiduciary Licence Agreement - the FLA? No, it's not an alterative to other free and open source license agreements that you're probably already familiar with, like the GPL, Mozilla License, and BSD License. Rather, it's an adjunct to any copyleft license, designed to help ensure the long-term survivability of free software projects. With the announcement last week that KDE has adopted an FLA, this notion may take on new prominence.

Here's the basic idea behind having an FLA. As free software projects grow, the successful ones attract participation from many developers and other contributors. By default, each individual contributor owns the copyright in their own code, but this could be a problem down the line. What happens if the project as a whole wants to change their licensing, but one of the contributors can no longer be contacted? They're stuck with either keeping the current license, or removing the contributor's work from the project.

The FLA - developed, in this case, by the Free Software Foundation Europe - is a formal assignment of copyright from individual contributors to an organization, which can then act as the legal custodian of the code. The FLA gives the assignee

the right to relicense the software as necessary for the long-term legal maintainability and protection of the software. The agreement also grants the author an unlimited amount of non-exclusive licences by FSFE, which allow using and distributing the program in other projects and under other licences. 

By  default, the FSFE is the recipient of the relicensing rights, but they have customizable versions of the FLA available for free software projects that have their own infrastructure in place to manage these rights. Projects that want to concentrate on technical issues can apply to use the FSFE's Fiduciary Services to manage their legal side.

Does your free software project need an FLA? If you're an individual developer, probably not. But once you start taking in contributions from others - especially if those others are located in more than one legal jurisdiction - it's definitely something that you should be looking into, to help guarantee the code's long-term survival as free software.


Browse Blog

Khürt Williams uses OStatic to support Open Source, ask and answer questions and stay informed. What about you?

3 Comments
 

Project lives on, even after the creators do not. Good stuff!

0 Votes

Linus said it best, when he was asked "What do you think will happen to Linux if you were to get hit by a bus?"

Linus: "I don't think I will really give a shit"

0 Votes

One of the problems with FOSS is the proliferation of licenses. Too many licenses just adds to the confusion of what can a user do and what is not allowed.

0 Votes
Share Your Comments

If you are a member, to have your comment attributed to you. If you are not yet a member, Join OStatic and help the Open Source community by sharing your thoughts, answering user questions and providing reviews and alternatives for projects.

Trackback URL
Please use the following URL to add a trackback to this article.
http://ostatic.com/trackback/171719