Note: lists.oasis-open-projects.org will be down for maintenance on Monday, September 26th, starting at 9AM Pacific Time (4PM Monday September 26, 2022 UTC), for approximately one hour.
Call for nominations to the OCA Technical Steering Commitee (TSC)
Greetings Open Cybersecurity Alliance members and interesting parties!
I am reaching out to you today on an important topic regarding the OCA Technical Steering Commitee (TSC). As per our governance processes (
ref: https://github.com/opencybersecurityalliance/oasis-open-project/blob/master/GOVERNANCE.md ), Technical Steering Committee members on the OCA serve for two year terms, whereupon they are re-confirmed by the governing board, an anniversary that is fast approaching (Oct 2021).
The project governing board is therefore issuing out a call for nominations for any community members who may wish to serve on the OCA TSC in the next two year term. This is a great way to build your external eminence, as well as help the open cybersecurity movement.
TSC members can come from anywhere in the community, and *do not* have to be OCA sponsors. The most important criteria is to have experience managing technical projects, the willingness to serve, and the ability to dedicate the time.
Nominations can be sent in confidence to the PGB co-chairs, Jason Keirstead (jason.keirstead@...) and Mark Mastrangeli (mark_mastrangeli@...) to bring to the PGB for consideration prior to October 7th.
What is the job of a TSC member?
You can find all of the details outlined in the above Governance document. At a high level, the TSC is responsible for work like:
What are the expectations RE time spent?
You must be able to spend an absolute minimum of a few hours a month dedicated to OCA activities. Time demands may be a bit higher during the time of new project onboarding, or definition of new release processes.
Can I nominate myself?
Can I forward this email to someone who may be interested?
What are the most immediate needs in the TSC? How could I help?
The most urgent need for the TSC right now is to define and formalize the code and release management process across the growing number of OCA projects. Currently, each project has it's own process for managing contributions and code - and we need a more defined process that can be quantified and operationalized, to ensure quality open governance across all current and future OCA projects.
Distinguished Engineer, CTO - IBM Security Threat Management
Assistant - Mauricio Durán Cambronero (mauduran@...)
Co-Chair - Open Cybersecurity Alliance, Project Governing Board