|
| 1 | +# Contributing |
| 2 | + |
| 3 | +The OpenPFC software framework is provided as an open-source software to support |
| 4 | +the open science principle. The framework is mainly developed in publicly funded |
| 5 | +research projects, but some maintenance and software development is done as |
| 6 | +voluntary work. We appreciate all the contributions to the software framework, |
| 7 | +whether they are to the code itself or to, e.g., the documentation or examples. |
| 8 | +To keep the framework package in shape, we have to follow certain strict |
| 9 | +practices, such as the contributions are always evaluated by the OpenPFC main |
| 10 | +developers and the copyright of the contribution is transferred to [VTT |
| 11 | +Technical Research Centre of Finland Ltd](https://www.vttresearch.com/en), the |
| 12 | +copyright holder of OpenPFC (see the details below). |
| 13 | + |
| 14 | +## How to contribute |
| 15 | + |
| 16 | +The general steps for contributing to OpenPFC software framework are: |
| 17 | +1. Read at least the files [README.md](README.md), |
| 18 | + [CONTRIBUTING.md](CONTRIBUTING.md), [LICENSE.md](LICENSE.md), and the |
| 19 | + documentation in the [docs](docs) directory. |
| 20 | +2. If the contribution is small, e.g., a small fault in the documentation, you |
| 21 | + can point it out by making an issue. |
| 22 | +3. For larger contributions, you should make your local fork of the OpenPFC |
| 23 | + repository, make the modifications and/or additions to it, and then make a |
| 24 | + *pull request*. |
| 25 | +4. To avoid unnecessary work, keep high quality in your coding and document |
| 26 | + writing, check your text and test your code carefully before your |
| 27 | + contribution. |
| 28 | + |
| 29 | +## Copyright Transfer |
| 30 | + |
| 31 | +VTT Technical Research Centre of Finland Ltd (VTT) is the sole Copyright Holder |
| 32 | +of *VTT properTune*, including all its parts and modules, e.g., allowing VTT to |
| 33 | +do further sublicensing of (parts of) *VTT properTune* to any party. To make |
| 34 | +this possible, VTT also needs to be the Copyright Holder of new contributions. |
| 35 | + |
| 36 | +Any party making a Contribution to *VTT properTune* also transfers the Copyright |
| 37 | +of the Contribution to VTT. Contributor(s) making a Contribution to *VTT |
| 38 | +properTune* thereby also makes a Transfer of Contribution Copyright. VTT has the |
| 39 | +right to accept or refuse the Contributions. |
| 40 | + |
| 41 | +**This program is provided under the terms of the GNU Affero General Public |
| 42 | +License (AGPL), version 3. Any use, reproduction, or distribution of this |
| 43 | +program constitutes recipient's acceptance of the GNU AGPL version 3.** |
| 44 | + |
| 45 | +"Transfer of Contribution Copyright" means that the Contributor(s) of a |
| 46 | +Contribution transfer the ownership and the copyright of the Contribution to |
| 47 | +VTT, the *VTT properTune* Copyright Holder, for inclusion in *VTT properTune*. |
| 48 | + |
| 49 | +To the best of its knowledge, the Contributor warrants that it/he/she has all |
| 50 | +necessary rights, ownership, and copyright to the Contribution and that the |
| 51 | +Contribution does not infringe any third-party intellectual property rights, |
| 52 | +such as patents, trademarks, or copyrights. |
| 53 | + |
| 54 | +In case the Contributor is an organisation, it confirms that for the purposes of |
| 55 | +this Agreement, it has received all necessary rights from its personnel involved |
| 56 | +on its behalf in making the Contribution. Such transfer may also be executed by |
| 57 | +having this Agreement signed both by the organisation and its personnel involved |
| 58 | +in making the Contribution. |
| 59 | + |
| 60 | +The transfer takes place upon the effective date when the Contribution is made |
| 61 | +available on the web site, by such Contributors themselves or anyone acting on |
| 62 | +behalf of such Contributors. The transfer is free of charge. |
0 commit comments