Software For Ransom

rbp writes "I just received a message from Adam Theo on the Jabber Developers Mailing List about what he calls "The Ransom Model" for software publishing. The principle, according to the above linked site, is that the "rights to the source code remain restricted until a set amount of money is collected or a set date passes, at which point the code is freed". Seems like a very interesting way to make money and produce free software. I think it's worth discussion. Take a look at the Ransom Model webpage and join the Ransom mailing list! (You might also be interested in recent news about Blender)" Reader Apreche adds a link to a Freshmeat editorial piece which draws on Theo's idea, writing "This has some obvious problems, but it is worth discussing. The biggest problem I see is where vaporware fits into the equation."

Comments

Re:Ransom is such a negative word

[Adam Theo]

Others have brought up the negative connotations about the name, but far more have liked it. I personally like the name because it makes people stop and look, and because it is so bold it actually comes off as being a bit goofy of a name. Also, it very appropriately describes the entire process in one simple word. How many other projects can claim that? :-)

Besides, end users are not likely to ever see the term "Ransom". I expect this model will mostly be seen and used by the developers and their sponsors, investors, and distributors/resellers (to use those terms loosely).

Street Performer Protocol

[Robotech_Master]

Actually, it has been thought of before, in the form of the Street Performer Protocol. Granted, the SPP as written assumes that it's going to be applied to textual works, but it doesn't seem like a great leap to apply it to the programming world.

Slashdotted...Here's the text

[Billy the Mountain]

"Ransom is a software publishing model where the rights to the source code remain restricted until a set amount of money is collected or a set date passes, at which point the code is freed".
This model is fair, legally sound, practical, and easy to understand. In the Ransom model, the programmers are paid by the simple demand and quality of their work, not by selling copies of their work by creating artificial supply restrictions.

The problem that Ransom solves is that many open source developers work very hard on their software projects, and usually end up giving their work away, due to the nature of open source. I firmly believe that their social-mindedness and generosity do not qualify as reasons why they shouldn't be fairly compensated for their work. It is impossible to ensure payments through closed source software use, so the rules of publishing the software in the first place need to be changed.

Current models do not work since they are not fair to all parties. Purely "closed source" softwares not only severely restrict the user's abilities and freedoms, but also ignore the laws of value by ignoring software's ability for unlimited supply using a simple 'copy' command. Purely open source software removes any chance of reliable income from the programmer and leaves them to the whims of gifts and benefactors. Neither of these are acceptable.

Details: In short, Authors (the programmers of the software) first publish their work under a Ransom License (a special proprietary license). There exists the stipulation that the code will be automatically freed to a set Open Source License ([OSI]/[FSF]-approved or the public domain) once a set amount of funds have been collected from Contributors (satisfied users, grateful corporate customers, or distributors/resellers) or a set amount of time passes, whichever comes first. You can read details of the complete step-by-step process.

The public gets completely open source software, and the programmers are fairly compensated for the real work they do, not the amount of "copies" they sell. Public interests are protected by legally-binding guarantees and oversight organizations. You can read details of all features and considerations.

Issues: The current issues being discussed are:

The list of Ransom Licenses (such as: /Simple).
The list of Free Licenses.
Whether Ransom should allow authors to completely hoard their source code until the full Ransom amount has been paid, not even selling restricted copies.
Discussion: All discussion of Ransom occurs on the Ransom mailing list, to which you can [subscribe, unsubscribe, or manage]. The list is not moderated, but you must subscribe to post. You can also [read and search the archives] of the mailing list.

Background: This project began as an idea from a friend, Eric Murphy, on how to finance a digital identity system (which has now grown into [PingID]). I took the idea and posted to [Crynwr's Free Software Business list] about it. This project is the final realization on how to achieve financial compensation for producing open & free software.

---

This is a valid model, used by Blender amongst other projects. However, I think the use of the term 'Ransom' creates a rather negative perception - do you really want an open source model associated with kidnapping? -- RichardDonkin

Perhaps a better name would be: 'Appreciation Model' or 'Threshold Model'. -- PipStuart