How to participate in OBIS

[behas]

OBIS (Open Blockchain Intelligence Standards) is a community effort developing open, vendor-neutral standards for blockchain intelligence. Documents are developed in the open, following a process modelled on the IETF and W3C and specified in OBIS-0001. Anyone may follow the work, comment on drafts, or contribute. No application or membership is required.

Where things happen

Channel	Use it for
Document review	Comments on a specific OBIS document. Every document has exactly one thread here, linked from the Discussion field in its status block. During Public Review that thread is the canonical venue for comments.
Proposals	Ideas for new work items before a Draft exists: a problem worth standardising, a format worth aligning on, prior work worth building on.
General	Anything else about the project.
Announcements	Documents entering Public Review, publications, and other project news from the editors.
Pull requests	Concrete text changes to a document, against the docs repository. A new document enters the lifecycle as a pull request titled Draft: OBIS-NNNN.
Issues	Errata, broken links, and site problems.
info@obistandards.org	General correspondence, and written commentary from institutions (see below).

How comments are handled

• Substantive comments received during a document's Public Review window (comments asserting a technical or normative defect) receive a public response from the editor before the document is published: accepted, declined with rationale, or deferred (OBIS-0001 §3.2).
• Comments on documents in Draft are welcome at any time and are taken into account as the draft evolves. Drafts may change without notice.
• Institutions whose internal processes do not accommodate public GitHub workflows may send written commentary on any Draft or Public Review document to info@obistandards.org with the subject line Commentary: OBIS-NNNN. The editor posts it to the document's review thread, where it receives the same public response as any other comment. On request, only the institutional affiliation is recorded, without naming the individual signatory.

Participation guidelines

• Stay on topic: one document per review thread, one idea per proposal thread.
• Argue from technical merit. Cite sources, prior work, or implementation experience where you can.
• Product and vendor promotion is out of scope. Implementation experience with a specific product is welcome where it informs the specification.
• Keep a professional tone. The editors may move off-topic posts, lock threads, or remove content that does not meet these guidelines.

Terms

Contributions to OBIS documents, whether by pull request, issue, or comment, are accepted under the project's licence and royalty-free patent policy (CC-BY 4.0).

Following the work

To be notified of new threads and announcements, watch the docs repository and choose Custom, then Discussions. Lifecycle transitions are also announced on obistandards.org.