OpenWOP openwop.dev

Community

Developed in the open.

OpenWOP is developed in the open on github.com/openwop/openwop. This page lists every place a question, design conversation, or bug report can land — and the cadence each channel runs on.

GitHub DiscussionsRead the governance

Channels

Where to report what

Spec ambiguity
GitHub issue against openwop/openwop, label spec.
Conformance scenario failure
GitHub issue, label conformance, attach the run log.
Schema break
GitHub issue, label schema, attach the diff.
Security vulnerability
Private advisory only (never the public tracker). See SECURITY.md.

The details

The code of conduct, RFC comment windows, office hours, and how to list your implementation.

Channels

ChannelUse it forCadence
GitHub DiscussionsDesign questions, RFC comments, "is this the right way?" threadsAcknowledged within 5 business days per MAINTAINERS.md
GitHub IssuesBug reports, conformance failures, spec ambiguityAcknowledged within 5 business days
YouTubeShort narrated films about OpenWOP, each with captions; the full list is on VideosA new film with each major feature
Security advisoriesCoordinated vulnerability disclosureAcknowledged within 3 business days per SECURITY.md
Real-time chat—Planned. Subscribe to GitHub Discussions for now; the channel choice (Discord / Matrix / Zulip) is tracked in ROADMAP.md.

Why no chat yet? A real-time channel announces "we're here" without proving "we're a standard." Until the working-group charter (RFC 0038) ratifies and at least one non-steward maintainer joins, GitHub Discussions is the canonical async channel — Discord would currently signal a product, not a protocol.

Code of conduct

Every channel above runs under CODE_OF_CONDUCT.md. Enforcement and removal-for-cause processes live in MAINTAINERS.md §"Removal for cause."

RFC comment windows

When a new RFC opens (status Draft) it carries a comment window declared in the RFC body — 7, 30, or 90 days depending on classification (normative addition, breaking change, safety-fix break) per GOVERNANCE.md §"Spec change process." A waived window is recorded in MAINTAINERS.md §"Bootstrap-phase RFC waivers." Subscribe to the RFCs index to see windows open and close.

Office hours

Not yet scheduled. The maintainer set is too small to run a recurring slot honestly. When the working-group charter ratifies, the first scheduled action is a public office-hours cadence — that change lands here and in CHANGELOG.md § Governance.

Reporting

  • Spec ambiguity → GitHub issue against openwop/openwop, label spec.
  • Conformance scenario failure → GitHub issue, label conformance, attach the run log.
  • Schema break → GitHub issue, label schema, attach the diff.
  • Security vulnerability → private advisory only (never the public tracker). See SECURITY.md.

Adopting OpenWOP

If you're shipping an OpenWOP-compatible host or workflow, open a PR adding a row to INTEROP-MATRIX.md. The roadmap tracks independent implementations.

How the project runs.