How to contribute¶
There are various ways to contribute to CryptPad, many of which do not require any coding skills. If you would like to discuss anything listed here, or other ways of contributing, please get in touch with the development team.
Spread the word¶
The simplest way to help CryptPad is to make the project known. As an Open Source project, CryptPad has very little budget to spare for marketing. We rely on the community to promote the service, for example by:
Using CryptPad and demonstrating it to friends and colleagues, highlighting why privacy is important.
Posting about CryptPad on social media.
Relaying the CryptPad Crowdfunding.
Presenting CryptPad in conferences or meetups, or inviting the team to present.
If you encounter a problem with CryptPad, reporting it helps improve the service for everyone. When reporting, please provide as much information as possible about the conditions in which the problem occurred, what you expected to happen, and what happened instead. These details help the team reproduce the error, which is the first step towards fixing it.
There are two ways to report bugs or issues:
The CryptPad team translates the software in English and French, with many more languages provided by the community. Translating CryptPad—and/or keeping translations up to date as the platform develops—is a much needed effort to make it available to as many people as possible.
To translate CryptPad itself please see the Translation guide.
Contribute to the code¶
Fixing a bug from the issue tracker.
Adding a new feature.
Building a new application or integrating an existing one to CryptPad's encrypted real-time collaboration.
Contribute to making CryptPad financially sustainable:
One-time or recurring donations on Open Collective.
Subscriptions to cryptpad.fr.
For larger organisations, contact the team if you would like to sponsor a feature or to discuss support contracts for an on-site instance.
Note to instance owners: cryptpad.fr used to offer a revenue sharing system for subscriptions on self-hosted instances. We have discontinued this possibility at this time. However if you are an instance owner and are interested in such a system we would still be interested to hear from you. In the future we might be interested to restore such a revenue sharing model with large instance owners.