If you would like to contribute, there are several different possibilities.
You can make the fastest contribution with the translation. If you find an error in one of the translations of the software, you can make a change on Transifex, which we will check and if necessary take over.
If you have programming skills or want to help with the programming work, you can also use the Github-Workflow to place a pull request on the platform. We will then look at your changes and accept them if they meet the following criteria. You can also find ideas and help on Github in the Issues.
Changes to Microservice components
To apply the changes to a running instance, the corresponding charts in the Helm-Repo must be updated. This requires a new chart for each component. In addition, the corresponding All- or Dev-Chart must be edited when changes are made, so that they also set up the correct container. The corresponding tag for such a container is taken from the Pipeline Number in Gitlab. These tags serve as identifiers for the containers created from the pipeline in the Gitlab Registry. Once a chart is updated, the Chart version should always be incremented to communicate the changes to the appropriate tools. A github pipeline in Helm-Repo will make the changes available online when a [git push] is performed.
If a new microservice has been added, the proxy must be adjusted in the installation help repo (in the configuration.yaml). If this does not happen, the requests will be forwarded to the wrong DNS server and will not be processed in the RDS system. The changes to proxies made by [kubectl -f configuration.yaml] must be applied by deleting and restarting the deployments, otherwise they will not be applied to the pods.
Changes to the documentation
Currently, documentation changes are only applied by the Gitlab pipeline when changes are made to microservice components. This will be improved in the future.
Changes to the integrations
|Currently only the integration into ownCloud via a plugin exists.|
To include changes to the ownCloud app in the ownCloud marketplace, these changes must first be displayed as a Pull Request. If these changes are to be included in the main thread of the git repo, the version number in the info.xml must now be raised and the signature.json regenerated. The signature is automatically built and offered in the github pipeline. The resulting [tar.gz] file must be uploaded to the Marketplace afterwards. Now the change is available for each instance and can be updated using ownCloud’s own processes.
Translated with www.DeepL.com/Translator (free version)