feat: add slack etiquettes #6178
Open
+17
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mamoodi
reviewed
Jan 10, 2025
| @@ -121,3 +121,20 @@ We need to be more careful with changes to the core agent, as it is imperative t | |||
| If it improves accuracy, efficiency, or both with only a minimal change to code quality, that's great we're happy to merge it in! | |||
| If there are bigger tradeoffs (e.g. helping efficiency a lot and hurting accuracy a little) we might want to put it behind a feature flag. | |||
| Either way, please feel free to discuss on github issues or slack, and we will give guidance and preliminary feedback. | |||
|
|
|||
| ### Slack Etiquettes | |||
There was a problem hiding this comment.
@rbren since you already approved this on Slack. Do you think this should go here? Do you want it anywhere in the code base or is pinning to Slack enough?
enyst
reviewed
Jan 12, 2025
| - When asking for help or raising issues, include necessary details like links, screenshots, or clear explanations to provide context. | ||
| - Keep discussions in public channels whenever possible to allow others to benefit from the conversation, unless the matter is sensitive or private. | ||
| - Always adhere to the [Code of Conduct](https://github.com/All-Hands-AI/OpenHands/blob/main/CODE_OF_CONDUCT.md) to ensure a welcoming and collaborative environment. | ||
| - After posting a message containing links, disable any auto-generated previews unless they provide essential context to the message. |
There was a problem hiding this comment.
Just to note, this is not the current custom, I don't think. To the contrary, previews are enabled a lot, the context from github issues doesn't, to my knowledge, bother anyone, and at least on research previews I'm pretty sure it's actually helpful.
enyst
reviewed
Jan 12, 2025
| - Avoid using flashing, blinking, or flickering emojis and GIFs, as they may trigger photosensitive epilepsy. | ||
| - Post questions or discussions in the most relevant channel (e.g., [#general](https://app.slack.com/client/T06P212QSEA/C06P5NCGSFP) for general topics, [#questions](https://openhands-ai.slack.com/archives/C06U8UTKSAD) for queries/questions). | ||
| - When asking for help or raising issues, include necessary details like links, screenshots, or clear explanations to provide context. | ||
| - Keep discussions in public channels whenever possible to allow others to benefit from the conversation, unless the matter is sensitive or private. |
There was a problem hiding this comment.
This is very good, I'm not sure it helps being written here, but I guess one can try. 😅
enyst
reviewed
Jan 12, 2025
| - Communicate respectfully and professionally, avoiding sarcasm or harsh language, and remember that tone can be difficult to interpret in text. | ||
| - Use threads for specific discussions to keep channels organized and easier to follow. | ||
| - Tag others only when their input is critical or urgent, and use @here or @channel sparingly to minimize disruptions. | ||
| - Before asking questions, check existing resources such as pinned messages, documentation, or previous conversations. |
There was a problem hiding this comment.
Suggested change
| - Before asking questions, check existing resources such as pinned messages, documentation, or previous conversations. |
enyst
reviewed
Jan 12, 2025
| - Post questions or discussions in the most relevant channel (e.g., [#general](https://app.slack.com/client/T06P212QSEA/C06P5NCGSFP) for general topics, [#questions](https://openhands-ai.slack.com/archives/C06U8UTKSAD) for queries/questions). | ||
| - When asking for help or raising issues, include necessary details like links, screenshots, or clear explanations to provide context. | ||
| - Keep discussions in public channels whenever possible to allow others to benefit from the conversation, unless the matter is sensitive or private. | ||
| - Always adhere to the [Code of Conduct](https://github.com/All-Hands-AI/OpenHands/blob/main/CODE_OF_CONDUCT.md) to ensure a welcoming and collaborative environment. |
There was a problem hiding this comment.
This might be already said elsewhere?
enyst
reviewed
Jan 12, 2025
| - Tag others only when their input is critical or urgent, and use @here or @channel sparingly to minimize disruptions. | ||
| - Before asking questions, check existing resources such as pinned messages, documentation, or previous conversations. | ||
| - Be patient, as open-source contributors and maintainers often have other commitments and may need time to respond. | ||
| - Avoid using flashing, blinking, or flickering emojis and GIFs, as they may trigger photosensitive epilepsy. |
There was a problem hiding this comment.
Suggested change
| - Avoid using flashing, blinking, or flickering emojis and GIFs, as they may trigger photosensitive epilepsy. |
I don't think this happens?
|
@Honyii I appreciate the write-up! I do think it's helpful if it's simple and easy to parse at a glance. You know, humans have a fairly limited context too. 😂 I made a few suggestions to simplify it a bit. Just thinking we can always add things if they prove needed, but if you care about them a lot, feel free to leave them in. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #6173