├── CODE_OF_CONDUCT.md ├── COMMUNITY_GUIDELINES.md └── README.md /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Platform Engineering Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members of the Platform Engineering Community pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | 40 | ## Events 41 | 42 | For events please refer to: https://platformcon.com/code-of-conduct. 43 | 44 | ## Enforcement Responsibilities 45 | 46 | Community leaders are responsible for clarifying and enforcing our standards of 47 | acceptable behavior and will take appropriate and fair corrective action in 48 | response to any behavior that they deem inappropriate, threatening, offensive, 49 | or harmful. 50 | 51 | Community leaders have the right and responsibility to remove, edit, or reject 52 | comments, commits, code, slack messages, wiki edits, issues, and other contributions that are 53 | not aligned to this Code of Conduct, and will communicate reasons for moderation 54 | decisions when appropriate. 55 | 56 | ## Scope 57 | 58 | This Code of Conduct applies within all community spaces, and also applies when 59 | an individual is officially representing the community in public spaces. 60 | Examples of representing our community include using an official e-mail address, 61 | posting via an official social media account, or acting as an appointed 62 | representative at an online or offline event. 63 | 64 | ## Enforcement 65 | 66 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 67 | reported to the community leaders responsible for enforcement in anonymous form at 68 | https://forms.gle/qpQ7anZsDVcqtuHa7 69 | 70 | All complaints will be reviewed and investigated promptly and fairly. 71 | 72 | All community leaders are obligated to respect the privacy and security of the 73 | reporter of any incident. 74 | 75 | ## Enforcement Guidelines 76 | 77 | Community leaders will follow these Community Impact Guidelines in determining 78 | the consequences for any action they deem in violation of this Code of Conduct: 79 | 80 | ### 1. Correction 81 | 82 | **Community Impact**: Use of inappropriate language or other behavior deemed 83 | unprofessional or unwelcome in the community. 84 | 85 | **Consequence**: A private, written warning from community leaders, providing 86 | clarity around the nature of the violation and an explanation of why the 87 | behavior was inappropriate. A public apology may be requested. 88 | 89 | ### 2. Warning 90 | 91 | **Community Impact**: A violation through a single incident or series 92 | of actions. 93 | 94 | **Consequence**: A warning with consequences for continued behavior. No 95 | interaction with the people involved, including unsolicited interaction with 96 | those enforcing the Code of Conduct, for a specified period of time. This 97 | includes avoiding interactions in community spaces as well as external channels 98 | like social media. Violating these terms may lead to a temporary or 99 | permanent ban. 100 | 101 | ### 3. Temporary Ban 102 | 103 | **Community Impact**: A serious violation of community standards, including 104 | sustained inappropriate behavior. 105 | 106 | **Consequence**: A temporary ban from any sort of interaction or public 107 | communication with the community for a specified period of time. No public or 108 | private interaction with the people involved, including unsolicited interaction 109 | with those enforcing the Code of Conduct, is allowed during this period. 110 | Violating these terms may lead to a permanent ban. 111 | 112 | ### 4. Permanent Ban 113 | 114 | **Community Impact**: Demonstrating a pattern of violation of community 115 | standards, including sustained inappropriate behavior, harassment of an 116 | individual, or aggression toward or disparagement of classes of individuals. 117 | 118 | **Consequence**: A permanent ban from any sort of public interaction within 119 | the community. 120 | 121 | ## Attribution 122 | 123 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 124 | version 2.0, available at 125 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 126 | 127 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 128 | enforcement ladder](https://github.com/mozilla/diversity). 129 | 130 | [homepage]: https://www.contributor-covenant.org 131 | 132 | For answers to common questions about this code of conduct, see the FAQ at 133 | https://www.contributor-covenant.org/faq. Translations are available at 134 | https://www.contributor-covenant.org/translations. 135 | -------------------------------------------------------------------------------- /COMMUNITY_GUIDELINES.md: -------------------------------------------------------------------------------- 1 | # Platform Engineering Community Guidelines 2 | 3 | Welcome to the [Platform Engineering Community](http://www.platformengineering.org "Platform Engineering Community"). 4 | 5 | This is a dedicated space for you to network with others, expand your knowledge and ask questions about Platform Engineering. 6 | You could be here to find a job, an answer to a problem, to inquire about a tool or study a use case for building your platform. 7 | 8 | Our mission is to nurture and grow the [Platform Engineering Community](http://www.platformengineering.org "Platform Engineering Community") and we are committed to hosting a space where our actions align with our vision and purpose. 9 | 10 | We developed the following community guidelines to provide guidance on how to engage with other users in the community and what you should expect from others. 11 | 12 | *These guidelines are first and foremost useful for the Community, so the Community will be the main actor responsible for manteinance and continuous review. Everyone is welcome to participate in this document and comment/ask for changes.* 13 | 14 | ## The PE Slack Channel 15 | 16 | The Slack channel is the main community platform. With more than 8000 people participating (Dec 2022), it represents a good picture of the current 17 | platform engineering community. 18 | 19 | The basic rules for the Slack channel in regards to promotion and product are: 20 | * Things you can do: Post links to your own website/product, promote your talks, promote your meetups, connect with others in the allocated spaces as specified below. 21 | * Things you can't do: Only post self-promotional posts/comments; send unsolicited private messages to members about your self-promotional content; use redirects to obfuscate your self-promotional content. 22 | 23 | It is comprised of a list of channels that are represented down below (*this list is not complete and is ever-changing dependent on community wishes*): 24 | 25 | **Generic - Community leaders led:** 26 | 27 | * *general*: this channel scope is to drive conversations, ask questions and discuss recent trends in the community or in the industry. It should be free of product-focussed conversations, conferences CTAs and sales-y pitches. 28 | * *intros*: this channel is for presenting yourself and your role when first entering the community. 29 | * *jobs*: this channel scope is to post job ads or to look for a job. 30 | * *local chapters*: these channels are community-led and populated and should promote local meetups and interactions in the community. A pinned message will collect all the local chapters already open. It will be updated monthly. 31 | 32 | **Tech based:** 33 | * *platform-tech*: this channel is for talks about tools, requests for feedback on technology. 34 | * *terraform*: this channel is focussed on terraform, support questions and tools integration. 35 | * *kubernetes*: this channel is focussed on kubernetes, support questions and tools integration. 36 | 37 | **New channels proposal:** 38 | * *events and meetups*: this channel will be the place to find talks, meetups, events. 39 | * More TBD 40 | 41 | **Channels to be deprecated:** 42 | * More TBD 43 | 44 | ## Meetups groups 45 | 46 | This is the list to all the Platform Engineering meetups group already existing: 47 | 48 | ### NAMER 49 | * ATX 50 | * SF & Bay Area 51 | * NYC 52 | * Toronto 53 | * Seattle 54 | * Vancouver 55 | * Denver 56 | * Los Angeles 57 | * Washington DC 58 | * Dallas 59 | 60 | ### EMEA 61 | * Berlin 62 | * London 63 | * Munich 64 | * Dublin 65 | * Stockholm 66 | * Copenhagen 67 | * Amsterdam 68 | * Barcelona 69 | * Tel Aviv 70 | 71 | ### LATAM 72 | * Sao Paulo 73 | * Buenos Aires 74 | 75 | ### APAC 76 | * Singapore 77 | * Sydney 78 | * Melbourne 79 | * New Delhi 80 | * Bangalore 81 | 82 | This list can be further populated and co-owned by anyone in the community. Co-owning a meetup group comes with responsibility for accepting meetup requests and amplifying community initiatives in that area. 83 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Welcome to the Platform Engineering Community 2 | 3 | A place for the [Platform Engineering Community Guidelines](https://github.com/InternalDeveloperPlatform/Platform-Engineering-Community/blob/main/COMMUNITY_GUIDELINES.md) and [Code of Conduct](https://github.com/InternalDeveloperPlatform/Platform-Engineering-Community/blob/main/CODE_OF_CONDUCT.md). 4 | 5 | To contribute please open an issue or comment in the in either the Community Guidelines or the Code of Conduct. 6 | The issue/comment will be reviewed asap by a Community leader. 7 | --------------------------------------------------------------------------------