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

[benjagm]

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

📺 See Recording

⏪ Go To Previous Meeting

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	[facilitator]
Create 3 email accounts for JSON Schema. hello@ newsletter@ and report@ issue	@benjagm	This is a good idea. We'll use the issue to discuss prices and vendors.
#425 - Identify the repositories inside and outside the organization.	@benjagm	Maintainers will help by providing the required information.
https://github.com//orgs/json-schema-org/discussions/506 - Curating a GitHub topic on JSON Schema	@egekorkan	This is a great idea. @egekorkan and @benjagm will collaborate to curate the topics, considering json-schema as primary option.
Do we need an ADR to deprecate the http://json-schema.org/schema redirect?	@benjagm	Yes. Deprecations will require ARD
transferring and funding learnjsonschema.com	@jviotti	The agreement was to work on the sponsorships packages and the contribution programs to make sure the policies and processes are clear and transparent to everyone.

Action items:

• @egekorkan and @benjagm will work on the curation of the JSON Schema github topics.
• We'll create and ADR for the deprecation of http://json-schema.org/schema redirect.
• @benjagm will work on the sponsorships packages and the contribution programs to make sure the policies and processes are clear and transparent to everyone so we can consider supporting running a contribution program to support Learn JSON Schema.

Notes:

• The team reviewed the action items of the past Meeting, including the arguments we provided to close the PR to publish a controversial blog post.

• @egekorkan presented the issue Curating a GitHub topic on JSON Schema #506 to suggest the curation of the Github topics used to tag JSON Schema and the team agreed on it. We'll suggest maintainers to use json-schema as main option.

• The team discussed the creation of email accounts for first contact, newsletters, and reporting code of conduct violations using the Open Collective funds. We'll use the issue JSON Schema public email addresses #393 to discuss vendors and pricing.

• @benjagm presented the issue Identify the repositories inside and outside the organization. #425 and asked maintainers to complete the contribution status.

• The team discussed the idea of transferring funds from Learn JSON Schema to create a grant for contributors to enhance the examples. The agreement was to work on the sponsorships packages and the contribution programs to make sure the policies and processes are clear and transparent to everyone.

• The team discussed if it will be necessary to create an ADR to work on the deprecation plan to deprecate the http://json-schema.org/schema redirect and the final decision was Yes, this will require ADR.

Summary: The speaker outlines a plan for documenting decisions and ensuring everyone is informed. They emphasize the importance of the EDR and express optimism about its implementation.

Agenda Items rolling over:

• list

Attendees

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

[egekorkan]

@benjagm I will try to join the call, at least the first half since it is a bit late in my time zone. Thank you for bringing this to the agenda.

[benjagm]

I will try

Don't worry @egekorkan . Our automation added you as owner (sorry for that) but I was planning to expose the topic. If you can join it will be great to speak live, but don't worry at all.

[benjagm]

This is the PR to curate the JSON Schema Topics: github/explore#4020

[github-actions]

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]

This issue did not get any activity in the past 180 days and thus has been closed. Please check if the main branch has fixed it. Please, create a new issue if the issue is not fixed.