Hi Michael,
I’m working on an open source accounting and bookkeeping software project called “PBooks”, and plan to release the software under the AGPLv3.
I’ve been holding off publishing the code until the AGPL v3 is final and published, because I’m not sure if I release it now under the AGPL version 1, whether or not I can change the license later on. I’m under the impression that if licensed under the AGPL v1, it will always be licensed that way, but future versions (of the new code anyway) could be licensed differently. On the other hand, would the new code be considered a modification and thus be required to be available under the AGPLv1? This legal stuff makes my head spin.
The licensing delay has given me the time to compare what I’ve created with the many other open source accounting software projects that either stalled in development, or ended up with some wacky functionality or licensing scheme that didn’t fit my needs. At the same time, I’m working to simplify and streamline everything having to do with PBooks, so that others who find it will be able to easily modify it to fit their vision.
I foresee the following scenarios:
* Small-to-large businesses that are tech savvy can take the code, modify it, integrate it into their operations, not make the service publicly available (or distribute it), and thus not have to worry about their changes.
* Hosting companies that offer small business services like email, blogs, and web services in general could use the code but would be required to publish their modifications to PBooks under the same open source license.
* Financial companies, like banks, that offer online banking and related services could offer the software as a service to their customers. I would also like to require these businesses to publish their modifications under the same open source license. Alternatively, they could purchase a commercial license for a fee, and not be required to publish their modifications. Many of these potential customers would also involve value-added “resellers”, who I would like to require to publish their modifications, or pay for commercial licenses.
It is ironic that in all likelihood, it will be the first category that ends up contributing the most to the project. After that, it would most likely be the hosting companies who would then “spread the word” about such a project, and it is questionable whether banks would consider using a product with any open source limitations at all. I imagine that banking customers would prefer the fee-based alternative for a license with a more commercial and private focus. It is because of the potential for a dual-license that I’ll either require contributors to assign their copyrights to my company, or not accept contributions at all. That is not to say that the modifications would not be required to be published under the open source license, it just means that my company wouldn’t be selling licenses to them!
Furthermore, I’m planning the integration of plug-ins, which could work with PBooks and to a limited degree modify its behavior. Those plug-ins would of course have no licensing restrictions at all.
I believe that the AGPLv3 is the right license for PBooks, and eagerly await the finalized version. Feel free to contact me about the project and the our use of the license at any time in the future. I’ve been working on it for almost three years, and will continue to do so in the foreseeable future.
From,
Albert
http://www.pbooks.org/
UPDATE: Nice, they approved my comment. 
Latest Comments
RSS