Description
Open Community Working Meeting 2022-02-04 - 20:00 UTC
(The 2022-01-21 did not have suffeciant attendance to conduct business)
Zoom Meeting link: https://postman.zoom.us/j/82093625720
Agenda:
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items | @Relequestual | @Relequestual to review json-schema-org/json-schema-spec#1143 |
| Proposal to change both meeting times to 20:00 GMT OR 12:00 PST | @Relequestual @jdesrosiers | Agreed to change to 12 PST |
| Schemas and other data are public domain (PR / Issue) | @awwright @karenetheridge | Could we stick with the current licences rather than re-licence? - Some concerns over what the current licence/s actually IS. Should be investigated. |
| Website rebuild and merge? | @Relequestual | We agreed it should be kept simple and use markdown for content as much as feasable. Create an issue to capture requirements and wishes - @Relequestual |
| Patch Release Milestone PRs json-schema-org/json-schema-spec#1155 | @Relequestual @karenetheridge | Re-reviewed, approved, and merged. |
| 2022 Q1 OKRs update and discussion #134 | @Relequestual |
AOB?
We discussed ietf-wg-httpapi/mediatypes#7
Action items:
- Update Open Community Working Meeting times on GH Discussion - @Relequestual
- ... on website - @Relequestual
- ... and notify on Slack and Twitter - @Relequestual
- Propose we stick with current licence (if we can determine what that is specifically) for main repo source material re explicit licence needed in schema files and all repositories json-schema-spec#1160 - @Relequestual
- Check with OpenJSF about license of meta-schema situation - @Relequestual -explicit licence needed in schema files and all repositories json-schema-spec#1160 (comment)
- Create an issue to capture requirements and wishes for the website rebuild - Done - @Relequestual
- Review and follow up on IETF HTTP-API WG mediatype registration - Done - @jdesrosiers
Notes:
Pre meeting note regarding the website rebuild and merge item:
Our website and content is spread over 3 repos. Wouldn't it be great to move them all in to the same repo and use a modern tech stack?
We have a financial sponsor for the work, and so far one potential candidate to do the work (from our community).
We should compile a wish list.
I want to see if anyone has any comments about what they would like to see, or any other thoughts or considerations to share.
An issue needs to be created to house the work and child issues.
Recording: link