Contribs and Licensing » History » Revision 2
Revision 1 (Hans-Martin Haase, 08/12/2015 10:27 AM) → Revision 2/3 (Hans-Martin Haase, 08/12/2015 03:06 PM)
{{toc}}
h1. Contributions to the Open eCard Project
The Open eCard project is an open source project which depends in several ways on contributions of the community. A contribution may be just a feature request or bug report in the corresponding tracker or to the e-mail address feedback@openecard.org. If you want to be an active member of the development process there is the possibility to contribute bugfixes or even complete new feature in form of source code. You may also become a member of the translator team and translate the software into other languages.
h2.
h1. Open eCard Core License
The Open eCard App and the corresponding sources (except the Third Party Libraries, see below) are released under a Dual License. So what are these licenses and how does they influence the contribution process?
There is on one side the General Public License in version 3 which grants that all contributions are made public under this license. On the other side there is a proprietary license which allows the currently maintaining company ("ecsec GmbH":https://www.ecsec.de) to sell copies of the software to parties which are interested in obtaining a copy under such a license. The maintaining company is obliged to share the revenues among the contributors. The legal question are clarified in the "Open eCard
h2. Contribution Agreement":https://dev.openecard.org/documents/35 which may be downloaded from the "Documents":https://dev.openecard.org/projects/open-ecard/documents section.
h3. Contribution Agreement
The contribution agreement is an agreement between the contributor and the maintaining company ("ecsec GmbH":https://www.ecsec.de). The agreement ensures that the complete software product may be distributed under the dual license stated above. A contributor in this sense is an individual or a legal entity which contributes source code or other digital media which is contained in some way in the software.
h2. h1. Foo
Third Party Libraries And Their Licenses
Following the used third party tools and libraries and their licenses are listed (direct dependencies only):
|Apache Commons (http://commons.apache.org) | Apache License Version 2 |
|Apache HttpComponents (http://hc.apache.org) | Apache License Version 2 |
| Apache Maven (https://maven.apache.org) | Apache License Version 2 |
|Bouncy Castle Crypto API (http://www.bouncycastle.org) | modified MIT License |
|Commons JCI FileAlterationMonitor (https://commons.apache.org/jci/commons-jci-fam) | Apache License Version 2 |
|FindBugs (http://findbugs.sourceforge.net) | LGPL Version 3 |
|Google Android SDK (http://source.android.com) | Android Software Development Kit License Agreement |
|Gson (https://code.google.com/p/google-gson/) | Apache License Version 2 |
|JMockit (http://jmockit.github.io/) | MIT License |
|Logback (http://logback.qos.ch/) | EPL Version 1 or LGPL Version 2.1 |
|Logback-Android (https://github.com/tony19/logback-android) | EPL Version 1 or LGPL Version 2.1 |
|Oxygen (http://www.oxygen-icons.org) | LGPL Version 3 |
|SLF4J (http://www.slf4j.org) | MIT License |
|Seek for Android (https://code.google.com/p/seek-for-android) | Apache License Version 2 |
|TestNG testing framework (http://testng.org) | Apache License Version 2 |
h2. h1. Addon Licenses
Contributions in form of an addon are not covered by the license of the core system. Every developer is free to select any license appropriate for his needs this may be an open source license or also a commercial/proprietary license there are no restrictions.