Skip to content
This repository was archived by the owner on Jul 8, 2026. It is now read-only.

owncloud/litmus-testing

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

26 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

⚠️ This repository is archived and no longer maintained. It is read-only and will not receive further updates or contributions.

Litmus Testing

License ownCloud OSPO

CI configuration for running the Litmus WebDAV compliance test suite on a nightly schedule against multiple ownCloud server builds. Litmus verifies correct implementation of WebDAV protocol operations, helping catch regressions in ownCloud's file access layer before they reach production.

Getting Started

This repository primarily contains CI pipeline configuration (Drone). The Litmus test suite runs automatically against ownCloud tarballs on a nightly schedule.

Running Locally

To report issues or suggest improvements, open an issue.

Documentation

Part of ownCloud Infrastructure

Litmus Testing is an automated quality gate in the ownCloud CI pipeline, validating WebDAV compliance across server releases.

Community & Support

Star this repo and Watch for release notifications!

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 MIT.

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.

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: MIT (Category A per Apache policy -- permissive, compatible with Apache-2.0).

Migration prerequisites for this repository:

  • CLA/DCO coverage: All past contributors must have signed agreements permitting relicensing
  • Header updates: All source file headers must be updated from MIT to Apache-2.0 notice
  • Dependency audit: Verify no incompatible transitive dependencies

About

Litmus testing running on DroneCI

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

9 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors