-
-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #538 from json-schema-org/benjagm-contributing-exp
Issue to review the contributing document and add a triage process proposal
- Loading branch information
Showing
4 changed files
with
145 additions
and
32 deletions.
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| # Community Manager Role | ||
|
|
||
| Community managers are responsible for managing many aspects of the JSON Schema community. The goal is to achieve and maintain a healthy and growing JSON Schema community where everyone feels welcome and is encouraged to share knowledge and learn from each other. This document outlines the responsibilities of a community manager and the process involved in becoming one. | ||
|
|
||
| ### Responsibilities | ||
|
|
||
| A community manager has the following responsibilities: | ||
|
|
||
| * Manage the JSON Schema Open Community Working Meetings: | ||
| * Host the call. | ||
| * Publish the community call recording to the YouTube channel. | ||
| * Manage the Slack community: | ||
| * Organize and monitor Slack channels. | ||
| * Ensure community rules are being followed. | ||
| * Help new Slack users find the right channels & answers. | ||
| * Announce JSON Schema updates and events. | ||
| * Review issues & pull requests in the community repository. | ||
| * Review and publish JSON Schema blog posts submitted by the community. | ||
| * Report on community health, growth trends, and top issues to maintainers and STC. | ||
| * Propose new partnerships with other adjacent communities to STC and manage them. | ||
| * Manage community analytics tools, including Plausible and CommonRoom.io. | ||
| * Manage the social media accounts: [@jsonschema](https://twitter.com/jsonschema) Twitter and [@jsonschema](https://twitter.com/jsonschema) and [@jsonschema](https://www.linkedin.com/company/jsonschema) Linkedin: | ||
| * Asking the community for community call topics. | ||
| * Announcing community calls (one day before and one hour before the call). | ||
| * Announcing that the recording of the community call is available on YouTube. | ||
| * Announcing JSON Schema updates like tooling or adopters. | ||
| * Announcing new JSON Schema blog posts. | ||
| * Reposting relevant tweets from the community. | ||
| * Manage the [@JSONSchemaOrgOfficial](https://www.youtube.com/@JSONSchemaOrgOfficial) YouTube account. | ||
| * Launch and manage Community programs. | ||
|
|
||
| ### Duties that require STC approval | ||
|
|
||
| * Add new analytics tools | ||
|
|
||
| ### Know more | ||
|
|
||
| Please join the `#community-mgmt` slack channel using this [link](#community-mgmt) if you like to know more. | ||
|
|
||
| ### Atribution | ||
|
|
||
| This document has been inspared by the [DAPR Community Manager document](https://github.com/dapr/community/blob/master/COMMUNITY-MANAGER.md). |
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,48 +1,97 @@ | ||
| # JSON Schema Community | ||
| [](https://json-schema.org) | ||
|
|
||
| <br/> | ||
| <p> | ||
| <a href="https://github.com/json-schema-org/website/graphs/contributors" alt="JSON Schema GitHub website contributors"> | ||
| <img src="https://img.shields.io/github/contributors/json-schema-org/website?color=orange" /> | ||
| </a> | ||
| <a href="https://github.com/json-schema-org/website/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22" alt="Good First JSON Schema issue"> | ||
| <img src="https://img.shields.io/github/issues/json-schema-org/website/good%20first%20issue.svg?color=%23DDDD00" /> | ||
| </a> | ||
| <a href="https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md" alt="Contributor Covenant"> | ||
| <img src="https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg" /> | ||
| </a> | ||
| <a href="https://www.repostatus.org/#active" alt="Repo status"> | ||
| <img src="https://www.repostatus.org/badges/latest/active.svg" /> | ||
| </a> | ||
| <a href="https://github.com/json-schema-org/community/discussions" alt="Discussions"> | ||
| <img src="https://img.shields.io/github/discussions/json-schema-org/community" /> | ||
| </a> | ||
| <a href="https://opencollective.com/json-schema" alt="Financial Contributors on Open Collective"> | ||
| <img src="https://opencollective.com/json-schema/all/badge.svg?label=financial+contributors" /> | ||
| </a> | ||
| <a href="https://adr.github.io" alt="part of ADR"> | ||
| <img src="https://img.shields.io/badge/part_of-ADR-blue" /> | ||
| </a> | ||
| <a href="https://json-schema.org/slack" alt="JSON Schema Slack"> | ||
| <img src="https://img.shields.io/badge/[email protected]?logo=slack&color=yellow" /> | ||
| </a> | ||
| </p> | ||
|
|
||
| [](https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md) | ||
| [](https://www.repostatus.org/#active) | ||
| [](https://opencollective.com/json-schema) | ||
| # JSON Schema Community | ||
|
|
||
| [](https://adr.github.io) | ||
|  | ||
| Welcome to the JSON Schema community! You've arrived at the perfect place to begin your journey as a contributor. Whether it's assisting with documentation, writing a blog post, enhancing the website, delivering presentations, or any other form of contribution, there's plenty of opportunities to get involved in the project. We are a friendly, collaborative group and look forward to working together. | ||
|
|
||
| # What is this repo? | ||
| - 👋 [Introduction](#introduction) | ||
| - 💬 [Discussions and slack](#discussions-and-slack) | ||
| - 🗓 [Community meetings](#community-meetings) | ||
| - 🌱 [Getting involved](#getting-involved) | ||
|
|
||
| ## Introduction | ||
| This repo is a place to discuss and debate various aspects of running the JSON Schema organisation, how we work as a community, and our expectations. | ||
|
|
||
| The discussions will primarily take place using [Github Discussions](https://github.com/json-schema-org/community/discussions) for this repo. | ||
| ### Discussions and Slack | ||
|
|
||
| Reach out with any questions you may have and we'll make sure to answer them as soon as possible and as a community member feel free to jump in and answer questions. | ||
|
|
||
| JSON Schema utilizes Slack and GitHub Discussions to facilitate our communications, each serving unique purposes to support our community effectively. | ||
|
|
||
| Slack is the go-to for lively conversations, channel announcements, one-on-one support, and immediate assistance, making real-time communication seamless and efficient. However, Slack isn't ideal for housing detailed discussions, long-term planning, or tracking the evolution of ideas and decisions. | ||
|
|
||
| For more in-depth discussions, planning, and documenting significant decisions, we use GitHub Discussions. It allows us to work together on significant decisions more effectively and provides long standing point of reference for our discussions. | ||
|
|
||
| Initially Github issues will be disabled as we evaluate how we should use them in this repo (through Discussions). | ||
| | Platforms | Link | | ||
| |:----------|:-------------| | ||
| | 💬 Slack (preferred) | https://json-schema.org/slack | ||
| | 💬 Discussions | https://github.com/orgs/json-schema-org/discussions | ||
|
|
||
| Once we have some links for the community, this readme will link to various locations, resources, and documents that are useful for the community. | ||
| ### Community meetings | ||
| We hold monthly Office Hours and weekly Open Community Working Meetings. Office Hours are every first Tuesday of the month at 15:00 BST, and by appointment. Open Community Working Meetings are every Monday at 14:00 PT. | ||
|
|
||
| # Who can use this repo? | ||
| **Office Hours (Monthly):** | ||
|
|
||
| Anyone who wants to learn about, be part of, or help improve the JSON Schema community is welcome here. | ||
| **Office Hours** provide time for the community for questions, discussions, comments, or just to chat about JSON Schema. | ||
|
|
||
| Anyone can start a discussion in any category. You can even start a discussion to suggest adding a new category! | ||
| More details [here](https://github.com/orgs/json-schema-org/discussions/34/). | ||
|
|
||
| # Why do we need this repo to have discussions? | ||
| **Open Community Working Meeting (Weekly):** | ||
|
|
||
| Slack is really great for chatting, working through tricky problems, having one-to-one support sessions. | ||
| **Open Community Working Meetings** are a 1 hour, agenda'd only, with a focus on furthering the JSON Schema specification and organization. | ||
|
|
||
| Slack is not so great for long running ideas, plans, or discussions, a point of reference for decisions, keeping a log of progress. | ||
| More details [here](https://github.com/orgs/json-schema-org/discussions/35). | ||
|
|
||
| Using Github Discussions, we can collaborate on important decisions over a longer period of time and have a long standing point of reference | ||
| You can always catch up offline by watching the recordings on the JSON Schema YouTube channel. | ||
|
|
||
| # Why not just use Github Issues? | ||
| | Asset | Link | | ||
| |:-----------|:------------| | ||
| | 🔗 Office Hours Meeting Link | [**Zoom Link**](https://postman.zoom.us/j/85358817067?pwd=NmFXTG5oL1paK0VyTEdrNU9TR2RMUT09)<br> | ||
| | 🔗 Open Community Working Meeting Link | [**Zoom Link**](https://www.google.com/url?q=https://postman.zoom.us/j/89562933116?pwd%3DOWlsQ0RrcDY4S1JQU2d2Q2M0aFFlZz09&sa=D&source=calendar&ust=1708431911262691&usg=AOvVaw14JoRXk9cLLBT-_wngWROA)<br> | ||
| | 🎥 Meeting Recordings | https://www.youtube.com/@JSONSchemaOrgOfficial | ||
|
|
||
| Github Issues are great for getting work done, but not so great at having threaded debates and discussions. | ||
| ## Getting involved | ||
|
|
||
| Picking to use Github Discussions before creating an issue allows us to seek consensus in discussion and keep Issues as the space for tracking work product and its progress. | ||
| JSON Schema is a community that lives on its contributors. As we grow, we need more people to help others. Do you like to get involved? You can contribute in many ways! | ||
|
|
||
| # Who decided all this? Is it up for debate? | ||
| Please check out our [Contribution guidelines](CONTRIBUTING.md) to know more. | ||
|
|
||
| Ben Hutton (@relequestual) created this repo and initial readme on April 2021, based on the expectations of community and organisational needs having grown, supported, and observed the community over the past 5 years. | ||
| ### Contributors | ||
|
|
||
| **None of this is set in stone. Humans are fallible. Everything is up for debate.** | ||
| Thanks goes to these wonderful people who contributed to this communtiy space: | ||
| <a href = "https://github.com/json-schema-org/community/graphs/contributors"> | ||
| <img src = "https://contrib.rocks/image?repo=json-schema-org/community"/> | ||
| </a> | ||
|
|
||
| While Ben has become the self-appointed core team lead at some point during those 5 years, we strive to work on a model of general consensus, which works well for specification development, and is something we rely on to move us forward. | ||
| <sub>Made with [contributors-img](https://contrib.rocks).</sub> | ||
|
|
||
| Ben acts in several ways as an executive for the organisation, and feels trusted enough to make organisational decisions like this with the expectation of change and with as much transparency as possible. | ||
| ## Code of Conduct | ||
| To get involved with our Community, please make sure you are familiar with our [Code of Conduct](https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md). |
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