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.

Sign up for GitHub

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

Jump to bottom

Open Community Working Meeting 2022-04-01 #164

Closed
2 tasks done
Relequestual opened this issue Apr 1, 2022 · 1 comment
Closed
2 tasks done

Open Community Working Meeting 2022-04-01 #164

Relequestual opened this issue Apr 1, 2022 · 1 comment
Labels
Working Meeting Identify working meetings

Comments

@Relequestual
Copy link
Member

Relequestual commented Apr 1, 2022 •
edited by benjagm
Loading

📺 See Recording

⏪ Go To Previous Meeting

Agenda

Topic Owner Decision/NextSteps
Review last call's action items @Relequestual The action items were reviewed
Update to Code of Conduct @Relequestual The updated CoC can be read @ PR #5
Add note (CREF) about ambiguous behaviour of additionalProperties when invalid @Relequestual The note on the topic can be read @ Issue #1172
Add note (CREF) about ambiguous behaviour of additionalProperties @Releuestual The PR can be read @ PR #1203

Highlights

  • Members shared comments on ambiguous behavior of additionalProperties

  • Organizational matters concerning processes, licensing, finances etc.

  • Members shared, clarified and discussed updates to Code of Conduct

  • Brief discussion on usage of logos and licensing

Actions

  • Add note (CREF) to ambiguous behaviour additionalProperties See here

  • Calender Events with Slack

Attendees

Account
@Relequestual
@jviotti
@jdesrosiers

Details

Ambiguous behaviour of additionalProperties

The complete discussion can be followed by reading the following:

Org Discussion #57

Spec Issue #1172

Spec Pull Request #1203

Updates to Code of Conduct1

Members discussed the modifications made to contributor covenant code of conduct and further clarified that the working group takes IETF BCP542 as a guide only. i.e guidelines for conduct based on discussions with OpenJS foundation. In light of those changes, escalation is now clearly defined and provides contact emails.

In brief, BCP542 acts as a guide to how the working group conducts itself and engages with each other particularly in cases of escalation and reporting. i.e as an organizational guide.

Whereas the covenant code of conduct has to do with how to be nice, deal with biases, fair treatment etc i.e as a community guide.

Read OpenJS Code of Conduct

Read JSON Schema Code of Conduct

Org Issue #163

Org Issue #129

JSON Logo

Members discussed fair usage of logo and respective licensing. The conclusion being, there are differences in usage allowed by trademark owner for products that are in incubation phase and the one already established.

Footnotes

  1. https://github.com/json-schema-org/.github/pull/5 ↩

  2. https://www.rfc-editor.org/info/bcp54 ↩ ↩2
@Relequestual Relequestual added the Working Meeting Identify working meetings label Apr 1, 2022
@Relequestual Relequestual changed the title Open Community Working Meeting 2022-05-01 Open Community Working Meeting 2022-03-01 Apr 1, 2022
@Relequestual Relequestual pinned this issue Apr 1, 2022
@Relequestual Relequestual changed the title Open Community Working Meeting 2022-03-01 Open Community Working Meeting 2022-04-01 Apr 1, 2022
@Relequestual Relequestual unpinned this issue May 20, 2022
@Relequestual Relequestual added the Needs minutes Flagging meetings that need minutes and actions for tracking label Oct 18, 2022
@benjagm benjagm removed the Needs minutes Flagging meetings that need minutes and actions for tracking label Dec 23, 2022
This was referenced Dec 23, 2022
Open
Open
@benjagm
Copy link
Collaborator

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Working Meeting Identify working meetings
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Relequestual @benjagm