Skip to content

owncloud/example-files

Repository files navigation

ownCloud Example Files

License ownCloud OSPO

A collection of example documents and photos used as the default user home skeleton in ownCloud. When a new user account is created, these files are copied into the user's home directory to provide a starting set of sample content including documents and photos.

Note: This repository is in maintenance/legacy mode and is no longer actively developed.

Getting Started

This repository contains static example files. To use them as a skeleton, place the contents in the ownCloud core/skeleton/ directory. No build step is required beyond make dist for packaging.

Documentation

Part of ownCloud Infrastructure

These example files are used by ownCloud Server as the skeleton directory for new user accounts.

Note: This repository is currently in Archived/Legacy mode. It is no longer actively maintained.

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

See LICENSE for license details.

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: Not detected. The OSPO will determine the current license status of this repository before planning any migration steps. If you know the intended license, please open an issue or contact ospo@kiteworks.com.

About

Some example files for the user home skeleton

Resources

Code of conduct

Contributing

Security policy

Stars

3 stars

Watchers

67 watching

Forks

Packages

 
 
 

Contributors