-
Notifications
You must be signed in to change notification settings - Fork 94
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1513 from HryhoriiHevorkian/feature/HHE_readme_up…
…date #obg-171 readme update.
- Loading branch information
Showing
1 changed file
with
5 additions
and
114 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,32 +9,11 @@ | |
| - Frontend: [](https://codecov.io/gh/adorsys/open-banking-gateway) | ||
| - Example code: [](https://codecov.io/gh/adorsys/open-banking-gateway) | ||
|
|
||
| # Changes in OSS release policy | ||
| This is the try-out version of adorsys Open Banking Gateway: an open source (AGPL v3) solution to get acquainted with the adorsys-developed gateway and test its AIS and PIS flows and the respective connectivity to the largest retail banks in Germany (see our XS2A [Adapter](https://github.com/adorsys/xs2a-adapter) project). | ||
|
|
||
| For the time being, version 1.0.0 will be the current try-out version of Open-Banking Gateway that adorsys publishes on GitHub. | ||
| With PSD2 standards and our solutions having grown to maturity in production, our continuous investment in development and maintenance | ||
| of our XS2A projects forces us to focus on our commercial engagements. | ||
| We are committed to continuous active development of our XS2A solutions to ensure constant adherence to the latest Berlin Group | ||
| specifications and to support OpenFinance initiatives. | ||
| Existing published versions will remain available under their respective open-source licenses. | ||
| If you are a user of our XS2A solutions and would like to either start or extend cooperation, please contact us under [email protected]. | ||
|
|
||
| # Licensing model change to dual license: _AGPL v.3_ or _commercial license_ | ||
|
|
||
| **Attention: this open-source project will change its licensing model as of _01.01.2022_!** | ||
|
|
||
| Constantly evolving and extending scope, production traffic and support in open banking world call for high maintenance and service investments on our part. | ||
|
|
||
| Henceforth, adorsys will offer all versions higher than v1.0 of Open Banking Gateway under a dual-license model. | ||
| Thus, this repository will be available either under Affero GNU General Public License v.3 (AGPL v.3) or alternatively under a commercial license agreement. | ||
|
|
||
| We would like to thank all our users for their trust so far and are convinced that we will be able to provide an even better service going forward. | ||
|
|
||
| For more information, advice for your implementation project or if your use case requires more time to adapt this change, | ||
| please contact us at [[email protected]](mailto:[email protected]). | ||
|
|
||
| For additional details please see the section [FAQ on Licensing Change](#faq-on-licensing-change). | ||
| If you are looking for a strong base framework to build up your own gateway capabilities, we would be thrilled to cooperate with you and share our know-how of the framework and overall open finance and development expertise. | ||
|
|
||
| If you are an organisation that would like to commercially use our solutions beyond AGPL v3 requirements, we are open to discuss alternative individual licensing options. If you are interested in working with us or have any other inquiries, please contact us under [[email protected]](mailto:[email protected]). | ||
|
|
||
| # Open Banking Gateway | ||
| Provides tools, adapters and connectors for transparent access to open banking apis. The initial effort focuses on the connectivity to banks that implement the European PSD2 directive either through one of the common market initiatives like : [The Berlin Group NextGenPSD2](https://www.berlin-group.org/psd2-access-to-bank-accounts), [The Open Banking UK](https://www.openbanking.org.uk/), [The Polish PSD2 API](https://polishapi.org/en/) or even through proprietary bank api like [the ING’s PSD2 API](https://developer.ing.com/openbanking/). | ||
|
|
@@ -170,94 +149,6 @@ For commercial support please contact **[adorsys Team](https://adorsys.de/)**. | |
|
|
||
| ## License | ||
|
|
||
| This project is dual licensed under Affero GNU General Public License v.3 (AGPL v.3) or alternatively under a commercial license agreement - see the [LICENSE](LICENSE) file for details. | ||
|
|
||
| For commercial inquiries please contact us at [email protected]. | ||
|
|
||
| For additional details please see the section: FAQ on Licensing Change. | ||
|
|
||
|
|
||
| ## FAQ on Licensing Change | ||
|
|
||
| ### What is a dual-licensing model? | ||
|
|
||
| Under a dual-licensing model, our product is available under two licenses: | ||
|
|
||
| - [The Affero GNU General Public License v3 (AGPL v3)](https://www.gnu.org/licenses/agpl-3.0.en.html) | ||
| - A proprietary commercial license | ||
|
|
||
| If you are a developer or business that would like to review our products in detail, test and implement in your | ||
| open-source projects and share the changes back to the community, the product repository is freely available under AGPL v3. | ||
|
|
||
| If you are a business that would like to implement our products in a commercial setting and would like to protect your | ||
| individual changes, we offer the option to license our products under a commercial license. | ||
|
|
||
| This change will still allow free access and ensure openness under AGPL v3 but with assurance of committing any | ||
| alterations or extensions back to the project and preventing redistribution of such implementations under commercial license. | ||
|
|
||
|
|
||
|
|
||
| ### Will there be any differences between the open-source and commercially licensed versions of your products? | ||
|
|
||
| Our public release frequency will be reduced as our focus shifts towards the continuous maintenance of the commercial | ||
| version. Nevertheless, we are committed to also provide open-source releases of our products on a regular basis as per our release policy. | ||
|
|
||
| For customers with a commercial license, we will offer new intermediate releases in a more frequent pace. | ||
|
|
||
|
|
||
|
|
||
| ### Does this mean that this product is no longer open source? | ||
|
|
||
| No, the product will still be published and available on GitHub under an OSI-approved open-source license (AGPL v3). | ||
|
|
||
|
|
||
|
|
||
| ### What about adorsys’ commitment to open source? Will adorsys provide future product releases on GitHub? | ||
|
|
||
| We at adorsys are committed to continue actively participating in the open-source community. Our products remain | ||
| licensed under OSI-approved open-source licenses, and we are looking forward to expanding our product portfolio on GitHub even further. | ||
|
|
||
|
|
||
|
|
||
| ### How does the change impact me if I already use the open-source edition of your product? | ||
|
|
||
| All currently published versions until v1.0 will remain under their current Apache 2.0 license and its respective | ||
| requirements and you may continue using it as-is. To upgrade to future versions, you will be required to either abide | ||
| by the requirements of AGPL v3, including documenting and sharing your implemented changes to the product when | ||
| distributing, or alternatively approach us to obtain a commercial license. | ||
|
|
||
|
|
||
|
|
||
| ### What if I cannot adjust to the new licensing model until 01.01.2022? Can I extend the deadline? | ||
|
|
||
| We understand that adjustment to licensing changes can take time and therefore are open to discuss extension options on | ||
| an individual basis. For inquiries please contact us at [[email protected]](mailto:[email protected]). | ||
|
|
||
|
|
||
|
|
||
| ### Which versions of the product are affected? | ||
|
|
||
| All versions of Open Banking Gateway after v1.0 will be affected by the licensing changes and move to a dual-licensing model. | ||
|
|
||
|
|
||
|
|
||
| ### What will happen to older, Apache 2.0 licensed product versions? | ||
|
|
||
| All older Apache 2.0 licensed versions prior and including v1.0 will remain available under their existing license. | ||
|
|
||
|
|
||
|
|
||
| ### What open-source products from Adorsys are affected by the licensing change? | ||
|
|
||
| The following products are affected: | ||
| - [XS2A Core](https://github.com/adorsys/xs2a) | ||
| - [XS2A Sandbox & ModelBank](https://github.com/adorsys/XS2A-Sandbox) | ||
| - [Open Banking Gateway](https://github.com/adorsys/open-banking-gateway) incl. [XS2A Adapters](https://github.com/adorsys/xs2a-adapter) | ||
| - [SmartAnalytics](https://github.com/adorsys/smartanalytics) | ||
| - [Datasafe](https://github.com/adorsys/datasafe) | ||
|
|
||
|
|
||
| ### I’m using one of these products indirectly via some software integrator. How does the licensing change affect me? | ||
| This project is licensed under Affero GNU General Public License v.3 (AGPL v.3) - see the [LICENSE](LICENSE) file for details. | ||
|
|
||
| The licensing change does not affect you as user, but it is relevant to your provider who has used our product in their | ||
| solution implementation. In case of uncertainty please contact your service provider or approach us at [[email protected]](mailto:[email protected]). | ||
| For alternative individual licensing options please contact us at [[email protected]](mailto:[email protected]). | ||