From 0064b3bfcfcee14b2d1f18e76d10ae31cf27df21 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkL61gEnGpxJlJkheoMMKd-wnixdnfdxuY" Date: Thu, 31 Oct 2013 18:06:29 +0100 Subject: [PATCH] --- ExistingProjects/SQLLedger.mdwn | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/ExistingProjects/SQLLedger.mdwn b/ExistingProjects/SQLLedger.mdwn index c0f1d46..a302ba7 100644 --- a/ExistingProjects/SQLLedger.mdwn +++ b/ExistingProjects/SQLLedger.mdwn @@ -27,6 +27,10 @@ Links: - Unclear directory structure - Seemingly no API documentation - Documentation not open source -- Many known security holes -- Primary developer hostile to outside contributions + +### Comments + +Josh Berkus: I was an early (uncredited) contributor to SQL-Ledger, and part of the fork. The reasons we created the fork: +- Many known security holes (reference early LedgerSMB releases, which fix these. They are still not fixed in current SQLLedger) +- Primary developer hostile to outside contributions, and did not credit the contributions he did receive. Also relicensed contributions without permission. I know, because some of the contributions were mine. - Basically the primitive ancestor of LedgerSMB