---
# System prepended metadata

title: Vocabulary Discussion
tags: [CDEvents]

---

---
tags: CDEvents
---

# Vocabulary Discussion
- Actions defined in the previous vocabulary meeting
    - Create an initial set of buckets for events and an initial set of events 
    - Keep it simple for now, indentify the most relevant events, their meaning, intended use and main attributes
    - Identify the main terms to be used and the right level of abstraction
- 4 Pull request were created and conversations are happening in the PRs. 
- 4 main buckets were created for events: 
    - **Project Management** (Teams, Users, Sprints, Requirements, Storyies, Isssues events)
    - **Source Code Version Control** (Repository & Change Events proposed)
    - **Continuous Integration** (Build, Package, Release events proposed)
    - **Continuous Deployment** (Environment and Service events proposed)
    - **Continuous Delivery** (PipelineRun, TaskRun)
    

# Questions
  
  - Are these the right buckets? Is there any bucket missing? Are the bucket names concrete enough? 
      - Continuous Delivery bucket? (creation, verification and release of compositions)
  - Is this the right level of abstraction? Does everyone agree with this initiative at this level? 
  - What would be needed to merge these initial PRs? Having an initial definition merged will help creating smaller PRs for changes and more scoped discussions
  - Should we have generic or concrete (or both) task/activity events? https://github.com/cdfoundation/sig-events/discussions/15
  - Should we support "a set of tasks/activities run together on the same environment instance"?
      - E.g. [ESCI Flow Activity Block](https://github.com/erkist/sig-interoperability/tree/erkist-esci/workstreams/events_in_cicd/input/enterprise-scale-ci#flow-activity-block)
  - Should we include Issue Events? (like github issues)
  - How do we correlate events (e.g. trace event chains back to the original source/event/etc. that caused the chain to start)
  - How does component from @erkist are going to fit into this vocabulary? 
      - @sbtaylor15 has ideas on changes to support Docker image references (vs. just supporting files)

# Actions
- @salaboy refactor PRs to reflect new buckets in discussion
- PoCs
    - define and create some proposals
    - @salaboy Focus on metrics 
- ~~@erkist 09 Mar:~~ Propose new Continuous Delivery bucket include pipeline/task and orchestration events
    - PR up: https://github.com/cdfoundation/sig-events/pull/23
- Change buckets names:
  - Continuous Integration -> Integration
  - Add Continuous Delivery bucket

# Pull Requests created:
- Introduction: https://github.com/cdfoundation/sig-events/pull/5
    - @salaboy thinks that we can merge this if it is not too controvertial 
- Source Code Version Control Events: https://github.com/cdfoundation/sig-events/pull/7
- Continuous Integration: https://github.com/cdfoundation/sig-events/pull/8
- Continuous Deployment: https://github.com/cdfoundation/sig-events/pull/9
# References
- Some other implementations: https://github.com/keptn/spec/blob/master/cloudevents.md
- CDF terms: https://github.com/cdfoundation/sig-interoperability/blob/master/docs/vocabulary.md#mapping-of-terms
