Contribution Guidelines
Found a Security Issue?
We do take security very seriously, and vulnerabilities are publicly disclosed after a fixing version was released.
If you find a vulnerability in the code, please do not post an issue directly in Github or in the forum, but directly send an email to security (at) pydio.com.
Scope of disclosure: if you would like to limit further dissemination of the information in the report, please say so in it. Otherwise the Pydio team may share information with other vendors if we find they may be affected by the same vulnerability. The Pydio Team will handle the information you provide responsibly.
Getting feedback: We cannot guarantee a prompt human response to every security bug filed. Still, it will probably a matter of hours before you get an answer. If you don’t, please try contacting us by other means to check that the message was correctly received and acknowledged.
Github Pull Requests
To protect both your code and the community, every contributor must first sign the Contributor License Agreement first.
Our code is located at https://github.com/pydio/cells. From here, you can fork to write your own services or provide bug fixes. The project is organized to use the main branch by default. Make sure to fork and submit PR on this branch only.
Once you are happy with your code, please use the standard Github "Pull Request" mechanism to submit your changes. If you are not familiar with git, reading https://help.github.com/articles/using-pull-requests is a good start.
Add or Proofread Translations (i18n)
Cells strings are open to the community contributions via CrowdIn, an online crowd-sourced translation tool: visit https://crowdin.com/project/pydio-cells and create an account if you want to contribute. Make sure to first sign the Contributor License Agreement first.
You are more than welcome to contribute to translations. To make sure languages are correctly supported, we only opened a set of languages, help us reaching 100% coverage! If you wish to add a new language, please contact us so that we can enable this both in the code and on the translation platform.
Contributor License Agreement (CLA)
The CLA is an agreement commonly used in major open source project, which aims at protecting all parties implied by a contribution : the contributor, the main code author, and above all, the community. The CLA model we have chosen basically tells the following : the contribution's copyright is shared between the contributor and the main author. This means each party can do whatever she want in term of relicensing with this contributed piece of code. This is important, because, if in the future, the author wants to change the license in something more in favor of the community, a singular contributor cannot block the process. To ease the process, the CLA is directly signable online using the form below.