Skip to content

Commit a106e54

Browse files
committed
docs(ospo): community health rollout v2 — README, agents.md, health files
Introduced by the Kiteworks Open Source Program Office (OSPO) on May 5, 2026. Changes: - README.md: rewritten with OSPO v2 template — license-specific migration guidance, Community & Support section, Contributing workflow, Security section pointing to security.owncloud.com + YesWeHack bug bounty - agents.md: AI agent context file with architecture, build commands, and OSPO Policy Constraints (GitHub Actions, Dependabot, Git Workflow) - CODE_OF_CONDUCT.md: redirect to https://owncloud.com/contribute/code-of-conduct/ - CONTRIBUTING.md: redirect to https://owncloud.com/contribute/ - SECURITY.md: redirect to https://security.owncloud.com + YesWeHack - SUPPORT.md: redirect to https://owncloud.com/contact-us/ + channels OSPO: https://kiteworks.com/opensource Signed-off-by: David Walter <david.walter@kiteworks.com>
1 parent 8bc02bd commit a106e54

6 files changed

Lines changed: 175 additions & 58 deletions

File tree

CODE_OF_CONDUCT.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# Code of Conduct
2+
3+
This project follows the ownCloud Code of Conduct.
4+
5+
Please read the full Code of Conduct at:
6+
**<https://owncloud.com/contribute/code-of-conduct/>**
7+
8+
By participating in this project, you agree to abide by its terms.

CONTRIBUTING.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Contributing
2+
3+
Thank you for your interest in contributing to this project!
4+
5+
Please read the full contributing guidelines at:
6+
**<https://owncloud.com/contribute/>**
7+
8+
For development setup, coding standards, and pull request process,
9+
see the README in this repository.

README.md

Lines changed: 67 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -1,93 +1,102 @@
11
# ownCloud Documentation
22

3-
**IMPORTANT**
3+
<!-- OSPO-managed README | Generated: 2026-04-16 | v2 -->
44

5-
Since April 2026, this repository requires [Commit Signing](https://docs.github.com/articles/about-gpg) and uses [Conventional Commits](https://www.conventionalcommits.org) for commits and the Pull Request title.
5+
[![License](https://img.shields.io/badge/License-AGPL--3.0-blue.svg)](LICENSE) [![ownCloud OSPO](https://img.shields.io/badge/OSPO-ownCloud-blue)](https://kiteworks.com/opensource)
66

7-
**Overview**
7+
The central Antora-based documentation site for all ownCloud products. This repository contains the site playbook (`site.yml`), Antora and AsciiDoc extensions, shared resources, fonts, and build scripts that aggregate content from all `docs-*` component repositories into a single published documentation site at [doc.owncloud.com](https://doc.owncloud.com).
88

9-
1. The platform and tools used to build the documentation is [Antora](./docs/what-is-antora.md).
10-
2. The file format that the documentation is written in is [AsciiDoc](./docs/what-is-asciidoc.md).
11-
3. The <abbr title="User Interface">UI</abbr> & <abbr title="User Experience">UX</abbr> of the documentation can be found at [docs-ui](https://github.com/owncloud/docs-ui)
9+
## Getting Started
1210

13-
**Table of Contents**
11+
Install dependencies and build the documentation locally:
1412

15-
* [Antora Site Structure for Docs](#antora-site-structure-for-docs)
16-
* [Extensions](#extensions)
17-
* [Documentation Guidelines](#documentation-guidelines)
18-
* [Contributing to the Documentation](#contributing-to-the-documentation)
19-
* [Generating the Documentation](#generating-the-documentation)
20-
* [Common Content and Styling the Documentation](#common-content-and-styling-the-documentation)
21-
* [Best Practices and Tips](#best-practices-and-tips)
22-
* [Target Branch and Backporting](#target-branch-and-backporting)
23-
* [When Does a Change Get Published to the Docs Web Site?](#when-does-a-change-get-published-to-the-docs-web-site)
24-
* [Create a New Version Branch for Docs](#create-a-new-version-branch-for-docs)
25-
* [HTML to PDF](#html-to-pdf)
13+
```bash
14+
npm install
15+
npm run antora-local
16+
npm run serve
17+
```
2618

27-
## Antora Site Structure for Docs
19+
This builds the site to `public/` and serves it at `http://localhost:8080`.
2820

29-
Refer to the [Antora Site Structure for Docs](./docs/antora-site-structure.md) for more information.
21+
## Documentation
3022

31-
## Extensions
23+
- [What is Antora](./docs/what-is-antora.md)
24+
- [What is AsciiDoc](./docs/what-is-asciidoc.md)
25+
- [Documentation Guidelines](./docs/doc-guidelines.md)
26+
- [Antora Site Structure](./docs/antora-site-structure.md)
27+
- [Extensions](./docs/extensions.md)
3228

33-
The documentation intensively uses Antora/Asciidoc extensions. These extensions enrich the base functionality with additional and required capabilities. Read the [extensions](./docs/extensions.md) documentation for more information.
29+
## Part of ownCloud Documentation
3430

35-
## Documentation Guidelines
31+
This is the top-level documentation build repository. It pulls content from component repositories such as [docs-server](https://github.com/owncloud/docs-server), [docs-ocis](https://github.com/owncloud/docs-ocis), [docs-client-desktop](https://github.com/owncloud/docs-client-desktop), and others. The published site is available at [doc.owncloud.com](https://doc.owncloud.com).
3632

37-
Refer to the [Documentation Guidelines](./docs/doc-guidelines.md) for more information about backgrounds and processes.
33+
## Community & Support
3834

39-
## Contributing to the Documentation
35+
**[Star](https://github.com/owncloud/docs)** this repo and **Watch** for release notifications!
4036

41-
To get started contributing to the documentation, please refer to the [Getting Started Guide](./docs/getting-started.md).
37+
- [ownCloud Website](https://owncloud.com)
38+
- [Community Discussions](https://github.com/orgs/owncloud/discussions)
39+
- [Matrix Chat](https://app.element.io/#/room/#owncloud:matrix.org)
40+
- [Documentation](https://doc.owncloud.com)
41+
- [Enterprise Support](https://owncloud.com/contact-us/)
42+
- [OSPO Home](https://kiteworks.com/opensource)
4243

43-
With regard to language and style issues, consult the [Style Guide](./docs/style-guide.md).
44+
## Contributing
4445

45-
Note that the documentation provides a setting for the [IntelliJ AsciiDoc-Antora Plugin](https://intellij-asciidoc-plugin.ahus1.de) to preview a page using the css sourced from `doc.owncloud.com`. The file required containing the necessary configuration is `.asciidoctorconfig`.
46+
We welcome contributions! Please read the [Contributing Guidelines](CONTRIBUTING.md)
47+
and our [Code of Conduct](CODE_OF_CONDUCT.md) before getting started.
4648

47-
## Generating the Documentation
49+
### Workflow
4850

49-
**IMPORTANT**
50-
We use `node 22 LTS`. In case you used a lower node version for your local doc repos, you must upgrade them **all**. See the link below for details.
51+
- **Rebase Early, Rebase Often!** We use a rebase workflow. Always rebase on the target branch before submitting a PR.
52+
- **Dependabot**: Automated dependency updates are managed via Dependabot. Review and merge dependency PRs promptly.
53+
- **Signed Commits**: All commits **must** be PGP/GPG signed. See [GitHub's signing guide](https://docs.github.com/en/authentication/managing-commit-signature-verification).
54+
- **DCO Sign-off**: Every commit must carry a `Signed-off-by` line:
55+
```
56+
git commit -s -S -m "your commit message"
57+
```
58+
- **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.
5159

52-
**IMPORTANT**
53-
We use `Antora 3.1.14` and npm instead of yarn. In case you used a lower Antora version for your local doc repos, you must upgrade them **all** by syncing them and running `npm install` in each doc repo.
60+
## Security
5461

55-
To generate and view the documentation locally or planning major changes, refer to the [Building the Documentation guide](./docs/build-the-docs.md).
62+
**Do not open a public GitHub issue for security vulnerabilities.**
5663

57-
## Common Content and Styling the Documentation
64+
Report vulnerabilities at **<https://security.owncloud.com>** -- see [SECURITY.md](SECURITY.md).
5865

59-
If you want to suggest an improvement to the ownCloud documentation theme, such as the layout, the header or the footer text, or if you find a bug, all the information that you need is in the `docs-ui` repository. Changes made in `docs-ui` are valid for the whole documentation.
66+
Bug bounty: [YesWeHack ownCloud Program](https://yeswehack.com/programs/owncloud-bug-bounty-program)
6067

61-
Please read how to test un-merged [docs-ui](./docs/test-ui-bundle.md) changes with content from the ownCloud documentation.
68+
## License
6269

63-
## Best Practices and Tips
70+
This project is licensed under the [AGPL-3.0](LICENSE).
6471

65-
Refer to [Best Practices and Tips for writing in AsciiDoc](./docs/best-practices.md) for more information.
72+
## About the ownCloud OSPO
6673

67-
To check for broken links manually, see [install and use a broken-link-checker](./docs/checking-broken-links.md).
74+
The [Kiteworks Open Source Program Office](https://kiteworks.com/opensource), operating under
75+
the [ownCloud](https://owncloud.com) brand, launched on May 5, 2026, to steward the open source
76+
ecosystem around ownCloud's products. The OSPO ensures transparent governance, license compliance,
77+
community health, and sustainable collaboration between the open source community and
78+
[Kiteworks](https://www.kiteworks.com), which acquired ownCloud in 2023.
6879

69-
## Target Branch and Backporting
80+
- **OSPO Home**: <https://kiteworks.com/opensource>
81+
- **GitHub**: <https://github.com/owncloud>
82+
- **ownCloud**: <https://owncloud.com>
7083

71-
Please always do your changes in `master` and backport them to the relevant branches.
72-
The **ONLY** reason for doing a PR in a branch directly is, to fix an issue which is
73-
_only_ present in that particular branch! When creating a PR and it is necessary to backport,
74-
document in the PR to which branches a backport is needed.
84+
For questions about the OSPO or licensing, contact ospo@kiteworks.com.
7585

76-
When backporting, consider using the [backport script](./docs/getting-started.md#backporting)
77-
which eases life a lot and speeds up the process. It is also very beneficial when using the
78-
extended code provided, because a clear naming structure of the backport PR is generated automatically.
86+
### License Migration to Apache 2.0
7987

80-
## When Does a Change Get Published to the Docs Web Site?
88+
The OSPO is driving a strategic relicensing of ownCloud repositories toward the
89+
[Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0), following
90+
the [Apache Software Foundation's third-party license policy](https://www.apache.org/legal/resolved.html).
8191

82-
Changes made will get published to the web under the following conditions:
92+
Individual repositories will migrate as their audit is completed. The LICENSE file
93+
in each repo reflects its **current** license status (not the target).
8394

84-
1. A merge in a component to one of the defined version branches triggers as a last step a master branch build.
85-
2. A merge to master triggers a site build which then pushes all versions defined in site.yml.
95+
**Current license: AGPL-3.0** (Category X per Apache policy -- cannot be included in Apache-2.0 works).
8696

87-
## Create a New Version Branch for Docs
97+
Migration prerequisites for this repository:
8898

89-
Please refer to [Create a New Version Branch for Docs](./docs/new-version-branch.md) for more information.
90-
91-
## HTML to PDF
92-
93-
At the moment, creating a pdf is dropped from the build process but can be re-implemented if required.
99+
- **CLA/DCO coverage**: All past contributors must have signed agreements permitting relicensing
100+
- **Copyleft dependency audit**: All AGPL/GPL dependencies must be replaced or isolated
101+
- **KDE heritage review**: Any code with KDE-era copyrights requires legal analysis
102+
- **Complete relicensing**: AGPL-3.0 is a strong copyleft license; migration requires full relicensing of all files, not just a header change

SECURITY.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Security Policy
2+
3+
## Reporting a Vulnerability
4+
5+
**Do NOT open a public GitHub issue for security vulnerabilities.**
6+
7+
Please report security issues responsibly via:
8+
**<https://security.owncloud.com>**
9+
10+
You can also report vulnerabilities through our YesWeHack bug bounty program:
11+
**<https://yeswehack.com/programs/owncloud-bug-bounty-program>**

SUPPORT.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
# Support
2+
3+
For support with this project, please use the following channels:
4+
5+
- **Enterprise Support**: <https://owncloud.com/contact-us/>
6+
- **Community discussions**: https://github.com/orgs/owncloud/discussions
7+
- **Matrix Chat**: <https://app.element.io/#/room/#owncloud:matrix.org>
8+
- **Documentation**: <https://doc.owncloud.com>
9+
10+
Please do not use GitHub issues for general support questions.

agents.md

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# AI Agent Guidelines for ownCloud Documentation
2+
3+
This file provides context for AI coding agents (Claude Code, GitHub Copilot, Cursor, etc.) working in this repository.
4+
5+
## Repository Overview
6+
- **Product family:** Documentation
7+
- **Primary language(s):** JavaScript
8+
- **Build system:** npm (Antora)
9+
- **Test framework:** broken-link-checker
10+
- **CI system:** GitHub Actions
11+
12+
## Architecture & Key Paths
13+
14+
- `site.yml` -- Antora playbook defining all content sources
15+
- `package.json` -- npm scripts for building and serving
16+
- `ext-antora/` -- Custom Antora extensions
17+
- `ext-asciidoc/` -- Custom AsciiDoc extensions
18+
- `docs/` -- Documentation about the docs build system itself
19+
- `resources/` -- Shared resources
20+
- `fonts/` -- Custom fonts
21+
- `supplemental/` -- Supplemental UI files
22+
- `book_templates/` -- PDF book templates
23+
24+
## Development Conventions
25+
- **Branching:** master
26+
- **Commit messages:** DCO sign-off required (`git commit -s`)
27+
- **Code style:** Prettier (`.prettierrc` or similar config present)
28+
- **PR process:** Open a PR against `master`. All CI checks must pass.
29+
30+
## Build & Test Commands
31+
```bash
32+
# Build
33+
npm run antora
34+
35+
# Test
36+
npm run linkcheck
37+
38+
# Lint
39+
Not detected (Prettier config present for formatting)
40+
```
41+
42+
## Important Constraints
43+
- All code contributions must be compatible with the **AGPL-3.0** license
44+
- Do not introduce new **copyleft-licensed dependencies** (GPL, AGPL, LGPL, MPL) without explicit discussion in an issue first. This is especially important for repos migrating to Apache 2.0.
45+
- Do not introduce new dependencies without discussion in an issue first
46+
47+
48+
## OSPO Policy Constraints
49+
50+
### GitHub Actions
51+
- **Only** use actions owned by `owncloud`, created by GitHub (`actions/*`), verified on the GitHub Marketplace, or verified by the ownCloud Maintainers.
52+
- Pin all actions to their full commit SHA (not tags): `uses: actions/checkout@<SHA> # vX.Y.Z`
53+
- Never introduce actions from unverified third parties.
54+
55+
### Dependency Management
56+
- Dependabot is configured for automated dependency updates.
57+
- Review and merge Dependabot PRs as part of regular maintenance.
58+
- Do not introduce new dependencies without discussion in an issue first.
59+
60+
### Git Workflow
61+
- **Rebase policy**: Always rebase; never create merge commits. Use `git pull --rebase` and `git rebase` before pushing.
62+
- **Signed commits**: All commits **must** be PGP/GPG signed (`git commit -S -s`).
63+
- **DCO sign-off**: Every commit needs a `Signed-off-by` line (`git commit -s`).
64+
- **Conventional Commits & Squash Merge**: Use the [Conventional Commits](https://www.conventionalcommits.org/) format where the repository enforces it. Many repos use squash merge, where the PR title becomes the commit message on the default branch — apply Conventional Commits format to PR titles as well. A reusable GitHub Actions workflow enforces this.
65+
66+
## Context for AI Agents
67+
- Match existing code style
68+
- Do not refactor unrelated code in the same PR
69+
- Write tests for new functionality
70+
- Keep PRs focused and atomic

0 commit comments

Comments
 (0)