docs(ospo): community health rollout v2 — README, agents.md, health files#1344
Open
dj4oC wants to merge 1 commit into
Open
docs(ospo): community health rollout v2 — README, agents.md, health files#1344dj4oC wants to merge 1 commit into
dj4oC wants to merge 1 commit into
Conversation
Introduced by the Kiteworks Open Source Program Office (OSPO) on May 5, 2026. Changes: - README.md: rewritten with OSPO v2 template — license-specific Apache 2.0 migration guidance, Community & Support section with mandatory links (GitHub Discussions, Matrix, docs, enterprise support), Contributing workflow (Rebase Early/Often, Dependabot, PGP-signed commits, DCO, GitHub Actions policy), Security pointing to security.owncloud.com + YesWeHack bug bounty - agents.md: added OSPO Policy Constraints (GitHub Actions, Dependabot, Git Workflow) for AI coding agents - 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>
| ### GitHub Actions | ||
| - **Only** use actions owned by `owncloud`, created by GitHub (`actions/*`), or verified on the GitHub Marketplace. | ||
| - Pin all actions to their full commit SHA (not tags): `uses: actions/checkout@<SHA> # vX.Y.Z` | ||
| - Never introduce actions from unverified third parties. |
Member
There was a problem hiding this comment.
it is possible to use "unverified" actions - in fact many good/useful actions are not verified. In this case org admins need to be informed to whitelist them- process to be defined ....
Author
There was a problem hiding this comment.
I will adjust to:
"- Only use actions: owned by owncloud, created by GitHub (actions/*), or verified on the GitHub Marketplace, or verified by the ownCloud Maintainers."
|
|
||
| ### Git Workflow | ||
| - **Rebase policy**: Always rebase; never create merge commits. Use `git pull --rebase` and `git rebase` before pushing. | ||
| - **Signed commits**: All commits **must** be PGP/GPG signed (`git commit -S -s`). |
Author
There was a problem hiding this comment.
intentionally:
-S == --gpg-sign[=]
-s == --signoff
or do I missunderstand something?
| - **Rebase policy**: Always rebase; never create merge commits. Use `git pull --rebase` and `git rebase` before pushing. | ||
| - **Signed commits**: All commits **must** be PGP/GPG signed (`git commit -S -s`). | ||
| - **DCO sign-off**: Every commit needs a `Signed-off-by` line (`git commit -s`). | ||
| - **Conventional Commits**: Use the [Conventional Commits](https://www.conventionalcommits.org/) format where the repository enforces it. |
Member
There was a problem hiding this comment.
many repos use squash merge where the PR title is going to be the final commit message on the default branch. conventional messages shall be used in pr titles as well - we have a reusable workflow for this ....
Author
There was a problem hiding this comment.
So:
- Conventional Commits & Squash Merge: Use the Conventional Commits format where the repository enforces it or Squash Merge where a clean linear history may over preserving individual commit noise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
Test plan
🤖 Generated with Claude Code as part of the ownCloud OSPO rollout.
Kiteworks OSPO: https://kiteworks.com/opensource