EOF - The Free Software Act
Free software licenses function in a number of different ways. First, they are a statement of rules about what free software programmers can and cannot do within their own communities. Part of the reason for complying with these conditions is the power of reputational capital: there is an incentive to play the game by the recognised rules, whether formal or informal, written or understood. The licenses also bind in a legal way because they are built on copyright and licensing or contract law. Copyright protects authors' original creations by allowing them to prevent access to their work; software licenses permit access to such works, under certain conditions. When the licenses are proprietary, what the user can do with the work is quite restricted, whereas free software licenses allow different degrees of freedom. Some, such as the BSD licenses, have practically no requirement to give anything back. Others, such as the GNU GPL, place strong obligations on authors when software is modified and published.
The law governing software licensing appears straightforward, but it is not. Contract law varies from jurisdiction to jurisdiction, as does copyright. A law drafted in one legal system may not bind in another. Therefore, ideally speaking, some international standardisation of law in this area should be in place to make sure rules that bind in one country do likewise in another.
This point was made clear to me when I began studying this area of law from a socio-legal perspective some years ago. I believed that free software legislation was something that programmers involved in this line of work should seek. I started work with the Free Software Consortium (FSC) during the summer of 2003 and was appointed as coordinator of their Legal Governing Body. In Costa Rica last September, I commenced a project to draft free software legislation with a view to getting it passed by legislatures around the world. The project is in its infancy but is maturing rapidly.
My early take on the matter was that because the GNU GPL was the most commonly used license among free software developers, the law should be put in place to protect this scheme. Draft 1 of the Free Software Act attempted to enshrine its terms and added a few more, such as protection for any programmers who inadvertently infringed a copyright. This latter point would preempt any recurrence of vexatious lawsuits, such as the current SCO vs. IBM case. I quickly was put right, however, by colleagues in the FSC and by Richard Stallman himself, who advised me that such legislation should not seek to copyleft all free software but, rather, should endeavour to grant legislative force to all free software licenses. Draft 2 was an improvement on the first draft but still appeared to copyleft all free software. I began work on Draft 3 after Christmas 2003, and it recently was completed. I currently am working on Draft 4, which I hope will hit the mark more closely. Once completed, Draft 4 will be available on the FSC Web site, as are the earlier versions.
My idea about this project is to make it a venture of the Free Software community as a whole. The worst types of law are those that disrupt beneficial and functioning social contracts, such as the introduction of copyright law to cover software when previously it had been a shared resource. Lawyers have to respond to social movements and change. They should take part in such movements and share such drafting activities, so they become linguistic facilitators of communities' customs and wishes, rather than interlopers who enter the fray and disrupt it.
This project continues to be a learning experience for me. Initially, I saw value in protecting only the copyleft system, as it is the most common one, makes the most demands and potentially is most vulnerable in the eyes of the law. Other considerations need to be taken into account, however. Such a law would prove divisive if it protects only one, albeit the majority, view. It would be preferable, indeed, to have an international law that gives protection to all free software licenses. This would mean any clashes between the license and the contract or copyright law of the particular country in which the case is being tried would be irrelevant: the legislation would act to bind third parties and would ensure that rights recognised in one place would be recognised similarly in another.
At the time of this writing, Draft 3 is the most recent version of the Act, and it can be viewed on the FSC Web site at www.fsc.cc. Comments are welcome, and participants to the FSAct mailing list at Fsact@lists.fsc.cc are encouraged. Alternatively, you can e-mail me at firstname.lastname@example.org.
Maureen O'Sullivan is a lecturer in law, based in the UK. Her research interests are in legal and socio-legal aspects of free software, including licensing.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide