So, in the next few weeks, I'll be introducing a tweaked licence model. In the past year I've been adding loads of new value into the product:īut all this takes development time to write and support, and so now is the time to address the debt. New releases of bliss average out at about one a month at the moment. The promise of unlimited updates forever essentially becomes a debt I have committed to. Why is it unsustainable? Well, because as the total volume of bliss users increases, so do support costs, hosting costs and more. Unfortunately, this model of development and licencing is unsustainable unless the number of customers continually increases. That was my promise and I'll be sticking to it for existing customers. So I sided with rolling updates and unlimited updates for life. It becomes an impediment to continual improvement. I've never liked that model, because of the artificial chunking of "major" and minor versions, delineations of what is a major new feature and what isn't, and so on. This is in contrast to most downloadable, self-hosted software that requires upgrade fees for new versions. That means, for £30, you get continual improvements in the product forever. So, as an example, if you purchase the unlimited licence, you can use those unlimited "fixes" on all future versions of bliss. Since bliss was started in 2009 I've provided unlimited updates for all customers. But please read on and let me know your opinion. TL DR: bliss will move to charging a yearly renewal fee to allow new licences to continue to work on new versions of bliss. I don't do this easily I've made two changes (to decrease the number of trial fixes, and to decrease the number of the top-up fixes) in the history of the bliss project, and the last one was over two years ago. It's time for an update to how bliss is licenced, and charged for.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |