docs(ospo): community health rollout v2 — README, agents.md, health files

[dj4oC]

Summary

This PR is part of the Kiteworks OSPO community health rollout (kiteworks.com/opensource), applied to all ~110 public ownCloud repositories starting May 5, 2026.

• README.md: Rewritten with v2 OSPO template
  • License-specific OSPO section with Apache 2.0 migration guidance
  • Mandatory Community & Support section: GitHub Discussions, Matrix, docs, enterprise support, OSPO home
  • Contributing workflow: Rebase Early/Often, Dependabot, PGP/GPG-signed commits, DCO sign-off, GitHub Actions policy
  • Security section pointing to security.owncloud.com + YesWeHack bug bounty
  • Translations link to Transifex (owncloud project)
• agents.md (new): AI agent context file with architecture, build commands, OSPO policy constraints
• CODE_OF_CONDUCT.md (new): Redirect to https://owncloud.com/contribute/code-of-conduct/
• CONTRIBUTING.md (new): Redirect to https://owncloud.com/contribute/
• SECURITY.md (new): Redirect to https://security.owncloud.com + YesWeHack
• SUPPORT.md (new): Redirect to https://owncloud.com/contact-us/ and support channels

Test plan

• README renders correctly on GitHub (badges, sections, links)
• All health file links resolve (CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT)
• agents.md loads correctly in Claude Code and GitHub Copilot
• License referenced in README matches actual LICENSE file in repo

---

🤖 Generated with Claude Code as part of the ownCloud OSPO rollout.
Kiteworks OSPO: https://kiteworks.com/opensource

[CLAassistant]

All committers have signed the CLA.

[phil-davis]

Not a really important suggestion, but the webui test command was missed.
Otherwise this LGTM, so I am approving.

[dj4oC]

Hi @phil-davis — applied your suggestion, thanks for the approval! The make test-acceptance-webui command is now included in the build commands section.

[phil-davis]

LGTM now.
It is complaining that the commits are not signed.

[DeepDiver1975]

Code Review — docs(ospo): community health rollout v2 — README, agents.md, health files

Overview: OSPO-driven documentation update across ownCloud core — rewrites README, adds agents.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md, SUPPORT.md.

README.md

The rewrite is comprehensive and well-structured. A few observations:

Positive: The new README is substantially more useful — clear prerequisites, actual build command (make), organized sections for community, contributing, security, and translations. The OSPO/license-migration section is transparent about AGPL-3.0 status and migration prerequisites. ✅

Removed content: The original README's feature list and screenshot were removed in favor of a technical description. Acceptable trade-off for a server-side component repository.

Build badge regression: The original had a Drone CI build status badge. The new version replaces CI badges with License/OSPO/Docker badges. The build status badge is useful for contributors to quickly assess CI health — consider whether it should be re-added, though this is a judgment call.

"Rebase Early/Often" under Contributing workflow: The statement "All commits must be PGP/GPG signed" is accurate per the existing contribution requirements. ✅

agents.md

This is a useful addition for AI coding agents. The architecture key paths, build/test commands, and OSPO policy constraints are all accurate based on the repository structure. The constraint about not introducing copyleft dependencies is particularly important given the Apache 2.0 migration goal. ✅

Health files (CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT)

All four files are redirect stubs pointing to external URLs. This is the standard pattern for organizations centralizing these policies. ✅

SECURITY.md correctly instructs not to open public issues for vulnerabilities and points to security.owncloud.com + YesWeHack. ✅

Summary

Aspect	Assessment
README rewrite	✅ Comprehensive, accurate, well-organized
agents.md	✅ Useful context for AI tools, accurate architecture paths
Health files	✅ Standard redirect stubs
CI badge	⚠️ Build status badge removed — consider re-adding

Verdict: Ready to merge.

[phil-davis]

Note: the text still has a few mentions of “OC10” or “ownCloud 10". Those will become out-of-date. But I suppose that we can edit them when "OC11" is ready and either write "11" or write some words that describe this repo (the “classic” file-sync-and-share server?)