Contributing by reporting issues

• Always report bugs via Github: that is the most reliable way to contacts us since we do not follow any process to check the forum and social media.
• For questions about the Nextcloud Desktop Client, use the 📋 Forum and the 💬 Desktop public Talk chat room.
• Alternativately, we also have 🐣 Twitter and 🐘 Mastodon accounts.

Bug Reporting Guidelines

• Important: Complete the bug report form. If you fill it correctly, it should give us enough information to start working on the issue.
• SECURITY: Please do not report security vulnerabilities through public GitHub issues. If you have discovered a security matter with Nextcloud, please first read our responsible disclosure guidelines and our security policy. Then contact us at hackerone.com/nextcloud.
• This repository is only for issues within the Nextcloud desktop client. Issues in other components should be reported in their own repositores:
  • Nextcloud server
  • Android client
  • iOS client
• Search the existing issues first, it's likely that your issue was already reported.
• If your issue appears to be a bug and hasn't been reported, open a new issue. Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues.

Contributing to Source Code

Thanks for wanting to contribute source code to Nextcloud. That's great!

We ask that you follow our Code of Conduct.

Please read the Contribution Guide to get started and follow the Coding Style when writing new code.

AI-assisted contributions

Nextcloud allows contributions made with the help of AI tools. You are the author of everything you submit - AI assistance does not change that responsibility.

• Disclosure: Declare AI tool use in the PR description and add an Assisted-by: AGENT_NAME:MODEL_VERSION git trailer to each affected commit.

• Accountability: You must be able to explain, defend, and modify every line you submit. If a reviewer asks why something works a certain way, "the AI wrote it" is not an answer.

• Communication: PR descriptions, review comments, and issue reports must be written in your own words. This applies throughout the review process - passing reviewer feedback to an AI and posting whatever comes out is not acceptable.

• Quality: AI output must be quality assured by the human, i.e. reviewed, cleaned up, and tested before submission. New features must be tested on a live instance by you, not by an agent. Code that has never been executed, or that shifts debugging work onto maintainers, will not be accepted. s

• Licensing: Ensure AI-generated code contains no material incompatible with the license of the repository you are contributing to.

For the full policy including autonomous agent rules, security reports, and beginner issues, read the AI Contribution Policy.

Sign your work

We use the Developer Certificate of Origin (DCO) as an additional safeguard for the Nextcloud project. This is a well established and widely used mechanism to assure contributors have confirmed their right to license their contribution under the project's license. Please read contribute/developer-certificate-of-origin. If you can certify it, then just add a line to every git commit message:

Signed-off-by: Random J Developer <[email protected]>

If you set your user.name and user.email git configs, you can sign your commit automatically with git commit -s. You can also use git aliases like git config --global alias.ci 'commit -s'. Now you can commit with git ci and the commit will be signed.

Apply a license

In case you are not sure how to add or update the license header correctly please have a look at contribute/HowToApplyALicense.md.

Translations

Please submit translations via Transifex.