Standing Technical Meetups

Technical
29

Hi all,

Here’s the video and transcript from our meeting last week (12th June) then see below for a summary of discussion points and follow-up actions.

Key discussion points

Committee Formation:

  • Membership to start with 5 (Devin, Kate, Sarah, Skyler, Mike). Ideally we’d get 2 more with the aim of adding diversity going forward.
  • Charter development is the responsibility of the committee but Greg happy to support.
  • Charter format (brainstorm):
    • Purpose & Values
    • Member roles & Primary responsibilities (to inc. advising on tooling)
    • Joining & Leaving process
    • Setting priorities
    • Decision-making process
    • Dissolution.
  • Devin to take the lead on charter development on behalf of the committee.

3.1 Backlog Review:

  • Matt walked through what was intended to be a very informal summary doc created in response to feedback regarding the difficulty people we we’re having parsing meaning from the github issues.
  • The doc being restricted was an oversight and was not intended to be kept from view as demonstrated by this post into the public forum. All agree on openness and creating opportunities for contribution from the broader community throughout.
  • We discussed how the summary doc fits in with the agreed process and reviewed the flowchart.
  • It was agreed that Github would be used for formal spec development and G-Doc for narrative summaries.
  • There was a request for timescales
  • Skyler and Kate emphasized the importance of the schedule table issue and careful consideration of referrals. There was agreement on setting up a seperate working group to pull together the proposal for this.

Community Survey:

  • Additional outreach now required to get responses from the broader community.

Summit Discussion:

  • Consensus to wait until 2025 for a summit.
  • Some expressed a preference for short, subject-specific deep-dive meetings.
  • Discussed the need for distinguishing between HSDS and Open Referral needs/audiences.
  • @bloom I think we should review the takeaways from last years summit as we start to think about the next one.

Communications:

  • @klambacher fed back on her difficulty keeping up with forum as someone that steps in and out and is not able to engage in the dynamic, ongoing communication that the forum lends itself to.

Actions:

  • Devin: Lead the charter development on behalf of the committee.
  • Committee & @bloom: Think about how best to recruit 2 additional members going forward to enhance diversity.

Upgrade to 3.1:

  • @Dan-ODS: Ensure the summary documents (and all future dosc) are open and accessible.
  • ODS: Use GitHub for formal spec development and G-Doc for narrative summaries.
  • @skyleryoung @mrshll @klambacher? : Set up a separate working group to develop the schedule table proposal.

Community Survey:

  • All: Share the survey with relevant people in their networks.

Summit

  • @bloom Consider short, subject-specific deep-dive meetings within or instead of a 2025 summit.
    @bloom Consider reviewing takeaways from last year’s summit to inform planning for the next one.

Communications:

  • @Dan-ODS to consider how we can communicate in a way that means people get the information they need based on their level of engagement.
1 Like