Log in

goodpods headphones icon

To access all our features

Open the Goodpods app
Close icon
headphones
Sustain

Sustain

SustainOSS

Sustain brings together practitioners, sustainers, funders, researchers and maintainers of the open source ecosystem. We have conversations about the health and sustainability of the open source community. We learn about the ins and outs of what ‘open source’ entails in the real world. Open source means so much more than a license; we're interested in talking about how to make sure that the culture of open source continues, grows, and ultimately, sustains itself.

Newsletter

bookmark
Share icon

All episodes

Best episodes

Top 10 Sustain Episodes

Goodpods has curated a list of the 10 best Sustain episodes, ranked by the number of listens and likes each episode have garnered from our listeners. If you are listening to Sustain for the first time, there's no better place to start than with one of these standout episodes. If you are a fan of the show, vote for your favorite Sustain episode by adding your comments to the episode page.

Guest

Nicholas Zakas

Panelists

Richard Littauer | Justin Dorfman

Show Notes

Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Our guest today is a returning guest that we’ve had on before. We are excited to have joining us, Nicholas Zakas, who’s one of the maintainers on ESLint, which is a tool that helps you find and fix problems in your JavaScript code. Today, we’ll learn all about ESLint, the maintainers, contributors, and how they get paid. Also, we’ll find out the success behind ESLint, and a post about sponsoring dependencies that Nicholas wrote on his blog. Go ahead and download this episode now to learn more!

[00:02:23] Nicholas tells us all about ESLint, their maintainers that work on the project, and how many people have contributed to the project on GitHub.

[00:07:29] Nicholas tells us how maintainers get paid as part of his governance strategy.

[00:10:04] Justin asked about the fact that ESLint not only pays contributors, but also pays downstream dependencies.

[00:12:04] Richard wonders where all the money comes from that gave ESLint this huge surplus, and Nicholas explains how they raised so much and what it is about ESLint that makes that possible.

[00:16:10] We hear some reflections from Richard as he congratulates Nicholas and makes some important points about the success of ESLint.

[00:20:19] Nicholas fills us in on the OpenJS Foundation Project.

[00:23:57] Richard talks about a blog post Nicholas wrote on his blog about sponsoring dependencies, and Nicholas explains the difference between large charismatic projects and smaller projects and how he sees the role of large projects in funding the smaller ones.

[00:31:41] We hear what ESLint did with sponsoring dependencies, and Nicholas tells us about some projects that they wanted to support financially, but turned them down.

[00:38:06] Find out where you can follow Nicholas and ESLint online.

Quotes

[00:07:43] “Everybody on the team, the committers, reviewers, technical steering committee, gets paid an hourly rate for their contributions.”

[00:07:53] “Contributions can be anything that contributes to the project, reviewing issues and pull requests, attending meetings, helping people on discord, helping people on GitHub discussions, and if people ever go to conferences or meetings representing the team, they can also charge for that.”

[00:10:15] “We made a decision the beginning of last year that it was time to start supporting our dependencies.”

[00:12:28] “I do think we are lucky in a lot of ways that we’ve had champions inside of companies who were working within their company to get ESLint’s support.”

[00:13:13] “In the beginning, we were hesitant to start spending the money because we didn’t know how reliable that source of income would be, and we were worried we wouldn’t be able to pay a living wage.”

[00:21:25] “Being in a foundation is one type of a reputational check mark that an open source project can get.”

[00:26:15] “I think OpenSSL is a great example of [the funding problem]. It’s a foundational piece of internet infrastructure.”

[00:28:31] “We went on backyourstack.com and started looking for the projects that we were depending on that had Open Collective pages and said, as a project, what is good for open source in general, is also good for ESLint.”

[00:29:20] “Open source, in general, is this collective of projects that are built on top of projects that are built on top of projects that are built on top of projects, and we have no problem giving that recognition when we’re talking about what the project is built upon.”

Spotlight
  • [00:39:47] Justin’s spotlight is the new book, What if? 2 by Randall Munroe.
  • [00:40:31] Richard’s spotlight is David Troupes, Buttercup Festival comic strips.
  • [00:41:03] Nicholas’s spotlight is the book, WebAssembly: The Definitive Guide by Brian Sletten
Links
Sponsored by Linode


Panelists

Eric Berry | Justin Dorfman | Pia Mancini | Richard Littauer

Guest

Kaitlin Thaney
Invest in Open Infrastructure (IOI)

Show Notes

Hello and welcome to Sustain! Today, we have Kaitlin Thaney, who is the Executive Director for Invest in Open Infrastructure (IOI). Kaitlin will tell us all about IOI and what she’s doing there. She also explains the history of the Mozilla Science Lab and how her team came up with it. How has COVID impacted the organization, especially since her first day of the job was when New York City went into lockdown! Download this episode now to find out!

[00:01:17] Kaitlin tells us what Invest in Open Infrastructure is and what she’s doing there.

[00:04:17] Eric wants to know is this organization built to create essentially just the technology behind these infrastructures or is it primarily ways of sharing data? Kaitlin explains the end goal in simplistic terms.

[00:09:50] With Kaitlin’s background and previous organization’s that she’s worked for (Wikimedia, Mozilla, and Creative Commons), Justin wants to know how those former employers shaped her for what she’s doing now as an Executive Director.

[00:16:41] Kaitlin explains Mozilla Science Lab. She also has a call to action called “Get credit for your code!” She talks about this and how she and her team came up with it.

[00:21:35] Richard asks Kaitlin to tell us what Elsevier is and how they represent what’s happening in academia now. Also, since she started this initiative before COVID happened, she tells us how she’s adapted, how she’s changed, and what’s happening moving forward.

[00:28:21] Pia wants to know from Kaitlin what the broad impact COVID has had and what are her plans going forward, and how are folks thinking about this?

[00:33:12] Richard gives a s/o to the Schmidt Foundation for funding Invest in Open Infrastructure (IOI).

[00:33:42] Kaitlin lets us know how you can get involved with her project if you are a software developer, work at a university, or a researcher. Also, how you can find her and where can you sign up.

Spotlight
  • [00:34:35] Richard’s spotlight is BibTeX.
  • [00:35:02] Justin’s spotlight is Undraw.co.
  • [00:35:28] Eric’s spotlight is Betterhelp.com and Therapistaid.com (both worth checking out)
  • [00:37:55] Pia’s spotlight is Excalidraw.
  • [00:38:43] Kaitlin’s spotlight is a portable Informed Consent Toolkit from Sage Bionetworks.
Quotes

[00:13:55] “You all know the deep roots that Open Source has, and software and the internet have in science. But beyond those initial stories, I think there’s an interesting kind of proof space that this sort of work allows for, because in terms of moving decisions forward, it’s not just talking about researchers. It also touches those in the education sector, universities, policy makers, for profit tech, and non-profit tech. All of these various elements that by their very nature, help bring and incubate different solutions that you can then apply to broader society.”

Links

Invest in Open Infrastructure

Open Infrastructure in times of crisis: How IOI can help

Kaitlin Thaney Twitter

Kaitlin Thaney (IOI)

Mozilla Science Lab-Get credit for your code!

BibTeX

unDraw.co

Betterhelp.com

TherapistAid.com

Excalidraw.com

Schmidt Family Foundation

Credits

Special Guest: Kaitlin Thaney.

Support Sustain

bookmark
plus icon
share episode
Guest

Mohammed Shah

Panelist

Richard Littauer

Show Notes

In this episode, host Richard engages in a conversation with guest Mohammed Shah about open source sustainability and the significant challenges faced by open source maintainers. Mohammed shares his background as a full-stack developer and discusses his involvement in a project aimed at reducing prediabetes risk using a WhatsApp chatbot. The discussion delves into the WhatsApp chatbot project, potential violations of WhatsApp’s terms of service, and the unique license used. Mohammed recounts the distressing experience of receiving cease and desist letters, leading to his decision to step down as the project’s maintainer. Richard and Mohammed explore the difficulties faced by open source maintainers and the need for collective representation, including the idea of forming an open source developer union. Mohammed also tells us about a climate-related initiative he’s working on and a website he set up called CVE.Earth, for tracking corporate environmental destruction. Press download now to hear more!

[00:01:03] Mohammed introduces himself as a full-stack developer and talks about his involvement in a project called Antler, aimed at reducing the risk of prediabetes in specific communities using a WhatsApp chatbot.

[00:02:55] Mohammed explains the project, which involved creating a CLI tool that allows users to interact with their own WhatsApp accounts programmatically.

[00:04:02] The discussion touches on the potential violation of WhatsApp terms of service and how many projects in the space could be in violation.

[00:06:19] Richard asks about the license Mohammed used to put this code up. He explains the unique license he sued for the project, which allows for specific purposes but not for nefarious activities, and Richard mentions Mohammed’s Hippocratic + Do Not Harm License.

[00:07:35] Mohammed describes the distressing experience of receiving cease and desist letters which led him to step down as the project’s maintainer.

[00:09:27] Richard discusses the stress and challenges open source maintainers face when receiving cease and desist letters and the lack of resources to respond effectively.

[0011:05] Mohammed shares that the project is on hold, and he cannot transfer it to others due to the legal risk.

[00:12:24] We hear Mohammed’s idea of forming an open source developer union to deal with unique legal cases affecting a small group of developers but with broader implications. This union could help address legal challenges and protect open source developers. He emphasizes the need for collective power in the open source community, like other worker unions or collectives that have the ability to advocate for the rights of their members.

[00:13:58] Mohammed expresses that he wishes he had not put himself at risk with the project but defends open source work as a valid and important endeavor. He believes in the significance of open source work and its impact on a wide range of people.

[00:15:22] The discussion delves into the role of large tech companies as gatekeepers and how they exert control over access to their APIs. Mohammed suggests that these companies should provide APIs as public infrastructure for interoperability.

[00:17:54] Mohammed mentions a new project related to climate and corporate environmental responsibility that he’s been working on, and a website he set up called CVE.Earth, for tracking corporate environmental destruction.

[00:18:58] Find out where you can reach out to Mohammed on the web.

Spotlight
  • [00:19:46] Richard’s spotlight is Tom ‘spot’ Callaway, an awesome developer.
  • [00:20:36 Mohammed’s spotlight is two books: The Creative Act: A Way of Being and Silent Coup: How Corporations Overthrew Democracy.
Links
bookmark
plus icon
share episode
Guest

Daniel S. Katz

Panelists

Richard Littauer | Ben Nickolls | Amanda Casari

Show Notes

Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. We are very excited to have as our guest Daniel S. Katz, who’s Chief Scientist at the National Center for Supercomputing Applications (NCSA), Research Associate Professor in Computer Science, Electrical and Computer Engineering, and the School of Information Sciences at the University of Illinois Urbana-Champaign. He’s also a Better Scientific Software (BSSw) Fellow and is one of the founding editors and the current Associate Editor-in-Chief of The Journal of Open Source Software. His interest is in cyber infrastructure, advanced cyber infrastructure, and solving problems at scale, but he’s also interested in policy issues, citation, and credit mechanisms. Today, Dan is joining us to talk about the Research Software Alliance (ReSA), how academia has changed over the years, and why funding is necessary for these projects. Go ahead and download this episode now to find out more!

[00:04:39] Dan explains what the Research Software Alliance is.

[00:08:09] We find out the difference between the ReSA and URSSI communities.

[00:11:34] Richard wonders why funding is necessary for all these projects and how do we diversify our funding to make sure that it’s not just Sloan that does this.

[00:17:40] Ben asks if Dan thinks the conversation within academia and within research institutions is more mature and developed or more trustful compared to what’s happening in commercial industry right now.

[00:22:00] We find out why research software is fundamentally different from corporate software from the makers perspective, and Dan shares with us a project he’s working on called Parsl.

[00:26:25] Amanda brings up the Journal of Open Source Software and asks Dan if he thinks that software is viewed yet as a first class research project online with a published paper, and if not, what are the barriers and what things need to change in the academia industry.

[00:30:38] If you’re a Research Software Engineer, Software Engineer, Engineer, or at companies or academies, find out how you can get involved in ReSA. Dan also tells us more about the importance of funding.

[00:34:03] Find out the best places you can follow Dan online.

Spotlight
  • [00:34:45] Ben’s spotlight is his favorite piece of research work called FITS.
  • [00:35:24] Amanda’s spotlight is a paper she read titled, “Did You Miss My Comment or What?” Understanding Toxicity in Open Source Discussions
  • [00:36:37] Richard’s spotlight is a paper he read titled, “How many genera of Stercorariidae are there?”
  • [00:37:29] Dan’s spotlight is the book, Radical Candor by Kim Scott.
Links
bookmark
plus icon
share episode
Guest

Nolan Lawson

Panelist

Richard Littauer | Eric Berry | Justin Dorfman

Show Notes

In this episode of Sustain, Richard, Justin, and Eric revisit an unreleased interview with Nolan Lawson from 2020. They discuss Nolan's experience as a former maintainer of PouchDB, the emotional labor of being an open source maintainer, and the challenges that led him to step away from such high-profile projects. Nolan also shares his thoughts on the impact of reputation-driven development, open source community dynamics, and his journey towards a healthier relationship with open source. The conversation delves into the candid realities of burnout and the personal sacrifices often made by unpaid open source contributors. Nolan highlights his transition to more sustainable open source practices and his new interests including his work on a Mastodon client called Pinafore. Download now to hear more!

[00:01:43] Nolan explains his background with PouchDB and shares his fascination with databases and browser technologies.

[00:02:58] Richard shares his personal connection to PouchDB, mentioning how he discovered Nolan through his work on the project.

[00:03:26] Nolan talks about his blog post form 2017 titled, “What it feels like to be an open source maintainer,” which reflected on the emotional toll and burnout he experienced for maintaining PouchDB.

[00:05:33] Justin reflects on the impact of Nolan’s blog post, describing it as a “shot heard around the world” in the open source community.

[00:06:48] Eric asks why Nolan and other maintainers stay involved in open source despite the challenges. Nolan explains that reputational benefits and personal interest in the technology were initial motivators for staying involved.

[00:10:27] Eric asks Nolan how he realized it was time to step away from maintaining PouchDB. Nolan shares that personal life changes helped him reassess his involvement in open source and reflects on advice he received from other maintainers.

[00:14:36] Richard emphasizes the personal and emotional investment many maintainers have in their projects and Nolan acknowledges the privilege of being able to work on open source, but also the challenges it poses for maintainers who feel they cannot leave.

[00:21:13] Nolan shares stepping away from PouchDB has improved his mental health and personal relationships and he maintains smaller open source projects.

[00:24:00] Nolan explains the importance of being personally invested in a project and realizing when it’s time to move on and Justin reflects on his own experience of stepping away from maintaining a project after years of involvement.

[00:26:00] Eric asks if funding could have made a difference for Nolan’s involvement in open source, and Nolan shares that he avoided funding, preferring to keep his work as a “labor of love.”

[00:26:52] What is Nolan currently doing? He talks about maintaining a Mastodon client and focusing on personal projects that bring him joy.

[00:30:00] Richard discusses the importance of balancing open source work with personal life and the need for a sustainable approach to maintaining projects.

[00:30:46] Eric highlights the vulnerability and self-awareness Nolan has shown in discussing his open source journey, thanking him for sharing his experiences.

[00:33:13] Find out where you can follow Nolan on the internet.

Spotlight
  • [00:33:41] Justin’s spotlight is Metabase.
  • [00:34:16] Eric’s spotlight is Parametric.
  • [00:35:08] Richard’s spotlight is IPFS.
  • [00:35:22] Nolan’s spotlight is fake-indexeddb.
Links
Guests

Amanda Casari | Julie Ferraioli | Juniper Lovato

Panelist

Richard Littauer

Show Notes

In today’s episode of Sustain, Richard is joined by guests, Amanda Casari, devrel engineer and open source researcher at Google Open Source Programs Office, Julie Ferraioli, an independent open source strategist, researcher, practitioner, and Partner at Open Chapters, and Juniper Lovato, Director of partnerships and programs at the Vermont Complex Systems Center at UVM and Data Ethics researcher. Amanda, Julia, and Juniper join the discussion, bringing a wealth of expertise in the open source domain. The conversation gravitates towards an article co-authored by the guests, striking a balance between open source software and open source ecosystems research. The episode dives deep into the “10 simple things” format of the article, the crucial importance of collective conversations, and a keen exploration of open source researchers. Hit download now to hear more cool stuff!

[00:01:29] Richard tells us why he invited our three guests today and he talks about their previous accomplishments and backgrounds.

[00:02:17] Our discussion moves to the title of a new article co-authored by the guests. We hear about the intended audience of the article and the distinction made between open source software and open source ecosystems research.

[00:03:31] Richard brings up where the article fits in the academic landscape, and it’s revealed to be more editorial than research.

[00:04:17] There’s a conversation about the “10 simple things” format, its origin, and the motivation behind it. They put an emphasis on the need for collective conversation and the value of sharing experiences and knowledge.

[00:07:28] Richard brings up the idea of open source researchers and mentions various figures and institutions involved in open source research. Juniper clarifies the target audience for the article and its intentions, Julie shares her perspective from the industry side and the importance of a critical framework, and Amanda expresses her emotional response to some researchers’ approach towards the open source community.

[00:12:03] Julie discusses the emotional challenges that inspired the paper’s best practices emphasizing not repeating negative behaviors, and Juniper notes tension in research between benefits for the community and for the researchers emphasizing understanding norms and values for studying open source communities.

[00:13:52] Richard mentions there are nine principles in the paper and asks about the principle regarding treating open source ecosystems as systems “in production.” Amanda highlights the importance of considering the real-world impact of research in open source and mentions an incident where a university was banned from the Linux kernel due to disruptive changes.

[00:16:33] Julie emphasizes the potential broader impact on industry systems when modifying open source systems and she raises the point that tampering with open source systems might inadvertently affect critical infrastructure. Amanda comments on the increasing cybersecurity concerns around open source.

[00:19:18] Richard brings up a real-world example of a university introducing bugs to the Linux kernel and points out the need for considering ethical implications beyond just production systems.

[00:20:59] Richard draws parallels between addressing these issues and addressing racism, and Juniper adds that the scientific process is ongoing and should evolve with technology and societal values.

[00:21:53] Julie describes the complexity of open source funding and compensation and points out the challenge in understanding motivations and expectations of open source participants.

[00:24:07] Amanda emphasizes the difficulty of summarizing each section, noting that each one could be a chapter or book and she expresses her concerns about not just individual equity but organizational equity.

[00:25:59] Juniper raises the issue of invisible labor in open source.

[00:26:39] Julie highlights the importance of recognizing that open source repository data might not capture all the activity and contributions made by community members.

[00:27:37] Amanda discusses the challenges and importance of capturing data, especially when it may put individuals at risk. Juniper stresses the importance of involving communities in the research process and gaining their consent, ensuring their dignity, security, and privacy.

[00:29:49] Julie discusses the complexities of identity within the open source community, highlighting that individuals can hold multiple identities in this space.

[00:31:10] Richard adds that the insight shared are not just for open source researchers but also for anyone involved in the open source ecosystem. He emphasizes the need to be aware of biases and the importance of understanding the data one works wi...

bookmark
plus icon
share episode
Sponsored by Linode


Panelists

Allen "Gunner" Gunn | Justin Dorfman | Pia Mancini | Richard Littauer

Guest

Tobie Langel

Show Notes

Welcome to Sustain! On today’s episode, we have special guest, Tobie Langel, the Founder of UnlockOpen, from Geneva, Switzerland. Tobie tells us all about UnlockOpen and what he does there. He tells us how he focuses on convincing companies that they need to contribute back to Open Source. Other topics we will talk about are DevOps culture, prototype JavaScript framework not being updated since 2015, which Tobie extensively explains what happened, as well as speaking about lessons to be learned and things we need to be aware of. There is so much great advice and stories shared on this episode. Download it now!

[00:01:19] Tobie tells us about UnlockOpen and what he does.

[00:02:30] Richard wants to know how do you get in the door as a consultant to try to talk to people about how they should use Open Source and how do you pitch that to people that don’t know what Open Source is?

[00:08:04] Tobie discusses how he focuses on convincing companies that they need to contribute back to Open Source. Pia wonders if Tobie thinks we’re making progress towards cultural changes within the audience?

[00:12:10] Allen asks Tobie if he’s advancing the notion of DevOps as a gateway drug for all of this open culture. Tobie mentions a book he’s reading called, Accelerate, that_ _talks about the benefits of DevOps culture to companies from a business perspective.

[00:14:13] Justin wants to know where Tobie got his kind of background and he also wonders about project abandonment, and prototype JavaScript framework hasn’t been updated since 2015. So, what happened there and what lessons could be learned?

[00:24:06] Tobie speaks about learning from history, about lessons to be learned, and things we have to be aware of.

[00:26:06] Tobie mentions how he’s a huge fan of DHH and Basecamp and he gives some great advice that he’s learned on focusing on things that matter long term. Justin and Richard also have some positive advice and stories to share as well.

[00:35:25] Richard makes an awesome statement here about being resilient.

[00:36:20] Tobie tells us where we can find him to learn more about him.

Spotlight
  • [00:38:03] Justin’s spotlight is our first bonus podcast episode (#41) with Dave Gandy, and we discussed Font Awesome 6, the donut diet, commitments, and more. Check it out! ☺
  • [00:42:23] Allen’s spotlight is Open Tech Fund.
  • [00:38:56] Richard’s spotlight is Aral Balkan, a cyborg rights activist.
  • [00:39:17] Toby’s spotlight is a book by Nadia Eghbal called, Working in Public: The Making and Maintenance of Open Source Software.
Quotes

“It boils down to bottom line and top line. To some degree it’s more than that, obviously, culture, brand, making people feel happy to work in a company. All of those are critical for a company.”

[00:10:45] “And we are at the point where we need to cross the chasm. So maybe move that from being something that is essentially something adopted by a few really performant companies at the helm of this effort and move that across to become more mainstream.

[00:16:47] “And so the funny thing is I essentially learned JavaScript by reading the source code because there was no documentation and I started contributing to the library by writing documentation for it.”

[00:17:44] “It took a lot of time for Sam to realize that he was burning out and just couldn’t spend the time that was needed to give more authority to other people on the project.”

[00:21:58] “There was a lot of energy, and people are ready to do a lot of things for the rocket ship because you also benefit personally quite a bit when you’re investing your time in a rocket ship.”

[00:25:19] “This goes right to the heart of what we’re trying to talk about here. And so I think one of the things that I’m really picking up from what you’re saying is that it’s better to dedicate yourself towards an ideology of working well in the open, of working with other people, of trying to consistently not just stay ahead of the curve, but work in a way that what you do will matter later.”

[00:34:20] “At the same time you could carry that comparison even further kind of ad absurdum, like everything’s the same, because we all need to eat and we all get tired and we all get sleepy and we all get hungry, we’re all kind of anxious and we have to work with other people and what wears kind of annoying and it’s pretty tough.”

Links

Tobie Langel Twitter

UnlockOpen

...
bookmark
plus icon
share episode
Guest

Manuel Riel

Panelists

Richard Littauer | Justin Dorfman

Show Notes

Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Today, we are super excited to have as our guest, Manuel Riel, joining us from Austria. Manu ran a web development agency and launched multiple open source related products, including an invoice processing tool, and a backup service. He’s also the Co-founder of PikaPods, which is a container hosting service for open source apps. Manu is with us to talk about PikaPods. We’ll find out what it does, why it’s needed, the benefits of having it, the most popular app, and plans he has in the future for PikaPods. Go ahead and download this episode to learn more!

[00:01:23] Manu tells us his background, what PikaPods is, and about the apps.

[00:03:32] What’s the difference between Heroku, Netlify, and PikaPods?

[00:04:29] Since you can’t run your own stuff and you can’t edit the apps, Manu explains how this is an open source marketplace. We hear about PikaPods user base, how long he’s been up and running, and how many people are using the platform.

[00:06:11] Manu explains the one source of revenue they provide to open source office.

[00:09:06] We hear Manu’s selling point he pitches to open source maintainers and open source projects.

[00:11:45] Why did Manu choose to work with open source projects to host when there are other things available to him? Why PikaPods?

[00:13:32] Justin brings up pricing on PikaPods site and comments a trend with the ones that paid the least had the most demands. He wonders how Manu deals with that.

[00:15:04] Justin wonders if the services are subsidized by using the BorgBase infrastructure, and Manu explains how they are totally separate, and he tells us about his team.

[00:16:31] We hear if there are any collabs with maintainers Manu is working with since there are a lot of projects he hosts.

[00:18:02] Find out PikaPods most popular app, if there’s a limit, and if bandwidth is an issue.

[00:21:17] Manu shares some things he would like to do in the future with PikaPods.

[00:23:35] How does Manu position himself in the ecosystem and are there other things that could be used in collaboration with PikaPods that makes it easier for maintainers?

[00:25:37] Find out where you can follow Manu and PikaPods online.

Quotes

[00:10:08] “Hosting is not a good fit for part-time maintainers because it’s a big responsibility.”

[00:12:20] “The motivating event for me was the Log4j Vulnerability.”

Spotlight
  • [00:26:42] Justin’s spotlight is pydantic, data validation and settings management using Python type hints.
  • [00:27:10] Richard’s spotlight is Amna Shamim.
  • [00:27:36] Manu’s spotlight is Uptime Kuma, a fancy self-hosted monitoring tool.
Links Credits

Special Guest: Manuel Riel.

Support Sustain

bookmark
plus icon
share episode
Guest

Max Jones

Panelist

Richard Littauer

Show Notes

In this first ever cross-over episode of Sustain and Open Source for Climate, host Richard welcomes guest Max Jones, a data scientist and open source software developer who works at Carbon Plan. Max discusses the importance of open source in bringing about effective climate action, the role of Carbon Plan in building accessible data products and tools, and how being a nonprofit is advantageous for open source development. The conversation also touches on funding models for open source projects in nonprofits, including support from individual donors, grants, and collaboration with governmental and private entities like NASA and Microsoft. Additionally, Max shares insights into the development of tools for better visualization of climate data, the impact of open source on climate action, and the challenges of ensuring software and data accessibility and reproducibility. Press download now to hear more!
[00:02:50] Richard outlines Max’s background in open source software development focused on climate action, including his leadership role at Carbon Plan.

[00:03:31] Max discusses the mission of Carbon Plan, emphasizing the importance of transparency and accessibility in climate solutions.

[00:04:23] Max describes his role in leading open source initiatives at Carbon Plan.

[00:03:23] The conversation shifts to the practical aspects of running a non-profit focused on open source projects, including funding mechanisms such as grants from NASA.

[00:06:58] Max explains one of their projects that involve tools for visualizing large-scale climate data to assist cities in planning and decision-making. He mentions how these tools are designed to be accessible to both scientists and the general public.

[00:08:13] There’s a discussion about community engagement with their tools, noting that while many people reach out with questions or feature requests, there have been few contributions in terms of pull requests.

[00:08:53] Max reflects on a collaboration with the Washington Post using their tools to inform public understanding of climate projections.

[00:10:37] Max discusses the broader use of the tools by various agencies and the importance of transparency for reproducibility in research.
[00:11:24] Max emphasizes the importance of reproducibility in open source projects across academia, industry, and the non-profit sector, and he acknowledges the challenges in ensuring that external users can engage with and reproduce their computational workflows.

[00:12:56] The conversation shares insights into building a community around open source projects, particularly through involvement with the Pangeo project, which supports reproducibility and scalability in earth science workflows.

[00:14:08] Max talks about the importance of finding common needs across different fields to promote broader collaboration and integration and mentions the Zarr project.

[00:15:51] We hear about the size of the team at Carbon Plan which includes various roles.

[00:16:28] Richard inquires about the funding landscape for open source projects at Carbon Plan. Max mentions the initial funding received through collaborations with NASA and Microsoft. He emphasizes the importance of ongoing government and agency support for both new tools and the maintenance of existing software.

[00:17:51] Max talks about contributing back to open source communities, highlighting the practice of reporting bugs and engaging with upstream dependencies to improve tools.

[00:18:38] The necessity of open source for transparency in climate solutions is discussed, contrasting with closed source companies that sell proprietary products to governments. Max argues for the importance of open source in ensuring accountability and better outcomes in climate solutions.

[00:20:07] Max discusses the broader aspects of open resources, such as leveraging open standards, data, and hardware. He mentions collaborating with other organizations to tackle scalable computing challenges.

[00:21:18] The conversation shifts to the environmental impact of computational work, with Max acknowledging the need for more efficient workflows and the broader implications of their organization’s focus, which includes understanding and adapting to climate change impacts.

[00:24:15] Richard and Max discuss the challenges of making data sets public in a market-driven environment. Max emphasizes the role of nonprofits in pushing for greater transparency and the potential impact of their work on broader technological practices.

[00:26:09] Finally, Max highlights a new project called OffsetsDB, and tell us where you can follow him and his work online.

Quotes
  • [00:03:44] “We believe that it’s necessary to have transparency and accessibility in our research, data, and tools in order to acco...
bookmark
plus icon
share episode
Guest

Jono Bacon

Panelists

Justin Dorfman | Richard Littauer

Show Notes

Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Today, we have as our special guest, Jono Bacon, a self-employed Community and Collaboration Consultant, author, speaker, and Founder of Jono Bacon Consulting. Jono tells us about his interesting journey with his career, the diversity of his clients, a concern he has with chat channels, and why community is the most important thing in open source. He talks about developers and how to help them see their value and potential to achieve their goals. We learn more about some of the things Jono wrote, including his most recent book, People Powered: How Communities Can Supercharge Your Business, Brands, and Teams, _and how he got the _“star power” behind it. Also, he also shares an awesome story when he worked at XPRIZE, and something that made him realize how unique the open source world really is. Go ahead and download this episode to hear much more!

[00:01:46] Jono tells us how he ended up doing what he does.

[00:03:36] We find out the type of clients Jono has and how he gets them often through referrals.

[00:06:34] Jono talks about how he feels about Discord, Discourse, Gitter, and the open source IRC replacements that are going on right now.

[00:09:42] Richard asks Jono what he thinks the value is of having these side conversations, and how does that help community members have better engagement and build value for them.

[00:13:28] Jono shares his opinion on one of the flaws with individuals in open source and why community is the most important thing.

[00:16:46] Richard wonders how Jono balances the needs of emotionally connecting to everyone in your group and how he makes sure that developers know there is a balance to be met to have the community thrive.

[00:20:30] We learn about some things Jono wrote and he tells us about his most recent book, _People Powered: How Communities Can Supercharge Your Business, Brands, and Teams. _Justin wonders how he got the “star power,” such as Jamie Hyneman and Joseph Gordon-Levitt, in his book.

[00:28:01] We hear an awesome story when Jono worked at XPRIZE and how personalities of people made him realize how unique the open source world really is.

[00:31:42] Richard asks Jono if there are any challenges, anything open source needs help with, and what is down the road for us.

[00:36:44] Find out where you can follow Jono online and learn more about what he does.

Quotes

[00:07:25] “The second priority that I’ve got is by extension, that anybody who joins the community should get amazing value out of it.”

[00:07:32] “As far as I concerned, if you join a community and you don’t get value out of it, that community hasn’t earned you.”

[00:07:56] “One of the concerns I have with chat channels and chat services in general and I’d include Slack, Mattermost, Discord, Git, all of these, is that by definition, it’s a linear stream of consciousness. So Slack claims that they’ve got history and you can kind of unlock history for example if you pay for it. It just doesn’t work.”

[00:08:41] “That’s why I think even Slack, don’s say this is for community building, it’s for building teams.”

[00:10:00] “So, to me what brings people into communities is they’re there to solve a problem. They’re there to improve their future state, such as they’re using pieces of open source software, and they want to make better use of it and solve their problems or build their applications.”

[00:10:16] “I think what people stay for in the community is an intrinsic sense of belonging and a sense that this is just a good place for me to be.”

[00:13:26] “My take on this is I think one of the flaws of a lot of open source communities, not so much communities but more individuals, is that they always talk about the most important thing is code, is getting code that can be created and shared with a group of people.”

[00:13:57] “But to me, I’m engineering for impact here, whether you’re building a little project to just make certain types of unit testing easier, or whether you’re building a replacement for a major piece of proprietary software.”

[00:14:48] “ The reason why I’m so passionate about community is because if you take a hundred people inside of those hundred people, there are so many ideas and insights and experiences and skills, and so much time available. Then when we can get all of that out into the open, it makes us the best we can be as people.”

[00:17:28] “But, I think most people, a much more kind of, I guess you could say practical than that, and they will do something if they can see the value, and it’s worth it, and they can achieve their broader outcomes.”

[00:18:36] “You need to be inclusive, not just in terms of a rich demographic of peo...

bookmark
plus icon
share episode

Show more best episodes

Toggle view more icon

FAQ

How many episodes does Sustain have?

Sustain currently has 261 episodes available.

What topics does Sustain cover?

The podcast is about Open Source, Software Development, Podcasts and Technology.

What is the most popular episode on Sustain?

The episode title 'Episode 46: Commercial Open Source with Joseph Jacks' is the most popular.

What is the average episode length on Sustain?

The average episode length on Sustain is 37 minutes.

How often are episodes of Sustain released?

Episodes of Sustain are typically released every 7 days.

When was the first episode of Sustain?

The first episode of Sustain was released on Aug 6, 2019.

Show more FAQ

Toggle view more icon

Comments