ownCloud QA

This repository contains public test plans for ownCloud components and apps. It provides structured QA workflows, test plan templates, and validation procedures for the ownCloud Server, Desktop Client, Mobile apps, and integrations. Test plans are organized by product area and follow a defined lifecycle from issue creation through validation and release.

Part of Infrastructure / Tooling

This repository supports quality assurance across all ownCloud products. It provides test plans used to verify features and bug fixes in ownCloud Server (Classic), ownCloud Infinite Scale (oCIS), the Desktop Client, the Android app, and the iOS app.

Getting Started

Browse the test plans by product area:

• Server/ - Server-side test plans
• Desktop/ - Desktop client test plans
• Mobile/ - Mobile app test plans
• Integrations/ - Integration test plans
• tools/ - QA tooling and utilities

QA Issue Workflow

1. Create a new QA issue with labels for the target platform and milestone
2. Create a test plan template branch and submit a QA PR
3. After PR review and merge, validate the feature using the test plan
4. Close the QA issue after successful validation

Documentation

• Test plans in this repository
• ownCloud documentation

Community & Support

Star this repo and Watch for release notifications!

• ownCloud Website
• Community Discussions
• Matrix Chat
• Documentation
• Enterprise Support
• OSPO Home

Contributing

We welcome contributions! Please read the Contributing Guidelines and our Code of Conduct before getting started.

Workflow

• Rebase Early, Rebase Often! We use a rebase workflow. Always rebase on the target branch before submitting a PR.
• Dependabot: Automated dependency updates are managed via Dependabot. Review and merge dependency PRs promptly.
• Signed Commits: All commits must be PGP/GPG signed. See GitHub's signing guide.
• DCO Sign-off: Every commit must carry a Signed-off-by line:

  git commit -s -S -m "your commit message"
  

• GitHub Actions Policy: Workflows may only use actions that are (a) owned by owncloud, (b) created by GitHub (actions/*), or (c) verified in the GitHub Marketplace.

Security

Do not open a public GitHub issue for security vulnerabilities.

Report vulnerabilities at https://security.owncloud.com -- see SECURITY.md.

Bug bounty: YesWeHack ownCloud Program

License

This project is licensed under the AGPL-3.0.

About the ownCloud OSPO

The Kiteworks Open Source Program Office, operating under the ownCloud brand, launched on May 5, 2026, to steward the open source ecosystem around ownCloud's products. The OSPO ensures transparent governance, license compliance, community health, and sustainable collaboration between the open source community and Kiteworks, which acquired ownCloud in 2023.

• OSPO Home: https://kiteworks.com/opensource
• GitHub: https://github.com/owncloud
• ownCloud: https://owncloud.com

For questions about the OSPO or licensing, contact ospo@kiteworks.com.

License Migration to Apache 2.0

The OSPO is driving a strategic relicensing of ownCloud repositories toward the Apache License 2.0, following the Apache Software Foundation's third-party license policy.

Individual repositories will migrate as their audit is completed. The LICENSE file in each repo reflects its current license status (not the target).

Current license: AGPL-3.0 (Category X per Apache policy -- cannot be included in Apache-2.0 works).

Migration prerequisites for this repository:

• CLA/DCO coverage: All past contributors must have signed agreements permitting relicensing
• Copyleft dependency audit: All AGPL/GPL dependencies must be replaced or isolated
• KDE heritage review: Any code with KDE-era copyrights requires legal analysis
• Complete relicensing: AGPL-3.0 is a strong copyleft license; migration requires full relicensing of all files, not just a header change