Open Community Working Meeting 2022-11-21 - 14:00 PT

[Relequestual]

📺 See Recording

⏪ Go To Previous Meeting

Agenda

Topic	Owner	Decision/NextSteps
Review last call's action items	@Relequestual	All action items were reviewed.
Twitter 😬 - Do we host our own Mastodon server? (Primarily for JSON Schema) There are some domain names we could use and a managed service we could use. Cost is small. Others can follow from other servers. I'm mostly thinking about for the primary JSON Schema account, not for just anyone to sign up. Or, we could just register on the main mastodon.social server. Thoughts?	@Relequestual	No particular action is favoured. Export JSON Schema account data.
JSON Schema Extensions discussion #257	@awwright	Feedback requested on discussion #257. Also, Break down the suggestions into individual proposals and changes if need be, are to be done incrementally to spec after feedback.
Proposal: Disallow non-vocabulary keywords discussion #241	@handrews	Rolled over to next meeting.
Flag usage in SDLC PR #1348	@gregsdennis	Adding flags to structured data and dealing with them presentationally is suggested.

Highlights

• All action items from the last call were reviewed.
• In light of current happenings at Twitter, discussion over usage of Mastodon server, to create or to join one.
• Updates shared by @awwright regarding JSON Schema Extensions. Feedback requested @ discussion #257.
• Discussion on flag usage to differentiate between stable and unstable features, and where to make the changes. Follow the discussion @ PR #1348

Actions

• Break down the document into individual proposals, from the discussion #257 and request for comments.
• Create an issue in referencing repo to capture the discussion on media-type from prev meeting
• Export account data of JSON Schema, in context of discussion on Twitter and Mastodon
• Request for more feedback on relevant issues.

Attendees

Account
@Relequestual
@jdesrosiers
@Julian
@gregsdennis
@jonaslagoni
@awwright

Details

Twitter-Mastodon

• Join an existing server ? or Set up our own ?
• Concern with joining an existing server, might get overloaded leading to loss of postings.
• Cross-posting setup is required.

No particular action is favoured for now.

---

Discussion on usage of flags

• Usage of flags for all and no flags for stable i.e all unflagged are stable.
• Use of yearly flag was discussed.
• Can the above changes be encoded in structured data itself ?
• Adding flags to all, allowing to hide or show flags, or how they are rendered once spec is converted from xml to its new avatar i.e dealing with them on presentation end.
• How to identify discrete features and flag them ? Tricky, in cases where there is interaction between different features.

[jdesrosiers]

Please review the new SLDC PR json-schema-org/json-schema-spec#1348 if you haven't yet. This meeting will be a good time to discuss any issues.

[handrews]

I probably can't make the meeting today so here are my thoughts on Mastodon:

We definitely should not use mastadon.social, as it's got scaling issues and also possibly content moderation issues that we don't want to get caught up in. We're a technical project and don't want to get caught up in battles over what "free speech" levels are appropriate.

fosstodon.org looks like an instance that would be suitable: It is focused on open source, and its code of conduct and other rules are designed to facilitate those conversations rather than political brawls.

I don't personally see an upside in running our own instance (and I would not migrate my account to it even if we had one). That just creates our own little silo that people then have to make a bit more effort to connect with. We want to encourage more relationships between our project and relevant people, and a instance like fosstodon would facilitate that. We already have a dedicated community space with slack.

[Relequestual]

I don't personally see an upside in running our own instance (and I would not migrate my account to it even if we had one).

If we had our own instance, I wouldn't intend to open it up to others to register. Just as a single user instance. Otherwise costs and management effort could be high.