Updates to security, governance and adopters

ADOPTERS.md

@@ -27,6 +27,8 @@ The companies listed here conform to [CNCF's definition of end-users](https://gi
 |[AB-Inbev](https://www.ab-inbev.com/)|Implementing Chaos Engineering as a practice at AB-Inbev|[Our Story](adopters/organizations/abinbev.md)|
 |[Group Baobab](https://baobab.com/en/home/)| Orchestrating Chaos using LitmusChaos at Baobab|[Our Story](https://github.com/litmuschaos/litmus/issues/2191#issuecomment-1647648343)|
 |[Flipkart](https://www.flipkart.com/)|Chaos Engineering at Flipkart|[Our Story](https://github.com/litmuschaos/litmus/issues/2191#issuecomment-1966904935)|
+|[Talend](https://www.talend.com/)|Chaos Engineering for our pipelines and weekly checks|[Our Story](https://github.com/litmuschaos/litmus/issues/2191#issuecomment-2005254600)|
+|[Delivery Hero](https://www.deliveryhero.com/)|Enhancing Resiliency of Our Services|[Our Story](https://github.com/litmuschaos/litmus/issues/2191#issuecomment-1997465958)|
 
 
 ### Cloud-Native Vendors
@@ -47,6 +49,7 @@ devops/reliability pipelines (such as for customer portals/websites etc.,) withi
 |[Container Solutions](https://www.container-solutions.com/)|Building Chaos Engineering for E-Commerce Customers|[Our Story](adopters/organizations/containersolutions.md)|
 |[Infracloud Technologies](https://www.infracloud.io/)|Developing Resiliency Framework at Infracloud|[Our Story](adopters/organizations/infracloud.md)|
 |[IFS](https://www.ifs.com/)|Checking Resiliency with LitmusChaos at IFS|[Our Story](https://github.com/litmuschaos/litmus/issues/2191#issuecomment-1966428068)|
+|[Ericsson](https://www.ericsson.com/en)|Chaos Engineering with Open Source LitmusChaos|[Our Story](https://github.com/litmuschaos/litmus/issues/2191#issuecomment-1985348431)|
 
 
 ### Cloud-Native Solutions & Service Providers

GOVERNANCE.md

@@ -87,6 +87,24 @@ person will contact the maintainer to ask if they want to continue being
 a maintainer. If the maintainer decides to step down as a maintainer, they
 open a pull request to be removed from the MAINTAINERS file.
 
+## Emeritus maintainers
+
+For committers who are stepping down or being removed due to inactivity,
+the project would like to memorialize their contributions to the project by
+recognizing them as Emeritus maintainers in the EMERITUS.md file. The EMERITUS.md
+file will include a brief paragraph summarizing their contribution to the
+containerd project and recognize them as permanent Emeritus members of the
+community. While Emeritus maintainers are not active in the project, their
+expertise is always valued and their LGTM may count towards the required LGTM
+count to merge a code change into the project.
+
+If in the future an Emeritus maintainer has the desire or ability to return to
+contributing to the project, Emeritus maintainers can submit a pull request
+reversing their removal from the MAINTAINERS file and approval only requires
+2 LGTMs from current committers to return to full committer status in the
+project.
+
+
 ## How are decisions made?
 
 LitmusChaos is an open-source project with an open design philosophy. This means

README.md

@@ -55,8 +55,6 @@ ChaosExperiment CRs are hosted on <a href="https://hub.litmuschaos.io" target="_
 application developers or vendors share their chaos experiments so that their users can use them to increase the resilience of the applications 
 in production.
 
-![chaos-operator-flow](/images/chaos-operator-flow.png)
-
 ## Use cases
 
 - **For Developers**: To run chaos experiments during application development as an extension of unit testing or integration testing.

SECURITY.md

@@ -15,8 +15,11 @@ To report a litmuschaos vulnerability, either:
     ![Github Advisories tab](./images/security-reporting2.png)
 
     Click on 'Report a vulnerability'
-
+   ![Github Report a Vulnerability](./images/security-reporting3.png)
+
 
+
+
 2. Send an email to `litmuschaos@gmail.com` detailing the issue and steps
 to reproduce.