You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems a good idea and the next step is the feasibility
Now that we have GitHub automations engage with Contributors we'll need to change the current permissions to require approval only for new to org AND new to GitHub
The team agreed on checking with the rest of leaders if they still find this useful
Action items:
@benjagm to modify this proposal of deprecation process to add 1) a clarification to explain that scope of the document and specify that this is not applicable to the spec development process and 2) add recommendations for handling communications of other non-breaking changes.
@benjagm to search for merchandising providers and estimated costs so that we can evaluate having a booth at API Days Paris. @Relequestual to check feasibility of travel and accommodations.
Check with the rest of leaders if they still find this useful.
Notes:
The meeting started with some community reminders and reviewing the actions items captured in the previous session.
The team discussed this proposal of deprecation process. It will be necessary to add a clarification to explain that scope of the document and specify that this is not applicable to the spec development process. The team also discussed if this document applies to cases of non breaking changes like adding a header and the agreement was to modify the proposal to add recommendations for those cases.
@gregsdennis discussed the removal of the "vocabulary" keyword from the vocab meta-schemas and everyone agreed on proceeding with the merge of the PRs. The team thanked @gregsdennis for informing and checking with @handrews so we can get their extremely valuable feedback.
@Relequestual presented a proposal to change the repository settings to be more permissive with the execution of GitHub Actions sending communications to new contributors because of the issues found testing this GitHub Action.
The meeting ended with a discussion about the idea of having a booth for free at a API Days Paris conference. Considering that OpenAPI and AsyncAPI will have dedicated tracks it seems a something worth exploring if we define clear goals like engage with potential sponsors and adopters. Everyone agreed on this a good idea and now is time to check its feasibility in terms of budget and time to produce the required merchandising.
Open Community Working Meeting 2023-11-06 - 14:00 PT
📺 See Recording
⏪ Go To Previous Meeting
Agenda:
$vocabulary
from vocab meta-schemas [discussion]Action items:
Notes:
The meeting started with some community reminders and reviewing the actions items captured in the previous session.
The team discussed this proposal of deprecation process. It will be necessary to add a clarification to explain that scope of the document and specify that this is not applicable to the spec development process. The team also discussed if this document applies to cases of non breaking changes like adding a header and the agreement was to modify the proposal to add recommendations for those cases.
@gregsdennis discussed the removal of the "vocabulary" keyword from the vocab meta-schemas and everyone agreed on proceeding with the merge of the PRs. The team thanked @gregsdennis for informing and checking with @handrews so we can get their extremely valuable feedback.
@Relequestual presented a proposal to change the repository settings to be more permissive with the execution of GitHub Actions sending communications to new contributors because of the issues found testing this GitHub Action.
@benjagm mentioned that https://github.com/json-schema-org/community/wiki hasn't been updated for weeks or months and is now outdated and the team agreed on checkin with the rest of leaders if they still find this useful.
The meeting ended with a discussion about the idea of having a booth for free at a API Days Paris conference. Considering that OpenAPI and AsyncAPI will have dedicated tracks it seems a something worth exploring if we define clear goals like engage with potential sponsors and adopters. Everyone agreed on this a good idea and now is time to check its feasibility in terms of budget and time to produce the required merchandising.
Agenda Items rolling over:
Attendees
The text was updated successfully, but these errors were encountered: