Skip to content

Blog post + docs: CIEL governance structure — public, transparent, community participation #2769

Description

@paynejd

Summary

WHO feedback (received ~2 months ago, see #2768) cited CIEL's governance process — alongside its QA history — as a reason they have not adopted CIEL and will not recommend it to others. #2768 scopes the QA-only response; this ticket is the governance companion, deliberately separate and sequenced later (P3, vs. #2768's P2).

Goal

Establish and publish CIEL's governance structure: who decides what, how community input is incorporated, and how that aligns with CIEL's status as a Digital Public Good. The announcement should build confidence that governance is public and transparent, not just describe it in the abstract.

Scope

Two deliverables, not one:

  1. Documentation — a durable reference describing the governance structure itself (decision-making roles, community participation mechanism, how it's maintained going forward). This is the source of truth; the blog post summarizes it.
  2. Blog post — the public announcement, linking to the documentation, written for a reader (like WHO) evaluating whether to trust and adopt CIEL.

Out of scope: QA content (see #2768) — keep the two posts distinct even though they're driven by the same feedback.

Open questions to resolve while drafting

  • What is the actual governance structure today (formal or de facto)? Needs to be defined/confirmed before it can be documented or announced — this may require input from Andy Kanter and whoever currently makes CIEL content decisions.
  • What does "community participation" concretely mean — proposal/review process, advisory input, something else?

Assignment

Not yet assigned — depends on who owns defining the governance structure itself before drafting can start (likely Andy Kanter, tbd).

Acceptance criteria

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions