[kziemski]

Summary

Adds kziemski (Kryspin Ziemski) to filesystems-wg-leads, the GitHub team nested under filesystems-wg.

Rationale

Due to availability issues, and with the blessing of @olaservo, Kryspin is joining the Filesystems Working Group leads in order to act as backup for meeting privileges and working group privileges.

Changes

src/config/users.ts — kziemski gains ROLE_IDS.FILESYSTEMS_WG_LEADS alongside the existing FILESYSTEMS_WG, GOVERNANCE_WG and FINANCIAL_SERVICES_IG memberships.

Verification

npm run check passes: Prettier, config validation, 79/79 tests.

[kziemski]

@localden @dsp wondering if someone can take look here push this through. Last meeting none of the ppl with priv were able to attend with olas blessing adding myself back in to provide backup coverage

[dsp-ant]

An existing filesystem wg lead needs to accept this.

[kziemski]

Apologies will follow up again her to react on here.

[olaservo]

Thanks for opening this. Like we chatted about in Discord, I’d prefer we continue to fix the access gaps directly instead of adding a lead role as a workaround, so I’d like to hold off on merging this. To my knowledge all the meetings are scoped to the same access level, and editing should be open to members beyond leads. If that still isn’t working in practice, let’s fix it there. Separately, we’re working through the gaps in our intended ‘graduation’ process for contributors (a.k.a. the contributor ladder) as it maps to roles, so I expect more communication from maintainers on that in the coming weeks.