Open Community Working Meeting 2022-11-28 - 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 - Provide comments on Impedence mismatch discussion
Current work list - What automations would make this useful, if any? Why are we not using it?	@Relequestual	Set up automation to remind people WEEKLY on slack contributor channel
Personal User Manuals - #269 Please provide feedback, even if it's "I think this is a waste of time because...". I am open to all feedback. If it's not for us, that's fine.	@Relequestual	- Add your Personal User Manual, you can use this Template - Read Ben's personal user manual
Discuss breaking up SDLC into discussion chunks - Current PR: Spec PR #1348	@Relequestual @handrews @jdesrosiers	- Follow the discussion @ PR #1348 - Write a primer to make it easy for people to get up to speed thereby allowing them to provide feedback.
Someone converted the spec to markdown PR #1357. Let's discuss if we are ready to code freeze and continue working on the markdown version.	@jdesrosiers	Discussion on tooling, their drawbacks etc is to be had.

Actions

• @Relequestual: Set up automation to remind once a week(at midweek) on the slack contributor channel of the current work list
• @Relequestual to ask for more people to come and provide feedback on various issues. In context of the points brought up by @handrews regarding subpar community involvement

- [ ] @jdesrosiers: A primer to introduce the community on what the SDLC is, where it stands, its goals and what sort of feedback, and thought is being seeked. To help make it easier for people to get involved.
Some discussion after the call in a private slack channel suggests we may no longer want to do this, and are in stead considering a different approach. I'll update here when there's something more to share.

Unassigned actions:

• Discuss tooling for specification conversion from xml to markdown. Drawbacks of certain tools and tools to take into consideration.

Attendees

Account
@Relequestual
@awwright
@Julian
@jviotti
@jdesrosiers
@gregsdennis
@handrews

Details

Personal User Manual

The aim of manual is to allow a community member to share their preferences. Like how one works/operates, stress points, how one prefers feedback, their expectations etc. This is hoped to help understand how to best to work with each other and reduce the potential for friction, especially in a diverse environment.

It's by no means a requirement. If you have concerns, try to write something that's as minimal as you feel is OK, yet still provides value to your colleagues and collaborators.

PR pending.

---

Specification from XML to Markdown

The conversion of specification made the working group ask, if to wait before committing to the changes and what are the things that need to be figured out before Org is ready to accept the changes ?

---

Further Reading

• HTTP Working Group Tools

  • The canonical format for RFCs is now XML. However, we recommend authoring in Markdown – specifically, kramdown-rfc2629. That format is not only easier to edit, it’s also easier for the community to review (think of the diffs) and provide input to in the form of PRs.

  • kramdown-rfc2629
  • Martin Thomson's I-D Template

[jdesrosiers]

Someone converted the spec to markdown json-schema-org/json-schema-spec#1357. Let's discuss if we are ready to code freeze and continue working on the markdown version.