├── Deleting_Content.md ├── Incident_Process.md ├── LICENSE ├── README.md └── Vendor_Guidelines.md /Deleting_Content.md: -------------------------------------------------------------------------------- 1 | # Things Are Sometimes Better Unread 2 | 3 | In any large digitial community with a diverse group of humans, communication can break down. Whether it's unintential miscommunication or intentional boundary pushing, Administrators are occasionally requested to delete a message someone wrote in the public channels. 4 | 5 | # In Brief 6 | 7 | * Admins may delete messages that violate the Code of Conduct. 8 | * In non-trolling cases, the authors of those messages will be notified and may be given a chance to modify the message themselves. 9 | 10 | # Don't Be a Troll 11 | 12 | A troll is a member who starts flame wars or intentionally upsets other members by posting inflammatory and digressive, extraneous, or off-topic messages with the intent of provoking members into displaying emotional responses and normalizing tangential discussion, either for the troll's amusement or a specific gain. 13 | 14 | The determination of whether a message is trolling is often a subjective assessment by administrators, but there is a specific situation where The MacAdmins Slack has a zero-tolerance policy where all of the following are met: 15 | 16 | 1. A message which is perceived and/or reported as trolling, 17 | 2. Is posted by a non-contributing member with little to no other engagement elsewhere in the Slack, and, 18 | 3. Is posted via a deliberately fake account. 19 | 20 | Content posted in this fashion results in a no-warning expulsion of the offending account from The Mac Admins Slack. Trolling which does not meet this high bar is managed via the usual content review process. 21 | 22 | # Content Review Process 23 | 24 | Admins may come across or be notified of content on The Mac Admins Slack that violates the Code of Conduct. In some situations, this may lead to an Administrator deleting the message (or messages) that violate the CoC. Messages that are most likely to be deleted are commercial solicitations, disrespectful messages to other members, or links to disturbing or distressing content without appropriate measures to warn of or hide the content (including image uploads and unfurls). 25 | 26 | Ideally, another Mac Admins Slack member notices this content and contacts the original poster, who then modifies or deletes the message so that it is no longer problematic. In this case, no further Administrator action is required. The Mac Admins Slack allows members to edit messages up to 30 mins after posting. If 30 mins have elapsed, an Administrator can delete the message if requested - see [Administrators](#Administrators) section below 27 | 28 | If Administrator action is desired, due to lack of response or any other reason, an Administrator will notify the original poster of the violation and the need to reword (if within the 30 min edit window) or remove the problematic message. The Administrator will also specify a time after which Administrator action will be taken to delete the content if it is not addressed. This time may be as little as a few minutes, or as much as 24 hours. 29 | 30 | The determination of how much time is allowed is up to the acting Administrator, but the following context will be used to help determine the time before Administrator action: 31 | 32 | * How blatant the violation is 33 | * How likely it is to be seen by others (higher-volume channels get less time) 34 | * How likely it is to trigger negative reactions in others 35 | 36 | Additional consequences beyond the removal of content are up to the acting Administrator, per the same incident process found in the [Incident Process](https://github.com/macadminsdotorg/codeofconduct/blob/master/Incident_Process.md) 37 | 38 | # Direct Messages ("Private Messages") 39 | 40 | Direct messages between one or more members are private. Administators have no access to these messages and have no ability to delete them, but the above rules apply to this content. Violations should be addressed with Administators via the [Incident Process](https://github.com/macadminsdotorg/codeofconduct/blob/master/Incident_Process.md). 41 | 42 | Slack Workplace owners, of which only a limited set of the Admin Team are, have other tools (such as export and migration tools) that may provide access to private channels and DMs. 43 | 44 | ## Administrators 45 | 46 | The current roster of Administrators is maintained in the primary [Current List of Administrators](https://github.com/macadminsdotorg/slack-assets/blob/master/Admins.md) document. 47 | 48 | --- 49 | 50 | Based upon https://github.com/randsleadershipslack/documents-and-resources/blob/main/deleting-content.md 51 | 52 | VXXX of this Code of Conduct was published on XXXXX, 2022. You can see all prior versions of this artifact [here](https://github.com/macadminsdotorg/codeofconduct/commits/master/README.md). -------------------------------------------------------------------------------- /Incident_Process.md: -------------------------------------------------------------------------------- 1 | 2 | # The Mac Admins Slack Incident Process 3 | 4 | Our brief governing philosophy: 5 | 6 | *Please strive to resolve the situation by yourself; if you think that isn’t possible or appropriate, please contact an Admin immediately.* 7 | 8 | ## Something is Off 9 | 10 | A significant part of the Mac Admins Slack Admins job is the management of incidents on the Mac Admins Slack, but ideally the community (that’s you) has both the tools and the desire to resolve many situations without Admin support. 11 | 12 | *As the Mac Admins Slack is a mature community, we find that the community naturally highlights CoC violations and they are resolved organically. If you are not comfortable with personally raising any violations of the CoC, please go ahead and jump to “It’s Admin O’Clock”.* 13 | 14 | The Mac Admins Code of Conduct (“CoC”) exists to give members a model idea of what is and isn’t acceptable in Mac Admins Slack including behaviour, marketing activity, and etiquette. If you experience strange behaviour in a channel and are wondering if it’s acceptable, please first consult the CoC. 15 | 16 | With CoC clarity in hand, please contact the member(s) and explain: 17 | 18 | 1. This is the activity I saw which I have an issue with, 19 | 2. It’s not allowed by the CoC, and, 20 | 3. Let’s figure out how to resolve it. 21 | 22 | Ideally, the above discussion can help resolve the situation. It often does. If does not, if you are not comfortable contacting the member(s), or if this is an obvious heinous situation, jump to “ It’s Admin O’Clock”. 23 | 24 | ## It’s Admin O’Clock 25 | 26 | Administrators can be contacted directly ([Current List of Administrators](https://github.com/macadminsdotorg/slack-assets/blob/master/Admins.md)) or in the [#ask-about-this-slack channel](https://macadmins.slack.com/archives/C06PS0JKA). Please choose the path most comfortable for you. 27 | 28 | When you contact an Administrator(s), provide the following: 29 | 30 | 1. The activity you saw that you have an issue with, 31 | 2. If applicable, the CoC violation. 32 | 33 | Things to know: 34 | 35 | * The Administrators are committed to a first response within 24 hours. Usually faster. If you directly contact a single Admin, it could be longer due to time zone differences and work schedules. 36 | * [#ask-about-this-slack channel](https://macadmins.slack.com/archives/C06PS0JKA) contains all the of the Administrators and is public. If you’re filing a formal incident, we strongly suggest directly contacting an Admin as formal incidents are confidential to the admins. 37 | 38 | Once you’ve contacted an Administrator, they’ll help you triage the incident. 39 | 40 | ## Formal Incident Process 41 | 42 | In the case of a formal incident being reported, there are two possible resolution paths: 43 | 44 | 1. Raising a concern to the Administrator to give them context, or, 45 | 2. Filing a formal complaint that will result in Administrative action. 46 | 47 | In both cases, the reporter needs to provide the following information to the Administrator: 48 | 49 | 1. What’s the nature of the incident or Code of Conduct violation? 50 | 2. Who is involved in this incident? 51 | 3. What material supports this situation? 52 | 4. Any privacy concerns? (Reporter consent is required before sharing any information regarding the incident) 53 | 54 | With this information in hand, the Administrator will: 55 | 56 | 1. Work to determine whether this is a raised concern or a formal complaint with the reporter. In the case of a raised concern, the understanding is there may be no action other than administrative awareness. 57 | 2. Ask clarifying questions of the reporter because every incident is different. 58 | 3. Work with publicly available content to confirm the report. 59 | 4. Talk with their fellow administrators to gather perspective. 60 | 5. The Administrator may deem it necessary to talk to the accused member(s) to gather additional perspective. 61 | 62 | With this information in hand, the Administrator will determine a consequence. Consequences include but are not limited to: 63 | 64 | 1. A Strike 65 | * The Mac Admins Slack operates on a three strike system whereby non-suspending CoC violations can result in one or more strikes. Administrators will use their judgement and historical precedent in determining what constitutes a strike. When a member receives three strikes, they will be suspended from the Mac Admins Slack for a period of time or permanently depending on the violation. Multiple strikes can be assessed depending on the violation. 66 | * We do not have a definition of what does and does not constitute a strike. 67 | * As of October 2022, we are keeping a record of all administrative activity to help calibrate strikes. This record will be a privately shared Googlesheet and is accessible only by the Admin Team. 68 | * Any activity to prior to the formal recording of strikes will not be included in the record of strikes. 69 | 2. Do Not Contact 70 | * A member may not contact (in any fashion, messages or emoji) either publicly or privately one more other members of the Slack for a predetermined period of time. 71 | 3. Temporary suspension 72 | * A member is suspended from The Mac Admins Slack for a predetermined period of time. 73 | 4. Permanent suspension 74 | * A member is permanently banned from The Mac Admins Slack 75 | 76 | For any type of suspension, the admins will conduct a private vote based on the incident. Majority wins. 77 | 78 | With the defined incident and consequence in hand, the Administrator will present the following to the accused member: 79 | 80 | * This is what occurred. 81 | * This incident is confidential. 82 | * This is how I confirmed what occurred. 83 | * This is what I decided in terms of consequence. In the case of a non-ban action, explain the terms of Do Not Contact, Strikes, Etc. 84 | * For strikes, members will be alerted to the strike policy and the number of current strikes they have. 85 | * For Do Not Contact, members will receive the time period when they can not contact other member(s) 86 | * For Temporary Suspension, members will receive the time period when they can not be a part of The Mac Admins Slack. 87 | * For Permanent Suspension, members will receive the content above and then permanent removed from The Mac Admins Slack. 88 | 89 | The Administrators are committed to resolve incidents **within five working days**. 90 | 91 | ## Administrators 92 | 93 | The current roster of Administrators is maintained in the primary [Current List of Administrators](https://github.com/macadminsdotorg/slack-assets/blob/master/Admins.md) document. 94 | 95 | --- 96 | 97 | Based upon https://github.com/randsleadershipslack/documents-and-resources/blob/main/incident-process.md 98 | 99 | VXXX of this Code of Conduct was published on XXXXX, 2022. You can see all prior versions of this artifact [here](https://github.com/macadminsdotorg/codeofconduct/commits/master/README.md). -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Welcome to the Mac Admins Slack. 2 | 3 | The Mac Admins Slack is a global online community of people who manage Apple devices and services at large and small scales. The community is built around public and private channels focusing on managing Apple devices and services. While many channels are not focused specifically on managing Apple devices and services, all community participants are asked to act as professionals and must comply with the following Code of Conduct(CoC). 4 | 5 | All principles in this CoC are important and enforceable. The Mac Admins Slack Admin Team will enforce this code throughout all channels within the Slack. 6 | 7 | 8 | 9 | ## Introduction 10 | The Mac Admins Slack is available as a means of collaboration for Apple device administrators, enthusiasts, and developers to interact with one another. It is meant to provide a safe, friendly community along side the already well established user forums, Facebook groups, and mailing lists to help facilitate more real-time collaboration when possible. 11 | 12 | We hope that you find the community to be enriching to your personal and professional lives, and above all else a place of camaraderie where our collective knowledge and differences are celebrated in a positive, welcoming environment. 13 | 14 | Thank you for following this code of conduct. We reserve the right to amend or change the code of conduct at any time and encourage you to periodically review these guidelines to ensure a safe environment for all. 15 | 16 | 17 | -[The Mac Admins Slack Administrative Team](https://github.com/macadminsdotorg/slack-assets/blob/master/Admins.md) 18 | 19 | 20 | # Table of Contents 21 | 22 | - [Introduction](#introduction) 23 | - [Table of Contents](#table-of-contents) 24 | - [Code Of Conduct](#code-of-conduct) 25 | - [Short Version:](#short-version) 26 | - [Long Version:](#long-version) 27 | - [Respect](#respect) 28 | - [Harassment-free](#harassment-free) 29 | - [Privacy](#privacy) 30 | - [Read the Room](#read-the-room) 31 | - [Direct Message Etiquette](#direct-message-etiquette) 32 | - [Content Review Process](#content-review-process) 33 | - [Resolve Peacefully](#resolve-peacefully) 34 | - [Additional Consequences](#additional-consequences) 35 | - [Vendor Guidelines](#vendor-guidelines) 36 | - [Press Guidelines](#press-guidelines) 37 | - [Reporting](#reporting) 38 | - [Administrators](#administrators) 39 | - [Administrator Information Access](#administrator-information-access) 40 | - [Administrative Team Guidelines](#administrative-team-guidelines) 41 | - [Contributions and Modifications](#contributions-and-modifications) 42 | # Code Of Conduct 43 | 44 | # Short Version: 45 | 46 | 47 | All are welcome to participate in the Mac Admins Slack as long as the tenets of this Code of Conduct are adhered to. 48 | 49 | Be a valuable postive contributor to this community. 50 | 51 | 52 | Be respectful of others, ask people to stop if you are bothered; respect privacy; understand this community is primarily not-for-profit, and attempt to resolve issues without Administrators, but if you can't resolve an issue, you can contact the Administrators. If you violate this Code of Conduct, it will be made clear to you, and you may be asked to leave the Mac Admins Slack. 53 | 54 | All community members are expected to: 55 | 56 | * respect differences in people, their ideas and opinions 57 | * treat one another with dignity and respect 58 | * respect and treat others fairly, regardless of race ancestry, place of origin, colour, ethnic origin, citizenship, religion, gender, sexual orientation, age or disability 59 | * respect the rights of others 60 | 61 | Additionally, if you are a reporter or a member of the press: 62 | 63 | * you must have that information listed in your profile - documentation on how to do that is [available here](https://slack.com/help/articles/204092246-Edit-your-profile) 64 | * if you want to interview someone about something, you need to ask permission to interview them and inform them about where their comments may end up being published prior to the start of the interview. 65 | 66 | Everyone is welcome to participate, and no judgement will be made on members of the greater Mac community who are not a part of the community. 67 | 68 | 69 | # Long Version: 70 | 71 | ## Respect 72 | 73 | The Mac Admins Slack is an inclusive environment based on treating all individuals respectfully, regardless of gender or gender identity (including transgender status), sexual orientation, age, disability, nationality, ethnicity, religion (or lack thereof), political affiliation, or career path. 74 | 75 | We value respectful behavior above individual opinions. 76 | 77 | Respectful behavior includes but is not limited to: 78 | 79 | * Be considerate, kind, constructive, and helpful. 80 | * Avoid demeaning, discriminatory, harassing, hateful, or physically threatening behavior, speech, and imagery. 81 | * Due regard for the feelings, wishes, rights, and traditions of others. 82 | 83 | If you're unclear if a communication, action, or behavior is respectful, ask someone instead of assuming. No, really. Just ask the ([Administrators](https://github.com/macadminsdotorg/slack-assets/blob/master/Admins.md)) publicly via [#ask-about-this-slack channel](https://macadmins.slack.com/archives/C06PS0JKA) or privately via Direct Message. We'd rather hear from you than hear about something you said or did after the fact, and we are here to help. 84 | 85 | Don't be a bystander, be a leader. Role model respectful behavior, but also help to address disrespect when you see it within your community. 86 | 87 | **Consequence**: Disrespectful behavior outside this community by active members may be considered a violation of this code of conduct at the Administrators' discretion. 88 | 89 | ## Harassment-free 90 | 91 | 92 | The Mac Admins Slack is dedicated to providing a harassment-free experience for everyone, regardless of (but not limited to): gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion, or preferred technological ecosystem. 93 | 94 | 95 | We do not tolerate harassment of Slack participants in any form. Sexual language and imagery is not appropriate for any venue. Slack participants violating these rules may be sanctioned or expelled from the Mac Admins Slack at the discretion of the Administrative Team. 96 | 97 | Harassment includes, but is not limited to: 98 | 99 | * Offensive and/or unwelcome comments related to gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion, or preferred technological ecosystem. 100 | * Sexual images in public spaces 101 | * Deliberate intimidation, stalking, or following 102 | * Harassing photography or recording 103 | * Sustained disruption of talks or other events 104 | * Physical contact and simulated physical contact (e.g. textual descriptions like “hug” or “backrub”) without consent or after a request to stop 105 | * Unwelcome sexual attention including gratuitous or off-topic sexual images or behaviour 106 | * Hate speech 107 | * Purposeful psychological manipulation of any kind 108 | * Spamming of GIFs 109 | * Advocating for, or encouraging, any of the above behaviour 110 | * Direct messages or postings in channels/private groups of an overly sales/advertising/spam manner ([additional vendor guidelines](https://github.com/macadminsdotorg/codeofconduct/blob/master/Vendor_Guidelines.md)) 111 | 112 | ## Privacy 113 | 114 | Protect IP and legally-protected information. This community is not a public space. However, no one has signed a non-disclosure agreement ("NDA") to participate, and you should not presume anything you say here will remain private, so act accordingly. 115 | 116 | If you want to disclose anything discussed here in a public channel publicly, use the [Chatham House Rule](https://www.chathamhouse.org/about/chatham-house-rule) as the guideline ("participants are free to use the information received, but neither the identity nor the affiliation of the speaker(s), nor that of any other participant, may be revealed"). 117 | 118 | For attribution of specific content found on this Slack on public channels, we ask that you ask the originator of the content for permission. If you don't receive consent in a reasonable time, we ask that you credit the "Mac Admins Slack." 119 | 120 | **Consequence**: Sharing content from private channels is discouraged without permission of the private channel. 121 | 122 | ## Read the Room 123 | 124 | Once onboard, you will likely find yourself in a popular channel with many members who sound like we've figured it out. We haven't. While advice on one channel might read definitive, it is one member's lessons, interpretations and learnings from their Mac Admin experience. While there is a diverse set of experiences within this community, we continue to learn at every level of expertise. The daily practice of being a Mac Admin is more art than science. 125 | 126 | This is a large community with many different humans populating hundreds of channels. Different channels have organically developed distinct personalities. Before posting in a channel with hundreds of members, we suggest you take the time to read the room. Specifically: 127 | 128 | * Read the last couple of days of messages. 129 | * Examine the channel topic for helpful tips. 130 | * Click on the channel details and read the about section to see how many members are present, what messages have already been pinned, and what files have been shared. 131 | * Use Slack's search feature. Your question has problably already been discussed, or a least something similar. The results might give you the answer or help you frame your question better. 132 | 133 | **Consequence**: Posting the same message to multiple channels is spamming. Don't spam. 134 | 135 | ## Direct Message Etiquette 136 | 137 | A direct message ("DM") is a private message to one or more other members. Sending a DM to another member you don't know might be jarring for the receiver. Before sending a DM to a member you've never contacted, consider the following: 138 | 139 | * Is it obvious to the other member why I am contacting them privately? If not, should I provide context, such as a public post? 140 | * Could this message be considered unsolicited spam? If so, should you be sending it? 141 | 142 | **Consequence**: Unsolicited DMs are likely Code of Conduct violations, especially with a commercial flavor. 143 | 144 | ## Content Review Process 145 | 146 | The Administrators may come across or be notified of Mac Admins Slack content violating the Code of Conduct. In some situations, this may lead to an Administrator deleting the message (or messages) that violate the CoC. Messages most likely to be deleted are commercial solicitations, disrespectful messages to other members, or links to disturbing or distressing content without appropriate measures to warn of or hide the content (including image uploads and unfurls). 147 | 148 | Ideally, another Mac Admins Slack member notices this content and contacts the original poster, who then modifies or deletes the message so that it is no longer problematic. In this case, no further Administrator action is required. Suppose Administrator action is desired due to lack of response or any other reason. In that case, an Administrator will notify the original poster of the violation and the need to reword or remove the problematic message. The Administrator will also specify a time after which Administrator action will be taken to delete the content if it is not addressed. This time may be as little as a few minutes or as much as 24 hours. 149 | 150 | 151 | ## Resolve Peacefully 152 | 153 | As a large online community, we believe peer-to-peer discussions, feedback, and corrections can help build a stronger, safer, more informed, and more welcoming community. 154 | 155 | If you see someone violating any part of this Code of Conduct, we urge you to respectfully dissuade them from such behavior using specifics from this document as guidelines. Expect that others in the community wish to help keep the community respectful and welcome your input. 156 | 157 | If you experience disrespectful behavior toward yourself or anyone else and feel unable or unwilling to respond or resolve it respectfully (for any reason), please immediately bring it to the attention of an Administrator. We want to hear from you about anything that you feel is disrespectful, threatening, or just something that could make someone feel distressed. We will listen and work to resolve the matter with your help promptly. 158 | 159 | Should you catch yourself behaving disrespectfully, or be confronted as such, listen intently, own up to your words and actions, and apologize accordingly. No one is perfect, and even well-intentioned people make mistakes. How you handle them and avoid repeating them in future matters. We are here to learn as professionals. 160 | 161 | ## Additional Consequences 162 | 163 | If you cannot resolve a situation peacefully, please refer to our [Incident Process](https://github.com/macadminsdotorg/codeofconduct/blob/master/Incident_Process.md) and choose a course of action that suits the situation. 164 | 165 | Suppose the Administrators determine that a member is violating any part of this Code of Conduct. In that case, they may take any action they deem appropriate, up to and including expulsion and exclusion from the Mac Admins Slack. 166 | 167 | As Administrators, we will seek to resolve conflicts peacefully and in a manner that is positive for the community. This Code of Conduct documents everyday situations we've seen, but we can't foresee every situation. If in the Administrator's judgment, the best thing to do is to ask a disrespectful individual to leave, we will do so. 168 | 169 | We expect participants to follow these rules in all public and private channels (including direct messages). 170 | 171 | ## Vendor Guidelines 172 | 173 | See [Vendor Guidelines](https://github.com/macadminsdotorg/codeofconduct/blob/master/Vendor_Guidelines.md) 174 | 175 | ## Press & Media Guidelines 176 | 177 | Additionally, if you are a reporter or a member of the press or media: 178 | 179 | * you must have that information listed in your profile - documentation on how to do that is [available here](https://get.slack.help/hc/en-us/articles/204092246-Edit-your-profile) 180 | * if you want to interview someone about something, you need to ask permission to interview them and inform them about where their comments may end up being published prior to the start of the interview. 181 | 182 | ## Reporting 183 | 184 | If you are being harassed, notice that someone else is being harassed, or have any other concerns, and you feel comfortable speaking with the offender, please inform the offender that they have affected you negatively. Often, the offending behavior is unintentional, and the accidental offender and offended will resolve the incident by having that initial discussion. As a world-wide community, we recognize that there are inherent language barriers we must work together to overcome. 185 | 186 | 187 | The Mac Admins Slack Workspace Administrative Team recognizes that there are many reasons speaking directly to the offender may not be workable for you (all reasons are valid, we will never ask you to explain nor defend your reasons). If you don't feel comfortable speaking directly with the offender *for any reason*, please report violations directly to a member of the Administrative Team. 188 | 189 | ## Administrators 190 | 191 | [Current List of Administrators](https://github.com/macadminsdotorg/slack-assets/blob/master/Admins.md). 192 | 193 | The Administrative Team will handle all reports with discretion. 194 | 195 | If a party to a dispute is also a member of the Admin team, that person may have no role in the dispute resolution process except as a party; forfeiting any involvement in the enforcement and resolution process. It is the responsibility of that person to immediately inform the Admin team of the conflict. The only way a conflict of interest is applicable is when a person involved in the mediation/resolution process is also involved in the conflict. As members, we are entrusted to make decisions in the best interest of the community and set aside personal interest for the best interest of our community as a whole. 196 | 197 | If you have concerns regarding this Slack, please feel free to contact the Administrative Team and we will work to understand and address them respectfully and with an appropriate level of privacy in the given situation. 198 | 199 | ## Administrator Information Access 200 | 201 | As part of the role, Administrators have information not available to all users. This information includes: 202 | 203 | * A member provides email addresses as part of our sign-up process. 204 | * Information contained within member requests to join the community. This might include email, name, and occupation. 205 | * Access log information provided by the Slack administrator interface. This includes name, login times, login device, and IP. 206 | 207 | Administrators do not have standing access to private channels unless they are members of that channel. 208 | 209 | Slack Workspace owners, of which only a limited set of the Admin Team are, have other tools (such as export and migration tools) that may provide access to private channels and DMs. As per the privacy section above, you should not presume anything you say here will remain private, so act accordingly. 210 | 211 | As part of Code of Conduct investigations, Administrators may choose to access this information. Administrators may also request information from private channels from current channel members to investigate a Code of Conduct violation. 212 | 213 | Administrators may use the above information as part of a Code of Conduct investigation. Usage of this information unrelated to administrator work is forbidden and will be treated as a Code of Conduct violation. 214 | 215 | ## Administrative Team Guidelines 216 | 217 | The Mac Admins Slack Administrative Team are here to ensure that the community runs within the spirit and guidelines of the [Code Of Conduct (CoC)](https://github.com/macadminsdotorg/codeofconduct), and to manage the technical aspects of keeping the Mac Admins Slack instance running. We are also fellow Mac Admins, so when it comes to products, how to do things, why to do things etc - please take our input only as fellow Mac Admins and not as statements or endorsements from the Administrative Team. 218 | 219 | On all subjects, other than running of the Mac Admins Slack and the [CoC](https://github.com/macadminsdotorg/codeofconduct), the Administrative Team’s opinions are their own and do not necessarily reflect those of the rest of Mac Admins Slack Administrative Team or the Mac Admins community. 220 | 221 | ## Contributions and Modifications 222 | 223 | Anyone may recommend modifications to this Code of Conduct by opening a pull request [here](https://github.com/macadminsdotorg/codeofconduct). The request will be reviewed by the admin team before being approved and merged. 224 | 225 | This Code of Conduct is released under the [CC0 public domain license](https://creativecommons.org/publicdomain/zero/1.0/). 226 | 227 | V2.0 RC1 of this Code of Conduct was published December, 2022. You can see all prior versions of this artifact [here](https://github.com/macadminsdotorg/codeofconduct/commits/master/README.md). -------------------------------------------------------------------------------- /Vendor_Guidelines.md: -------------------------------------------------------------------------------- 1 | # Vendor Guidelines 2 | 3 | Vendors can make up an important part of our community, and our Slack Workspace provides a unique method to engage with a user base directly, but vendors should adhere to the following guidelines to help ensure they do not engage in behaviour that violates our Code of Conduct. 4 | 5 | ## Direct messages 6 | 7 | It is not permitted to direct message or use other communications tools to contact a member of our community for the purposes of promoting your product without their clear permission beforehand. 8 | 9 | ### What is okay 10 | 11 | > Vendor: Hey @personX, is it ok if I message you about #productY? 12 | 13 | > personX: Sure, that's fine. 14 | 15 | ### What is not okay 16 | 17 | * Sending direct messages or using outside communications tools to contact the user when they have responded in any manner that could be taken as a negative response to a posting in a public channel like the above. 18 | 19 | ## Promoting your product in public channels 20 | 21 | If you wish to promote your product in a public channel, it is important that: 22 | 23 | * Your message is relevant to the current discussion topic. For example, if you make a disk partitioning tool, it may be useful to post a link to your own channel if the current discussion is on that topic. 24 | * Your message cannot be considered 'spam' - in addition to being on topic, it shouldn't be posted repeatedly, either in the same channel or in multiple channels. 25 | 26 | ### What is okay 27 | 28 | > personX: I'm looking for a tool that performs X - does anyone have any ideas? 29 | 30 | > Vendor: Hey @personX, I work for companyY and we make something that may help. Maybe you would like to come over to #companyY? 31 | 32 | ### What is not okay 33 | 34 | > [Unrelated conversation] 35 | 36 | > Vendor: So is it true that : The new MacOS eliminates IMAGING… Deploy Studio??? [competitor] or OurProduct.com have possible the solutions? 37 | --------------------------------------------------------------------------------