5 mins

Introductions

• Name, company, areas of architectural interest

20 mins

Mission and Goals

Dave Ormsbee (Axim) , David Joy (Deactivated)

• Brief overview of OEP-56

  • proposal around ADRs, to add structure and responsibilities

  • someone writing an ADR has the responsibility to get feedback from stakeholders and subject matter experts that are impacted

  • the responsibility of the people creating ADRs to write down all feedback

  • “decision maker’s checklist”

  • it’s not always clear in our community who should be part of the conversation

  • this WG is how to make that a reality

• Coordination, not review/gatekeeping

• Goals

  • share where the community is at, what they’re planning to work on

  • make sure forum posts get answered

  • do the connections manually (short term)

  • replace the need for this team (long term)

  • documentation how the arch process happens

• Feedback / Discussion:

20 mins

How we Work

Dave Ormsbee (Axim)

• Tactical vs. Strategic work

  • Tactical: How to help groups and individuals in the short term?

  • Strategic: What key initiatives will help teams to make the right decisions in the longer term?

• Decision making process

• Meeting cadence

  • 2 weeks (fine to start)

    • But forum triage should happen constantly

    • After three months, should re-evaluate

    • This group has a sunset at some point

    • Andy: want to hook people up as soon as possible, before they have to write a whole ADR. Emphasis on early feedback.

    • Ned: historically, groups have problems making progress on their backlog when not meeting regularly

• Communications channels

  • Slack group

  • Discourse

    • New category for discussions about the operation of this group

    • Architecture posts go to Development > Architecture
      

10 mins

Next Steps

• Suggestions for future agenda items

  • ++++++ Backstage introduction

  • Establishing draft guidelines beyond OEP-56 (or adding them to OEP-56)?

  • ++Architecture process best practices or recommendations we can give to delivery teams

  • ++++How to get that early feedback Andy is talking about above

  • Documentation brainstorming

  • .

  • ++How does this group’s coordination work aid or overlap with the product working group, roadmap, etc?

  • An updated ADR template and where to share it/make it discoverable.

  • +++++Communication to the community about the existence of this group, and to evangelize OEP-56 (which hasn’t happened yet - it has been merged as “provisional”).

  • How to make sure that participation of the knowledge experts does happen in a bound timeframe?

  • +How to track and present current items?

  • Does the group have any kind of structure in terms of roles?

  • How do we track the connections we make for decision makers so that we can feed them into our automated process?