Date: Fri, 29 Mar 2024 08:07:20 +0000 (UTC) Message-ID: <1103671908.27.1711699640679@8fdbf95ce13d> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_26_1145518296.1711699640679" ------=_Part_26_1145518296.1711699640679 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page is about adding software to Mifos. It includes adding = source code or binary libraries in the form of jars.
As an open source developer, you are responsible for doing the work to m= ake sure that the software you want to use will be compatible on legal as w= ell as technical terms.
When developing code, if you see a place where external software would b= e appropriate, please add it! See below for some criteria to help you decid= e what is appropriate.
All software (including library jars) incorporated into Mifos must be co= mpatible with the Apache License 2.0. These include Apache 2.= 0, BSD, MIT, and others. GPL v2 and v3 software are not co= mpatible, and software using these licenses may not be incorporated into Mi= fos.
If you are in doubt, do not add the software to Mifos, and ask on the De= veloper mailing list.
Mifos does not include certain kinds of cryptographic software that is r= estricted by the United States government. This is because Grameen Foundati= on, the maker of Mifos, is located in the United States and must abide by i= ts laws.
Not all cryptographic software is excluded - for example, secure hashing= functions like MD5 and SHA1 are not restricted. Symmetric and asymmetric e= ncryption and decryption software with keys in excess of 64 bits are restri= cted. If in doubt, do not add to Mifos, and contact the Mifos Developer Mai= ling list for help.
For more information see:
To add source code to Mifos, you must sign the Mifos Contributor Agreement.
In general, do not add source code to Mifos if it can added via a jar fi= le. (See Don't Repeat Yourself.) If in d= oubt, contact the Mifos Developer mailing list for help.
All jars added to Mifos - via Maven pom.xml files or other means - must =
be compatible with the Apache License 2.0 as noted above, and must not cont=
ain restricted cryptographic software in the jar or any dependencie=
s of the jar. Use mvn dependency:analyze
to see jar d=
ependencies that are managed by maven.
If in doubt, do not add the jar, and contact the Mifos Developer mailing= list for help.