CHAOSScast

Thank you to the folks at Sustain 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:

Panelists:

Georg Link

Dawn Foster

Sophia Vargas

Alyssa Wright

Anita ihuman

Links:

CHAOSS

CHAOSS Project Twitter

CHAOSScast Podcast

[email protected]

Ford Foundation

Georg Link LinkedIn

Dawn Foster Twitter

Sophia Vargas Twitter

Alyssa Wright LinkedIn

Anita ihuman Twitter

Linux Foundation Research Open Source Maintainers July 2023 Report

Mozilla-Open Source Archetypes: A Framework For Purposeful Open Source

Yayoi Kusama

Special Guests: Alyssa Wright and Anita ihuman.

Support CHAOSScast

Thank you to the folks at Sustain for providing the hosting account for CHAOSSCast!

CHAOSScast – Episode 72

In this episode, our host, Matt Germonprez, is joined by Dawn Foster from the CHAOSS Community, Sophia Vargas from Google, and Gary White from Verizon. Today, they dive into the crucial topic of assessing the viability of open source projects for adoption within organizations. The discussion covers the intricacies of evaluating project viability, the challenges of project failure, and the necessity of continuous assessments. The panelists provide valuable insights on mitigating risks, leveraging metrics, and the importance of active engagement within open source communities. This episode offers a wealth of knowledge and practical advice for navigating the world of open source software. Download this episode now to hear more!

[00:02:13] The discussion begins on the importance of assessing the viability of open source projects for adoption within organizations. Gary emphasizes the need to formalize the assessment of open source project viability beyond just technical metrics, Sophia stresses the importance of rigor in evaluating open source tools due to the lower barrier to adoption, and Dawn points out the importance of context, where the viability assessment depends on how the project is used within the organization.

[00:06:32] The conversation shifts to when an open source project fails or changes significantly within an organization. Dawn discusses the challenges and uncertainty companies face when an open source project becomes unusable due to license changes or discontinuation, Sophia highlights the complexities and burdens of change management when a project fails, and Gary mentions the negative impact on morale and the time-consuming nature of dealing with project failures.

[00:10:55] Sophia discusses the challenges in communication between project leaders and end users, particularly when projects are consumed through third-party package managers. Gary highlights the challenge of getting project leaders and developers motivated to assess project viability and the need for data-driven metrics to facilitate communication between leadership and implementation teams.

[00:13:09] Dawn stresses the importance of continuous assessments of open source project viability rather than treating it as a one-time task.

[00:14:06] How do we assess if a project is good? Dawn discusses her historical approach to assessing open source projects, which included manual assessments.

[00:16:31] Gary emphasizes the common practice of engineers making quick project choices without thorough assessments due to the ease of finding solutions online.

[00:19:41] Sophia highlights the importance of considering how a project is used within the organization and the strategic implications of choosing open source projects, especially in large organizations.

[00:21:50] Matt asks about monitoring and mitigating risks when using open source projects that may not be ideal from a viability perspective but are popular. Dawn acknowledges that project viability is not binary and can vary in terms of risk, suggesting that contributing to open source projects can mitigate risks.

[00:22:56] Gary emphasizes the importance of becoming engaged and active members of open source communities to gain insight into project changes and mitigate potential risks.

[00 24:15] Sophia highlights the role of metrics and monitoring in risk mitigation, mentioning that tracking certain information may not be easy but it is crucial. Dawn notes the lack of ongoing viability monitoring and suggests the need for more sophisticated approaches.

[00:26:37] Gary agrees that monitoring is essential and mentions a metric called “lib year” to track the age of dependencies as an example of monitoring for open source projects, and he discusses the importance of automated recommendations within software scanning tools to help users make informed decisions about dependencies.

[00:28:27] Sophia addresses the challenge of scale when dealing with many open source projects, emphasizing the need to adapt monitoring and risk mitigation approaches based on the organization’s portfolio size.

Value Adds (Picks) of the week:

*Panelists: *

Dawn Foster

Sophia Vargas

Gary White

Links:

CHAOSS

CHAOSS Project Twitter

CHAOSScast Podcast

[email protected]

Ford Foundation

Georg Link Twitter

Matt Germonprez Twitter

Dawn Foster Twitter

Sophia Vargas Twitter

Gary White LinkedIn

libyear

OSS Project Viability Metrics Models:

Special Guest: Gary White.

Support CHAOSScast

Thank you to the folks at Sustain for providing the hosting account for CHAOSSCast!

CHAOSScast – Episode 71

In this episode, the CHAOSScast team is back! Georg Link, Dawn Foster, Sean Goggins, Matt Germonprez, and Elizabeth Barron discuss the relaunch of the podcast after taking a short break. They delve into the fascinating world of open source community health, focusing on metrics, metric models, and the CHAOSS Project’s role in measuring the health of open source communities. They share insights on how they’re working to make metrics more accessible and how they interpret these metrics within the context of specific projects. Additionally, they highlight the Data Science Initiative, the growth of CHAOSS community chapters worldwide, and their initiative to improve newcomer experience and promote diversity and inclusion in open source. Download this episode now to find out much more!

[00:02:48] We hear more about where CHAOSS is with developing metrics and metric models and the Context Groups they’ve developed to bring together individuals interested in the health of specific projects or communities.

[00:06:06] The Metric Development Process is brought up, which is the process of defining and releasing metrics has evolved. While some working groups still develop metrics, there’s an effort to consolidate and organize metrics to make them more accessible to users, including categorizing and tagging them.

[00:08:11] Dawn brings up Metrics Models which are collections of metrics that provide insights into specific aspects of open source community health. These models help users understand various phenomena in open source software health and use metrics effectively.

[00:12:14] Georg brings up something new called the Data Science Initiative within CHAOSS, and Dawn talks about her role as Director of Data Science. The initiative aims to provide guidance to users of CHAOSS metrics and tools for interpreting data effectively and she tells us all the key areas that it’s focused on.

[00:16:14] Matt asks Dawn about the balance between maintain an agnostic stance on metrics and providing more guidance to users in interpreting metrics. Dawn discusses the importance of helping users interpret metrics in the context of their specific projects.

[00:17:55] Georg and Dawn talk about using metrics as pointers to prompt users to investigate specific aspects of their communities and projects.

[00:18:53] Elizabeth asks if CHAOSS should play a role in advising users on how to make changes in their communities based on metric insights without adversely affecting other metrics. Dawn shares her thoughts and Sean mentions the experience of CHAOSS members in evaluating different communities and interpreting metrics.

[00:20:34] Georg expresses excitement about the future of CHAOSS and its journey.

[00:21:54] Sean provides an overview of Augur and its evolution over time, including its ability to capture large volumes of data and the development of an API.

[00:24:19] Georg discusses recent developments in Grimoire Lab, including multi tenancy support, scalability improvements, and optimization of data enrichment processes. He also talks about the migration of Grimoire Lab from Elasticsearch to OpenSearch for data storage and visualization, and Sorting Hat, a module within Grimoire Lab for managing identities.

[00:27:40] Dawn asks about the future use of Kibiter, the Kibana fork used in Grimoire Lab, and Georg confirms a full migration to OpenSearch and Open Search Dashboards, indicating that Kibiter may be phased out.

[00:28:52] Matt asks about recent challenges and achievements related to data management and data cleaning in Augur and Grimoire Lab. Sean mentions the importance of data in operationalizing metrics and making them tangible. Georg emphasizes two critical aspects of data quality.

[00:33:32] Elizabeth shares insight into the growth of the CHAOSS community. She discusses the challenges of managing the growing community, and a group CHAOSS is partnering with called “All in” to develop badging for open source projects, addressing scalability challenges.

[00:41:53] Elizabeth talks about the DEI Reflection Project which was crucial in identifying blind spots and improving the CHAOSS community. It led to valuable recommendations, including enhancing the newcomer experience and promoting diversity and inclusion.

Value Adds (Picks) of the week:

*Panelists: *

Georg Link

Dawn Foster

Matt Germonprez

Sean Goggins

Elizabeth Barron

Links:

CHAOSS

CHAOSS Mastodon

CHAOSScast Podcast

[email protected]

Ford Foundation

Georg Link Website

Dawn Foster Twitter

Matt Germonprez Twitter

Sean Goggins Twitter

Elizabeth Barron Twitter

CHAOSS Data Science Working Group

Data Science Initiative-Raw data from the Understanding Challenges survey

Augur repositories

Project Aspen

8Knot-Metrix CHAOSS

Bitergia Analytics- GrimoireLab

OpenSearch

Sorting Hat

Kibiter

OpenSearch Dashboards

All In

GitHub All in

CHAOSS Software

CHAOSScast Podcast-Episode 54: CHAOSS DEI Reflection Project

Support CHAOSScast

Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. Venia and Lori are hosting a special revisit episode with special guest, Chris Mercer, Co-Founder of Measurement Marketing.io. Today, we’ll find out what Measurement Marketing does, where we were with measurement when Chris was on last, and how things have changed throughout the years. He goes in depth about the new Measurement Marketing Framework, the ACE model, and he shares his thoughts on Google Analytics 4 and why he thinks now is the time to get into it. Download this episode now to find out much more, and don’t forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues!

[00:02:22] Chris tells us his background and what Measurement Marketing does.

[00:03:47] When Chris was on this podcast previously there was this notion of measuring frameworks and measuring a system, Chris details where we were originally with measurement and how things have changed.

[00:05:17] We hear about the new Measurement Marketing Framework and the three simple steps: Plan it out, build it out, and launch it.

[00:09:39] Chris lets us know what has stayed the same in his business.

[00:10:57] We find out how Chris applies the measurements to open source as a customer journey, and he explains the ACE model that they teach.

[00:14:36] Venia wonders if Chris is finding that Google Analytics 4 moving more in line with that synchronicity of measuring behaviors as they happen and as people use the system, and where does he see Google Analytics fitting into this new way of measure.

[00:19:52] Chris shares his thoughts on whether he thinks that Google Analytics 4 is going to move more into a community operations role in any way.

[00:21:22] Lori asks Chris for tips on some struggles she has as a Community Manager with how to relate data to someone in a CEO or OPS position in their language versus speaking community speak.

[00:32:03] Find out how measurement is changing as Chris explains.

[00:36:03] Venia wonders how Chris imagines community and this new notion of a measurement department meshing and working together.

Value Adds (Picks) of the week:

**Panelists:

Guest:

Sponsor:

Links:

Special Guests: Chris Mercer and Lori Goldman.

Support CHAOSScast

Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. Welcome back to Part Two to a conversation we had with our amazing guest, Hedan Zeng, who’s the Director of Product Management at Common Room. In Part One, we spoke to Hedan about the development of Common Room, the history of Hedan’s personal journey in community, and what Common Room’s real philosophies around community health have been. Today, we brought her back so we can talk more about our metrics. Download this episode now to find out much more, and don’t forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues!

[00:03:22] Hedan does a quick recap of what Common Room the platform does.

[00:04:19] In the last episode, Hedan mentioned area they look at the health of the community, and one of them was around engagement and metrics around engagement, and she tells us things she has found valuable for her customers to look at.

[00:10:24] Venia brings up grapevine or unstructured community spaces, and she wonders how Hedan tackles these different sentiment developments in the actual metrics path and data flow for her system.

[00:12:48] Sophia wants to know if there are different ways that Hedan addresses the same kind of questions in terms of guiding her customers and understanding the nuances between platform sources and sentiments.

[00:14:52] We find out how Common Room addresses the nuance between these personas that while they might have some overlap, tend to have different orientations.

[00:16:47] Does Hedan think that there’s some explicit differences between how Common Room would tackle to completely different community avatars?

[00:19:07] Hedan tells us about some specific metrics to understand the different pieces that she’s been seeing.

[00:21:41] Venia brings up community interaction and Hedan talks more about how she’s generating that 3X engagement factor.

[00:23:38] Sophia wonders if Common Room can identify whether or not folks are at risk of burnouts, and Hedan tells us about how Common Room does a surface sentiment at a member level.

[00:28:38] We find out how Hedan’s user experience makes decisions about the metrics and the way she visualizes this data in her platform.

[00:32:22] We learn the process Common Room makes the users who are interacting and visualizing the data they go through.

[00:35:10] Looking at the membership statistics around various different platforms, Sophia wonders if this could be an effective way to gauge an open source project’s usage and then knowing that, we find out if it’s enough or if anything is missing to make a better assessment of the overall user community size.

[00:36:47] Find out where you can follow Hedan and Common Room online.

Value Adds (Picks) of the week:

Panelists:

Guest:

Sponsor:

Links:

Special Guest: Hedan Zeng.

Support CHAOSScast

Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. We are super excited to have joining us as our guest, Hedan Zeng, Director of Product Management at Common Room, the intelligent community growth platform for today’s fastest-growing companies. Today, we’ll learn all about Common Room and how they think about metrics. We’ll also find out about the metrics they use, and Common Room’s theory and approach to design, from data to user interface. Download this episode now to find out much more, and don’t forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues!

[00:01:38] Hedan tells us all about Common Room.

[00:04:11] Hedan dives into how they think about metrics at the Common Room, and she explains each of the metrics they use such as membership, community responsiveness, and sentiment.

[00:08:26] We find out what Hedan’s role is at Common Room and the steps that led her to forming where she is today, which includes her experience working at Medallia.

[00:15:02] Sophia wonders if Hedan is seeing any behaviors that surprised her or she wasn’t expecting to see from the application of the software.

[00:20:32] Find out if Common Room have words that they’ve put to that different philosophy of measurement.

[00:23:12] We learn about the process Hedan has for identifying which of these different usernames on different platforms actually belong to the same person.

[00:26:03] Hedan explains how she navigates the difference between I need to present in my community and engage in the social contract of listening to people versus this is a thing I could automate and build a workflow for this.

[00:28:42] We hear how Hedan is helping customers navigate through varying privacy/data sharing policies, and she shares advice for open source projects and communities.

[00:31:45] Find out where you can follow Hedan online.

Value Adds (Picks) of the week:

Panelists:

Guest:

Sponsor:

Links:

Special Guest: Hedan Zeng.

Support CHAOSScast

Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. Today, we are excited to be joined by two guests, Iyimide Adegunloye (Mide) and Precious Abubakar, who participated in the She Code Africa Program. We invited them to talk about the program and share what they’ve done, as well as discussing bots and the welcoming of newcomers. Download this episode now to find out much more, and don’t forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues!

[00:02:55] Mide and Precious give us a brief introduction about themselves.

[00:04:20] We find out the details on the She Code Africa Program, their experience with getting into She Code Africa, how they found CHAOSS, and how they decided to engage with the CHAOSS Project.

[00:08:54] We learn how the idea of the bot came about and the design process.

[00:13:26] There’s a discussion about the kinds of challenges they faced in creating the bot and what they learned in the process.

[00:16:34] Georg wonders how the response has been in the community since the bot was implemented.

[00:19:14] Mide explains more about the use of the bot at She Code Africa.

[00:20:22] Precious and Ruth fill us in where they think the project will go next and share some ideas for the future.

[00:21:50] If you would like to get involved, find out where you can connect to get started.

[00:23:34] Mide and Precious share how the mentorship helped them understand CHAOSS. We also hear from the mentors what they’ve learned in this program or if they’ve learned to appreciate CHAOSS in a different way.

Value Adds (Picks) of the week:

Panelists:

Guests:

Sponsor:

Links:

Special Guests: Iyimide Adegunloye (Mide) and Precious Abubakar.

Support CHAOSScast

Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. Today, we are joined by two wonderful guests that Venia met during an amazing talk at the Community Spaces. We have Victoria Cumberbatch, Founder of adventuresOFcommunity, a Community Development Consultancy, and Bri Leever, a Community Architect and Founder of Ember. Our conversations take us through finding out how everyone got their start in community, and what numbers mean for our brands and what they’ll mean for open source health. Also, we’ll find out about Bri’s learning journey, and more about the metrics Bri and Viki are using and the kinds of stories they’re telling with them. Download this episode now to find out much more, and don’t forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues!

[00:02:33] Bri, Lori, and Viki fill us in on how they got started in community and where their love of community came from.

[00:09:15] Georg shares his story of how he got his start in community.

[00:12:57] There’s a great discussion about what numbers really mean for our brands and what they’ll mean for open source health afterward.

[00:16:45] Venia brings up a story about Morning Brew talking about the progression of their community, and Bri tells us about a community she’s managing for the company Piktochart and how they manage their metrics and interesting things they do with her.

[00:20:29] Bri mentioned the learning journey, and she explains what she considers the learning journey, the kinds of stories she finds herself telling, and the metrics she’s weaving in with the learning journeys.

[00:24:04] Venia talks about Chris Mercer and one of his main statements is no one is a numbers person, and Bri adds be saying, the power is in the pattern, and she tells us about a book called, Think Again: The Power of Knowing What You Don’t Know by Adam Grant.

[00:25:56] We hear what kind of metrics Viki uses, the kinds of stories she’s telling with them, and using the Cultural Adjustment Graph. Bri and Lori share some thoughts as well.

[00:32:30] Lori explains some of the behaviors she was speaking about.

[00:34:40] Venia asks everyone how they would systemize and turn that story into something that people can query on a weekly basis whenever they need. Bri tells us about a community platform called, Heartbeat.

[00:41:41] Georg highlights CHAOSS software.

[00:42:41] Find out where you can follow Viki and Bri online.

Value Adds (Picks) of the week:

Panelists:

Guests:

Sponsor:

Links:

Special Guests: Bri Leever, Lori Goldman, and Victoria C.

Support CHAOSScast

Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. Today, Georg has two experts in analyzing open source community repositories joining him from Arnica, which is focused on software security supply chain security. Our two guests today are Chris Abraham, Head of Data Science, and Nir Valtman, Co-Founder and CEO, and they’re here to tell us about an analysis they conducted called, “How do top open-source projects protect their code?”, the story behind why they decided to do this, and some surprising things they learned from the analysis. Download this episode now to find out much more, and don’t forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues!

[00:01:09] Chris and Nir introduce themselves, how they got into open source, what brought them to Arnica, and what they’re doing now.

[00:05:38] Georg brings up a blog post that Chris and Nir wrote on, “How do top open-source projects protect their code?” and we hear why they did this study and how they went about doing it.

[00:09:11] When looking at the data, Georg asks if people have policies around it and if we can infer from it if there’s a security issue or not. Also, Nir and Chris detail how they went about collecting data and looking at what open source is doing.

[00:14:15] Chris and Nir wanted to know if code owners contribute to quality, and we find out how they assessed quality.

[00:19:57] We learn some surprising things Chris and Nir learned from the analysis.

[00:22:10] Georg mentions maintainer burnout and the workload that is being put on maintainers, and he asks how Chris and Nir see the security controls contributing to maintainer burnout or even helping the demands on maintainers.

[00:27:24] Chris and Nir looked at the top 250 projects on GitHub, they tell us how the findings apply to smaller open source and the long tail of projects we have.

[00:33:28] Find out where you can follow Chris and Nir and the work they’re doing.

[00:34:45] Nir tells us about their open source project called, GitGoat.

Value Adds (Picks) of the week:

Panelist:

Guests:

Sponsor:

Links:

Special Guests: Chris Jacob Abraham and Nir Valtman.

Support CHAOSScast

Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. We are super excited to have joining us, Maurice Hendriks, who works for the Municipality of Amsterdam as a policy maker, specifically on the topic of Open Source. He’s here to share his journey into open source and to talk more about his views on open source. Download this episode now to find out much more, and don’t forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues!

[00:01:56] Maurice shares his journey into open source and how he got into the field.

[00:05:23] Sean wonders if misunderstandings affect the work that Maurice is trying to accomplish, and Maurice talks about the laws in Netherlands and how open source is essential for the morality of the city.

[00:09:36] From the government perspective Maurice talked about, he explains different perspectives on what a healthy open source project or community is.

[00:12:24] Are these other governments, other municipalities in Netherlands that are using the open source software, built in Amsterdam?

[00:17:28] Maurice explains how policy would potentially influence this social system.

[00:21:16] We find out the difference between open sourcing something and having something publicly available.

[00:23:39] What bothers Maurice as a policy maker?

[00:26:15] Sean brings up a point about if software is a social good open sourcing, there needs to be a way for that to be sustainable so it’s not just Maurice that’s maintaining a particular project, and he wonders how Maurice balances that.

[00:29:08] We hear the main lesson people should get from Maurice’s vision.

[00:30:05] Find out where you can follow Maurice’s and his work online.

Value Adds (Picks) of the week:

Panelists:

Guest:

Sponsor:

Quotes:

Links:

Special Guest: Maurice Hendriks.

Support CHAOSScast