From b8da9e317f7404f29ecab09b378fc7e116c5f314 Mon Sep 17 00:00:00 2001 From: Miroslav Pejic Date: Tue, 3 Dec 2024 23:52:53 +0100 Subject: [PATCH] [mirotalkc2c] - lint --- CODE_OF_CONDUCT.md | 28 ++++++++++++++-------------- README.md | 8 ++++---- SECURITY.md | 8 ++++---- 3 files changed, 22 insertions(+), 22 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index e68a1ec..56e6000 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -35,23 +35,23 @@ socioeconomic status, or other similar personal characteristics. Examples of behavior that contributes to creating a positive environment include: -- Using welcoming and inclusive language -- Being respectful of differing viewpoints and experiences -- Gracefully accepting constructive criticism -- Focusing on what is best for the community -- Showing empathy toward other community members +- Using welcoming and inclusive language +- Being respectful of differing viewpoints and experiences +- Gracefully accepting constructive criticism +- Focusing on what is best for the community +- Showing empathy toward other community members Examples of unacceptable behavior by participants include: -- The use of sexualized language or imagery and unwelcome sexual attention or - advances -- Personal attacks, insulting/derogatory comments, or trolling -- Public or private harassment -- Publishing, or threatening to publish, others' private information—such as - a physical or electronic address—without explicit permission -- Other conduct which could reasonably be considered inappropriate in a - professional setting -- Advocating for or encouraging any of the above behaviors +- The use of sexualized language or imagery and unwelcome sexual attention or + advances +- Personal attacks, insulting/derogatory comments, or trolling +- Public or private harassment +- Publishing, or threatening to publish, others' private information—such as + a physical or electronic address—without explicit permission +- Other conduct which could reasonably be considered inappropriate in a + professional setting +- Advocating for or encouraging any of the above behaviors ## Our Responsibilities diff --git a/README.md b/README.md index 7d6c896..da5a9b7 100644 --- a/README.md +++ b/README.md @@ -91,13 +91,13 @@ Open [http://localhost:8080](http://localhost:8080) in your browser.
-- `Ngrok/HTTPS:` You can start a video conference directly from your local PC and make it accessible from any device outside your network by following [these instructions](docs/ngrok.md), or expose it directly on [HTTPS](backend/ssl/README.md). +- `Ngrok/HTTPS:` You can start a video conference directly from your local PC and make it accessible from any device outside your network by following [these instructions](docs/ngrok.md), or expose it directly on [HTTPS](backend/ssl/README.md). -- `Stun/Turn:` Install your own [Stun & Turn](https://docs.mirotalk.com/coturn/stun-turn/) by following [this instructions](./docs/coturn.md). +- `Stun/Turn:` Install your own [Stun & Turn](https://docs.mirotalk.com/coturn/stun-turn/) by following [this instructions](./docs/coturn.md). -- `Self-hosting:` For `self-hosting MiroTalk C2C` on your own dedicated server, please refer to [this comprehensive guide](docs/self-hosting.md). It will provide you with all the necessary instructions to get your MiroTalk C2C instance up and running smoothly. +- `Self-hosting:` For `self-hosting MiroTalk C2C` on your own dedicated server, please refer to [this comprehensive guide](docs/self-hosting.md). It will provide you with all the necessary instructions to get your MiroTalk C2C instance up and running smoothly. -- `Rest API:` The [API documentation](https://docs.mirotalk.com/mirotalk-c2c/api/) uses [swagger](https://swagger.io/) at http://localhost:8080/api/v1/docs or check it on live [here](https://c2c.mirotalk.com/api/v1/docs). +- `Rest API:` The [API documentation](https://docs.mirotalk.com/mirotalk-c2c/api/) uses [swagger](https://swagger.io/) at http://localhost:8080/api/v1/docs or check it on live [here](https://c2c.mirotalk.com/api/v1/docs). ```bash # The response will give you a entrypoint / Room URL for your meeting. diff --git a/SECURITY.md b/SECURITY.md index 327d28c..8f5874c 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -9,10 +9,10 @@ We prefer a Coordinated Vulnerability Disclosure (CVD) to properly understand an Your report should include: -- Product version ([GitHub](https://github.com/miroslavpejic85/mirotalkc2c/commits/main) commit hash or [DockerHub](https://hub.docker.com/r/mirotalk/c2c) sha256 digest hash) -- The affected component if possible (client.js, server.js, etc.) -- A vulnerability description -- Reproduction steps +- Product version ([GitHub](https://github.com/miroslavpejic85/mirotalkc2c/commits/main) commit hash or [DockerHub](https://hub.docker.com/r/mirotalk/c2c) sha256 digest hash) +- The affected component if possible (client.js, server.js, etc.) +- A vulnerability description +- Reproduction steps A member of the security team will confirm the vulnerability, determine its impact, and develop a fix. The fix will be applied to the master branch, tested, and packaged in the next security release.