text
stringlengths
0
2.67k
**Marc Boorshtein:** I'm a GUI guy. I'm enterprise. I love my GUIs.
**Justin Garrison:** Yeah. I mean, in the GitOps war or whatever it is out there, there's a lot of opinions on either side, and I'm just kind of curious. I think I've seen more and more people going towards Argo now.
**Marc Boorshtein:** Yeah. And I'm actually talking at ArgoCon next week about multi-cluster identity in Argo.
**Justin Garrison:** By the time this comes out, it'll be two weeks in the past, so...
**Marc Boorshtein:** Two weeks. So I've already talked about Argo. \[unintelligible 01:05:47.17\]
**Justin Garrison:** Awesome. Well, thank you so much, Marc, for coming on the show. Thank you, everyone, for listening this week, and we will talk to you again soon.
**Marc Boorshtein:** Thanks for having me.
• The hosts, Justin Garrison and Autumn Nash, discuss their personal experiences with cold weather in California compared to other regions.
• Upcoming guest Chris Swan will talk about open SSSF scorecards, a security metric for open source software.
• The hosts share interesting links they've found recently, including:
• A list of leap day bugs that occurred due to the extra day in February.
• Prescription orders delayed at US pharmacies due to a cyber attack.
• Concerns about technology's impact on critical infrastructure, such as pharmacies, and the potential consequences for people relying on life-saving medication.
• Discussion of AI's increasing presence in daily life and the need to consider its limitations and vulnerabilities.
• Ransomware attacks and their financial implications, with references to a recent law enforcement victory against a ransom group.
• The stress and desperation caused by prescription medication shortages and the rise of spam and robocalls preying on vulnerable individuals, particularly older adults.
• Personal anecdotes about navigating complex insurance systems and the high costs of medications.
• The White House's initiative to promote memory-safe languages, such as Rust, for writing software.
• Discussion of Cobalt and its vulnerabilities
• Importance of memory-safe languages in secure coding practices
• Military and government applications' need for stable infrastructure
• Update of legacy technology with modern technical applications
• Security concerns in open-source software, including code trust and best practices
• Century's product launch week, featuring new metrics offering and AI-powered features
• Mobile app development capabilities and performance enhancements
• Open SFF (Open Source Security Foundation) and its focus on securing the supply chain
• Scorecards: a badge for GitHub repos, indicating security score out of 10 based on various security metrics
• Implementation as a GitHub Action, checking for known vulnerabilities, dependency management, and other security practices
• Gamification aspect of scorecards, encouraging developers to improve security through visible progress and competition
• Challenges in achieving high scores, with diminishing returns after reaching 80% security compliance
• Scorecard for evaluating open-source projects
• Scoring system based on security best practices
• Visual representation (e.g., red, yellow, green) to indicate score
• Tool uses GitHub API to gather data from repositories
• Large organizations (e.g., Google, Intel) adopting and implementing scorecards
• Versioning of scorecard specifications to ensure up-to-date assessments
• Challenges of maintaining accuracy as new tools and best practices emerge
• Security posture and continuous improvement
• Challenges in open-source projects, including different approaches to security and contribution processes
• Scorecard tool and its ability to provide a common framework for evaluating security and contributing to open-source projects
• Scoring system with binary checks (pass/fail) and spectrum-based checks (scored 0-10)
• Gaming the system and potential challenges in achieving accurate scores
• Applying scorecard to different types of repositories, including docs repos, with creative testing approaches
• Cultural impact of using scorecard on organization's approach to security and contribution processes
• Markdown is now consistently formatted in repos, making it easier for contributors.
• Linting markdown files has become a norm.
• The scorecard project can serve as a gateway for newcomers to contribute to open source by starting with simple tasks like fixing documentation or linting code.
• Hacktoberfest participation was impacted when the organization stopped giving away t-shirts.
• Documentation is often overlooked and underappreciated, but it's crucial for users to understand how to use software.
• Gatekeeping around contributions, such as typo corrections or minor updates, can be counterproductive.
• The importance of documentation in making software accessible and understandable.
• Dependency pinning as a learning opportunity
• Importance of hands-on experience in tech to build confidence
• Supply chain security and openSSF's focus on securing software supply chains
• Scorecards' role in measuring security quality and attention in projects
• Challenges with maintaining dependencies, such as frequent updates and vulnerabilities
• Limited tooling for verifying signed artifacts in some ecosystems
• Concerns about pinning dependencies and maintaining a scorecard for vulnerabilities
• Discussion on the benefits and challenges of having a software bill of materials (SBOM)
• The impact of the federal government's executive order mandating SBOMs on industry practices
• The trade-off between security and experimentation in personal projects vs. professional work
• The importance of being conscious about active projects and archiving repos when necessary
• The cost of open-source software development lies not in replicating code, but in providing attention and maintenance to maintainers.
• The assumption that open-source projects can be freely altered or improved by anyone is a misconception.
• Contributors should ask permission before making changes, rather than forking the project and doing it themselves.
• A scorecard system can provide visibility into a project's value and help contributors gauge their own contributions.
• The comparison of scores between similar projects can serve as a benchmark for improvement.
• Maintainers' attention is finite, and prioritizing tasks based on importance is crucial to sustaining open-source projects.
• Scorecard tool for security visibility and credit
• Open Source Security Foundation (OpenSSF) community and its benefits
• Getting involved with OpenSSF: member vs non-member approaches
• Scorecard usage, implementation, and potential applications
• Teaching security practices to developers using scorecards
• Pathways for college students and others to get involved in OpenSSF and open source communities
• The importance of having good quality templates with repeatable configurations
• Terraform as a tool for consistent config across all GitHub repos
• Automation and abstraction in infrastructure and software development
• Open Ssf Scorecards as a tool to help developers improve their security and best practices
• Nats vs Kafka conversation, with discussion on the operational pain and overhead of Kafka deployments and how Nats can provide a more granular way of addressing messages.
• Kafka vs Nats discussion and comparison
• Costs and operational benefits of Nats architecture
• Resources available for comparing Nats and Kafka, including white papers and benchmarks
• Sanadia's managed service offering powered by Nats
• Origins of technology names, including Linux, Git, and Kubernetes
• Etymology of various technical terms, including Venn diagrams, Trojan horses, Bluetooth, and algorithms
• Interesting names of people behind some technical terms, such as John Venn and Harold Bluetooth
• Explanation of the origins of some software and operating system names, like Debian and Hadoop
• Discussion of geek culture and personal interests in mythology and obscure facts
• Software interacting with physical world and IoT
• Robotics and coding camps for kids
• Adult space camp idea
• Upcoming events: Southern California Linux Expo (SCALE) in Pasadena, CA, March 14-17
• Nerd Olympics at SCALE
• Meeting attendees and recording a podcast episode at SCALE