Update Community_Guidelines.md, Sections 3 and 4 (partial)#38
Update Community_Guidelines.md, Sections 3 and 4 (partial)#38bradtchapman wants to merge 3 commits intomacadminsdotorg:masterfrom
Conversation
Finished revising all other sections, and added section / TOC links. Wrote a bunch of new material for Sections 1, 2, and 3 to help with history, culture, and aiding new members in acclimating to the community.
Removed the term 'netiquette' from the Community Guidelines for clarity.
|
@bradtchapman thank you. I've started off with in-line comments for markdown structural changes that are needed. There are other changes I can see that I think the team will want to review in more detail. A mix of general structure, formatting as well as specific content/language as well (so a bit of everything). As this is a large PR, it may not make it into the CoC release next week as we likely won't have time to fully review all your changes by our deadline. Don't worry - it just means it'll sit here and we'll continue to work through/review/discuss etc after that. |
|
Good morning. Looking forward to others' comments and revisions on this. |
|
This is now based from the new master branch, ready to continue the review :) |
|
Minor typo in section 1: "Do not take the bait of disrepectful" (with apologies - noticing things like this is a curse). |
|
Hi @bradtchapman have you had a chance to review the comments above please? We are approaching the 30 day threshold and will likely need to close this if they aren't addressed/discussed further. Due to the size of this PR, it may also be best to re-submit a bunch of smaller ones - that way they can be reviewed/discussed individually which increases the chance of them being merged at the 30 day mark. Thank you. |
|
@neilmartin83 @arekdreyer @scriptingosx @Daz-wallace @ninxsoft @grahampugh @matdotcx I looked at the "Files Changed" tab and am not seeing the referenced "inline comments." If the consensus of the review panel is that they'd prefer me to submit these changes section-by-section, please advise on the most efficient way to do this (as a private message on Slack, not here in the comments, thanks). |
This is the beginning of my effort to expand upon the shorthand writing style of the community guidelines.
I felt that some key policy and etiquette details were missing, some clarification was needed in places, and I split up the description of the jobs-board and jobs-chat channels.
I completed this much on my phone in 45 minutes, but editing on GitHub is a pain in the ass on a mobile phone due to idiosyncrasies and/or bugs with GitHub where tapping the backspace button too rapidly ends up deleting more than I wanted to.
I will finish revising this on a computer this afternoon and over the weekend.