Skip to content

Commit 5b394ae

Browse files
dwelsch-esidwelsch-esi
authored
Combined Community and More Resources pages. (#314)
* Combined Community and More Resources pages. Signed-off-by: Dave Welsch <[email protected]> * Update community page per PR#314 review Signed-off-by: Dave Welsch <[email protected]> --------- Signed-off-by: Dave Welsch <[email protected]>
1 parent 5cdca74 commit 5b394ae

File tree

6 files changed

+140
-130
lines changed

6 files changed

+140
-130
lines changed

‎website/docs/introduction/community.md

Lines changed: 67 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -6,80 +6,85 @@ sidebar_label: Community
66

77
---
88

9+
## Join the Litmus community
10+
911
Created by our users, contributors, and adopters, the Litmus community truly believes in adding to the value of open source culture. Serving and listening to the community is a priority to us.
1012

11-
We welcome Kubernetes SREs and Developers to join this zealous community to learn and share all about Cloud-Native Chaos Engineering. There are many contributors in our community who are ready to mentor those who want to contribute. Ask a question in [our slack channel](https://slack.litmuschaos.io/).
12-
13-
## Join our Slack channel
14-
15-
Join Our Community On Slack For Detailed Discussion, Feedback & Regular Updates On Chaos Engineering For Kubernetes, join `#litmus` on `Kubernetes Slack` and connect with SREs and Chaos Engineering enthusiasts.
16-
17-
Join here: https://slack.litmuschaos.io/
18-
19-
## Join our Community meetings
20-
21-
We meet on every 3rd Wednesday of the month!
22-
23-
#### Topics we discuss
24-
25-
- Updates to Litmus in the last one month
26-
- Contributor Experiences & Insights
27-
- SIG-Documentation Charter
28-
and many more!
29-
30-
## Community Events
31-
32-
Our resolve is to reach the global community and escalate the value of Cloud-Native Chaos Engineering among Kubernetes Developers and SREs. We organize meetups every month to reach out to the community. Join into one of our meetups and experience the real aura of Chaos. You can also conduct your own meetup, join our community, and put forward your idea.
33-
34-
<table>
35-
<tr>
36-
<td>
37-
<a href="https://zoom.us/j/91358162694">
38-
<img src={require("../assets/introduction/community/CommunitySyncUp.webp").default} />
39-
<br />
40-
<div style={{width: "300px"}}>
41-
Community Sync Up
42-
</div>
43-
<div style={{width: "300px", color: "#696F8C"}}>
44-
Meet and learn from the maintainers, contributors and developers of Litmus, everything about Chaos Engineering
45-
</div>
46-
</a>
47-
</td>
48-
<td>
49-
<a href="https://community.cncf.io/events/details/cncf-kubernetes-chaos-engineering-meetup-group-presents-kubernetes-chaos-engineering-meetup-1/#/">
50-
<img height={200} src={require("../assets/introduction/community/CNCF.webp").default} />
51-
<br />
52-
<div style={{width: "300px"}}>
53-
Kubernetes Chaos Engineering Meetup
54-
</div>
55-
<div style={{width: "300px", color: "#696F8C"}}>
56-
Discussion about the best practices and tutorials for practicing Chaos Engineering
57-
</div>
58-
</a>
59-
</td>
60-
</tr>
61-
</table>
13+
We invite Kubernetes SREs and Developers to join this community to learn and share knowledge about Cloud-Native Chaos Engineering. Many in our community are ready to mentor those who want to contribute. This page lists Litmus information and community resources.
6214

63-
## Contribute
15+
### Join our Slack channel
6416

65-
We invite contributions in all forms. Join us in writing blogs on DEV.to about experiments, features, and your experience. Use the `#litmuschaos` tag for your blog to get featured.
17+
Join our community on Slack For detailed discussion, feedback, and regular updates on Chaos Engineering For Kubernetes.
6618

67-
[Go to dev.to](https://dev.to/t/litmuschaos)
19+
Join [here](https://slack.litmuschaos.io/) (`#litmus` on `Kubernetes Slack`) and connect with SREs and Chaos Engineering enthusiasts.
6820

69-
## How to Contribute
21+
### Attend our meetings
7022

71-
- If you are a first-time contributor, please see [Steps to Contribute](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md#steps-to-contribute-).
72-
- If you would like to suggest new tests to be added to litmus, please go ahead and [create a new issue](https://github.com/litmuschaos/litmus/issues/new) describing your test. All you need to do is specify the workload type and the operations that you would like to perform on the workload.
73-
- If you would like to work on something more involved, please connect with the Litmus Contributors.
74-
- If you would like to make code contributions, all your commits should be signed with Developer Certificate of Origin. See [Sign your work](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md#sign-your-work).
23+
Fill out the [LitmusChaos Meetings invite form](https://forms.gle/xYZyZ2gTWMqz7xSs7) to get a calendar invite to Litmus community or contributor meetings.
24+
25+
#### Community meetings
26+
27+
Community meetings are online the third Wednesday of every month at 5:30 p.m. GMT (6:30 p.m. CEST, 10 p.m. IST). Everyone in the community is invited to participate in the LitmusChaos community meetings.
28+
29+
Notes from past meetings and links to the upcoming meeting are [here on HackMD](https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q).
30+
31+
Among other things, we discuss community updates, share updates on new features and releases, and discussing user/adopter stories.
32+
33+
#### Contributor meetings
7534

76-
### Contribute your chaos experiments
35+
Contributor meetings are on the second and last Thursday of every month at 2:30 p.m. GMT (3:30 p.m. CEST, 7 p.m. IST).
7736

78-
We are devoted to being an open source driven community and appeal to our community members to contribute chaos experiments, file issues, raise pull requests, and provide feedback to help enhance the user experience and bring in new enhancements to develop LitmusChaos.
37+
Contributor meetings are only for discussion of technical and non-technical contributions to LitmusChaos. Maintainers, present contributors, and aspiring contributors are invited to participate. We discuss issues, fixes, enhancements, and future contributions.
7938

80-
Check out the [CONTRIBUTING.md](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md) page on [Litmus repository](https://github.com/litmuschaos/litmus) for instructions on how to contribute. Feel free to discuss about your contributions on [our slack channel](https://slack.litmuschaos.io/).
39+
Here is the [contributor meeting link](https://harness-io.zoom.us/j/95100368978?pwd=b2VrdCtaakE5U3dhOElFMUJOaXVOUT09).
40+
41+
View the [release tracker](https://github.com/litmuschaos/litmus/milestones).
42+
43+
### Find Litmus on social media
44+
45+
Follow us on these social media platforms:
46+
47+
- [X](https://x.com/LitmusChaos)
48+
- [YouTube](https://www.youtube.com/channel/UCa57PMqmz_j0wnteRa9nCaw)
49+
- [Slack](https://app.slack.com/client/T09NY5SBT/CNXNB0ZTN/)
8150

8251
## Learn more
8352

53+
Check out the [official website](https://litmuschaos.io/) and get updates and what is happening around the LitmusChaos Community and all new feature releases.
54+
55+
Below are some further resources for chaos practitioners and Litmus contributors.
56+
57+
### Read blogs by the Litmus community and contributors
58+
59+
Check out blogs on Litmus written solely by the maintainers, contributors, and community folks.
60+
61+
- [Dev.to](https://dev.to/t/litmuschaos/latest)
62+
- [Medium](https://medium.com/litmus-chaos)
63+
64+
### Dive into chaos experiments
65+
66+
Find publicly available Chaos Experiments at [ChaosHub](http://hub.litmuschaos.io/), the central repository for chaos experiments.
67+
68+
Read about [chaos experiments](https://litmuschaos.github.io/litmus/).
69+
70+
## Contribute
71+
72+
We invite contributions in all forms. Join us in writing blogs on [Dev.to](https://dev.to/t/litmuschaos/latest) about experiments, features, and your experience. Use the `#litmuschaos` tag for your post to be featured.
73+
74+
Participation in the Litmus community is governed by our [code of conduct](https://github.com/litmuschaos/litmus/blob/master/CODE_OF_CONDUCT.md).
75+
76+
### Contribute to Litmus open source
77+
78+
See the Litmus [contribution document](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md).
79+
80+
Contributors meet twice a month. See [Contributor meetings](#contributor-meetings).
81+
82+
- If you are a first-time contributor, please read [Steps to Contribute](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md#steps-to-contribute-).
83+
- If you would like to suggest new tests to be added to Litmus, [create a new issue](https://github.com/litmuschaos/litmus/issues/new) describing your test. Specify the workload type and the operations that you would like to perform on the workload.
84+
- If you would like to work on something more involved, connect with the [Litmus Maintainers](https://github.com/litmuschaos/litmus/blob/master/MAINTAINERS.md).
85+
- If you would like to make code contributions, all your commits should be signed with Developer Certificate of Origin. See [Sign your work](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md#sign-your-work).
86+
87+
Other Litmus open source links:
88+
8489
- [Meta Repository](https://github.com/litmuschaos/litmus)
8590
- [Release Tracker](https://github.com/litmuschaos/litmus/milestones)

‎website/docs/introduction/what-is-litmus.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Thus it is important to verify your application resilience whenever a change has
2626

2727
Chaos Experiments are fundamental units within the LitmusChaos architecture. Users can choose between readily available chaos experiments or create new ones to construct a required Chaos Scenario.
2828

29-
## What is a Chaos Scenarios
29+
## What is a Chaos Scenario
3030

3131
A chaos scenario is much more than a simple chaos experiment. It supports the user in defining the expected result, observing the result, analysing the overall system behaviour, and in the decision-making process if the system needs to be tuned for improving the resilience.
3232

‎website/sidebars.js

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,7 @@ module.exports = {
66
'introduction/features',
77
'introduction/usage',
88
'introduction/core-principles',
9-
'introduction/community',
10-
'introduction/other-links'
9+
'introduction/community'
1110
]
1211
},
1312
{

‎website/versioned_docs/version-3.12.0/introduction/community.md

Lines changed: 67 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -6,80 +6,85 @@ sidebar_label: Community
66

77
---
88

9+
## Join the Litmus community
10+
911
Created by our users, contributors, and adopters, the Litmus community truly believes in adding to the value of open source culture. Serving and listening to the community is a priority to us.
1012

11-
We welcome Kubernetes SREs and Developers to join this zealous community to learn and share all about Cloud-Native Chaos Engineering. There are many contributors in our community who are ready to mentor those who want to contribute. Ask a question in [our slack channel](https://slack.litmuschaos.io/).
12-
13-
## Join our Slack channel
14-
15-
Join Our Community On Slack For Detailed Discussion, Feedback & Regular Updates On Chaos Engineering For Kubernetes, join `#litmus` on `Kubernetes Slack` and connect with SREs and Chaos Engineering enthusiasts.
16-
17-
Join here: https://slack.litmuschaos.io/
18-
19-
## Join our Community meetings
20-
21-
We meet on every 3rd Wednesday of the month!
22-
23-
#### Topics we discuss
24-
25-
- Updates to Litmus in the last one month
26-
- Contributor Experiences & Insights
27-
- SIG-Documentation Charter
28-
and many more!
29-
30-
## Community Events
31-
32-
Our resolve is to reach the global community and escalate the value of Cloud-Native Chaos Engineering among Kubernetes Developers and SREs. We organize meetups every month to reach out to the community. Join into one of our meetups and experience the real aura of Chaos. You can also conduct your own meetup, join our community, and put forward your idea.
33-
34-
<table>
35-
<tr>
36-
<td>
37-
<a href="https://zoom.us/j/91358162694">
38-
<img src={require("../assets/introduction/community/CommunitySyncUp.webp").default} />
39-
<br />
40-
<div style={{width: "300px"}}>
41-
Community Sync Up
42-
</div>
43-
<div style={{width: "300px", color: "#696F8C"}}>
44-
Meet and learn from the maintainers, contributors and developers of Litmus, everything about Chaos Engineering
45-
</div>
46-
</a>
47-
</td>
48-
<td>
49-
<a href="https://community.cncf.io/events/details/cncf-kubernetes-chaos-engineering-meetup-group-presents-kubernetes-chaos-engineering-meetup-1/#/">
50-
<img height={200} src={require("../assets/introduction/community/CNCF.webp").default} />
51-
<br />
52-
<div style={{width: "300px"}}>
53-
Kubernetes Chaos Engineering Meetup
54-
</div>
55-
<div style={{width: "300px", color: "#696F8C"}}>
56-
Discussion about the best practices and tutorials for practicing Chaos Engineering
57-
</div>
58-
</a>
59-
</td>
60-
</tr>
61-
</table>
13+
We invite Kubernetes SREs and Developers to join this community to learn and share knowledge about Cloud-Native Chaos Engineering. Many in our community are ready to mentor those who want to contribute. This page lists Litmus information and community resources.
6214

63-
## Contribute
15+
### Join our Slack channel
6416

65-
We invite contributions in all forms. Join us in writing blogs on DEV.to about experiments, features, and your experience. Use the `#litmuschaos` tag for your blog to get featured.
17+
Join our community on Slack For detailed discussion, feedback, and regular updates on Chaos Engineering For Kubernetes.
6618

67-
[Go to dev.to](https://dev.to/t/litmuschaos)
19+
Join [here](https://slack.litmuschaos.io/) (`#litmus` on `Kubernetes Slack`) and connect with SREs and Chaos Engineering enthusiasts.
6820

69-
## How to Contribute
21+
### Attend our meetings
7022

71-
- If you are a first-time contributor, please see [Steps to Contribute](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md#steps-to-contribute-).
72-
- If you would like to suggest new tests to be added to litmus, please go ahead and [create a new issue](https://github.com/litmuschaos/litmus/issues/new) describing your test. All you need to do is specify the workload type and the operations that you would like to perform on the workload.
73-
- If you would like to work on something more involved, please connect with the Litmus Contributors.
74-
- If you would like to make code contributions, all your commits should be signed with Developer Certificate of Origin. See [Sign your work](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md#sign-your-work).
23+
Fill out the [LitmusChaos Meetings invite form](https://forms.gle/xYZyZ2gTWMqz7xSs7) to get a calendar invite to Litmus community or contributor meetings.
24+
25+
#### Community meetings
26+
27+
Community meetings are online the third Wednesday of every month at 5:30 p.m. GMT (6:30 p.m. CEST, 10 p.m. IST). Everyone in the community is invited to participate in the LitmusChaos community meetings.
28+
29+
Notes from past meetings and links to the upcoming meeting are [here on HackMD](https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q).
30+
31+
Among other things, we discuss community updates, share updates on new features and releases, and discussing user/adopter stories.
32+
33+
#### Contributor meetings
7534

76-
### Contribute your chaos experiments
35+
Contributor meetings are on the second and last Thursday of every month at 2:30 p.m. GMT (3:30 p.m. CEST, 7 p.m. IST).
7736

78-
We are devoted to being an open source driven community and appeal to our community members to contribute chaos experiments, file issues, raise pull requests, and provide feedback to help enhance the user experience and bring in new enhancements to develop LitmusChaos.
37+
Contributor meetings are only for discussion of technical and non-technical contributions to LitmusChaos. Maintainers, present contributors, and aspiring contributors are invited to participate. We discuss issues, fixes, enhancements, and future contributions.
7938

80-
Check out the [CONTRIBUTING.md](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md) page on [Litmus repository](https://github.com/litmuschaos/litmus) for instructions on how to contribute. Feel free to discuss about your contributions on [our slack channel](https://slack.litmuschaos.io/).
39+
Here is the [contributor meeting link](https://harness-io.zoom.us/j/95100368978?pwd=b2VrdCtaakE5U3dhOElFMUJOaXVOUT09).
40+
41+
View the [release tracker](https://github.com/litmuschaos/litmus/milestones).
42+
43+
### Find Litmus on social media
44+
45+
Follow us on these social media platforms:
46+
47+
- [X](https://x.com/LitmusChaos)
48+
- [YouTube](https://www.youtube.com/channel/UCa57PMqmz_j0wnteRa9nCaw)
49+
- [Slack](https://app.slack.com/client/T09NY5SBT/CNXNB0ZTN/)
8150

8251
## Learn more
8352

53+
Check out the [official website](https://litmuschaos.io/) and get updates and what is happening around the LitmusChaos Community and all new feature releases.
54+
55+
Below are some further resources for chaos practitioners and Litmus contributors.
56+
57+
### Read blogs by the Litmus community and contributors
58+
59+
Check out blogs on Litmus written solely by the maintainers, contributors, and community folks.
60+
61+
- [Dev.to](https://dev.to/t/litmuschaos/latest)
62+
- [Medium](https://medium.com/litmus-chaos)
63+
64+
### Dive into chaos experiments
65+
66+
Find publicly available Chaos Experiments at [ChaosHub](http://hub.litmuschaos.io/), the central repository for chaos experiments.
67+
68+
Read about [chaos experiments](https://litmuschaos.github.io/litmus/).
69+
70+
## Contribute
71+
72+
We invite contributions in all forms. Join us in writing blogs on [Dev.to](https://dev.to/t/litmuschaos/latest) about experiments, features, and your experience. Use the `#litmuschaos` tag for your post to be featured.
73+
74+
Participation in the Litmus community is governed by our [code of conduct](https://github.com/litmuschaos/litmus/blob/master/CODE_OF_CONDUCT.md).
75+
76+
### Contribute to Litmus open source
77+
78+
See the Litmus [contribution document](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md).
79+
80+
Contributors meet twice a month. See [Contributor meetings](#contributor-meetings).
81+
82+
- If you are a first-time contributor, please read [Steps to Contribute](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md#steps-to-contribute-).
83+
- If you would like to suggest new tests to be added to Litmus, [create a new issue](https://github.com/litmuschaos/litmus/issues/new) describing your test. Specify the workload type and the operations that you would like to perform on the workload.
84+
- If you would like to work on something more involved, connect with the [Litmus Maintainers](https://github.com/litmuschaos/litmus/blob/master/MAINTAINERS.md).
85+
- If you would like to make code contributions, all your commits should be signed with Developer Certificate of Origin. See [Sign your work](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md#sign-your-work).
86+
87+
Other Litmus open source links:
88+
8489
- [Meta Repository](https://github.com/litmuschaos/litmus)
8590
- [Release Tracker](https://github.com/litmuschaos/litmus/milestones)

‎website/versioned_docs/version-3.12.0/introduction/what-is-litmus.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ Thus it is important to verify your application resilience whenever a change has
2626

2727
Chaos Experiments are fundamental units within the LitmusChaos architecture. Users can choose between readily available chaos experiments or create new ones to construct a required Chaos Scenario.
2828

29-
## What is a Chaos Scenarios
29+
## What is a Chaos Scenario
3030

3131
A chaos scenario is much more than a simple chaos experiment. It supports the user in defining the expected result, observing the result, analysing the overall system behaviour, and in the decision-making process if the system needs to be tuned for improving the resilience.
32+
33+

‎website/versioned_sidebars/version-3.12.0-sidebars.json

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,7 @@
66
"introduction/features",
77
"introduction/usage",
88
"introduction/core-principles",
9-
"introduction/community",
10-
"introduction/other-links"
9+
"introduction/community"
1110
]
1211
},
1312
{

0 commit comments

Comments
 (0)