You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Update out-of-date data on the mainpage
- Add project logos to the mainpage
- Update the contribution guide to include SDKs
- Update the roadmap for 2023/2024, remove achieved items, add new ones
- Update the community page with new links to the community repo
Signed-off-by: Andrea Frittoli <[email protected]>
Represent events associated with Testing activities
120
+
{{< /card >}}
121
+
{{<cardheader="Continuous Deployment Events" >}}
119
122
Represent events related to environments where the artifacts produced by the integration pipelines are intended to run
120
123
{{< /card >}}
124
+
{{< /cardpane >}}
125
+
{{<cardpane>}}
126
+
{{<cardheader="Continuous Operations Events" >}}
127
+
Represent events associated with Continuous Operations activities, such as incidents and their resolution
128
+
{{< /card >}}
121
129
{{<cardheader="Core Events" >}}
122
130
Represent shared abstractions such as Task Runs and Pipeline Runs
123
131
{{< /card >}}
124
132
{{< /cardpane >}}
125
133
126
134
<p>
127
-
There is interest in implementing in many of your favorite CI/CD tools, including ArgoCD, Flux, Jenkins, Jenkins-X, Keptn, Knative, Ortelius, Shipwright, Spinnaker, Tekton. Some of them have started proof-of-concept implementations with CDEvents.
135
+
CDEvents is implemented or being integrated by many of your favorite SDLC tools, including Argo, Flux, Guac, Harbor, Jenkins, Keptn, Spinnaker, Tekton, Testkube, Tracetest and more.
128
136
</p>
129
137
<br/><br/>
130
138
<divclass="mx-auto">
@@ -134,20 +142,39 @@
134
142
</div>
135
143
{{< /blocks/cdelead >}}
136
144
145
+
{{<blocks/lead title="CDF" color="light">}}
146
+
CDEvents is implemented or being integrated by many of your favorite SDLC tools, including Argo, Flux, Guac, Harbor, Jenkins, Keptn, Spinnaker, Tekton, Testkube, Tracetest and more.</br></br>
The project is developed and maintained by the <ahref="https://github.com/cdfoundation/sig-events">Events Special Interest Group</a> at the CDF. We welcome <ahref="community">contributions</a>!
Our first <ahref="https://github.com/cdfoundation/sig-events/tree/main/poc#cdf-sig-events-protocol-proof-of-concept">proof of concept</a> includes CDEvents in <ahref="https://tekton.dev">Tekton</a> and <ahref="https://keptn.sh">Keptn</a>.
171
+
Our <ahref="https://github.com/cdfoundation/sig-events/tree/main/poc#cdf-sig-events-protocol-proof-of-concept">proof of concepts</a> includes CDEvents in <ahref="https://tekton.dev">Tekton</a> , <ahref="https://spinnaker.io/">Spinnaker</a> and <ahref="https://keptn.sh">Keptn</a>.
145
172
We are building the next PoC to produce DevOps metrics through CDEvents.
Our specification work is driven by interoperability use cases.
150
-
Our first<ahref="https://github.com/cdevents/spec/releases/tag/v0.1.0">release v0.1.0</a> includes a <ahref="https://github.com/cdevents/sdk-go/releases/tag/v0.1.0">Go SDK</a>.
177
+
Our latest<ahref="https://github.com/cdevents/spec/releases/tag/v0.3.0">release v0.3.0</a> includes a <ahref="https://github.com/cdevents/sdk-go/releases/tag/v0.3.0">Go SDK</a>.
Copy file name to clipboardExpand all lines: content/en/community/_index.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -46,15 +46,15 @@ <h2>Develop and Contribute</h2>
46
46
</section>
47
47
{{% cardpane %}}
48
48
{{<blocks/feature title="Are you developing a CI/CD tool?" image_anchor="center" width="50%" height="min" color="dark" >}}
49
-
<h2class="text-center">The CDEvents SIG needs you!</h2>
49
+
<h2class="text-center">CDEvents needs you!</h2>
50
50
<pclass="lead">We need your help to spread the implementation of CDEvents as an international standard. Get in touch and let us help you extend your product to provide new capabilities for your users.</p>
51
51
<pclass="lead">You can find out how to contribute to CDEvents in our <ahref="/community/contribution-guidelines/">Contribution Guidelines</a></p>
52
52
{{< /blocks/feature >}}
53
53
54
54
{{<blocks/feature title="Want to shape the standard?" image_anchor="center" width="50%" height="min" color="dark" icon="fa-sharp fa-solid fa-hand-holding-heart">}}
55
55
<h2class="text-center">You can help to make a difference</h2>
56
56
<pclass="lead">We would love you to get involved in defining new events and helping to evolve our specification as we grow to meet the demands of Continuous Delivery.</p>
57
-
<pclass="lead">Come along to a CDEvents SIG meeting <ahref="https://github.com/cdfoundation/sig-events">How to getinvolved</a></p>
57
+
<pclass="lead">Come along to a <ahref="https://github.com/cdevents/community?tab=readme-ov-file#how-to-get-involved">CDEvents meeting</a></p>
Copy file name to clipboardExpand all lines: content/en/community/contribution-guidelines.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,12 @@ description: >
13
13
<!-- cSpell:locale en-US -->
14
14
# Contribution Guidelines
15
15
16
-
Thank you for contributing your time and expertise to CDEvents. This document describes the contribution guidelines for the project.
16
+
Thank you for contributing your time and expertise to CDEvents. This document describes the contribution guidelines for the project specification and website:
The CDEvents SDKs have dedicated contributing guides in the respective repositories.
17
22
18
23
**Note:** Before you start contributing, you must read and abide by our **[Code of Conduct](https://github.com/cdevents/.github/blob/main/docs/CODE_OF_CONDUCT.md)**.
19
24
@@ -32,7 +37,7 @@ CDEvents welcomes all of contributions! We encourage you to engage with the
Copy file name to clipboardExpand all lines: content/en/community/roadmap.md
+23-11Lines changed: 23 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,10 +10,11 @@ description: >
10
10
Roadmap
11
11
---
12
12
-->
13
+
13
14
<!-- cSpell:locale en-US -->
14
15
# CDEvents Mission and Roadmap
15
16
16
-
This document describes the mission of the CDEvents and its overall roadmap for 2022.
17
+
This document describes the mission of the CDEvents and its overall roadmap for 2023/2024.
17
18
18
19
## Mission & Vision
19
20
@@ -29,18 +30,29 @@ We envision an ecosystem of tools to generate, store, process and visualize CDEv
29
30
30
31
The continuous delivery ecosystem is quite large as it includes tools and services that span from the design of software, through its implementation, build, test, release, deployment and operation.
31
32
32
-
In 2022 we want to focus on a few [key use cases](/docs/primer#use-cases) and make sure that we can fully support them with the protocol specification. More specifically:
33
+
In 2023/2024 we want to focus on a few [key use cases](/docs/primer#use-cases) and make sure that we can fully support them with the protocol specification. More specifically:
33
34
34
-
- Capture our key use cases and design decisions in the [CDEvents primer](/docs/primer) document
35
-
- Develop the spec to fully support our [key use cases](/docs/primer#use-cases)
- Validate and demonstrate the spec through proofs-of-concept
40
-
- Specify and rework the CloudEvents binding, and develop SDKS:
41
-
- Re-create the SDK for the `go` language
42
-
- Create a new SDK for the `python` language
43
-
- Evolve the project bootstrap governance into a full governance
44
-
- Grow the CDEvents community of projects and contributors
56
+
- Continue to collaborate with various communities to promote CDEvents adoption
45
57
46
58
The implementation of proofs of concept will require having CDEvents emitted by various platforms which do not support CDEvents yet. Where possible we will work with the community; it is likely we will have to develop producers and consumers of CDEvents that can adapt existing event formats into CDEvents. We will host such reference implementations in the `cdevents` organization at least until they can find a new home in the target project. These implementations will be useful to identify the mapping between the data model of a specific platform and CDEvents; we can add these mappings to supporting documentation in `cdevents` organization.
0 commit comments