changes to meet the code of conduct #891
Conversation
The code of conduct states no sexualized language should be used. This needs to be professional and safe for work and all ages. This language is not necessary. https://github.com/frenck/spook/blob/main/.github/CODE_OF_CONDUCT.md
📝 WalkthroughWalkthroughThe pull request involves a minor text modification in the Changes
Suggested labels
Suggested reviewers
Possibly related PRs
Poem
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
CodeRabbit Configuration File (
|
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
documentation/index.md (1)
21-21: Consider improving sentence structure.The current sentence structure could be simplified for better readability.
Consider this revision:
-If you would ever ask me, if you should use Spook? I would say: Absolutely! (But, I might be biased 😉) +Should you use Spook? Absolutely! (But I might be biased 😉)🧰 Tools
🪛 LanguageTool
[uncategorized] ~21-~21: If “ if” starts an indirect question, you do not need to put a comma before it.
Context: ...istant itself. If you would ever ask me, if you should use Spook? I would say: Abso...(NO_COMMA_BEFORE_INDIRECT_QUESTION)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
documentation/index.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
documentation/index.md
[uncategorized] ~21-~21: If “ if” starts an indirect question, you do not need to put a comma before it.
Context: ...istant itself. If you would ever ask me, if you should use Spook? I would say: Abso...
(NO_COMMA_BEFORE_INDIRECT_QUESTION)
🔇 Additional comments (1)
documentation/index.md (1)
21-21: Content change aligns with code of conduct.The replacement of inappropriate language with "Absolutely!" maintains the enthusiastic tone while making the documentation more inclusive and appropriate for all audiences.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~21-~21: If “ if” starts an indirect question, you do not need to put a comma before it.
Context: ...istant itself. If you would ever ask me, if you should use Spook? I would say: Abso...(NO_COMMA_BEFORE_INDIRECT_QUESTION)
|
I am not able to add labels to fix the approval workflow. Can somebody point me to documentation to fix this? |
|
Hehe sorry, but I am going to friendly decline. Spook is designed to be the rebel. ../Frenck |
|
seriously? so anybody can just act how and say whatever they want as long as they say they're designed to be the rebel? seems... unjustifiable. what's the point of the code of conduct then? |
|
I can, this is my repo. Like it or not. Dude... chill... drink a beer a bit more and enjoy life instead of getting on top this stuff. This repo is less serious, Spook is a little rebbel, there are more bad words to be found. Chill. |
|
implying that i don't enjoy life? or that i need to "chill"? that's borderline a personal attack. i can care about what i care about and if it's not the same things that you care about, i don't need to "chill." let's keep this constructive. demonstrating empathy and kindness toward other people would include not using offensive language. being respectful of differing opinions, viewpoints and experiences would include using all inclusive language. gracefully accepting constructive feedback would be taking this change as it is clearly against the repository's code of conduct. focusing on what is best not just for you as an individual but for the overall community also comes into play. in many parts of the world this type of language is not common or representative of the people. this language is sexualized. the word, in fact, literally means the act of forcefully having sex. it is not appropriate in some professional settings. it is not appropriate in some academic settings. the language is at odds with many religious organizations and personal and beliefs. for those groups, this language can be offensive, alienating and exclusionary. if you follow and believe in your code of conduct, there is literally no reason for you to not remove that word. you can get similar emphasis using other language/words. why is this even a discussion? this seemed so obvious. i'm not going after contribution. don't accept the pr. it's just not needed to be so offensive. if you intend for this repo to be less serious then modify the code of conduct or drop it. right now you are not being inclusive or respectful to various groups of people to use language like that and are not following the code of conduct. |
Stopped reading there. |
very respectful. right on cue. |
The code of conduct states no sexualized language should be used. The code of conduct also places an emphasis and focus on safety and inclusivity. I would assume that this safety and inclusivity should extend to all ages and all people. This means that the documentation should be safe for all ages.
For reference:
https://github.com/frenck/spook/blob/main/.github/CODE_OF_CONDUCT.md
I removed the word "fucking"
Description
In the documentation/index.md file I removed the word "fucking" so that this change would reflect on the main page of https://spook.boo/
Motivation and Context
This repository and project should be for all ages and all walks of life. For all people. This language is not for all people.
How has this been tested?
I used VS Code to view the markup.
Screenshots (if appropriate):
N/A
Types of changes
Checklist