Establish CDEventsX Registry and Event Promotion Process

[dsanyika]

The CDEventsX namespace (dev.cdeventsx) is intended for experimental events, but there is currently no formal registry or process for promoting an event from the CDEventsX repository to full adoption as a CDEvent.

Without a structured process, experimental events risk remaining undefined, lacking standardization, or conflicting with other proposals.

Proposal:

1. Create a CDEventsX Registry:
   • Document criteria for event acceptance into the CDEventsX repository that ensures no naming collisions
   • Maintain a user facing list of experimental events under dev.cdeventsx.
   • Include event schemas in a dedicated cdeventsx directory in the repository.
2. Define Event Vetting Criteria:
   • Require a clear use case before adding an event to the CDEventsX repository.
   • Establish minimum adoption requirements before promoting an event.
3. Event Promotion Process:
   • Events move from dev.cdeventsx → dev.cdevents once they meet adoption thresholds.
   • Include a deprecation policy for unused experimental events.

Use Cases:

1. A DORA-focused team wants to introduce branch.initialCommit as an experimental event before proposing it as a standard CDEvent.
2. A tool vendor introduces a new tool type then creates custom event and wants community feedback before formal adoption.
3. The CDEvents SIG needs a structured way to evaluate new event requests.

Impact:

• Provides a clear path for experimental events to become standard CDEvents.
• Prevents namespace conflicts by centralizing experimental event tracking.
• Encourages community-driven innovation in event standardization.