Difference between revisions of "Talk:Lokad business forecasting"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(calling for discussion on limitations of paid usage model)
(answers concerning OS commitment + vendor lock-in for Lokad)
Line 8: Line 8:
  
 
:There is new info that there is a non-free service from Lokad. We are discussing with Vermore further on what actually that model is, whether its restrictive to the OS nature or if it affects the GPLv2 licensing here. We welcome ideas from others meanwhile - [[User:Red1|Red1]]
 
:There is new info that there is a non-free service from Lokad. We are discussing with Vermore further on what actually that model is, whether its restrictive to the OS nature or if it affects the GPLv2 licensing here. We welcome ideas from others meanwhile - [[User:Red1|Red1]]
 +
 +
::I will try to answer the questions that have been raised in the various emails. Concerning '''open source commitment''', we are trying to make the things as open as possible. All the ''Lokad Desktop'' source code is being hosted on sourceforge.net, all documentation being made available through our wiki. Everything is released under a BSD license. It means that all the code can be reused within open or closed source products without any licensing hassle. In particular, the BSD license is compatible with the GPL license. We do intend to ever change of licensing model because it would not make any sense in the Lokad business model. The more applications with business forecasting modules out-there, the more potential customers for Lokad.
 +
 +
::Concerning the question about '''vendor lock-in''', we believe that the Lokad approach is fair. The Lokad forecasting technology is a commercial technology that requires a paid subscription plan. Yet, we are designing our products in a "clean" manner. If you want to replace the Lokad forecasting services by any other web services or by a locally implemented algorithm, it is completely straightforward (just a single class to replace). Yet, by doing that you would loose the two of main benefits of Lokad: ''collaborative forecasting'' (data are shared to improve accuracy on a collective basis) and ''accuracy monitoring'' (accuracy gets monitored in a continuous manner in order to maintain/improve the forecast accuracy).--[[User:Vermorel|Vermorel]] 12:19, 24 February 2007 (EST)

Revision as of 10:19, 24 February 2007

So far we have tested the add-on only with the latest version of ADempiere (3.14 at the time of this post) under Oracle database. Since this add-on relies on very elementary database tables of ADempiere, I would guess that we are actually supporting many different version of ADempiere. If you start using this add-on with different versions of ADempiere, do not hesitate to report that it works on the wiki page, or, on the contrary, to make a bug report if it does not. --Vermorel 04:22, 24 February 2007 (EST)

Welcome and many thanks Vermore, for such an important addon and well done finished works. U been added as the latest hottest add-on in http://www.adempiere.org! We appreciate the smart partnership to allow our users enjoy a more feature-rich application suite. This cross-brand of products and user-bases is mutually encouraged within the bazaar. Feel free to put in more of your relevant product or services info to advertise your business as needed. Equally do ask us if u need any further assistance. Like to also credit Carlos Ruiz who assisted in translating the LOKAD/ADempiere SQL query statement for this to work. - Red1 05:47, 24 February 2007 (EST)

Thank you very much for your support. I have added a special thanks section at the bottom of the page. Carlos Ruiz is also mentioned directly on the Lokad website (see the bottom of the Lokad Desktop page). I have also clarified the business model of Lokad based on the feedback of Ramiro Vergara.--Vermorel 09:39, 24 February 2007 (EST)

There is new info that there is a non-free service from Lokad. We are discussing with Vermore further on what actually that model is, whether its restrictive to the OS nature or if it affects the GPLv2 licensing here. We welcome ideas from others meanwhile - Red1
I will try to answer the questions that have been raised in the various emails. Concerning open source commitment, we are trying to make the things as open as possible. All the Lokad Desktop source code is being hosted on sourceforge.net, all documentation being made available through our wiki. Everything is released under a BSD license. It means that all the code can be reused within open or closed source products without any licensing hassle. In particular, the BSD license is compatible with the GPL license. We do intend to ever change of licensing model because it would not make any sense in the Lokad business model. The more applications with business forecasting modules out-there, the more potential customers for Lokad.
Concerning the question about vendor lock-in, we believe that the Lokad approach is fair. The Lokad forecasting technology is a commercial technology that requires a paid subscription plan. Yet, we are designing our products in a "clean" manner. If you want to replace the Lokad forecasting services by any other web services or by a locally implemented algorithm, it is completely straightforward (just a single class to replace). Yet, by doing that you would loose the two of main benefits of Lokad: collaborative forecasting (data are shared to improve accuracy on a collective basis) and accuracy monitoring (accuracy gets monitored in a continuous manner in order to maintain/improve the forecast accuracy).--Vermorel 12:19, 24 February 2007 (EST)