From ea109bc8c98fd022bf43efdd9554241db7af3da1 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Wed, 22 Nov 2023 12:01:19 +0100 Subject: [PATCH 01/18] Issue to review the contributing document and add a triage process proposal As per issue #508 this PR is intended to review the org wide contributing document and provide a standard approach for issues triage. --- CONTRIBUTING.md | 12 ++++++--- TRIAGE.md | 65 +++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 73 insertions(+), 4 deletions(-) create mode 100644 TRIAGE.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a583438a..5648b7db 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,16 +1,16 @@ # Guidelines for contributing to the JSON Schema project GitHub organisation -🚨 Work in progress! (2021/07 - @relequestual) - We invite you to join us working on JSON Schema. -The fastest way to get involved and become active in the community is to join our Slack server at https://json-schema.org/slack. +The fastest way to get involved and become active in the community is to join the `#contribute` channel in our Slack server at https://json-schema.org/slack. If you have suggestions on how to improve our community, please do check out our [Community Discussions](https://github.com/json-schema-org/community/discussions), and start a new discussion. # General -While each repository may have its own guidance for contributing, the following sections apply organisation wide. +The JSON Schema organization hosts different projects, and while most have similar contributing guidelines as described in this document, the JSON Schema Specification development process follows different contributing guidelines. Please, check-out the [Spec repository](https://github.com/json-schema-org/json-schema-spec/blob/main/CONTRIBUTING.md) to know more. + +The following sections apply organisation wide to all repositories. ## Key "Architectural" decisions @@ -45,6 +45,10 @@ Once an ADR is part of a pull request which is labelled with `adr-required`, the The process is designed to be lightweight, and a template is provided for ease of use. +### Triage + +Please check the [triage process](TRIAGE.md) to learn how we review and label incoming issues . + ### Feedback Feedback on this process can be made informally through our [Slack server](https://json-schema.org/slack) and formally using our [Community Discussions](https://github.com/json-schema-org/community/discussions). diff --git a/TRIAGE.md b/TRIAGE.md new file mode 100644 index 00000000..8064a2c5 --- /dev/null +++ b/TRIAGE.md @@ -0,0 +1,65 @@ +## Introduction + +This document will outline the process of triaging GitHub issues. **Triage** is the process of reviewing and labeling incoming issues, identifying any which are critical, and escalating the critical ones. + +The core maintainers of each project are responsible for categorizing all incoming issues and delegating any critical or important issue to other maintainers. Currently one maintainer each week is responsible. Besides that part, triage provides an important way to contribute to an open source project. + +Triage helps ensure issues resolve quickly by: + +- Ensuring the issue's intent and purpose is conveyed precisely. This is necessary because it can be difficult for an issue to explain how an end user experiences a problem and what actions they took. +- Giving a contributor the information they need before they commit to resolving an issue. +- Lowering the issue count by preventing duplicate issues. +- Streamlining the development process by preventing duplicate discussions. + +If you don't have the knowledge or time to code, consider helping with triage. The community will thank you for saving them time by spending some of yours. + +## GitHub Labels + +Area labels help categorize issues based on their scope: +| Label | Description | +| ------------------------ | ------------------------------------------------------------------------- | +| `bug` | Indicates that the issue is a bug or a software defect. | +| `enhancement` | Indicates that the issue suggests an improvement or new feature. | +| `documentation` | Indicates improvements or additions to documentation. | +| `roadmap` | Indicates epics and tasks related to roadmap items. | +| `programs` | Indicates epics and tasks related to Community programs. | +| `team` | Indicates issues for team collaboration. | +| `adr-required` | Indicates issues requiring Architectural Decision Record | + +Severity labels: +| Label | Description | +| ------------------------ | ------------------------------------------------------------------------- | +| `High priority` | High priority flow or feature is broken/non-functional, crash. | +| `Critical priority` | Indicates Critical impact on data or site: data loss (posts, pages, comments), unexpected publishing, security issue.| + + + +Other labels: +| Label | Description | +| ------------------------ | ------------------------------------------------------------------------- | +| `good first issue` | Indicates that the issue is suitable for newcomers to contribute to the project.| +| `question` | Indicates that the issue lacks sufficient information to be able to act on it right now and requires additional details from the reporter. The maintainer for the area must remove the tag when more info is provided, or close it if it is too old.| +| `duplicate` | Indicates that is duplicated. | + +## Triage process + +At the end of reading an issue, you should do one of the following: + +1. Make sure to search in previous issue to ensure this is not a duplicated issue. If that is the case, mark it as `duplicate` and close it referencing the original issue. If the issue is clear, ensure it has the correct `area` assigned. Also consider if it is a `good first issue`. + +2. Asses the issue severity to determine what functionality is affected and how broken it is and use the severity labels just for High and Critical cases. + +3. If the submitter or the reviewer believe the resolution of the Issue is likely to result in a significant or noteworthy change it will be labeled as `adr-required`. + +4. Move the issue to the correct repo if required. + +5. If it's not clear what the problem or issue is, add a note for the requestor (or occasionally some other user on the thread), and mark it as `question`. If a `question` issue persists for longer than a week or so (past a second followup), it's reasonable to `close` the issue and encourage the requester to reopen if they have more details. + +6. If the request is infeasable, or complete, follow up directly in the issue with the information, and `close` the issue. + +### References + +This process has been inspired by some great processes defined by Open Source projects like: +- [Knative triage process](https://github.com/knative/serving/blob/main/support/TRIAGE.md). +- [Grafana triage process](https://github.com/grafana/faro-web-sdk/blob/main/ISSUE_TRIAGE.md). +- [Wordpress triage process](https://github.com/wordpress-mobile/WordPress-iOS/blob/trunk/docs/issue-triage.md). \ No newline at end of file From f5c7d0080d57e6c357d3a8abd2f4dac6df1ce080 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 18 Jan 2024 07:04:26 +0100 Subject: [PATCH 02/18] Updated to adhere to Sensible Github Labels --- TRIAGE.md | 54 ++++++++++++++++++++++++++++++++++++------------------ 1 file changed, 36 insertions(+), 18 deletions(-) diff --git a/TRIAGE.md b/TRIAGE.md index 8064a2c5..8b85e90b 100644 --- a/TRIAGE.md +++ b/TRIAGE.md @@ -15,39 +15,56 @@ If you don't have the knowledge or time to code, consider helping with triage. T ## GitHub Labels -Area labels help categorize issues based on their scope: +Labels are assigned based on [Sensible Github Labels](https://github.com/Relequestual/sensible-github-labels). + +Type labels help categorize issues based on their scope: | Label | Description | | ------------------------ | ------------------------------------------------------------------------- | -| `bug` | Indicates that the issue is a bug or a software defect. | -| `enhancement` | Indicates that the issue suggests an improvement or new feature. | -| `documentation` | Indicates improvements or additions to documentation. | -| `roadmap` | Indicates epics and tasks related to roadmap items. | -| `programs` | Indicates epics and tasks related to Community programs. | -| `team` | Indicates issues for team collaboration. | -| `adr-required` | Indicates issues requiring Architectural Decision Record | - -Severity labels: +| `🐛 Bug` | Indicates that the issue is a bug or a software defect. | +| `✨ Enhancement` | Indicates that the issue suggests an improvement or new feature. | +| `📝 Documentation` | Indicates improvements or additions to documentation. | +| `🎯 Roadmap` | Indicates epics and tasks related to roadmap items. | +| `🏗️ Programs` | Indicates epics and tasks related to Community programs. | +| `👥 Team` | Indicates issues for team collaboration. | +| `🗃️ Adr-required` | Indicates issues requiring Architectural Decision Record | +| `💬 Question` | A query or seeking clarification. Probably doesn't need the attention of everyone, just a few to help bring clarification or explain intent.| +| `🤝 Vote` | Indicates issues for voting on an specific topic. | + +Priority labels: | Label | Description | | ------------------------ | ------------------------------------------------------------------------- | -| `High priority` | High priority flow or feature is broken/non-functional, crash. | -| `Critical priority` | Indicates Critical impact on data or site: data loss (posts, pages, comments), unexpected publishing, security issue.| - +| `Priority: Critical` | This should be dealt with ASAP. Not fixing this issue would be a serious error.| +| `Priority: High` | After critical issues are fixed, these should be dealt with before any further issues.| +| `Priority: Medium` | This issue may be useful, and needs some attention.| +| `Priority: Low` | This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix.| +Status labels: +| Label | Description | +| ------------------------ | ------------------------------------------------------------------------- | +| `Status: Available` | No one has claimed responsibility for resolving this issue. Generally this will be applied to bugs and enhancement issues, but may be applied to others.| +| `Status: Accepted` | It's clear what the subject of the issue is about, and what the resolution should be.| +| `Status: Blocked` | There is another issue that needs to be resolved first, or a specific person is required to comment or reply to progress. There may also be some external blocker.| +| `Status: Completed` | Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness, or can be closed by a project member.| +| `Status: In Progress` | This issue is being worked on, and has someone assigned.| +| `Status: On Hold` | Similar to blocked, but is assigned to someone. May also be assigned to someone because of their experience, but it's recognised they are unable to process the issue at this time.| +| `Status: Review Needed` | The issue has a PR attached to it which needs to be reviewed. Should receive review by others in the community, and at least one member / comitter. Specifics on when merging PRs is allowed is still up for debate.| +| `Status: Revision Needed`| At least two people have seen issues in the PR that makes them uneasy. Submitter of PR needs to revise the PR related to the issue.| +| `Status: Abandoned` | It's believed that this issue is no longer important to the requestor and no one else has shown an interest in it.| Other labels: | Label | Description | | ------------------------ | ------------------------------------------------------------------------- | | `good first issue` | Indicates that the issue is suitable for newcomers to contribute to the project.| -| `question` | Indicates that the issue lacks sufficient information to be able to act on it right now and requires additional details from the reporter. The maintainer for the area must remove the tag when more info is provided, or close it if it is too old.| | `duplicate` | Indicates that is duplicated. | +| `inf-required` | Indicates that the issue lacks sufficient information to be able to act on it right now and requires additional details from the reporter. The maintainer for the area must remove the tag when more info is provided, or close it if it is too old.| ## Triage process At the end of reading an issue, you should do one of the following: -1. Make sure to search in previous issue to ensure this is not a duplicated issue. If that is the case, mark it as `duplicate` and close it referencing the original issue. If the issue is clear, ensure it has the correct `area` assigned. Also consider if it is a `good first issue`. +1. Make sure to search in previous issue to ensure this is not a duplicated issue. If that is the case, mark it as `duplicate` and close it referencing the original issue. If the issue is clear, ensure it has the correct `type` assigned and the status `status: Available`. Also consider if it is a `good first issue`. -2. Asses the issue severity to determine what functionality is affected and how broken it is and use the severity labels just for High and Critical cases. +2. Asses the issue priority to determine what functionality is affected and how broken it is and use the priority labels. 3. If the submitter or the reviewer believe the resolution of the Issue is likely to result in a significant or noteworthy change it will be labeled as `adr-required`. @@ -55,11 +72,12 @@ At the end of reading an issue, you should do one of the following: 5. If it's not clear what the problem or issue is, add a note for the requestor (or occasionally some other user on the thread), and mark it as `question`. If a `question` issue persists for longer than a week or so (past a second followup), it's reasonable to `close` the issue and encourage the requester to reopen if they have more details. -6. If the request is infeasable, or complete, follow up directly in the issue with the information, and `close` the issue. +6. If the request is infeasable, or complete,use `status: Completed`` follow up directly in the issue with the information, and `close` the issue. ### References This process has been inspired by some great processes defined by Open Source projects like: - [Knative triage process](https://github.com/knative/serving/blob/main/support/TRIAGE.md). - [Grafana triage process](https://github.com/grafana/faro-web-sdk/blob/main/ISSUE_TRIAGE.md). -- [Wordpress triage process](https://github.com/wordpress-mobile/WordPress-iOS/blob/trunk/docs/issue-triage.md). \ No newline at end of file +- [Wordpress triage process](https://github.com/wordpress-mobile/WordPress-iOS/blob/trunk/docs/issue-triage.md). +- [Sensible Github Labels](https://github.com/Relequestual/sensible-github-labels). \ No newline at end of file From 3a3c07d2e186c8e1fad997eeb848a4c359e2650b Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 18 Jan 2024 07:08:44 +0100 Subject: [PATCH 03/18] Update 'info-required' wording --- TRIAGE.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/TRIAGE.md b/TRIAGE.md index 8b85e90b..4fdc85d6 100644 --- a/TRIAGE.md +++ b/TRIAGE.md @@ -56,7 +56,7 @@ Other labels: | ------------------------ | ------------------------------------------------------------------------- | | `good first issue` | Indicates that the issue is suitable for newcomers to contribute to the project.| | `duplicate` | Indicates that is duplicated. | -| `inf-required` | Indicates that the issue lacks sufficient information to be able to act on it right now and requires additional details from the reporter. The maintainer for the area must remove the tag when more info is provided, or close it if it is too old.| +| `info-required` | Indicates that the issue lacks sufficient information to be able to act on it right now and requires additional details from the reporter. The maintainer for the area must remove the tag when more info is provided, or close it if it is too old.| ## Triage process @@ -70,9 +70,9 @@ At the end of reading an issue, you should do one of the following: 4. Move the issue to the correct repo if required. -5. If it's not clear what the problem or issue is, add a note for the requestor (or occasionally some other user on the thread), and mark it as `question`. If a `question` issue persists for longer than a week or so (past a second followup), it's reasonable to `close` the issue and encourage the requester to reopen if they have more details. +5. If it's not clear what the problem or issue is, add a note for the requestor (or occasionally some other user on the thread), and mark it as `info-required`. If a `info-required` issue persists for longer than 2 weeks or so (past a second followup), it's reasonable to `close` the issue using `Status: Abandoned` and encourage the requester to reopen if they have more details. -6. If the request is infeasable, or complete,use `status: Completed`` follow up directly in the issue with the information, and `close` the issue. +6. If the request is infeasable, or complete,use `status: Completed` follow up directly in the issue with the information, and `close` the issue. ### References From c39cacd86d64ec424923cccffbe65e01d9ac18f2 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 18 Jan 2024 07:54:33 +0100 Subject: [PATCH 04/18] Remove vote as type of issue. This will be made through discussions. --- TRIAGE.md | 1 - 1 file changed, 1 deletion(-) diff --git a/TRIAGE.md b/TRIAGE.md index 4fdc85d6..5bbde05f 100644 --- a/TRIAGE.md +++ b/TRIAGE.md @@ -28,7 +28,6 @@ Type labels help categorize issues based on their scope: | `👥 Team` | Indicates issues for team collaboration. | | `🗃️ Adr-required` | Indicates issues requiring Architectural Decision Record | | `💬 Question` | A query or seeking clarification. Probably doesn't need the attention of everyone, just a few to help bring clarification or explain intent.| -| `🤝 Vote` | Indicates issues for voting on an specific topic. | Priority labels: | Label | Description | From e26e41fac7629688cc8103601c5d29b4709a69f4 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Fri, 19 Jan 2024 11:56:31 +0100 Subject: [PATCH 05/18] Add clear paths to contributions --- CONTRIBUTING.md | 21 +++++++++++++++++++++ docs/blog-guidelines.md | 2 +- 2 files changed, 22 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5648b7db..6129de41 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -12,6 +12,27 @@ The JSON Schema organization hosts different projects, and while most have simil The following sections apply organisation wide to all repositories. +### Types of contributions + +JSON Schema is a community that lives on its contributors. As we grow, we need more people to help others. You can contribute in many ways, either in the specification development or in the wider ecosystem. + +Here are some areas where you can contribute: + * 🌱 [Specification development](https://github.com/json-schema-org/json-schema-spec) + * 🐞 Reporting Bugs + * 💡 Issues and feature requests + * 🧐 Reviewing PRs + * ❓ Answer questions + * 🙏 Join discussions and provide feedback + * 🛠️ [Add new JSON Schema tooling](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#%EF%B8%8F-add-a-new-implementation) + * ✍️ [Publish a blog post](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#%EF%B8%8F-publish-a-blog-post) + * 📈 [Publish a case study](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-publish-a-case-study) + * 📋 [Improving The Documentation](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-improving-the-documentation) + * 🏗 [Website development](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.mdhttps://github.com/orgs/json-schema-org/projects/11/views/1) + * 🎨 [Improving The Design](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-improving-the-design) + * 😍 [Collaborating with Community Management tasks](https://github.com/json-schema-org/community) + * 🚀 [Adding a new Adopter](https://github.com/json-schema-org/community/blob/main/ADOPTERS.md) + + ## Key "Architectural" decisions In most repositories, we would like to utilise [Architectural Decision Records (ADRs)](https://adr.github.io/) to help us work effectively. diff --git a/docs/blog-guidelines.md b/docs/blog-guidelines.md index 7e2265dd..3289dd96 100644 --- a/docs/blog-guidelines.md +++ b/docs/blog-guidelines.md @@ -2,7 +2,7 @@ ## JSON Schema Blog Overview ## -The JSON Schema blog serves as a channel for project maintainers and contributors, implementation maintainers, and JSON Schema Champions to share content with the JSON Schema Community. +[The JSON Schema blog](https://json-schema.org/blog) serves as a channel for project maintainers and contributors, implementation maintainers, and JSON Schema Champions to share content with the JSON Schema Community. The content on our blog consists of: * Use cases and success stories From 21f8a2953c2c65123fc144c583c939bd9a8179ea Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Tue, 13 Feb 2024 11:32:01 +0000 Subject: [PATCH 06/18] Remove double space --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6129de41..c557c4cf 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,7 +8,7 @@ If you have suggestions on how to improve our community, please do check out our # General -The JSON Schema organization hosts different projects, and while most have similar contributing guidelines as described in this document, the JSON Schema Specification development process follows different contributing guidelines. Please, check-out the [Spec repository](https://github.com/json-schema-org/json-schema-spec/blob/main/CONTRIBUTING.md) to know more. +The JSON Schema organization hosts different projects, and while most have similar contributing guidelines as described in this document, the JSON Schema Specification development process follows different contributing guidelines. Please, check-out the [Spec repository](https://github.com/json-schema-org/json-schema-spec/blob/main/CONTRIBUTING.md) to know more. The following sections apply organisation wide to all repositories. From a3499f728975342ddda892439ec7900447b5a182 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Wed, 14 Feb 2024 11:11:40 +0100 Subject: [PATCH 07/18] Fix contributing to focus on community repo and add community manager role. --- COMMUNITY-MANAGER.md | 38 ++++++++++++++++++++++++++++++++++++++ CONTRIBUTING.md | 12 +++--------- 2 files changed, 41 insertions(+), 9 deletions(-) create mode 100644 COMMUNITY-MANAGER.md diff --git a/COMMUNITY-MANAGER.md b/COMMUNITY-MANAGER.md new file mode 100644 index 00000000..4cde33d4 --- /dev/null +++ b/COMMUNITY-MANAGER.md @@ -0,0 +1,38 @@ +# 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 + +### Atribution + +This document has been inspared by the [DAPR Community Manager document](https://github.com/dapr/community/blob/master/COMMUNITY-MANAGER.md). \ No newline at end of file diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c557c4cf..4c489f85 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,4 +1,4 @@ -# Guidelines for contributing to the JSON Schema project GitHub organisation +# Guidelines for contributing to the JSON Schema Community We invite you to join us working on JSON Schema. @@ -6,12 +6,6 @@ The fastest way to get involved and become active in the community is to join th If you have suggestions on how to improve our community, please do check out our [Community Discussions](https://github.com/json-schema-org/community/discussions), and start a new discussion. -# General - -The JSON Schema organization hosts different projects, and while most have similar contributing guidelines as described in this document, the JSON Schema Specification development process follows different contributing guidelines. Please, check-out the [Spec repository](https://github.com/json-schema-org/json-schema-spec/blob/main/CONTRIBUTING.md) to know more. - -The following sections apply organisation wide to all repositories. - ### Types of contributions JSON Schema is a community that lives on its contributors. As we grow, we need more people to help others. You can contribute in many ways, either in the specification development or in the wider ecosystem. @@ -26,8 +20,8 @@ Here are some areas where you can contribute: * 🛠️ [Add new JSON Schema tooling](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#%EF%B8%8F-add-a-new-implementation) * ✍️ [Publish a blog post](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#%EF%B8%8F-publish-a-blog-post) * 📈 [Publish a case study](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-publish-a-case-study) - * 📋 [Improving The Documentation](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-improving-the-documentation) - * 🏗 [Website development](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.mdhttps://github.com/orgs/json-schema-org/projects/11/views/1) + * 📋 [Improving The Documentation](https://github.com/orgs/json-schema-org/projects/16) + * 🏗 [Website development](https://github.com/orgs/json-schema-org/projects/11/views/1) * 🎨 [Improving The Design](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-improving-the-design) * 😍 [Collaborating with Community Management tasks](https://github.com/json-schema-org/community) * 🚀 [Adding a new Adopter](https://github.com/json-schema-org/community/blob/main/ADOPTERS.md) From 68f58425ab8160022134de58d43eaa6a6eaf42db Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 15 Feb 2024 13:30:41 +0100 Subject: [PATCH 08/18] Refactoring of the Community README --- README.md | 87 ++++++++++++++++++++++++++++++++++++++----------------- 1 file changed, 60 insertions(+), 27 deletions(-) diff --git a/README.md b/README.md index 7e7d9196..ddb0dce3 100644 --- a/README.md +++ b/README.md @@ -1,48 +1,81 @@ -# JSON Schema Community +[![JSON Schema logo - Build more, break less, empower others.](https://raw.githubusercontent.com/json-schema-org/.github/main/assets/json-schema-banner.png)](https://json-schema.org) + +
+

+ + + + + + + + + + + + + + + + + + + + + + + + +

-[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md) -[![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#active) -[![Financial Contributors on Open Collective](https://opencollective.com/json-schema/all/badge.svg?label=financial+contributors)](https://opencollective.com/json-schema) +# JSON Schema Community -[![part of ADR](https://img.shields.io/badge/part_of-ADR-blue)](https://adr.github.io) -![GitHub Discussions](https://img.shields.io/github/discussions/json-schema-org/community) +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. - -Initially Github issues will be disabled as we evaluate how we should use them in this repo (through 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. +### Discussions and Slack -# Who can use this repo? +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. -Anyone who wants to learn about, be part of, or help improve the JSON Schema community is welcome here. +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. -Anyone can start a discussion in any category. You can even start a discussion to suggest adding a new category! +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. -# Why do we need this repo to have discussions? +| Platform | Link | +|:----------|:------------| +| 💬 Slack (preferred) | https://json-schema.org/slack -Slack is really great for chatting, working through tricky problems, having one-to-one support sessions. +### 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. -Slack is not so great for long running ideas, plans, or discussions, a point of reference for decisions, keeping a log of progress. +**Office Hours (Monthly):** -Using Github Discussions, we can collaborate on important decisions over a longer period of time and have a long standing point of reference +"Office Hours" provide time for the community for any questions, discussions, comments, or just to chat about JSON Schema. More details [here](https://github.com/orgs/json-schema-org/discussions/34/). -# Why not just use Github Issues? +**Open Community Working Meeting (Weekly):** -Github Issues are great for getting work done, but not so great at having threaded debates and discussions. +Open Community Working Meetings are a 1 hour, agenda'd only, with a focus on furthering the JSON Schema specification and organization. More details [here](https://github.com/orgs/json-schema-org/discussions/35). -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. +You can always catch up offline by watching the recordings on the JSON Schema YouTube channel. -# Who decided all this? Is it up for debate? +| Asset | Link | +|:-----------|:------------| +| 🔗 Office Hours Meeting Link | **Zoom Call:** https://postman.zoom.us/j/85358817067?pwd=NmFXTG5oL1paK0VyTEdrNU9TR2RMUT09
+| 🔗 Open Community Working Meeting Link | **Zoom Call:** https://www.google.com/url?q=https://postman.zoom.us/j/89562933116?pwd%3DOWlsQ0RrcDY4S1JQU2d2Q2M0aFFlZz09&sa=D&source=calendar&ust=1708431911262691&usg=AOvVaw14JoRXk9cLLBT-_wngWROA
+| 🎥 Meeting Recordings | https://www.youtube.com/@JSONSchemaOrgOfficial -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. +## Getting involved -**None of this is set in stone. Humans are fallible. Everything is up for debate.** +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! -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. +Please check out our [Contribution guidelines](CONTRIBUTING.md) to know more. -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). \ No newline at end of file From f5f5e1f49b6c001b786f686781162cd2ef558f53 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 15 Feb 2024 13:33:15 +0100 Subject: [PATCH 09/18] Update README.md --- README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index ddb0dce3..0a8786ac 100644 --- a/README.md +++ b/README.md @@ -42,15 +42,18 @@ This repo is a place to discuss and debate various aspects of running the JSON S ### 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. +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. -| Platform | Link | -|:----------|:------------| +| Platforms | Link | +|:----------|:-------------| | 💬 Slack (preferred) | https://json-schema.org/slack +| 💬 Discussions | https://github.com/orgs/json-schema-org/discussions ### 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. From f03f4339a38cafcc4f549c126a431f60595ba71c Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 15 Feb 2024 13:35:05 +0100 Subject: [PATCH 10/18] Style of links --- README.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 0a8786ac..cb6c5ad9 100644 --- a/README.md +++ b/README.md @@ -60,18 +60,22 @@ We hold monthly Office Hours and weekly Open Community Working Meetings. Office **Office Hours (Monthly):** -"Office Hours" provide time for the community for any questions, discussions, comments, or just to chat about JSON Schema. More details [here](https://github.com/orgs/json-schema-org/discussions/34/). +"Office Hours" provide time for the community for any questions, discussions, comments, or just to chat about JSON Schema. + +More details [here](https://github.com/orgs/json-schema-org/discussions/34/). **Open Community Working Meeting (Weekly):** -Open Community Working Meetings are a 1 hour, agenda'd only, with a focus on furthering the JSON Schema specification and organization. More details [here](https://github.com/orgs/json-schema-org/discussions/35). +Open Community Working Meetings are a 1 hour, agenda'd only, with a focus on furthering the JSON Schema specification and organization. + +More details [here](https://github.com/orgs/json-schema-org/discussions/35). You can always catch up offline by watching the recordings on the JSON Schema YouTube channel. | Asset | Link | |:-----------|:------------| -| 🔗 Office Hours Meeting Link | **Zoom Call:** https://postman.zoom.us/j/85358817067?pwd=NmFXTG5oL1paK0VyTEdrNU9TR2RMUT09
-| 🔗 Open Community Working Meeting Link | **Zoom Call:** https://www.google.com/url?q=https://postman.zoom.us/j/89562933116?pwd%3DOWlsQ0RrcDY4S1JQU2d2Q2M0aFFlZz09&sa=D&source=calendar&ust=1708431911262691&usg=AOvVaw14JoRXk9cLLBT-_wngWROA
+| 🔗 Office Hours Meeting Link | [**Zoom Link**](https://postman.zoom.us/j/85358817067?pwd=NmFXTG5oL1paK0VyTEdrNU9TR2RMUT09)
+| 🔗 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)
| 🎥 Meeting Recordings | https://www.youtube.com/@JSONSchemaOrgOfficial ## Getting involved From a3d1e9e5e9c2310c306ec85716620d716fb7a36c Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 15 Feb 2024 13:37:51 +0100 Subject: [PATCH 11/18] added emojis to index --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index cb6c5ad9..2bcc28ae 100644 --- a/README.md +++ b/README.md @@ -32,10 +32,10 @@ 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. -- [Introduction](#introduction) -- [Discussions and slack](#discussions-and-slack) -- [Community meetings](#community-meetings) -- [Getting involved](#getting-involved) +- [👋 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. From fe7383aea24de5b968cc04d3c6d1c03c4e171c62 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 15 Feb 2024 13:38:51 +0100 Subject: [PATCH 12/18] Update README.md --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 2bcc28ae..fe158b22 100644 --- a/README.md +++ b/README.md @@ -32,10 +32,10 @@ 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. -- [👋 Introduction](#introduction) -- [💬 Discussions and slack](#discussions-and-slack) -- [🗓 Community meetings](#community-meetings) -- [🌱 Getting involved](#getting-involved) +- 👋 [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. From f874488ff6686097e6e1586a55fe06e28d0832f9 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 15 Feb 2024 13:40:10 +0100 Subject: [PATCH 13/18] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index fe158b22..6d649ae2 100644 --- a/README.md +++ b/README.md @@ -60,7 +60,7 @@ We hold monthly Office Hours and weekly Open Community Working Meetings. Office **Office Hours (Monthly):** -"Office Hours" provide time for the community for any questions, discussions, comments, or just to chat about JSON Schema. +"Office Hours" provide time for the community for questions, discussions, comments, or just to chat about JSON Schema. More details [here](https://github.com/orgs/json-schema-org/discussions/34/). From a631d884d4724a8cb89f792df21f1884ef750328 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 15 Feb 2024 13:40:40 +0100 Subject: [PATCH 14/18] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6d649ae2..47cf4eb7 100644 --- a/README.md +++ b/README.md @@ -60,13 +60,13 @@ We hold monthly Office Hours and weekly Open Community Working Meetings. Office **Office Hours (Monthly):** -"Office Hours" provide time for the community for questions, discussions, comments, or just to chat about JSON Schema. +**Office Hours** provide time for the community for questions, discussions, comments, or just to chat about JSON Schema. More details [here](https://github.com/orgs/json-schema-org/discussions/34/). **Open Community Working Meeting (Weekly):** -Open Community Working Meetings are a 1 hour, agenda'd only, with a focus on furthering the JSON Schema specification and organization. +**Open Community Working Meetings** are a 1 hour, agenda'd only, with a focus on furthering the JSON Schema specification and organization. More details [here](https://github.com/orgs/json-schema-org/discussions/35). From 32214a9140e0bbc3e4c35b51e77183a3ccaf7453 Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Thu, 15 Feb 2024 13:47:25 +0100 Subject: [PATCH 15/18] Added contributors --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 47cf4eb7..28632e61 100644 --- a/README.md +++ b/README.md @@ -84,5 +84,14 @@ JSON Schema is a community that lives on its contributors. As we grow, we need m Please check out our [Contribution guidelines](CONTRIBUTING.md) to know more. +### Contributors + +Thanks goes to these wonderful people who contributed to this website: + + + + +Made with [contributors-img](https://contrib.rocks). + ## 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). \ No newline at end of file From f4c62678754f0f099631ca7cd99bf62c8280b32a Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Fri, 16 Feb 2024 11:55:19 +0100 Subject: [PATCH 16/18] Changes to clarify slack channel for discussion --- COMMUNITY-MANAGER.md | 4 ++++ CONTRIBUTING.md | 5 ++++- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/COMMUNITY-MANAGER.md b/COMMUNITY-MANAGER.md index 4cde33d4..cbba0830 100644 --- a/COMMUNITY-MANAGER.md +++ b/COMMUNITY-MANAGER.md @@ -33,6 +33,10 @@ A community manager has the following responsibilities: * 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). \ No newline at end of file diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4c489f85..374991ee 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -23,9 +23,12 @@ Here are some areas where you can contribute: * 📋 [Improving The Documentation](https://github.com/orgs/json-schema-org/projects/16) * 🏗 [Website development](https://github.com/orgs/json-schema-org/projects/11/views/1) * 🎨 [Improving The Design](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-improving-the-design) - * 😍 [Collaborating with Community Management tasks](https://github.com/json-schema-org/community) + * 😍 [Collaborating with Community Management tasks](#community-management-tasks) * 🚀 [Adding a new Adopter](https://github.com/json-schema-org/community/blob/main/ADOPTERS.md) +#### Community management tasks + +To get involved in the Community management tasks, please join the `#community-mgmt` slack channel using this [link](#community-mgmt). ## Key "Architectural" decisions From b0b47fe29ad2929d35d62789b6d41793be4d530b Mon Sep 17 00:00:00 2001 From: Benjamin Granados Date: Fri, 16 Feb 2024 12:47:45 +0100 Subject: [PATCH 17/18] Moved the triage back to org level --- CONTRIBUTING.md | 2 +- TRIAGE.md | 82 ------------------------------------------------- 2 files changed, 1 insertion(+), 83 deletions(-) delete mode 100644 TRIAGE.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 374991ee..725f33ed 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,7 @@ The process is designed to be lightweight, and a template is provided for ease o ### Triage -Please check the [triage process](TRIAGE.md) to learn how we review and label incoming issues . +Please check the [triage process](https://github.com/json-schema-org/.github/blob/main/TRIAGE.md) to learn how we review and label incoming issues . ### Feedback diff --git a/TRIAGE.md b/TRIAGE.md deleted file mode 100644 index 5bbde05f..00000000 --- a/TRIAGE.md +++ /dev/null @@ -1,82 +0,0 @@ -## Introduction - -This document will outline the process of triaging GitHub issues. **Triage** is the process of reviewing and labeling incoming issues, identifying any which are critical, and escalating the critical ones. - -The core maintainers of each project are responsible for categorizing all incoming issues and delegating any critical or important issue to other maintainers. Currently one maintainer each week is responsible. Besides that part, triage provides an important way to contribute to an open source project. - -Triage helps ensure issues resolve quickly by: - -- Ensuring the issue's intent and purpose is conveyed precisely. This is necessary because it can be difficult for an issue to explain how an end user experiences a problem and what actions they took. -- Giving a contributor the information they need before they commit to resolving an issue. -- Lowering the issue count by preventing duplicate issues. -- Streamlining the development process by preventing duplicate discussions. - -If you don't have the knowledge or time to code, consider helping with triage. The community will thank you for saving them time by spending some of yours. - -## GitHub Labels - -Labels are assigned based on [Sensible Github Labels](https://github.com/Relequestual/sensible-github-labels). - -Type labels help categorize issues based on their scope: -| Label | Description | -| ------------------------ | ------------------------------------------------------------------------- | -| `🐛 Bug` | Indicates that the issue is a bug or a software defect. | -| `✨ Enhancement` | Indicates that the issue suggests an improvement or new feature. | -| `📝 Documentation` | Indicates improvements or additions to documentation. | -| `🎯 Roadmap` | Indicates epics and tasks related to roadmap items. | -| `🏗️ Programs` | Indicates epics and tasks related to Community programs. | -| `👥 Team` | Indicates issues for team collaboration. | -| `🗃️ Adr-required` | Indicates issues requiring Architectural Decision Record | -| `💬 Question` | A query or seeking clarification. Probably doesn't need the attention of everyone, just a few to help bring clarification or explain intent.| - -Priority labels: -| Label | Description | -| ------------------------ | ------------------------------------------------------------------------- | -| `Priority: Critical` | This should be dealt with ASAP. Not fixing this issue would be a serious error.| -| `Priority: High` | After critical issues are fixed, these should be dealt with before any further issues.| -| `Priority: Medium` | This issue may be useful, and needs some attention.| -| `Priority: Low` | This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix.| - -Status labels: -| Label | Description | -| ------------------------ | ------------------------------------------------------------------------- | -| `Status: Available` | No one has claimed responsibility for resolving this issue. Generally this will be applied to bugs and enhancement issues, but may be applied to others.| -| `Status: Accepted` | It's clear what the subject of the issue is about, and what the resolution should be.| -| `Status: Blocked` | There is another issue that needs to be resolved first, or a specific person is required to comment or reply to progress. There may also be some external blocker.| -| `Status: Completed` | Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness, or can be closed by a project member.| -| `Status: In Progress` | This issue is being worked on, and has someone assigned.| -| `Status: On Hold` | Similar to blocked, but is assigned to someone. May also be assigned to someone because of their experience, but it's recognised they are unable to process the issue at this time.| -| `Status: Review Needed` | The issue has a PR attached to it which needs to be reviewed. Should receive review by others in the community, and at least one member / comitter. Specifics on when merging PRs is allowed is still up for debate.| -| `Status: Revision Needed`| At least two people have seen issues in the PR that makes them uneasy. Submitter of PR needs to revise the PR related to the issue.| -| `Status: Abandoned` | It's believed that this issue is no longer important to the requestor and no one else has shown an interest in it.| - -Other labels: -| Label | Description | -| ------------------------ | ------------------------------------------------------------------------- | -| `good first issue` | Indicates that the issue is suitable for newcomers to contribute to the project.| -| `duplicate` | Indicates that is duplicated. | -| `info-required` | Indicates that the issue lacks sufficient information to be able to act on it right now and requires additional details from the reporter. The maintainer for the area must remove the tag when more info is provided, or close it if it is too old.| - -## Triage process - -At the end of reading an issue, you should do one of the following: - -1. Make sure to search in previous issue to ensure this is not a duplicated issue. If that is the case, mark it as `duplicate` and close it referencing the original issue. If the issue is clear, ensure it has the correct `type` assigned and the status `status: Available`. Also consider if it is a `good first issue`. - -2. Asses the issue priority to determine what functionality is affected and how broken it is and use the priority labels. - -3. If the submitter or the reviewer believe the resolution of the Issue is likely to result in a significant or noteworthy change it will be labeled as `adr-required`. - -4. Move the issue to the correct repo if required. - -5. If it's not clear what the problem or issue is, add a note for the requestor (or occasionally some other user on the thread), and mark it as `info-required`. If a `info-required` issue persists for longer than 2 weeks or so (past a second followup), it's reasonable to `close` the issue using `Status: Abandoned` and encourage the requester to reopen if they have more details. - -6. If the request is infeasable, or complete,use `status: Completed` follow up directly in the issue with the information, and `close` the issue. - -### References - -This process has been inspired by some great processes defined by Open Source projects like: -- [Knative triage process](https://github.com/knative/serving/blob/main/support/TRIAGE.md). -- [Grafana triage process](https://github.com/grafana/faro-web-sdk/blob/main/ISSUE_TRIAGE.md). -- [Wordpress triage process](https://github.com/wordpress-mobile/WordPress-iOS/blob/trunk/docs/issue-triage.md). -- [Sensible Github Labels](https://github.com/Relequestual/sensible-github-labels). \ No newline at end of file From 57d821604275606247a9ab67e6a59fecb051fb38 Mon Sep 17 00:00:00 2001 From: Benjamin Granados <40007659+benjagm@users.noreply.github.com> Date: Fri, 16 Feb 2024 17:45:33 +0100 Subject: [PATCH 18/18] Apply suggestions from code review Co-authored-by: Ben Hutton --- CONTRIBUTING.md | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 725f33ed..5dbea1b8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -28,7 +28,7 @@ Here are some areas where you can contribute: #### Community management tasks -To get involved in the Community management tasks, please join the `#community-mgmt` slack channel using this [link](#community-mgmt). +To get involved in the Community management tasks, please join the [`#community-mgmt` slack channel](https://json-schema.slack.com/archives/C0209BTU2UQ). ## Key "Architectural" decisions diff --git a/README.md b/README.md index 28632e61..55b6ed08 100644 --- a/README.md +++ b/README.md @@ -86,7 +86,7 @@ Please check out our [Contribution guidelines](CONTRIBUTING.md) to know more. ### Contributors -Thanks goes to these wonderful people who contributed to this website: +Thanks goes to these wonderful people who contributed to this communtiy space: