Closed
Description
Open Community Working Meeting 2023-10-23 - 14:00 PT
Agenda:
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items | [facilitator] | |
| Reach agreement on the best way to close the discussion for the controversial blog post proposal. | @benjagm | The final decision is not to accept the PR because the blog is not the right channel for that type of message as stated by the blog guidelines. Instead, Github discussions or Slack seems the right place to share that type of content with the Community. |
Action items:
- Reject the PR of the controversial post because the blog is not the right channel for that type of message as stated by the blog guidelines.
Notes:
- The team discussed whether or not to allow this type of critical posts on the JSON Schema blog . While we'd love to have different voices the main purpose of the blog is to promote JSON Schema adoption, and support the JSON Schema Community which is not the aligned with this post. Keeping in mind the purpose of the blog, we are open for different voices and opinions following the blog guidelines. Finally, they decided to politely reply and encourage further discussion in other channels like Github or Slack.
- @benjagm suggested accelerating the creation of the code of conduct committee to evaluate violations and involve more people in content-related decisions.
Attendees
| Account |
|---|
| @gregsdennis |
| @Relequestual |
| @jdesrosiers |
| @benjagm |
| @Julian |
| @jviotti |