Forming a Technical Committee

Governance
1

Now that we’ve upgraded our governance model, it’s time to prepare to form the Technical Committee.

I’ve produced a draft of a description of the Committee here, pulling material from our governance proposal(s), and filling in some gaps.

As mentioned in there, any member of our previous Technical Working groups is welcome to self-nominate; that group alone may provide more than enough prospective membership to get started. That said, I expect that I will also extend invitations to specific perspectives that we ought to have represented.

(Once formed, the Committee will be expected to manage its own membership moving forward.)

I expect this process to take about a mont. Over the next couple of weeks, please review and provide any reactions to the content in that document – and reach out if you’re interested in serving on the Committee!

Thanks in advance to all who step up to help with this process :smile:

2

Just tagging those who have been involved in the discussions we’ve been having regarding this.
@devin @skyleryoung @SarahP @klambacher @MikeThacker

We’d appreciate it you could:

  1. Review and check you’re happy with the what Greg has drafted here

  2. Let us know if you’re looking to self-nominate.

Thanks,

Dan

3

I am happy to continue to serve on this committee.

1 Like
4

Hi folks – thanks to all who’ve discussed this with me in one form or another over the past month. Seems like we have a sufficient set of nominated committee members who are ready to write this next chapter – @devin @skyleryoung @SarahP @klambacher @MikeThacker – all of whom served on our technical working group for 3.0. I think among them we have a solid cross-section of experience, perspectives, and at least three nationalities. (I do think the committee could eventually benefit from an additional two more members, and toward that end I will advocate for further diversification. But this seems like it could be a good starting point.)

Our next standing technical meetup is just under two weeks away (June 12th, 11a ET). So the community has that time to identify any other issues with the Technical Committee proposal and/or bring any other nominations or concerns to the table. If no other issues arise, we’ll plan to shift into a formalization process – drafting a charter, etc.

Thanks again to all who’ve helped carve this path – let me know if you have any other questions or suggestions!

onward :smiley:
~greg

1 Like
5

Hi folks – we’ve formed the Technical Committee! Big welcome and thanks to @devin @skyleryoung @SarahP @klambacher @MikeThacker

See video of the recent Technical Meeting here.

And stay tuned for updates as the Committee drafts a charter and begins work on HSDS v3.1.

Looking forward to this next chapter :slight_smile:

2 Likes
6

Heads up that I have drafted a blog post announcing the new technical committee (and welcoming committee members by name.

@devin @skyleryoung @SarahP @klambacher @MikeThacker Please review and let me know if you have any feedback – I’ll aim to post after next week, if I don’t receive any substantive input. Thanks!

7

I’m happy with Open Referral Blog Posts – Committee + HSDS 3.1 subject to one tiny issue on which I have commented. The content is pretty dry but needed to let people know we have good open processes.

The complete this survey link will need more prominence here and elsewhere if we want a good response.

8

Blog post is up! https://openreferral.org/upgrading-our-governance-introducing-the-open-referral-standing-technical-committee/

Thanks y’all. I will send out an email newsletter announcement soon.