Skip to content

Open Community Working Meeting 2022-08-15 #222

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
1 task
gregsdennis opened this issue Aug 14, 2022 · 2 comments
Open
1 task

Open Community Working Meeting 2022-08-15 #222

gregsdennis opened this issue Aug 14, 2022 · 2 comments
Labels
Status: Stale It's believed that this issue is no longer important to the requestor. Working Meeting Identify working meetings

Comments

@gregsdennis
Copy link
Member

gregsdennis commented Aug 14, 2022

Open Community Working Meeting 2022-08-15 - 14:00 PT

Zoom Meeting link: https://postman.zoom.us/j/89562933116?pwd=OWlsQ0RrcDY4S1JQU2d2Q2M0aFFlZz09

Agenda: Compiling!

Topic Owner Decision/NextStep
Review last call's action items @gregsdennis
JSON Schema glossary page or site json-schema-org/website#266 @Julian
Schedule for release of draft-next @jdesrosiers
Core team support of non-validation use cases @gregsdennis
$vocabulary in test suite #574 [owner]
[TOPIC] [IssuePRDiscussion] [owner]

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.

Attendees:

Action items:

  • Curate draft-next / draft-future / unmilestoned issues to ensure that completed stuff and to-do issues are in the right places

Notes:

  • Media type registration discussion is stalled for the time being.
  • @Julian has created a glossary page with a few items on it 🎉
  • @jdesrosiers suggested first quarter next year as a goal for release of next version/draft
    • getting through the topics (see below about themes) is more important than hitting a date
  • Lots of discussion around the best tools to use for managing features/releases. We want to stay with milestones, but they need to be cleaned up.
  • Can we have releases based on one or a few themes?
    • media type
    • decouple from IETF
    • output
  • We should start asking whether questions that arise represent problems that actually need solving
    • backwards compatibility
  • Discussions around having the implementation provide filtering so that it only returns requested annotation types, etc.
    • performance & memory space

Agenda Items rolling over:

  • list

Recording: link

@Relequestual Relequestual pinned this issue Aug 15, 2022
@jdesrosiers
Copy link
Member

We should discuss roadmap and timeline for the next release. Should we set a release date goal? What features/changes are "must haves" and what can wait? Do we have an overall theme for what we want to accomplish before the next release? etc.

@Relequestual Relequestual added the Working Meeting Identify working meetings label Aug 19, 2022
@Relequestual Relequestual unpinned this issue Aug 22, 2022
@benjagm benjagm closed this as completed Apr 5, 2023
@benjagm benjagm reopened this Apr 5, 2023
Copy link

Hello! 👋

This issue has been automatically marked as stale due to inactivity 😴

It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.

There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.

Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack

Thank you for your patience ❤️

@github-actions github-actions bot added the Status: Stale It's believed that this issue is no longer important to the requestor. label Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale It's believed that this issue is no longer important to the requestor. Working Meeting Identify working meetings
Projects
None yet
Development

No branches or pull requests

4 participants