Created A strong Software Policy for FrontAccounting.com about fa HOT 2 OPEN

Will having such a policy bring upon the project unintended warranties implied or otherwise?

As there is nothing to sell and each user can harden their installations from within FA (additional captcha, checking internal logs and acting on them, etc) and from outside it (firewalls, routing permissions, etc), the use case for such a document will probably be for those who want to make commercial services around it. In fact quite a few are using it commercially and some shamefully not even giving credit to the project and not contributing their fixes back to the project either. Donations are scarce too.

Since the law is different in different places, the project should not undertake to "comply" with all such whims and fancies of every government in place. This software is only a skeleton which end users can mould to suit their needs and be responsible for it.

The project relies primarily on insecure MD5 hash of passwords, unsalted. Each user will tweak this to secure their installs, though many use it to teach Accounting where it may not matter.

"User Beware" is the best way forward in my opinion. Let each end user take appropriate counsel and considered expertise before venturing into FA.

The Policy is attached herein and it is better to place it in markdown syntax in the GitHub Wiki herein.

Certainly a very nice effort and hopefully some "Consultants" may seek your professional copy-writing skills for FA and other products / services they may have on offer!

FrontAccounting Software Security Policy full.docx

from fa.

from fa.