Onboarding — 2025 Technical Advisory Council
Open
@riaankleinhans is already working on this.
Since Jan 5, 2025.
- Dominant language
- No language data
- Stars
- 152
- Forks
- 86
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
Tracking issue for onboarding the 2025 Technical Advisory Council
New (or returning) members
Community-elected TAC members
- Bob Callaway, Google — @bobcallaway
- Michael Lieberman, Kusari — @mlieberman85
- Zach Steindler, GitHub — @steiza
GB-appointed TAC members
- Stephen Augustus, Independent — @justaugustus
- Georg Kunz, Ericsson — @gkunz
- Michael Scovetta, Microsoft — @scovetta
Emeriti
- Dan Appelquist — @torgo
- Sarah Evans — @sevansdell
Tasks
Please use the onboarding draft as a reference point: https://github.com/ossf/tac/pull/429
- Update references to and terms for 2025 TAC: https://github.com/ossf/tac/pull/425
- [Chair/Vice Chair] Prepare and send onboarding email to new/returning members
New members
- Create or update TAC bios
- Join the openssf-tac@lists.openssf.org mailing list
- Join the following public Slack channels
- #general — general topics
- #openssf-operations — OpenSSF staff support
- #tac — OpenSSF TAC discussions
- (optional) #tac-gh — GitHub notifications for the
ossf/tacrepository
OpenSSF staff
- Ensure new members have access to the following private Slack channels and remove emeriti
- #tac_members-openssf_staff (private) — communications channel for OpenSSF TAC and staff
- #mac-editorial-review-panel (private) — editorial review board for the OpenSSF Marketing Committee
- Add new members to the
@ossf/tacGitHub team and remove emeriti - Add new members to TAC private mailing list and remove emeriti
Follow-ups
- Draft initial TAC onboarding document: https://github.com/ossf/tac/pull/429
- Create onboarding issue template once onboarding draft has merged
- Complete follow-up items in https://github.com/ossf/tac/issues/430
cc: @steiza
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.