Thursday, July 14, 2022
HomeOperating SystemJamie Thomas: What's the OpenSSF

Jamie Thomas: What’s the OpenSSF


Jamie Thomas is the Common Supervisor, Programs Technique and Growth at IBM and can also be the OpenSSF Board chair. She sat down with Alan Shimel of TechStrong TV throughout OpenSSF Day in Austin to share about OpenSSF and the way the open supply neighborhood is rallying collectively to extend the resilience of open supply software program. 

You may watch the complete interview or learn the transcript under. However, since we’re all busy, I’ve pulled collectively a few of the key factors Jamie comprised of the interview:

OpenSSF is concentrated on a proactive posture. How can we stop these sorts of occasions? And so to do this, we expect there’s quite a few issues we have now to do: 

In the beginning is training, after all, by way of primary safety training for builders.
One other key tenant is how do you set automation on steroids? So the automation and finest practices which can be mirrored in that automation that open supply initiatives can devour? How do you get that out to probably the most important initiatives, after which present some assist for the lengthy tail initiatives
It’s additionally about working, frankly, with different business consortia in addition to the federal government. In Specific, we’ve been working with the US authorities within the OpenSSF to outline what are some actions which can be actually going to make a distinction. 
And I feel important to all of that is getting collaboration throughout the completely different insights from the governing physique, which incorporates plenty of expertise corporations, in addition to industrial corporations. Like there’s plenty of monetary corporations really concerned within the governing physique. What are the important thing components that we actually want to handle first. So getting these priorities set, after which having an execution agenda and actually getting one thing finished within the quick time period, I feel is de facto going to be essential for this group.

On this planet of cybersecurity, you usually be taught that nobody pays consideration to plenty of issues except there’s an enormous compelling occasion. And that’s what log4j was. So whereas it was not desired, it was useful in that vein. . . So popping out of the entire conferences that we’ve had, the collaboration that we’ve had throughout the business, it’ll be crucial that we execute, and that the issues that we have now recognized as high priorities that we make measurable progress on these initiatives this 12 months. That’s the significance of this OpenSSF day right here right this moment in Austin, which is permitting us, with a key set of stakeholders, to begin to share views of the initiatives which can be underway, and the way others can have interaction in these initiatives. And the way, as soon as once more, working collectively, we are able to really make a distinction. 

 Working collectively, we are able to really make a distinction. 

We’re turning the nook on a brand new stage of dedication round safety, there’s all the time been a dedication in open supply round innovation, round function operate. I imply, that’s what’s pushed open supply and allowed it to be so profitable. And for others, different firms like IBM, we take an infinite benefit out of that, proper, we’ve all gotten an enormous benefit in productiveness out of that. However now, it’s actually about turning the main focus just a little bit extra, getting that concentrate on safety, in order that we are able to use open supply and proceed to have that productiveness, however with confidence as we go ahead.

How can we make it straightforward for the maintainers of those open supply initiatives? How can we make it straightforward for the contributors, as a result of with out doing that, it is not going to have the consumption by builders at giant.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments