Merge in my changes from today from those done in online wiki editing.
This merges branch 'master' of oak.sfconservancy.org:npo-acct Resolving Conflicts: ExistingProjects/EvaluationTemplate.mdwn There didn't seem to be any real conflicts there, but auto-merger got confused.
This commit is contained in:
commit
1d880031ff
6 changed files with 14 additions and 10 deletions
|
@ -20,17 +20,12 @@ TODO:
|
|||
* [[ExistingProjects/Garradin]]
|
||||
* [[ExistingProjects/GNUEnterprise]]
|
||||
* [[ExistingProjects/GNUCash]]
|
||||
* [[ExistingProjects/HomeBank]]
|
||||
* [[ExistingProjects/JFire]]
|
||||
* [[ExistingProjects/JGnash]]
|
||||
* [[ExistingProjects/Kuali]]
|
||||
* [[ExistingProjects/Ledger]]
|
||||
* [[ExistingProjects/LedgerSMB]]
|
||||
* [[ExistingProjects/npo-ledger-cli]]
|
||||
* [[ExistingProjects/OpenERP]]
|
||||
* [[ExistingProjects/OpenPetra]]
|
||||
* [[ExistingProjects/Phreedom]]
|
||||
* [[ExistingProjects/Postbooks]]
|
||||
* [[ExistingProjects/SQLLedger]]
|
||||
* [[ExistingProjects/Tryton]]
|
||||
* [[ExistingProjects/TurboCASH]]
|
||||
|
|
|
@ -27,7 +27,8 @@ The information on this page is preliminary, open for comments.
|
|||
|
||||
* [In transitional phase](https://en.wikipedia.org/wiki/Apache_OFBiz#Open_Source_Libraries)
|
||||
* One tool for everything, possibly hard to streamline. <https://cwiki.apache.org/confluence/display/OFBREQDES/OFBiz+EZBiz> points to the contrary.
|
||||
* Documentation is spotty
|
||||
* Documentation is split up in one page per section, hard to overview (it uses confluence, the same documentation system as [[Kuali]]). The documentation also has TODOs in multiple locations and is lacking content.
|
||||
* The community is hard to get in contact with, three mailing lists are provided, a request for assistance has been sent to the `user` mailing list.
|
||||
|
||||
### Comments
|
||||
|
||||
|
|
|
@ -22,7 +22,7 @@ Links:
|
|||
|
||||
## Preliminary evaluation
|
||||
|
||||
- [Initial open source release in August 2013](https://github.com/system76/beansbooks/commit/96e8605d7553e56004376336bb961ffcd9380b3c)
|
||||
- [Initial source release in August 2013](https://github.com/system76/beansbooks/commit/96e8605d7553e56004376336bb961ffcd9380b3c)
|
||||
|
||||
### Positive
|
||||
|
||||
|
@ -33,4 +33,4 @@ Links:
|
|||
### Negative
|
||||
|
||||
- 1 [active contributor](https://github.com/system76/beansbooks/graphs/contributors) as of 2013-11-12
|
||||
- Odd licensing: <https://beansbooks.com/home/opensource>
|
||||
- Not free software: <https://beansbooks.com/home/opensource>
|
||||
|
|
|
@ -23,6 +23,7 @@
|
|||
|
||||
### Negative
|
||||
|
||||
- Community: The mailing lists are not very active, see <http://mail.tiolive.com/pipermail/erp5-users/>, <http://mail.tiolive.com/pipermail/erp5-dev/>
|
||||
|
||||
### Comments
|
||||
|
||||
|
|
|
@ -64,3 +64,6 @@ data does, so I think it's tough to do it as a list of questions.
|
|||
|
||||
FIXME: This is assessment of what the API for storing the accounting data
|
||||
does, so I think it's tough to do it as a list of questions.
|
||||
=======
|
||||
## [[UseCases/WorkFlow]] evaluation
|
||||
- [[Unaccrued Invoice|UseCases/WorkFlow#unaccrued-invioice]]: FIXME
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
Links:
|
||||
|
||||
- [Project homepage](http://kuali.org)
|
||||
- [Live demo](http://testdrive.kfs.kuali.org/kfs-ptd/portal.do)
|
||||
|
||||
## Technical
|
||||
|
||||
|
@ -10,10 +11,13 @@ Links:
|
|||
|
||||
Kuali seems like a complex set of machinery, with many projects or distributions with different attributes.
|
||||
|
||||
- Partially under "All rights reserved" licensing: http://testdrive.kfs.kuali.org/kfs-ptd/acknowledgements.jsp, should not be an issue.
|
||||
|
||||
### Positive
|
||||
|
||||
- Backed by Kuali Foundation
|
||||
- Backed by Kuali Foundation.
|
||||
|
||||
### Negative
|
||||
|
||||
- [Goofy licensing](http://testdrive.kfs.kuali.org/kfs-ptd/acknowledgements.jsp)
|
||||
- No public source control.
|
||||
- No open community channels such as mailing list, message board, IRC channel. This makes it very hard to find information about Kuali. The documentation is also very inconvenient as every section is a separate page, making it hard to get an overview of how Kuali works and its capabilities.
|
||||
|
|
Loading…
Reference in a new issue