Logo

    maintainers

    Explore " maintainers" with insightful episodes like "Today's Air Force - April 29, Part 3", "Episode 73: Reflections on the LF OSS Maintainer Report", "Kelsey Hightower—Present", "Freedom Watch Update - June 17" and "Air Force Report: Joint Warrior Rotors" from podcasts like ""Today's Air Force", "CHAOSScast", "The ReadME Podcast", "Freedom Watch Update" and "Air Force Report"" and more!

    Episodes (12)

    Today's Air Force - April 29, Part 3

    Today's Air Force - April 29, Part 3
    This edition features stories on an Aviano Airman receiving the 2009 Lt. Gen. Leo Marquez Award for his hard work and dedication to his Airmen, an air traffic control interpreter who teaches Turkish culture, customs, and language to people at Incirlik Air Base, and a teacher who decided to substitute at a Landstuhl school while she was stranded awaiting a flight due to the recent Icelandic volcanic eruption. Hosted by Staff Sgt. Nicholas Kurtz.

    Episode 73: Reflections on the LF OSS Maintainer Report

    Episode 73: Reflections on the LF OSS Maintainer Report
    Thank you to the folks at Sustain (https://sustainoss.org/) for providing the hosting account for CHAOSSCast! CHAOSScast – Episode 73 In today’s episode, the conversation dives deep into the Linux Foundation Research Open Source Maintainers Report. Georg, Alyssa, Dawn, Sophia, and Anita engage in a thoughtful discussion about the report's methodology, findings, and implications for open source projects. They explore topics such as the challenges of obtaining a representative sample in open source research, the bias toward technical contributors, and the importance of considering the long-term engagement lifecycle of contributors. Additionally, they touch upon the report's best practices, including documentation and diversity, and how these practices can be connected across different categories. Download this episode now to learn more! [00:2:50] Georg discusses the two main sections of the report: demographics of maintainers and contributors and maintainer best practices. He asks for thoughts and questions about the report. [00:03:13] Alyssa expresses curiosity about the methodology, the number of interviews (32), and the diversity of projects covered in the research. Dawn shares her perspective on the number of interviews, stating that in-depth qualitative interviews can lead to convergence on key topics. [00:05:32] Sophia discusses the challenges of obtaining a representative sample in open source research and mentions the effort to increase diversity in project types. She highlights the discussion of findings in percentages and expresses that it may be more quantitative than typical interview-based research. [00:07:54] Dawn agrees with Sophia’s points and mentions her skepticism about percentages based on a small sample size. Georg mentions concerns about small sample sizes affecting the ability to make claims, especially with regards to best practices. [00:09:49] Alyssa expresses that some sections of the report resonated with her, while others, like the funding and satisfaction sections, did not. She questions the methodology and the types of questions asked. Sophia responds, mentioning the challenges of sampling in open source research and how the findings resonated with her to some extent. She highlights the issue of funding and its potential impact on open source community culture. [00:13:24] Georg asks if the findings and best practices aligned with their understanding the methodology helped in interpreting the findings. Anita adds her perspective, mentioning that the research highlights the transition from contributors to maintainers but raises questions about the representation of non-technical contributors. [00:14:45] Alyssa notes the term “super coders” used in the report and how it implies a technical background for maintainers. Dawn and Anita express concerns about bias towards technical contributors and the exclusion of non-technical contributors in the research. Sophia acknowledges the bias in open source data and the need for more inclusive understanding of contributors. [00:17:19] Georg raises the intriguing issue of maintainers being paid but feeling unsupported by their organizations. Dawn shares her experience of challenges in justifying promotions for open source developers within companies, and the visibility issue of open source work within organizations. [00:19:33] Alyssa highlights the tension between company priorities and open source community priorities, and the balancing act that open source developers have to manage while wearing multiple hats, and Sophia shares her thoughts on this. [00:21:53] Georg transitions the discussion to the best practices section of the report, and Anita shares that she finds the documentation, especially when engineers are tasked with writing it. She discusses issues related to technical jargon and the usability of documentation. [00:24:00] Georg acknowledges the recuring challenge of documentation in open source projects and mentions the importance of considering different learning styles when creating documentation. Alyssa suggests that there could be opportunities to connect best practices across different categories. [00:26:27] Now the conversation shifts towards the diversity section of the report, where Georg discusses the lack of well-structured diversity efforts in many open source projects. [00:28:09] Sophia comments about the identifiable interviews in the research, noting that having named participants may have limited the depth of the diversity discussion due to privacy concerns. Alyssa comments on the decision to have identifiable interviews and highlights that it influenced the way the research results were presented, including the discussion on diversity. [00:30:41] Georg brings up the connection between the discussion in the report and the work being done in the CHAOSS Project. Dawn emphasizes the importance of thinking about metrics and how they can be applied in open source projects, and she provides examples of how metrics can be used to measure specific aspects of project health. [00:32:43] Alyssa expresses curiosity about what others think of the report’s conclusion and the attributes table, which suggests a strategy for project health assessment and improvement. [00:33:30] Georg shares his perspective on the conclusion and mentions that the strategy for improving project health based on complexity and lifecycle stages seems self-evident. Sophia mentions that it doesn’t fully address the lifecycle of contributors beyond the onboarding phase and points out there is a lack of discussion about when contributors may want to step away from a project and the issue of aging out of longstanding projects. Value Adds (Picks) of the week: [00:36:44] Georg’s pick is visits from families. [00:37:08] Anita’s pick is recently getting her Bachelor of Science in Microbiology and wondering what her next steps are. [00:37:39] Dawn’s pick is walks around the Old Town section of her neighborhood seeing really old buildings. [00:38:18] Alyssa’s pick is the sun and seeing a Yayoi Kusama art show. [00:39:14] Sophia’s pick is making a lot of homemade herbal tea. Panelists: Georg Link Dawn Foster Sophia Vargas Alyssa Wright Anita ihuman Links: CHAOSS (https://chaoss.community/) CHAOSS Project Twitter (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) podcast@chaoss.community (mailto:podcast@chaoss.community) Ford Foundation (https://www.fordfoundation.org/) Georg Link LinkedIn (https://www.linkedin.com/in/georglink/) Dawn Foster Twitter (https://twitter.com/geekygirldawn?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Sophia Vargas Twitter (https://twitter.com/Sophia_IV) Alyssa Wright LinkedIn (https://www.linkedin.com/in/alyssapwright/) Anita ihuman Twitter (https://twitter.com/Anita_ihuman) Linux Foundation Research Open Source Maintainers July 2023 Report (https://project.linuxfoundation.org/hubfs/LF%20Research/Open%20Source%20Maintainers%202023%20-%20Report.pdf?hsLang=en) Mozilla-Open Source Archetypes: A Framework For Purposeful Open Source (https://blog.mozilla.org/wp-content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf) Yayoi Kusama (https://en.wikipedia.org/wiki/Yayoi_Kusama) Special Guests: Alyssa Wright and Anita ihuman.

    Kelsey Hightower—Present

    Kelsey Hightower—Present

    In this bonus episode, we hear from Kubernetes superstar Kelsey Hightower. Diving into crucial elements like empathy in maintainership, succession planning, and the identification of future leaders, hosts Martin Woodward and Neha Batra explore Kelsey’s philosophy on fostering thriving open source communities—and his hopes for the future state of Kubernetes. Dedicated to GitHub’s Maintainer Month, the conversation focuses on the people behind the projects, highlighting their extraordinary effort and celebrating their impact on the community. To close out this special episode, members of The ReadME Podcast community thank maintainers who have had a positive impact on them.

    Here’s what’s in store for this episode:

    • 00:00 - Introduction: The hosts discuss GitHub May-ntainer Month and introduce Kelsey Hightower!
    • 1:07 - The interview: Kelsey talks the hosts through how he got into tech, how maintainers can avoid burnout, the importance of identifying new leaders, what the future holds for Kubernetes and much much more!
    • 32:55 - Maintainer shout-out!  ​​Aaron Francis, Cassidy Williams, Frances Coronel, Anthony Sottile, Peter Strömberg, and Brandon Ringe call in to  share their appreciation for fellow maintainers in their lives.

    Special thanks to our guest, Kelsey Hightower, and to all of the maintainers who called in to share appreciation for their fellow maintainers. 

    Check-out The ReadME Project, for more episodes as well as featured articles, developer stories, helpful guides, and much more! Send your feedback, questions, and ideas to thereadmeproject@github.com.

    Freedom Watch Update - June 17

    Freedom Watch Update - June 17
    This edition features a story about how every machine in the military requires maintainers. Marine Cpl. Clayton Rogers takes us to forward operating base Fenty where air craft maintainers from Task Force Six Shooters keep busy to keep the birds in the sky. Soundbite includes Spc. Alan Janes - Delta Troop 66 Maintenance Platoon - Black Hawk Mechanic. Hosted by Petty Officer 2nd Class Sally Foster and Produced by Cpl. Clayton Rogers. Also available in High Definition.

    Engage the 3 Types of Employees: Builders, Maintainers, and Departers with Chet Lovegren

    Engage the 3 Types of Employees: Builders, Maintainers, and Departers with Chet Lovegren

    On this episode of the In the Club Podcast by Club Colors, we feature Chet Lovegren, the Founder of The Sales Doctor, Host of The Sales RX, and The Founder's Formula Podcasts. Today, Chet digs into how leadership styles fundamentally differ between Boomers, Gen X-ers, Millennials, and now Gen Z.

    Chet describes the 3 types of employees: Builders, Maintainers, and Departers. Each type plays a role in the company, but the goal is to concentrate 80% on the top 20%, which comprises Builders and Maintainers. As for the Departers, Chet says to either move them up to become a Maintainer or move them out.

    Leaders need to engage with each employee type differently. John shares his own Highlighter Method while Chet talks about the environments in which Builders and Maintainers excel. Chet also shares his 5-5-5 Rule that instills good leadership within a culture and gives his insights on better communication, building brand advocates, and helping SaaS companies grow their sales teams.

    As always, stick around for the Hot Iron with JMo where we find out about Chet's dream to advertise at SaaStr and his thoughts on what the moon really is! 

    HIGHLIGHT QUOTES

    Defining the Builder - Chet: "In any company, there are 3 types of employees. There's Builders, there's Maintainers, and Departers. Builders are your day ones, they're the people that are going to build with you, they're going show up early, they're going to put in the extra effort."

    Do NOT punish Builders to deal with Departers - Chet: "Stop spending 80% of your time on the bottom 20% of people because what ends up happening, and I see this all the time is you turn into what's called a reactive leader where somebody at the bottom, it's one of your departers, does something that either ticks you off or hurts your number or gets your boss to talk down to you, or whatever that might be, and then you go implement this wild accountability rule that you're builders are like, dude, I'm doing my job."

    Reps who don't perform well are a reflection of their leaders - Chet: "The sad truth is everything about your reps has to do with you as a leader. And so if you have people that are experiencing symptoms that are bringing them down, it's your inability to give them a clear-cut vision. I think leaders do such a bad job of tying things to personal goals. Even if I'm a Maintainer, I have a goal."

    Connect with Chet:

    LinkedIn | TikTok | Linktree

    If you enjoyed this episode of In the Club Podcast with Club Colors, please leave us a review on your favorite podcasting platform!

    Listos para el commit: la lucha por el código abierto

    Listos para el commit: la lucha por el código abierto

    ¿Quieres iniciarte en el código abierto pero no sabes por dónde empezar? ¿Ya eres colaborador y no entiendes por qué solo se aceptan algunas solicitudes de extracción? ¿Eres mantenedor y te sientes abrumado? En este episodio analizamos lo que implica el compromiso con un proyecto de código abierto. Acompañamos a nuestros héroes a medida que avanzan en su papel de colaboradores del código abierto: desde encontrar proyectos y contribuir a ellos, hasta desarrollar y mantener comunidades prósperas. Shannon Crabill nos cuenta cómo se inició en el código abierto en Hacktoberfest 2017. Existen muchas maneras de contribuir al código abierto. Vamos a verlas juntos.

    Three Types of Technology Leaders

    Three Types of Technology Leaders

    Technology leaders have many different focus areas and motivations. On today’s show, we’ll discuss three common types of leaders - Visionaries, Maintainers and Resume-Builders.

    SHOW: 501

    SHOW SPONSORS:


    CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw

    CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"

    SHOW NOTES:

    THREE TYPES OF TECHNOLOGY LEADERS

    VISIONARIES | TRANSFORMERS

    • Speak in stories, painting big pictures.
    • Truly understand the overall business, the broader markets, and the potentially changing landscapes ahead over both the near-term and long-term
    • Understand the timing of the markets and when change is needed vs. nice-to-have
    • Understand the breadth of competitive threats to the business
    • Understand both opportunities and opportunity costs 

    MAINTAINERS | PROTECTORS 

    • Would like to be a visionary, but always default back to focusing on re-optimizing legacy investments
    • Tend to believe that all decisions are build vs. buy. Aren’t focused on creating longer-term partnerships
    • Run long RFI processes vs. creating a mindset of incremental experimental scenarios.
    • Have a protectionist mindset (“avoid vendor lock-in”) with new opportunities, but don’t release that with sunk costs. 

    RESUME BUILDERS

    • Recognize that the world is moving fast (lots of new technologies, business models), but aren’t in an optimal starting position.
    • Establish a big, audacious goal that portrays a visionary mindset. 
    • Establish an “everything” or “all-inclusive” policy, even when it doesn’t make economic sense. 
    • The old 5yrs of building an ERP system is now the 2yrs of transforming to the cloud. Springboard to build the resume without finishing the project. 


    FEEDBACK?

    Ep06 - Supporting FOSS Maintainers, handling conflict, Homebrew & Software Freedom Conservancy with Mike McQuaid

    Ep06 - Supporting FOSS Maintainers, handling conflict, Homebrew & Software Freedom Conservancy with Mike McQuaid
    On this episode we welcome Mike McQuaid, a long standing maintainer (10+ years) and project lead of Homebrew. We talk about Mike’s journey of becoming a maintainer and how he manages to sustain a healthy relationship with his project and it’s community by establishing a good work life balance and having a clear definition of a maintainer’s responsibilities. As a strong advocate for supporting maintainers Mike describes how he and Homebrew’s team of maintainers deal with the negativity of both the job and certain members of the community by the use of tools, bots and a supportive approach to day to day working with one another. We also talk about Homebrew’s progression to becoming a member project of the Software Freedom Conservancy and the benefits it brings to both the project and those involved.

    Ready to Commit: Contributing to Open Source

    Ready to Commit: Contributing to Open Source

    Looking to get into open source but not sure where to start? Are you a contributor trying to understand why only some pull requests get accepted? Or are you a maintainer who’s feeling overwhelmed?

    This episode looks at what it means to commit to an open source project. We follow our heroes as they progress through the roles of open source contributors: from finding projects and contributing to them, to building and maintaining thriving communities. Shannon Crabill shares how she got her start in open source at Hacktoberfest 2017, and Corinne Warnshuis describes how important it is to include people from all backgrounds to create good software. There are many ways to contribute to open source. Let’s walk through this together.

    For more about the characters, history, and stories of this episode, visit redhat.com/commandlineheroes. While there, check out how you can contribute to hero-engine and Command Line Heroes: The Game — all levels welcome.