ocf-managed-container/packaging/PROVENANCE.md

Licensing and provenance status

License selection is pending. No MIT, Apache, or GPL license has been granted for this project by this document. LicenseRef-Provenance-Pending in the draft RPM spec is a local status marker, not an assertion of an approved license. Builds are development artifacts; this workflow does not publish releases or upload to an RPM registry.

The original development conversation is: https://chatgpt.com/share/6aa4e495-3e6c-83e9-a13c-fc65a972146b

The relevant discussion references the OCF developer guide and ClusterLabs' heartbeat/podman, heartbeat/docker, heartbeat/anything, and heartbeat/pgsql agents. One early proposal describes Podman as a model/base; other passages discuss combining concepts from the container and PostgreSQL agents. These establish influence, not proof of copied implementation.

On 2026-09-12 a preliminary comparison of the frozen reference against the current upstream main versions of those four agents found only short exact runs after trimming whitespace and omitting blank lines (maximum 3–4 lines). The inspected matches were ordinary XML and shell control-flow fragments. This is not a historical-version audit and does not exclude adapted code.

Source references:

• https://github.com/ClusterLabs/resource-agents/blob/main/doc/dev-guides/ra-dev-guide.asc
• https://github.com/ClusterLabs/resource-agents/blob/main/heartbeat/podman
• https://github.com/ClusterLabs/resource-agents/blob/main/heartbeat/docker
• https://github.com/ClusterLabs/resource-agents/blob/main/heartbeat/anything
• https://github.com/ClusterLabs/resource-agents/blob/main/heartbeat/pgsql

The inspected podman, docker and anything headers specify GPL version 2. The inspected pgsql header says GPL without a version. The developer guide explains that LGPL-licensed ocf-shellfuncs can be used by non-GPL agents. The RPM depends on the system OCF library and does not bundle that library.

Before a licensed release, resolve the provenance of any adapted material, retain required notices, select an appropriate license for project-owned contributions, add the actual license text, and replace the draft RPM marker. The private development conversation itself is not bundled in source archives.