Open Community Working Meeting 2023-09-11 - 14:00 PT #474
Description
Open Community Working Meeting 2023-09-11 - 14:00 PT
Agenda:
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items | [facilitator] | |
| Progress the works of the stable release. Backlog available in this project board. | @benjagm | The board was prioritized and there are PRs waiting for review. |
| Update on the new website release (Planning). Estimated release date Sept. 25th. | @benjagm | Continue with the content migration. |
Action items:
- @benjagm to clarify in slack the purpose of the format registry discussion to ensure everyone was on the same page.
- @benjagm to create a page explaining the rules to publish blog content.
- @benjagm to invite to continue the discussion of the blog about defects in public schema PR moving to a github discussion.
- Plan to build a FAQ page in the future.
Notes:
-
The team continued the discussion about format registry and some participants shared what it wasn't fully clear the intend of the vote asked by @benjagm in slack and Open Community Working Meeting 2023-09-04 - 14:00 PT #470. They agreed to clarify the issue in a Slack discussion to ensure everyone was on the same page.
-
The team discussed the progress on the stable release development and the new website development.
-
@benjagm share that the new website development is completed and the expected launch date will be the last week of September. He also mentioned that we now have a branding repository with resources, including logos and Figma files, which would allow them to evolve and collaborate on the new website in the future.
-
The team discussed the status of the stable release using the board, and prioritized the pull requests (PRs) and agreed that PR 1435 was the top priority. They also discussed promoting the discussion about unstable features in Slack.
-
The team discussed about this recent PR for a blog post that was not suitable for their blog. The team agreed on invite the authors to move to a github discussion to have a more suitable format to have a discussion to better learn from each other positions. At the end of the discussion we can continue the PR review and decide I we 'd like to content additional posts. The also discussed about the benefits of publishing the rules for publishing content in the blog.
-
The team decided to pin Using `$schema` in JSON documents #473 discussion to make it easier to gather more feedback.
-
The meeting ended with discussion about the benefits of having a FAQ page and @benjagm added it to the list of things to implement in the future.
Attendees
| Account |
|---|
| @gregsdennis |
| @Relequestual |
| @benjagm |
| @jviotti |
| @jdesrosiers |
| @Julian |