-
Notifications
You must be signed in to change notification settings - Fork 6
Create rules-info-channel.md #215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kaosine
wants to merge
9
commits into
main
Choose a base branch
from
discord-rules-and-info-organization
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
3e47d95
Create rules-info-channel.md
kaosine 9adf07b
Create roles-and-colors.md
kaosine 43a29b1
Update social-media/discord/roles-and-colors.md
kaosine c835305
Update social-media/discord/roles-and-colors.md
kaosine bad4538
Update social-media/discord/rules-info-channel.md
kaosine 4c1cdeb
Update social-media/discord/rules-info-channel.md
kaosine 4b6c7a7
Update rules-info-channel.md
kaosine 3d00448
Update roles-and-colors.md
kaosine eea073a
Merge branch 'main' into discord-rules-and-info-organization
kaosine File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| # Description | ||
|
|
||
| This document serves as a way to group our roles into a logical manner with color designations so things fit better for accessibility reasons. It is part of what goes into `rules-info-channel.md` that is also in this folder. | ||
|
|
||
| After reading up on these, head to #role-select and pick up what roles suit you. We're glad to have you here and look forward to your contributions or any support we can provide you! | ||
|
|
||
| Admins and support: | ||
| - Team - knowledgeable people in the community who have shown they have the projects best interests in mind. they can handle most general questions, however recommend pinging the specific organizational team for your question. (#color-here) | ||
| - Admin (discord) - those who run and execute decisions in the community (#color-here) | ||
| - Mod (discord) - those who moderate the community in some way or another (#color-here) | ||
|
|
||
| Organizational: | ||
| - Documentation - for our documentation. This relates to our site and all the documents we handle between it and the pulsar-edit/.github repo (#color-here) | ||
| - Backend - API and server related development (#color-here) | ||
| - Developer - contributes where they can, not based on topic but availability (#color-here) | ||
| - Core - Works on the core editor and all the things that make it tick. (#color-here) | ||
| - Packages - our core packages (#color-here) | ||
| - Updates - when we post updates you'll get a notification. Consider this pulsar-announcements and eventually community-updates (#color-here) | ||
| - Community - if you develop a package on your own outside the org and submit it grab this one! We'll try to post updates about development on this soon as this is a upcoming feature in the v2 backend! (#color-here) | ||
| OS: | ||
| - Windows (#color-here) | ||
| - Linux (#color-here) | ||
| - MacOS (#color-here) |
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| # Rules | ||
|
|
||
| - Be Kind - This isn't a place for aggression, this is a place to work together to create awesome code. | ||
| - Be Respectful - We aim to have a community of accepting individuals. Being respectful includes not making racist, homophobic, or sexist insults. No matter someone's race, gender, sexuality, political affiliation, or experience we all are here together and should be treated with respect. | ||
| - No Private Messages - Unless confirmed publicly on the server you should never send private unsolicited messages to any members of this server. The only exception would be to report a sensitive issue to the @Admins or @Moderators. But even then it is recommended to publicly confirm that they are okay with you sending a private message. | ||
| - No Advertising - Please no advertisements of products or services independent of organic conversation. | ||
| - (recommended) Match your display name to what is on github. This helps for us assigning you to a team on there and allows us to contact you better for updates and concerns on contributions. This is ***NOT*** a strict requirement but it is extremely helpful in operations here. | ||
|
|
||
|
|
||
| # Conduct | ||
|
|
||
| https://github.com/pulsar-edit/pulsar/blob/master/CODE_OF_CONDUCT.md | ||
|
|
||
|
|
||
| # Contributing | ||
|
|
||
| If you are a new contributor to Pulsar and want to know how to help, feel free to interact on the server or GitHub. But if you'd like to just start programming please read our new contributor help guide. https://github.com/pulsar-edit/.github/blob/main/project-birth/CONTRIBUTING-DURING-START.md | ||
|
|
||
|
|
||
| # Roles | ||
|
|
||
| <!-- Contents for this part are in the roles-and-colors file in this directory. Please refer to that for the content of this section when pasting into discord or elsewhere. --> | ||
|
|
||
| # Invite | ||
|
|
||
| Invite link to the server: https://discord.gg/7aEbB9dGRT |
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, I was asked to post the stuff I was saying in the Discord about trying to find some accessible (contrasting, color-blindness compatible) colors for all the roles. Here's that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From Discord:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[ . . . ]
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example Palette 1 (click to expand):
#B359F8#C0EBE6#1BCAFF#FA8D71#6FFF3DExample Palette 2 (click to expand):
#B359F8#F72070#074BF7#F7B920#39FA6DUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just want to pop in and say there's a tool that makes palettes with more than 5 colors somewhat easier:
Example expanded palettes of 8 colors:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea I'm having a lot of doubt though with some of the roles. I know I named them trying to cover all our bases(and a lot of them are solely placeholders until others came up with better names when we scrambled to get everything together).
Like in a ideal world(with renames) I'd suggest these in this order w/renames and different colors if needed. Obviously lumping in Dee's suggestion of the separation that we may not be the same on github in perms:
Now those ARE up for debate but that's my more definitive list imo. Bot roles not included bc these are a given and probably need to be moved to just below admins for sake of what it does w/bots. Just bc it CAN cause issues if any of the original ones are still used, which I doubt for the most part lol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dunno about renaming, since less change is better and none of them struck me as needing renaming.
The
@teamrole is what it is, either it refers to folks who do internal deliberations before presenting to the broader group and who are pretty much collectively responsible for admin (i.e. "the team" basically) or it isn't and we shouldn't have the role and go back to managing#teamchannel the way we were before. Either way, IMO. (Not that I would want go and change it again without everyone agreeing first. Less change unless it's outright broken, IMO.)Maybe there's some other option I'm not thinking of, but it doesn't all matter a ton. It mostly just think it needs to be functional, which it is currently.
I do think we can get 7 or 8 good distinct colors, though. And we can prefer to use the most similar ones to the existing ones where possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well I mention the team bit because of what @confused-Techie has mentioned and I think maybe even @Daeraxa? That it being explicitly named team can seem a bit exclusionary and contradictive to it's true nature. But I feel like the list I came up w/in that last post is the one to focus on. Albeit w/out recoloring admins/mods since I feel having team higher up negates it and is a good idea. Mods/Admins are still pingable like I've said a few times so yea.
I just see team as the general ping for help, but ideally people would go for the actual team over that bit. I'm just overthinking and wanting to fix a few things I feel were massive leftovers from my initial rushed setup of the discord and other things....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd warn against scope creep bringing up renaming and new teams during a PR, nothing wrong with it, just makes it harder to keep a solid goal in mind.
As for the other teams, I'm actually very actively against, any kind of coloration to the "Linux", "Windows", and "macOS" roles. If anything it may be prudent to bring up separately about disabling the general public from pinging these roles. I don't think these roles should stand out in any particular way, they already don't appear on the sidebar, and are nearly unused. Except for the rare instance we need to ping it for help in testing something. But as our server grows, there's now far to many people attached to those pings that are not present during the day to day, that the odd time it gets pinged for no reason, it seems to leave a few days of messages asking why they were pinged. So I don't think these roles should stand out at all, in any way, so they shouldn't be included in any kind of re-colorizing.