Skip to content

Update TSC member details and replacement#40

Merged
mdklein merged 1 commit intomainfrom
alexlovelltroy-patch-2
Feb 13, 2026
Merged

Update TSC member details and replacement#40
mdklein merged 1 commit intomainfrom
alexlovelltroy-patch-2

Conversation

@alexlovelltroy
Copy link
Member

Replaced Harold Longley with Jay DePasse as TSC member.

Replaced Harold Longley with Jay DePasse as TSC member.

Signed-off-by: Alex Lovell-Troy <alovelltroy@lanl.gov>
@j0hnL
Copy link

j0hnL commented Feb 12, 2026

Welcome, Jay! Looking forward to working with you and continuing to work with Harold on the project.

Copy link
Contributor

@rainest rainest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Arguably better for someone from HPE (ideally @haroldlongley ) to give a ✔️ here too, but as this repo doesn't have merge protections or auto-merge anyway, my approving it is not gonna trigger unexpected confirm and merge.

Welcome @jvd10!

@github-actions
Copy link
Contributor

github-actions bot commented Feb 13, 2026

Approvals: 3/4 from tsc. Need 1 more.

Approved by: @alexlovelltroy, @haroldlongley, @rainest
Still needed from: @j0hnL, @mdklein, @milliams

Team size considered: 6. This comment auto-updates as reviews change.

@rainest
Copy link
Contributor

rainest commented Feb 13, 2026

Nevermind, we do have automations that work now, and they even suggest relevant approvers (though only in comments, not in the requested approvers).

@j0hnL if you could proper press the ✔️ I think that'll make the bot happy, and then if Harold can as well, 👨‍🍳 👌

@rainest
Copy link
Contributor

rainest commented Feb 13, 2026

@alexlovelltroy minor question on automation stuff--it looks like we currently have merge whenever if humans with permission choose to, and then the Actions bot will merge if it hits the vote threshold?

I think that's the case, I'm just more used to human-selected auto-merge and then native Github merge once required approvals tally.

If I'm right about how automation works here currently--that probably makes more sense for community (whereas code repos have more reason for "no merge til all checks pass/approval requirements met, but auto-merge once they do"): we do want automation on consensus, but with the option to force merge prior if need be.

Don't think anything needs to change, but wasn't 100% sure :)

@mdklein mdklein merged commit f71b395 into main Feb 13, 2026
3 checks passed
@mdklein mdklein deleted the alexlovelltroy-patch-2 branch February 13, 2026 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants