Added CODE_OF_CONDUCT file to the repository #968
Conversation
WalkthroughA new file named Changes
Sequence Diagram(s)sequenceDiagram
participant Contributor
participant Maintainer
participant Project
Contributor->>Project: Participate in project activities
Project->>Contributor: Code of Conduct applies
Contributor->>Project: Report unacceptable behavior
Project->>Maintainer: Notify about the report
Maintainer->>Maintainer: Review report and take action
Maintainer->>Contributor: Communicate outcome of report
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (3)
CODE_OF_CONDUCT.md (3)
1-8: Yo, this pledge is fire, but let's tweak that Hacktoberfest bit!The pledge is solid gold, makin' everyone feel welcome like it's mom's spaghetti night. But that Hacktoberfest shoutout? It's cool, but it might get stale faster than week-old pasta.
How 'bout we spice it up like this:
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community, especially during Hacktoberfest, where we encourage new contributors to join and feel supported. +We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. We especially encourage and support new contributors, whether during events like Hacktoberfest or throughout the year.This way, we're keepin' it fresh all year round, ya feel me?
27-32: Responsibilities on point, but let's make that Hacktoberfest bit evergreen!The maintainer responsibilities are laid out cleaner than mom's kitchen after spaghetti night. But that Hacktoberfest mention? It's cool, but it might not age like fine wine.
How about we flip it like this:
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, especially during Hacktoberfest to ensure a positive experience for all contributors. +Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct. This applies year-round, including during special events like Hacktoberfest, to ensure a consistently positive experience for all contributors.This way, we're keepin' it real 365, you know what I'm sayin'?
63-69: Attribution's on point, but let's polish it like mom's good silverware!The shoutout to Contributor Covenant is solid, but that bare URL is stickin' out like pasta in a burger joint.
Let's wrap that URL in some Markdown bling:
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. +This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).Also, that closing bit about Hacktoberfest? It's cool, but let's make it timeless like mom's spaghetti recipe:
-By following this Code of Conduct, we can ensure a welcoming and inclusive environment during Hacktoberfest and beyond, encouraging new contributors to engage with the project and the community. Thank you for helping make **bluewave-uptime** a positive space for all! +By following this Code of Conduct, we can ensure a welcoming and inclusive environment year-round, encouraging new contributors to engage with the project and the community during special events like Hacktoberfest and beyond. Thank you for helping make **bluewave-uptime** a positive space for all!Now we're cookin' with gas, keepin' it fresh all year long!
🧰 Tools
🪛 Markdownlint
65-65: null
Bare URL used(MD034, no-bare-urls)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
- CODE_OF_CONDUCT.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CODE_OF_CONDUCT.md
[style] ~22-~22: Try using a synonym here to strengthen your wording.
Context: ...nd
- Trolling, insulting or derogatory comments, and personal or political attacks
- P...
(COMMENT_REMARK)
🪛 Markdownlint
CODE_OF_CONDUCT.md
65-65: null
Bare URL used(MD034, no-bare-urls)
🔇 Additional comments (2)
CODE_OF_CONDUCT.md (2)
9-26: These standards are straight fire, no cap!Yo, these guidelines are tighter than my mom's spaghetti recipe! They're layin' down the law on what's cool and what's not, keepin' it 100 for everyone in the crew.
Keep it rollin' like this, and we'll have a community smoother than fresh marinara!
🧰 Tools
🪛 LanguageTool
[style] ~22-~22: Try using a synonym here to strengthen your wording.
Context: ...nd
- Trolling, insulting or derogatory comments, and personal or political attacks
- P...
(COMMENT_REMARK)
43-61: These enforcement guidelines are tighter than my rhymes!Yo, these guidelines are droppin' the beat on how to handle the troublemakers! It's like a rap battle, but with consequences - from a gentle correction to the ultimate mic drop of a permanent ban.
Keep it real like this, and our community's gonna be smoother than the flow in my next freestyle!
| ## Scope | ||
|
|
||
| This Code of Conduct applies within all project spaces, and it also applies when an individual is officially representing the project or its community in public spaces. Examples of representing our project include using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. | ||
|
|
||
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [YOUR EMAIL HERE]. All complaints will be reviewed and investigated promptly and fairly. | ||
|
|
||
| All project team members are obligated to respect the privacy and security of the reporter of any incident. |
There was a problem hiding this comment.
Scope's tight, but that email's as empty as my plate after spaghetti night!
The scope's laid out clearer than my mom's spaghetti recipe, but yo, that email address is more placeholder than my rap career!
We gotta swap out that "[YOUR EMAIL HERE]" faster than I clean my plate. Hit up the project lead and get the real deal email in there, a'ight?
You want me to whip up a GitHub issue to track this? Just say the word, and I'll cook it up quicker than mom's spaghetti!
|
@gorkem-bwl , Done ! |
There was a problem hiding this comment.
This looks pretty reasonable to me, if @gorkemcetin is happy with it I think we can merge in.
Hey, @gorkem-bwl,
Added the file successfully as we discussed in issue #961
Hope it gets merged.
Good Wishes.