Changeset - 55b89a306494
[Not reviewed]
0 1 0
http://wandborg.se/ Joar@web - 10 years ago 2013-11-20 20:21:57

1 file changed with 1 insertions and 1 deletions:
0 comments (0 inline, 0 general)
ExistingProjects/ERPNext.mdwn
Show inline comments
...
 
@@ -81,25 +81,25 @@ restricted asset type?
 
- Is a [[specific workflow dictated by the system|UseCases/WorkFlow#workflow-dictated]] ? Yes
 
- Is a [[the workflow configurable|UseCases/WorkFlow#workflow-configurable]] ? No
 
- [[Unaccrued Invoice|UseCases/WorkFlow#unaccrued-invioice]] ? No
 

	
 
### Evaluation of the [[Reading and Reporting API|UseCases/ReadingAPI]]
 

	
 
See below.
 

	
 
### Evaluation of the [[Storage API|UseCases/StorageAPI]]
 

	
 
It is a web application using JavaScript to communicate with the backend, so there is an API endpoint for everything you'll ever see in the application.
 

	
 
- Is the accounting API separate from the ERP stuff? Kind of, it's in its own section, but it's still the same application, and I suspect you'll get information about links from any accounting-related models to any of the erp-related models
 
- Is the accounting API separate from the ERP stuff? No
 

	
 
### Evaluation of the [[Community Health|UseCases/CommunityHealth]]
 
- To post in [erpnext-developer-forum](https://groups.google.com/forum/#!forum/erpnext-developer-forum) you must first apply for membership.
 
- Is the [[license both determined as Free Software by FSF and OSI-approved|USeCases/CommunityHealth#license-approved]]? Yes, it's [GPLv3](https://github.com/webnotes/erpnext/blob/master/license.txt), (CC-BY-SA 3.0 for documentation).
 
- Is the [[license GPL-compatible||USeCases/CommunityHealth#gpl-compatible]]? Yes, it's [GPLv3](https://github.com/webnotes/erpnext/blob/master/license.txt), (CC-BY-SA 3.0 for documentation).
 

	
 
## Final(-ish) Evaluation
 
<a id="final-eval"></a>
 

	
 
Unfortunately, we discovered
 
[this policy early in our evaluation](https://github.com/webnotes/erpnext#copyright-for-contributors),
 
and decided that until this policy can be corrected to something more fitting
0 comments (0 inline, 0 general)