Open Community Working Meeting 2024-01-29 - 14:00 PT

[benjagm]

Open Community Working Meeting 2024-01-29 - 14:00 PT

📺 See Recording

⏪ Go To Previous Meeting

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	[facilitator]
Try to reach agreement on a definition of lexical/dynamic scopes for @jviotti 's article. See comment	@jviotti	@jviotti will adapt the blog post targeting schema writers.
Call for Project ideas for GSoC 2024 : #596	@benjagm	We are now waiting for project ideas
v1 of the JSON Schema Ambassadors Program #589	@benjagm	@the PR is ready for more reviews

Action items:

• @jviotti will adapt the blog post targeting schema writers.

Notes:

• The discussion started with @jviotti summarizing the differing scope views found during the review of his last blog post and solicited feedback. Debate emerged around technical accuracy versus simplicity, targeting schema authors. The final decisions was to adapt the blog post targeting schema writers with a simplified approach of scopes. In addition, @gregsdennis suggested that in this context we need to consider that scope is only in regard to how references are resolved.

• The discussion continued with @benjagm calling for ideas and mentors for Google Summer of Code. @jdesrosiers will think about adding an idea for the language server. @jviotti will think about adding an idea for Alter Schema and @Julian will do the same for Bowtie. @benjagm will add some for the website and some community automations.

• @jdesrosiers shared and updated about his progress with the JSON Schema Language Server.

• The discussion ended with @benjagm sharing a first proposal of Ambassadors Program and asked for feedback improve the proposal before its launch.

Account
@Relequestual
@benjagm
@gregsdennis
@jdesrosiers
@jviotti
@Julian

[jviotti]

@benjagm I want to add an item for trying to reach agreement on a definition of lexical/dynamic scopes to continue making progress with my article. I'd like to propose @gregsdennis 's definition here: json-schema-org/website#274 (comment):

• Lexical scope is the resource that contains the subschema/keyword being evaluated. (A fragment-only URI points to the same lexical scope, whereas a non-fragment-only URI indicates a new scope to resolve.)
• Dynamic scope is the ordered set of resources through which evaluation has passed.

Seems to be a good middle ground from a lot of the discussions in there, and I think its both elegant and easy to understand.

[gregsdennis]

@benjagm why are we still discussing stable spec? We reached an agreement for now. Jason and I are working on it.

[benjagm]

@benjagm why are we still discussing stable spec? We reached an agreement for now. Jason and I are working on it.

We are not going to discuss the stable spec. There has been an issue with the github action adding topics to the agenda because I forgot to remove the "agenda" label so it was added again. I just removed the topic and I'll work on a fix to avoid that type of manual intervention again.

[benjagm]

@jviotti 's blog has been published.