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-10-02 - 14:00 PT #487

Closed
benjagm opened this issue Sep 26, 2023 · 2 comments
Closed

Open Community Working Meeting 2023-10-02 - 14:00 PT #487

benjagm opened this issue Sep 26, 2023 · 2 comments
Labels
Working Meeting Identify working meetings

Comments

@benjagm
Copy link
Collaborator

benjagm commented Sep 26, 2023

Open Community Working Meeting 2023-10-02 - 14:00 PT

📺 See Recording

Go To Previous Meeting

Agenda:

Topic Owner Decision/NextStep
Review last call's action items [facilitator]
Steps to complete the new website rollout and disable pipelines of previous repos. More information here @Relequestual
Website release causes HTTP requests to 301 redirect to HTTPS. One user has reported this causes a problem for one implementation (net.jimblackler.jsonschemafriend) which does not follow the redirect. - Question: Do we want to fix this? Should old meta-schemas be available on http only URLs? (We should be able to without huge effort if we want.) (OP filed an Issue with the implementation.) @Relequestual

Action items:
No action items has been captured.

Notes:

  • We started discussing various topics including updating the Jason schema playground and sharing schemas.

  • The team discussed some steps to complete the roll-out of the new website including disabling GitHub pages and archiving repositories for the old website, the blog and Understanding JSON Schema.

  • They also addressed the problem of an implementation (net.jimblackler.jsonschemafriend) breaking due to HTTP to HTTPS redirect, and agreed that it exposed bugs that needed fixing. They debated whether to revert the implementation or fix the library, ultimately deciding to bundle the master schemas or stop doing schema validation.

  • The discussion revolved around a specific implementation that required calling a method called loadSchema to validate using a schema, which would automatically download the schema if it was not already in the schema store. They concluded that although it was a temporary solution, it was not ideal and should be modified to avoid the need for such a method.

Attendees

Account
@gregsdennis
@Relequestual
@jviotti
@jdesrosiers
Eli Sherer
@benjagm benjagm added the Working Meeting Identify working meetings label Sep 26, 2023
@jviotti
Copy link
Member

jviotti commented Oct 2, 2023

Should old meta-schemas be available on http only URLs?

This sounds right to me. Old metaschemas were hosted on HTTP only, and even a 301 in those cases is somewhat a breaking change.

@benjagm
Copy link
Collaborator Author

benjagm commented Oct 8, 2023

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

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

2 participants