TAC - The Vuln WG has voted and the majority expressed interest in adopting OpenVEX as a sandbox project & SIG underneath our umbrella. 11 eligible members voted in favour with 5 opposing. Therefore w

TAC – I have been requested to bring the Vuln Disclosure WG’s vote to adopt OpenVEX as a project underneath our working group(1)(2) before the TAC for our next call. I’d also love to get this process

TAC – Myself and several members and community folks have been collaborating on an idea to hold a focused workshop(1) for web developers since our meetup in Dublin last fall at the OSS-EU. We’d like t

Hi Tac Folks et al, So staying good to my word, I did not go forward for re-election this year. Having served two successful terms on the OpenSSF TAC, I recognise the importance of ensuring diverse re

Hello TAC! I just wanted to update everyone on the status of the electorate and self-nominations for the OpenSSF Technical Advisory Council (TAC) and Security Community Individual Representative (SCIR

Please take a look at https://github.com/ossf/tac/pull/137 which is a proposal sponsored by the Securing Software Repositories WG to add a new project called "Repository Service for TUF (RSTUF)" to th

Hi all, At the last TAC call we agreed to update the schedule of quarterly reports to the TAC by the Working Groups and top-level Projects. I've listed below the upcoming TAC meetings - I checked for

Hello TAC-friends! On our next call the BEST WG will be reporting out on our current and upcoming activities. To that end, we’re providing our report(1) today as a pre—read for you all. We’re looking

Hello everyone, I'm pleased to announce the nomination and election process for the OpenSSF Technical Advisory Council (TAC) and Security Community Individual Representative (SCIR). Please read below

Team – During a TAC-GB Governance committee call earlier today we received feedback that the GB and leadership were interested to see our “CI/CD Overlay” diagram updated and leveraged to start to spea

TAC – This note is to collect sentiment around TAC Issue 131 - [Proposed Initiative] OpenSSF OSS-SIRT Mobilization Plan Review (1). In addition to providing feedback/comments to the OSS-SIRT SIG’s pla

I am unable to make the TAC call tomorrow due to an unexpected last-minute conflict. I also see that Luke and Abhishek won't make it either. Is anyone else able to chair in my place? Topics for discus

TAC – This note is to collect sentiment around TAC Issue 134 - [Proposed Initiative] OpenSSF EDU.SIG Mobilization Plan Review (1). In addition to providing feedback/comments to the EDU.SIG’s plan prop

Hi Everyone, We're pleased to share the results of the OpenSSF General Member Representative Election with you. The following individuals have been elected by the General Member class: Duane O'Brien,

Hi everyone, Today we announced OpenSSF Day in Vancouver registration and call for proposals are open. OpenSSF Day will be on Wednesday, May 10th as part of Open Source Summit North America. Please su

Dear TAC and other interested parties, The OpenSSF Charter section 6 says: "The TAC will be composed of four representatives elected annually by all active contributors to technical projects (as defin

My vote is "yes" if we can shape their infrastructure direction and recommend use of SaaS infra (see also Justin's comments here), otherwise it is a "no".

Hello, Last week we sent out an email to all voting and technical representatives of the General Membership class about the upcoming General Member Representative Election (see below for a copy of tha

Please review TAC Issue 132(1) and reply here with your vote on the matter. During the TAC call today were 3 “yes” votes from Aeva, Josh, & CRob. Please re-affirm on this thread. - https://github.com/

I vote yes