Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Community Working Meeting 2023-03-13 - 14:00 PT #343

Closed
benjagm opened this issue Mar 7, 2023 · 8 comments
Closed

Open Community Working Meeting 2023-03-13 - 14:00 PT #343

benjagm opened this issue Mar 7, 2023 · 8 comments
Labels
Working Meeting Identify working meetings

Comments

@benjagm
Copy link
Collaborator

benjagm commented Mar 7, 2023

Open Community Working Meeting 2023-03-13 - 14:00 PT

📺 See Recording

Go To Previous Meeting

Agenda:

Topic Owner Decision/NextStep
Review last call's action items [facilitator]
Update on the results on the survey asking for alternatives to unknown keywords. Issue: #241 @benjagm Continue the promotion of the survey this week
Would like to hear thoughts on "in scope" for JSON Schema. Jason and Greg have provided some feedback, would like to hear from others. 286#discussioncomment-5010756 @Relequestual Wait for more feedback during the week with the intend of getting this point closed at the end of this week

AOB?
If you want to discuss any other business not on the agenda, please add comments during the meeting.
If we do not complete the agenda, your discussion item will likely be rolled over to the next call.

Action items: No actions have been captured.

Notes:

  • We have review together the survey's data with 38 responses with these 3 options as the preferred ones (10 @, 10 x- and 9 #).
  • Some participants of the meeting shared again their arguments agains the usage "x-" .
  • We had a large discussion about the possible side effects of deciding for "@" in cases where JSON Schema and JSON-LD being used together and @jviotti shared the use case of W3C Web of Things as an example. We expect a reduced number of collateral effects but more research needs to be done.
  • We discussed about the scope proposed in the Charter. There was no objections regarding the current items and the discussion was more focused in the pros and cons of using a high level scope vs a low level scope which our case:
    • A high level scope will make it easier to maintain the Charter document but will be less actionable.
    • A low level scope will help to prioritize and make decisions and will make it easier to understand or priorities.
  • We agreed on the benefits of linking the use cases documents to the Charter document.

Agenda Items rolling over:

  • list

Attendees

Account
@jdesrosiers
@awwright
@gregsdennis
@jviotti
@Relequestual
@benjagm
@Julian
@benjagm benjagm added the Working Meeting Identify working meetings label Mar 7, 2023
@benjagm
Copy link
Collaborator Author

benjagm commented Mar 14, 2023

@Relequestual
Copy link
Member

@awwright here are some charters I found during my initial research that contained a "scope" section, if you feel seeing examples from other projects would be helpful: https://www.notion.so/fe39594a34e94277a77639db1816f9f5?v=49937cb402e246c398cced2abfad457c

@benjagm
Copy link
Collaborator Author

benjagm commented Apr 5, 2023

Closing this issue as all tasks are completed. Thanks for your contributions!

@benjagm benjagm closed this as completed Apr 5, 2023
@sandrina-p
Copy link

sandrina-p commented Apr 17, 2023

Hi folks! I wanted to share some feedback:

Today I went to the discussion Still Kinda Supporting Unknown Keywords - A call for proposals as there weren't any updates in the last weeks. Then, I realized the discussion was closed and the description was edited with the final decision.

  • Feedback 1): When closing a discussion, please leave a final comment about it so everyone who subscribed to it gets notified.

The decision says "... After hosting a survey, the results indicated that..." Where was this survey hosted? I looked through multiple issues but didn't find any link.

  • Feedback 2) It would be nice if you had cross-shared this survey in the discussion itself too, to notify the subscribers.

Last but not least, where can I see this new spec documented? (Again, I looked for issues about it, but without success)

Thank you.

@benjagm
Copy link
Collaborator Author

benjagm commented Apr 17, 2023

Thanks a lot for this feedback @sandrina-p !! I agree on every point you highlighted and I take responsibility on it.

The decision says "... After hosting a survey, the results indicated that..." Where was this survey hosted? I looked through multiple issues but didn't find any link.

My fault. When I promoted the survey on Social Media and Slack I didn't create a new issue to to keep everyone subscribed properly informed.

@sandrina-p
Copy link

Thanks, @benjagm, it's okay, probably I'd have voted x- too ;). I realized now that I don't follow JSON Schema on Twitter 🙈 Not anymore!

@sandrina-p
Copy link

Also, I clicked the Slack link to JSON Schema in your homepage but it's no longer valid. Could you update it and let me know? Thanks :)

@Relequestual
Copy link
Member

I'll get a new link up right away. While you're waiting: https://join.slack.com/t/json-schema/shared_invite/zt-1tc77c02b-z~UiKXqpM2gHchClKbUoXw

@benjagm benjagm changed the title Open Community Working Meeting 2022-03-13 - 14:00 PT Open Community Working Meeting 2023-03-13 - 14:00 PT Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Working Meeting Identify working meetings
Projects
None yet
Development

No branches or pull requests

3 participants