|
1 | | -# JSON Schema Community |
| 1 | +[](https://json-schema.org) |
| 2 | + |
| 3 | +<br/> |
| 4 | +<p> |
| 5 | + <a href="https://github.com/json-schema-org/website/graphs/contributors" alt="JSON Schema GitHub website contributors"> |
| 6 | + <img src="https://img.shields.io/github/contributors/json-schema-org/website?color=orange" /> |
| 7 | + </a> |
| 8 | + <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"> |
| 9 | + <img src="https://img.shields.io/github/issues/json-schema-org/website/good%20first%20issue.svg?color=%23DDDD00" /> |
| 10 | + </a> |
| 11 | + <a href="https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md" alt="Contributor Covenant"> |
| 12 | + <img src="https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg" /> |
| 13 | + </a> |
| 14 | + <a href="https://www.repostatus.org/#active" alt="Repo status"> |
| 15 | + <img src="https://www.repostatus.org/badges/latest/active.svg" /> |
| 16 | + </a> |
| 17 | + <a href="https://github.com/json-schema-org/community/discussions" alt="Discussions"> |
| 18 | + <img src="https://img.shields.io/github/discussions/json-schema-org/community" /> |
| 19 | + </a> |
| 20 | + <a href="https://opencollective.com/json-schema" alt="Financial Contributors on Open Collective"> |
| 21 | + <img src="https://opencollective.com/json-schema/all/badge.svg?label=financial+contributors" /> |
| 22 | + </a> |
| 23 | + <a href="https://adr.github.io" alt="part of ADR"> |
| 24 | + <img src="https://img.shields.io/badge/part_of-ADR-blue" /> |
| 25 | + </a> |
| 26 | + <a href="https://json-schema.org/slack" alt="JSON Schema Slack"> |
| 27 | + <img src="https://img.shields.io/badge/[email protected]?logo=slack&color=yellow" /> |
| 28 | + </a> |
| 29 | +</p> |
2 | 30 |
|
3 | | -[](https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md) |
4 | | -[](https://www.repostatus.org/#active) |
5 | | -[](https://opencollective.com/json-schema) |
| 31 | +# JSON Schema Community |
6 | 32 |
|
7 | | -[](https://adr.github.io) |
8 | | - |
| 33 | +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. |
9 | 34 |
|
10 | | -# What is this repo? |
| 35 | +- 👋 [Introduction](#introduction) |
| 36 | +- 💬 [Discussions and slack](#discussions-and-slack) |
| 37 | +- 🗓 [Community meetings](#community-meetings) |
| 38 | +- 🌱 [Getting involved](#getting-involved) |
11 | 39 |
|
| 40 | +## Introduction |
12 | 41 | 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. |
13 | 42 |
|
14 | | -The discussions will primarily take place using [Github Discussions](https://github.com/json-schema-org/community/discussions) for this repo. |
| 43 | +### Discussions and Slack |
| 44 | + |
| 45 | +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. |
| 46 | + |
| 47 | +JSON Schema utilizes Slack and GitHub Discussions to facilitate our communications, each serving unique purposes to support our community effectively. |
| 48 | + |
| 49 | +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. |
| 50 | + |
| 51 | +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. |
15 | 52 |
|
16 | | -Initially Github issues will be disabled as we evaluate how we should use them in this repo (through Discussions). |
| 53 | +| Platforms | Link | |
| 54 | +|:----------|:-------------| |
| 55 | +| 💬 Slack (preferred) | https://json-schema.org/slack |
| 56 | +| 💬 Discussions | https://github.com/orgs/json-schema-org/discussions |
17 | 57 |
|
18 | | -Once we have some links for the community, this readme will link to various locations, resources, and documents that are useful for the community. |
| 58 | +### Community meetings |
| 59 | +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. |
19 | 60 |
|
20 | | -# Who can use this repo? |
| 61 | +**Office Hours (Monthly):** |
21 | 62 |
|
22 | | -Anyone who wants to learn about, be part of, or help improve the JSON Schema community is welcome here. |
| 63 | +**Office Hours** provide time for the community for questions, discussions, comments, or just to chat about JSON Schema. |
23 | 64 |
|
24 | | -Anyone can start a discussion in any category. You can even start a discussion to suggest adding a new category! |
| 65 | +More details [here](https://github.com/orgs/json-schema-org/discussions/34/). |
25 | 66 |
|
26 | | -# Why do we need this repo to have discussions? |
| 67 | +**Open Community Working Meeting (Weekly):** |
27 | 68 |
|
28 | | -Slack is really great for chatting, working through tricky problems, having one-to-one support sessions. |
| 69 | +**Open Community Working Meetings** are a 1 hour, agenda'd only, with a focus on furthering the JSON Schema specification and organization. |
29 | 70 |
|
30 | | -Slack is not so great for long running ideas, plans, or discussions, a point of reference for decisions, keeping a log of progress. |
| 71 | +More details [here](https://github.com/orgs/json-schema-org/discussions/35). |
31 | 72 |
|
32 | | -Using Github Discussions, we can collaborate on important decisions over a longer period of time and have a long standing point of reference |
| 73 | +You can always catch up offline by watching the recordings on the JSON Schema YouTube channel. |
33 | 74 |
|
34 | | -# Why not just use Github Issues? |
| 75 | +| Asset | Link | |
| 76 | +|:-----------|:------------| |
| 77 | +| 🔗 Office Hours Meeting Link | [**Zoom Link**](https://postman.zoom.us/j/85358817067?pwd=NmFXTG5oL1paK0VyTEdrNU9TR2RMUT09)<br> |
| 78 | +| 🔗 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> |
| 79 | +| 🎥 Meeting Recordings | https://www.youtube.com/@JSONSchemaOrgOfficial |
35 | 80 |
|
36 | | -Github Issues are great for getting work done, but not so great at having threaded debates and discussions. |
| 81 | +## Getting involved |
37 | 82 |
|
38 | | -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. |
| 83 | +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! |
39 | 84 |
|
40 | | -# Who decided all this? Is it up for debate? |
| 85 | +Please check out our [Contribution guidelines](CONTRIBUTING.md) to know more. |
41 | 86 |
|
42 | | -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. |
| 87 | +### Contributors |
43 | 88 |
|
44 | | -**None of this is set in stone. Humans are fallible. Everything is up for debate.** |
| 89 | +Thanks goes to these wonderful people who contributed to this communtiy space: |
| 90 | +<a href = "https://github.com/json-schema-org/community/graphs/contributors"> |
| 91 | + <img src = "https://contrib.rocks/image?repo=json-schema-org/community"/> |
| 92 | +</a> |
45 | 93 |
|
46 | | -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. |
| 94 | +<sub>Made with [contributors-img](https://contrib.rocks).</sub> |
47 | 95 |
|
48 | | -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. |
| 96 | +## Code of Conduct |
| 97 | +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). |
0 commit comments