| |||||||||||||
another SQL Ledger fork: LX Office ERPanother SQL Ledger fork: LX Office ERPPosted Mar 22, 2007 13:28 UTC (Thu) by terber (subscriber, #3311)Parent article: SQL-Ledger and LedgerSMB: a study in security reporting LedgerSMB wasn't the only or even the first fork from SQL Ledger. LX Office ERP went that road before, also because of disagreements with Mr Simader. Today the project politely states among other reasons that "co-ordination of the development got increasingly delicate". At times the reaction concerning the fork on SQL-Ledger side wasn't all that moderate.
(Log in to post comments)
another SQL Ledger fork: LX Office ERP Posted Mar 31, 2007 19:35 UTC (Sat) by einhverfr (guest, #44407) [Link] In the LedgerSMB project, we looked at joining LX Office, OpenLedger, and one other fork I forget the name of. Unfortunately, of those, LX Office was the only one with any development activity and the fork was from a much older version (meaning getting existing users to be able to make it work for them was going to be far harder).
In the end, we chose to go our own separate way.
I suspect though that we may be the first credible threat to SQL-Ledger in a long time. We try to remain cordial, sharing security and bug reports where appropriate with Mr Simader, but we have found increasing hostilities towards our project (the apparent intent to move from the GPL being the most recent).
After about six months with the SQL-Ledger codebase, the work before us is to re-engineer the entire application, moving it to a new architecture, and preparing for a full UI redesign. We are also adding features in the mean time. 1.2.0 will be released on Monday and after that point, work will be largely aimed at removing the code from the current codebase.
|
|||||||||||||