https://github.com/cdevents/implementation-wg
CDEvents Implementation Working Group
https://github.com/cdevents/implementation-wg
Last synced: 5 months ago
JSON representation
CDEvents Implementation Working Group
- Host: GitHub
- URL: https://github.com/cdevents/implementation-wg
- Owner: cdevents
- License: apache-2.0
- Created: 2024-06-26T09:25:22.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-08-06T15:11:23.000Z (almost 2 years ago)
- Last Synced: 2024-08-06T17:55:32.473Z (almost 2 years ago)
- Size: 27.3 KB
- Stars: 0
- Watchers: 6
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Security: docs/security_automation.drawio.svg
Awesome Lists containing this project
README
# CDEvents Implementation Working Group
* [Overview](#overview)
* [Objectives](#objectives)
* [Areas of Focus](#areas-of-focus)
* [Members](#members)
* [New Members](#new-members)
* [Governance](#governance)
* [Communication](#communication)
* [Meetings](#meetings)
## Overview
The CDEvents Implementation Working Group focuses on defining the functional and non-functional requirements for implementing [CDEvents](https://cdevents.dev). Our aim is to create an architecture and implementation plan that ensures seamless integration, scalability, and performance of CDEvents within various CI/CD ecosystems without the requirement to update every pipeline or workflow.
### Objectives
* Define Functional Requirements: Establish clear and concise functional requirements for CDEvents to ensure interoperability and ease of use across different tools and platforms.
* Identify Non-Functional Requirements: Outline the non-functional requirements, including performance, scalability, security, testing, and maintainability.
* Develop Reference Architectures: Create reference architectures that demonstrate best practices for implementing CDEvents, based on use cases identified.
* Tooling Recommendations: Provide recommendations for tools and technologies that can be used to implement and support CDEvents.
* Tooling and Library Consistency: Ensure our tooling and libraries utilize consistent patterns and semantics allowing users to transition between different tools/libraries more easily while also following best practices per language.
* Documentation and Guidelines: Develop comprehensive documentation and examples on how to use CDEvents.
### Areas of Focus
* Message Broker - Cloud event pub/sub technologies
* Persistence - Document store and graph data retrieval
* Data Collection - Active and passive event creation, how are events triggered
* CDEvent tooling and libraries - Allow for tools and libraries that we support to work seamlessly with CDEvents related technologies
* Cross project collaboration - Getting project to implement events
* Visualization - Ability to see the event paths.
## Members
In alphabetical order, by first name.
* Andrea Frittoli [afrittoli](https://github.com/afrittoli), IBM
* Ben Powell [xibz](https://github.com/xibz), Apple
* Jalander Ramagiri [rjalander](https://github.com/rjalander), Ericsson
* Rasheed Mudasiru [taiwrash](https://github.com/Taiwrash), FUTMinna
* Steve Taylor [sbtaylor15](https://github.com/sbtaylor15), DeployHub
* Tracy Ragan [tracyragan](https://github.com/tracyragan), DeployHub
### New Members
Membership to this Working Group is open to public and self-declared: submit a PR to add yourself to the members list.
Advice for new members
Join the community:
- Go through this [README.md](.) document.
- Join the CDEvents mailing list
- Join the CDF Slack and jump into the #cdevents channel and introduce themselves.
- Regularly join the working group meetings.
Various ways to get involved:
- Share your thoughts by joining the meetings, posting to the mailing list, discussions forum or Slack channel.
- Add a topic you would like to discuss to the agenda of upcoming meeting.
- Create a new issue or start a discussion to start gathering feedback and collaborating.
- Choose an issue where help is needed and comment on it expressing interest.
## Governance
The CDEvents Implementation Working Group is part of the CDEvents project and follows the its [governance](https://github.com/cdevents/community/blob/main/governance.md)
and [Code of Conduct](https://github.com/cdevents/.github/blob/main/docs/CODE_OF_CONDUCT.md). Violations to the code of conduct may be reported via the [e-mail](https://groups.google.com/g/cdevents-code-of-conduct) or directly to the members to the CDEvents Governing Board.
## Communication
- [CDEvents Mailing List](https://groups.google.com/g/cdevents-dev)
- [`#cdevents`](https://cdeliveryfdn.slack.com/archives/C030SKZ0F4K) Channel on the [CDF Slack (link to the invite)](https://join.slack.com/t/cdeliveryfdn/shared_invite/zt-nwc0jjd0-G65oEpv5ynFfPD5oOX5Ogg)
## Meetings
The CDEvents Implementation Working Group meets bi-weekly on Tuesdays at 3pm UTC in the summer time and at 4pm UTC in winter time. (*See your timezone [here](https://time.is/3pm_in_UTC)*).
- [Meeting agenda and minutes](./meeting_notes.md).
- [Zoom Bridge](https://zoom.us/j/98408983891?pwd=VXBxMjJTaThGRGFWRXFmdUxsRUZUdz09).
- [Zoom International dial-in numbers](https://zoom.us/zoomconference).
- [CDF Public Calendar (UTC)](https://calendar.google.com/calendar/u/0/embed?src=linuxfoundation.org_mhf0kmgedn67ihni8r129avp24@group.calendar.google.com&ctz=UTC).
Meetings are automatically recorded an posted on [YouTube](https://www.youtube.com/playlist?list=PL2KXbZ9-EY9RlxWAnAjxs8Azuz11XVhkC).