Contributions Guidelines

Pydio is an open source software, and the code is published under the AGPL License. As such, the code is publicly available on GitHub, and forking is particularly recommanded! Still, contribution must be done following some guidelines.

Contributor License Agreement


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 this form.

Coding guidelines

Please read before contributing

Pydio currently does not impose some PSR norm for the PHP coding. Still, every contribution will be reviewed very carefully, and we want to draw your attention on the following

  • If you are fixing a simple bug, through some kind of one-line commit, please test the changes you made in many contexts. With modularity, comes the variety of situation in which Pydio can be deployed, and as such, having a working patch for a given set of plugins do not necessarily means it will be working well when switching to other plugins. E.g. switching between DB-based & Serial-based configs storage, testing with various workspaces access drivers, etc...
  • If you want to provide a brand new feature, the very first step will be to understand the plugin architecture, and the events that are triggered to "communicate" between them. That way, for most feature, you should be able to provide a unique self-containing plugin with all necessary data. When accepted, plugins will first be published as "contributed" plugins, from the website and not directly available in the core package. If the feature is successful, plugins may integrate the core at one point.
  • Take me to the developer guide!

GH organization & Pull Requests

The code is located at From here, you can fork to write your own plugins or provide bug fixes. The pydio-core project is organized to use the develop branch by default. Make sure to fork and submit PR on this branch only. Once you are happy with your code, please use the now standard Github "Pull Request" mechanism to submit your changes. If you are not familiar with git, reading is a good start.

Pydio versions numbering

The version numbering is fairly simple. Based on the Major.Branch.Minor, all even branches are considered stable (2.2, 2.4, 3.0.1, 3.0.2, etc.) and all odd branches are considered development branches.