Podcast appearances and mentions of nadia eghbal

Play Episode Listen Later Sep 19, 2024 40:12

Thank you to the folks at Sustain (https://sustainoss.org/) for providing the hosting account for CHAOSSCast! CHAOSScast- Episode 93 Guests: Elizabeth Barron Luis Cañas-Diaz Dawn Foster Panelists: Alice Sowerby Richard Littauer In this episode of CHAOSScast, it's a crossover with Sustain, host Richard Littauer is joined by three guests, Dawn Foster, Elizabeth Barron, and Luis Cañas Diaz, to discuss the CHAOSS Project's recent development of Practitioner Guides. The show delves into the purpose of these guides, which are designed to help open source projects interpret and utilize metrics to improve community health and sustainability. The guests explain the significance of metrics in open source projects, the challenges of defining and making them accessible, and how the guides can benefit different types of projects, from large corporations to individual developers. Topics covered include the background and format of the guides, specifics on the metrics discussed, and the practical applications and improvements these guides aim to facilitate. Go ahead and download this episode now! [00:03:03] Dawn fills us in on the connections between the guests and their collective work on the CHAOSS Practitioner Guides. [00:03:43] The conversation shifts to the specifics of the CHAOSS Project, highlighting the international community involvement and various working groups focusing on different aspects of open source projects like corporate OSPOs, university OSPOs, and diversity and equity initiatives. [00:05:31] Luis describes the origin and work of Bitergia and its collaboration with CHAOSS Project, particularly in developing tools like Grimoire Lab. [00:07:17] Richard turns the discussion to the CHAOSS Project's Practitioner Guides, where Dawn discusses the purpose of the introduction guide in the series, designed to help users understand and apply metrics effectively across various open source contexts. [00:10:58] There's a discussion on the format of the guides, emphasizing their accessibility, ethical considerations in data handling, and how they're designed to be adaptable to different needs. Luis highlights the need for CHAOSS and Bitergia projects to provide actionable insights rather than just more metrics. [00:13:28] Elizabeth and Dawn explain the broader goal of the guides to not only provide metrics but also helps users interpret and apply these to drive tangible improvements in open source projects. [00:14:54] We learn about the target audience for the guides and how they cater to both large organizational structures (OSPOs) and individual project maintainers. [00:16:15] Dawn explains what the Contributor Sustainability Guide focuses on, emphasizing strategies for sustainable contribution and community involvement in open source projects. [00:17:53] The discussion centers on renaming the “bus factor” metric to “contributor absence factor” to avoid the negative connotations of the original term, Luis emphasizes the relevance of metrics, particularly in small projects, and Dawn explains that the guides focus on a few key metrics per guide, chosen for their ease of understanding and minimal requirement for data collection. [00:21:58] Richard inquires about the effectiveness of metrics in identifying if a project is on the wrong path, prompting a discussion on the goals of a project and how metrics align with those metrics. Elizabeth and Dawn stress the importance of aligning metrics with project goals and involving project contributors in discussions about what metrics are most relevant. [00:24:35] The discussion continues with considerations on how metrics should supplement, not replace, expert judgement and involvement in project management. Elizabeth and Richard discuss the potential for projects to start with community growth in mind and the challenges in measuring and guiding such growth. [00:28:18] The conversation switches to the remaining guides not yet covered, with Richard asking about the guides on Responsiveness and Organizational Participation. Dawn explains the Responsiveness guide, with its focus on key metrics like time to first response, time to close, and change request closure ratio. Elizabeth and Luis share why this is one of their favorite guides. [00:33:23] We hear about the broader applicability of the guides. Richard questions if the guides are only for corporate-driven projects or if they can serve more relaxed open source environments. Dawn and Luis emphasize that the guides are valuable for a variety of stakeholders, including foundations and volunteers. [00:35:00] Find out where you can look at the Practitioner Guides online. Quotes: [00:07:44] “At the CHAOSS Project we have a whole bunch of metrics, and we have tools or software that help you gather those metrics.” [00:08:06] “There is no one-size-fits-all approach to interpreting metrics.” [00:15:10] “A lot of these guides were designed with OSPOs in mind. They're all useful to anyone who's managing a project.” [00:19:55] “For metrics, the bigger the project, the more useful they are.” Spotlight: [00:35:54] Richard's spotlight is Johnny Wilson, an eBird reviewer. [00:36:34]** Elizabeth's **spotlight is a project called Clocker. [00:37:30] Dawn's spotlight is Nadia Eghbal's book, _Working in Public: The Making and Maintenance of Open Source Software, _and her paper, “Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure.” [00:38:29] Luis's spotlight is Moodle, the OSS learning platform. Links: CHAOSS (https://chaoss.community/) CHAOSS slack (https://chaoss-workspace.slack.com/join/shared_invite/zt-28p56bayt-67TRjdA4yJWQmUd4hCzULg#/shared-invite/email) CHAOSS Practitioner Guides (https://chaoss.community/about-chaoss-practitioner-guides/) SustainOSS (https://sustainoss.org/) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) Open Collective-SustainOSS (Contribute) (https://opencollective.com/sustainoss) Richard Littauer Socials (https://www.burntfen.com/2023-05-30/socials) Alice Sowerby Website (https://www.rosmarin.co.uk/) Elizabeth Barron Website (https://www.elizabeth-barron.com/) Elizabeth Barron LinkedIn (https://www.linkedin.com/in/elizabethn/) Luis Cañas-Diaz Website (https://sanacl.wordpress.com/) Luis Cañas-Diaz LinkedIn (https://www.linkedin.com/in/canasdiaz/) Dawn Foster Website (https://fastwonderblog.com/) Dawn Foster LinkedIn (https://www.linkedin.com/in/dawnfoster/) Johnny Wilson-Ventures Birding Tours (https://www.birdventures.com/Johnny-Wilson.html) Clocker (https://abhishekbanthia.com/clocker/) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/dp/0578675862/) “Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure” by Nadia Eghbal (https://www.fordfoundation.org/work/learning/research-reports/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/) Nadia Asparouhova (Eghbal) Website (https://nadia.xyz/oss/) Moodle (https://moodle.org/) Sustain Podcast featuring Nadia Eghbal (https://podcast.sustainoss.org/guests/nadia) Credits: Produced by [Richard Littauer] (https://www.burntfen.com/) (https://www.burntfen.com/) Edited by Paul M. Bahr at [Peachtree Sound] (https://www.peachtreesound.com/) (https://www.peachtreesound.com/) Show notes by DeAnn Bahr [Peachtree Sound] (https://www.peachtreesound.com/) (https://www.peachtreesound.com/) Special Guests: Luis Cañas-Díaz and Richard Littauer.

quotes maintenance roads edited diaz guides practitioners spotlight sustain oss open source software responsiveness moodle credits produced ebird johnny wilson dawn foster nadia eghbal luis ca

Episode 243: Elizabeth Barron, Luis Cañas-Diaz & Dawn Foster on CHAOSS Practitioner Guides

Play Episode Listen Later Aug 16, 2024 39:03

Guests Elizabeth Barron | Luis Cañas-Diaz | Dawn Foster Panelist Richard Littauer Show Notes In this episode of Sustain, host Richard Littauer is joined by three guests, Dawn Foster, Elizabeth Barron, and Luis Cañas Diaz, to discuss the CHAOSS Project's recent development of Practitioner Guides. The show delves into the purpose of these guides, which are designed to help open source projects interpret and utilize metrics to improve community health and sustainability. The guests explain the significance of metrics in open source projects, the challenges of defining and making them accessible, and how the guides can benefit different types of projects, from large corporations to individual developers. Topics covered include the background and format of the guides, specifics on the metrics discussed, and the practical applications and improvements these guides aim to facilitate. Go ahead and download this episode now! [00:01:53] Dawn fills us in on the connections between the guests and their collective work on the CHAOSS Practitioner Guides. [00:02:33] The conversation shifts to the specifics of the CHAOSS Project, highlighting the international community involvement and various working groups focusing on different aspects of open source projects like corporate OSPOs, university OSPOs, and diversity and equity initiatives. [00:04:21] Luis describes the origin and work of Bitergia and its collaboration with CHAOSS Project, particularly in developing tools like Grimoire Lab. [00:06:07] Richard turns the discussion to the CHAOSS Project's Practitioner Guides, where Dawn discusses the purpose of the introduction guide in the series, designed to help users understand and apply metrics effectively across various open source contexts. [00:09:48] There's a discussion on the format of the guides, emphasizing their accessibility, ethical considerations in data handling, and how they're designed to be adaptable to different needs. Luis highlights the need for CHAOSS and Bitergia projects to provide actionable insights rather than just more metrics. [00:12:18] Elizabeth and Dawn explain the broader goal of the guides to not only provide metrics but also helps users interpret and apply these to drive tangible improvements in open source projects. [00:13:44] We learn about the target audience for the guides and how they cater to both large organizational structures (OSPOs) and individual project maintainers. [00:15:04] Dawn explains what the Contributor Sustainability Guide focuses on, emphasizing strategies for sustainable contribution and community involvement in open source projects. [00:16:42] The discussion centers on renaming the “bus factor” metric to “contributor absence factor” to avoid the negative connotations of the original term, Luis emphasizes the relevance of metrics, particularly in small projects, and Dawn explains that the guides focus on a few key metrics per guide, chosen for their ease of understanding and minimal requirement for data collection. [00:20:47] Richard inquires about the effectiveness of metrics in identifying if a project is on the wrong path, prompting a discussion on the goals of a project and how metrics align with those metrics. Elizabeth and Dawn stress the importance of aligning metrics with project goals and involving project contributors in discussions about what metrics are most relevant. [00:23:26] The discussion continues with considerations on how metrics should supplement, not replace, expert judgement and involvement in project management. Elizabeth and Richard discuss the potential for projects to start with community growth in mind and the challenges in measuring and guiding such growth. [00:27:07] The conversation switches to the remaining guides not yet covered, with Richard asking about the guides on Responsiveness and Organizational Participation. Dawn explains the Responsiveness guide, with its focus on key metrics like time to first response, time to close, and change request closure ratio. Elizabeth and Luis share why this is one of their favorite guides. [00:32:12] We hear about the broader applicability of the guides. Richard questions if the guides are only for corporate-driven projects or if they can serve more relaxed open source environments. Dawn and Luis emphasize that the guides are valuable for a variety of stakeholders, including foundations and volunteers. [00:33:49] Find out where you can look at the Practitioner Guides online. Quotes [00:06:34] “At the CHAOSS Project we have a whole bunch of metrics, and we have tools or software that help you gather those metrics.” [00:06:56] “There is no one-size-fits-all approach to interpreting metrics.” [00:14:00] “A lot of these guides were designed with OSPOs in mind. They're all useful to anyone who's managing a project.” [00:18:45] “For metrics, the bigger the project, the more useful they are.” Spotlight [00:34:43] Richard's spotlight is Johnny Wilson, an eBird reviewer. [00:35:23] Elizabeth's spotlight is a project called Clocker. [00:36:19] Dawn's spotlight is Nadia Eghbal's book, _Working in Public: The Making and Maintenance of Open Source Software, _and her paper, “Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure.” [00:37:18] Luis's spotlight is Moodle, the OSS learning platform. Links SustainOSS (https://sustainoss.org/) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) Open Collective-SustainOSS (Contribute) (https://opencollective.com/sustainoss) Richard Littauer Socials (https://www.burntfen.com/2023-05-30/socials) Elizabeth Barron Website (https://www.elizabeth-barron.com/) Elizabeth Barron LinkedIn (https://www.linkedin.com/in/elizabethn/) Luis Cañas-Diaz Website (https://sanacl.wordpress.com/) Luis Cañas-Diaz LinkedIn (https://www.linkedin.com/in/canasdiaz/) Dawn Foster Website (https://fastwonderblog.com/) Dawn Foster LinkedIn (https://www.linkedin.com/in/dawnfoster/) CHAOSS (https://chaoss.community/) CHAOSS slack (https://chaoss-workspace.slack.com/join/shared_invite/zt-28p56bayt-67TRjdA4yJWQmUd4hCzULg#/shared-invite/email) CHAOSS Practitioner Guides (https://chaoss.community/about-chaoss-practitioner-guides/) Johnny Wilson-Ventures Birding Tours (https://www.birdventures.com/Johnny-Wilson.html) Clocker (https://abhishekbanthia.com/clocker/) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/dp/0578675862/) “Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure” by Nadia Eghbal (https://www.fordfoundation.org/work/learning/research-reports/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/) Nadia Asparouhova (Eghbal) Website (https://nadia.xyz/oss/) Moodle (https://moodle.org/) Sustain Podcast featuring Nadia Eghbal (https://podcast.sustainoss.org/guests/nadia) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guests: Dawn Foster, Elizabeth Barron, and Luis Cañas Diaz.

quotes maintenance roads edited diaz guides practitioners spotlight sustain barron oss open source software responsiveness moodle ebird johnny wilson dawn foster nadia eghbal luis ca

Episode 241: Tracy Hinds & Ashley Williams on Open Source Funding and Inequities

Play Episode Listen Later Jul 12, 2024 40:53

Guests Tracy Hinds | Ashley Williams Panelist Richard Littauer Show Notes On today's episode of Sustain, host Richard Littauer is joined by guests, Tracy Hinds and Ashley Williams, to discuss the structural inequities and funding issues in open source. The episode delves deep into the misaligned incentives in the open source community, how regulatory and policy awareness is growing, and the potential for government regulations to create opportunities for open source maintainers. The conversation also covers the roles of various open source foundations, the impact of large corporations, and the need for more effective advocacy and compensation avenues for contributors. Tracy and Ashley announce their involvement in a working group focused on the European CRA legislation, aiming to bridge gaps between maintainers and policymakers. Press download now! [00:02:22] Ashley responds to Richard's comment about everything being “totally screwed” in open source, but also points out misaligned incentives. She discusses the economic challenges of open source, such as the failure of sustaining efforts and its broader economic impact. [00:04:54] Richard mentions his other podcast “Open Source for Climate” which focuses on leveraging open source technology to combat the climate crisis. [00:06:10] There's a discussion about potential regulatory and policy changes affecting open source, highlighting the need for a more equitable system. Ashley delves into economic theories relating to open source, particularly the concept of externalities and potential regulatory solutions, and upcoming regulations like the software bill of materials. [00:10:05] Tracy stresses the importance of involving open source maintainers in policy discussions to avoid misrepresentation by larger organizations alone. [00:11:47] Richard and Ashley discuss the representations of open source interests in policy making, particularly the dominance of large companies and the potential exclusion of individual maintainers. [00:16:04] Ashley critiques many language-based foundations for their minimal contribution to ecosystem, using Node Foundation as an example of one that has been beneficial due to its library ecosystem, notably NPM. [00:17:35] Tracy acknowledges the efforts of the Python Software Foundation (PSF) and Open Collective in fostering ecosystems that support paid contributors, emphasizing the importance of these roles for sustainability. [00:19:50] Richard notes that while centralized support like AWS services vouchers are helpful, these foundations do not effectively facilitate crucial conversations between maintainers and governments regarding open source regulation and standardization. [00:21:52] Ashley reflects on her experience as the Individual Membership Director at the Node Foundation, discussing the challenges of representing a diverse community within open source projects and foundations. [00:24:45] Tracy mentions her role as the first community seat director on the board, highlighting the evolution and ongoing adjustments in community representation within foundation governance. Also, she discusses the importance of involving individual maintainers in regulatory discussions. [00:27:47] Tracy talks about the economic opportunities in open source, facilitated by platforms like GitHub Sponsors and Patreon, which help reduce barriers for maintainers seeking financial support for their projects. [00:29:20] Ashley puts a small spin on Tracy's optimistic view, noting significant opposition to the empowerment of small open source businesses, primarily due to corporate-dominated structures and antitrust-friendly environments in tech. She argues that open source has been consolidating. [00:33:29] Ashley fills us in on where you can follow her and their future discussions. She mentions a working group at the Eclipse Foundation focusing on CRA legislation, announcing an initiative to gather maintainer feedback on this legislation through a reading group. [00:35:42] Tracy mentions where you can find her online. Quotes [00:03:30] “We have open source – people who maintain open source don't really make a lot of money from it. Attempts to sustain open source have largely failed.” [00:06:24] “Every OSS hacker is also incentivized to be a lawyer.” Spotlight [00:36:32] Richard's spotlight is Jingna Zhang and her new social network, Cara. [00:37:25] Tracy's spotlight is the book, Working in Public: The Making and Maintenance of Open Source Software. [00:38:09] Ashley's spotlight is exercising for mental health. Links SustainOSS (https://sustainoss.org/) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (email) (mailto:podcast@sustainoss.org) richard@theuserismymom.com (email) (mailto:richard@theuserismymom.com) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) Open Collective-SustainOSS (Contribute) (https://opencollective.com/sustainoss) Richard Littauer Socials (https://www.burntfen.com/2023-05-30/socials) Tracy Hinds X/Twitter (https://x.com/hackygolucky?lang=en) Tracy Hinds Mastodon (https://mastodon.social/@hackygolucky) Sustain Podcast-Episode 135 featuring Tracy Hinds (https://podcast.sustainoss.org/guests/hinds) Ashley Williams Twitter (https://x.com/ag_dubs) Ashley Williams LinkedIn (https://www.linkedin.com/in/ashleygwilliams/) Sustain Podcast-Episode 145 featuring Ashley Williams (https://podcast.sustainoss.org/guests/williams) Open Source Initiative (https://opensource.org/) OSS for Climate Podcast (https://ossforclimate.sustainoss.org/) Eclipse Foundation (https://www.eclipse.org/org/foundation/) Jingna Zhang (https://www.zhangjingna.com/) Cara (https://cara.app/login) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862) Sustain Podcast-Episode 51 featuring Nadia Eghbal (https://podcast.sustainoss.org/guests/nadia) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guests: Ashley Williams and Tracy Hinds.

S8 E10 | Organizational Design and Governance Frameworks w/Amy Jung (Safe)

Rehash: A Web3 Podcast

Play Episode Listen Later Jun 20, 2024 54:57

On this episode of Rehash, we're speaking with Amy Jung, Governance Lead at Safe and an OG in the Ethereum and specifically DAO space, about all things organization design, governance, and her hottest takes about DAOs.Amy joined the Safe team back in March of this year and also has her own DAO operations and strategy consultancy called Shared Realities, where she helps organizations and teams with their progressive decentralization strategy and execution, organizational design, and community development. Previously, she worked at MakerDAO for two years as their Head of Community Development and ConsenSys as their Design Operations Lead.In this episode, Amy reveals many of her strategies and frameworks she uses to help organizations decentralize, starting with questions any organization should ask themselves to decide first and foremost whether it even makes sense for them to decentralize.Amy presents information in really clearly thought out frameworks that anyone can take back to their organization and implement, and her dedication to the space and deep expertise in DAO organization design is unmatched. COLLECT THIS EPISODEhttps://www.rehashweb3.xyz/ SUBSCRIBE TO REHASH PODCAST CLUB (RPC)https://hypersub.withfabric.xyz/collection/rehash-podcast-club-s9c8bb45vg1s?referrer=0x4b65caf44055f910fd94eae4f14307ffe3233b12 SPONSORS:Forage FOLLOW USRehash: https://twitter.com/rehashweb3Diana: https://twitter.com/ddwchenAmy: https://twitter.com/itsamyjungSafe: https://twitter.com/safe LINKSS8 E1 | Multiparty Ops Onchain w/Jonah Erlich (Den): https://www.youtube.com/watch?v=ErdxzFt1rEo“Working in Public” by Nadia Eghbal: https://www.amazon.co.uk/Working-Public-Making-Maintenance-Software/dp/0578675862Rehash Podcast Club on Hypersub: https://hypersub.withfabric.xyz/collection/rehash-podcast-club-s9c8bb45vg1s?referrer=0x4b65caf44055f910fd94eae4f14307ffe3233b12“Owning is the New Sharing” by Nathan Schneider: https://nathanschneider.info/2014/12/owning-is-the-new-sharing/ TIMESTAMPS0:00 Intro2:53 Amy's background in DAOs5:26 Frameworks for decentralized organizational design13:20 How do DAOs scale?17:37 How to balance growth with quality20:08 How to make tradeoffs between decentralized and centralized components of DAOs27:48 Decentralization process for Safe38:28 Compensation in DAOs44:22 Best and worst examples of governance in DAOs48:05 Amy's hot take on the one thing all DAOs are doing wrong49:32 Can You Not52:11 Follow Amy DISCLAIMER: The information in this video is the opinion of the speaker(s) only and is for informational purposes only. You should not construe it as investment advice, tax advice, or legal advice, and it does not represent any entity's opinion but those of the speaker(s). For investment or legal advice, please seek a duly licensed professional.

Episode 81: Managing Federal CHAOSS at CMS.gov

public open code communities open source projects nadia eghbal

Play Episode Listen Later Mar 12, 2024 40:25

Thank you to the folks at Sustain (https://sustainoss.org/) for providing the hosting account for CHAOSSCast! CHAOSScast – Episode 80 On today's episode of CHAOSScast, we focus on the experiences and initiatives of the Open Source Program Office at the U.S. Centers for Medicare and Medicaid Services (CMS). Host Dawn Foster is joined by Sean Goggins along with guests, Remy DeCausemaker, Natalia Luzuriaga, Isaac Milarsky, and Aayat Ali, all from various backgrounds within the CMS, who share insights into their efforts in maintaining and promoting an open source culture within federal services. Key discussion points include the launch of the CMS's first open source program office, the development of a maturity model framework to evaluate open source projects, the creation of tools such as Repo Scaffolder and Duplifier to support open source practices, and efforts towards open source software security. This episode emphasizes the distinct aspects of opens source work in government settings compared to the private sector and highlights upcoming presentations at conferences. Download this episode now to hear more! [00:02:21] Dawn asks about the team's work at the U.S. Centers for Medicare and Medicaid Services. We start with Remy, who explains the launch of the first open source program office at a federal agency in the U.S. and details CMS's mission to improve healthcare experience for over 150 million people and the role of the digital service within CMS. [00:05:36] Natalia discusses the maturity model framework developed to assess the open source maturity level of projects. She describes a “Repo Scaffolder” tool created in collaboration with the U.S. digital response to help projects align with the majority model, and she speaks about additional features for public repositories to aid in development. [00:10:51] Isaac takes over, explaining how they use Auger metrics and “Nadia labeling” to categorize projects and encourage the adoption of their maturity model. He details a metrics website that provides visual representations of project health and activity and introduces “Duplifier,” a deduplication tool for healthcare data, which uses an open source library called Splink. [00:15:14] Sean inquires how they actualize their user needs in metrics visualization and about the process that informs the creation of these visual metrics. Isaac addresses front-end design aspects of metric visualization and the importance of making the metrics understandable at a glance. Natalia emphasizing designing for both technical and non-technical stakeholders, ensuring metrics are clear and understandable. [00:17:44] Aayat discusses her role in strategy development and the creation of a CMS OSPO guide. She emphasizes advocacy withing CMS for open source and plans to conduct workshops and usability testing to determine which metrics are most valuable to stakeholders. [00:19:23] Remy talks about consulting with the chief information security officer and the chief information officer for internal metric priorities and engaging with an external OSPO metrics working group convened by CHAOSS for broader insights. [00:20:47] Dawn asks Remy for more details on the differences with government engagement in open source to the corporate environments. Remy describes the early journey of OSPOs at the federal level and contrasts it with his private sector experience. [00:25:18] Sean asks about what success would look like a year from now for the OSPO group's work. Remy acknowledges the limited four-year term for digital service members, emphasizing the urgency to execute and make an impact within the next year. He highlights the transformative impact of Isaac and Natalia's entrance into the program and the successful shipping of the metrics website, a deduplication tool, and other repositories. [00:27:50] Isaac envisions success as propagating maturity models and open source standards throughout the government, demonstrating value to stakeholders, and growing the OSPO. Natalia is excited to share their foundational OSPO work and contribute to open data initiatives and mentions speaking this year at the Linux Foundation Open Source Summit and PyCon about their work. Aayat defines success as achieving goals in source code stewardship, understanding the maturity and content of repositories, and supporting the team in communicating the value of open source. [00:29:53] Remy brings up Nadia Eghbal giving her credit for influential work and mentioning a team book club inspired by her writings. Value Adds (Picks) of the week: [00:32:39] Dawn's pick is Beat Saber for indoor workouts. [00:33:05] Sean's pick is the HBO max show, True Detective, Season 4. [00:33:22] Remy's pick is the BRAVO Hackathon Series he recently attended. [00:38:14] Natalia's pick is visiting her local library and getting a library card. [00:38:39] Aayat's pick is a good book she read called, “Demon Copperhead.” [00:39:36] Isaac's pick is enjoying the nice weather and getting outside. **Panelists: Dawn Foster Sean Goggins Guests: Remy DeCausemaker Natalia Luzuriaga Isaac Milarsky Aayat Ali Links: CHAOSS (https://chaoss.community/) CHAOSS Project X/Twitter (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) podcast@chaoss.community (mailto:podcast@chaoss.community) Georg Link Website (https://georg.link/) Dawn Foster X/Twitter (https://twitter.com/geekygirldawn?lang=en) Sean Goggins X/Twitter (https://twitter.com/sociallycompute) Remy DeCausemaker X/Twitter (https://twitter.com/Remy_D) Remy DeCausemaker LinkedIn (https://www.linkedin.com/in/decause/) Natalia Luzuriaga LinkedIn (https://www.linkedin.com/in/natalialuzuriaga/) Isaac Milarsky LinkedIn (https://www.linkedin.com/in/isaac-milarsky-24471b1b6) Aayat Ali LinkedIn (https://www.linkedin.com/in/aayat-ali-a5850134/) Aayat Ali Website (https://aayatali.com/) CMS.gov (https://moj-analytical-services.github.io/splink/index.html) Digital Service at CMS (DSACMS)-GitHub (https://github.com/dsacms) Centers for Medicare & Medicaid Services-GitHub (https://github.com/CMSgov) United States Digital Corps (https://digitalcorps.gsa.gov/) Splink (https://moj-analytical-services.github.io/splink/index.html) Repo Scaffolder-GitHub (https://moj-analytical-services.github.io/splink/index.html) Metrics Dashboard for CMS Open Source Projects (https://github.com/dsacms/metrics) Repo Metrics Website (https://dsacms.github.io/metrics/) github-ospo (https://github.com/github/github-ospo) The Linux Foundation Open Source Summit-April 16-18, 2024, Seattle, WA (https://events.linuxfoundation.org/open-source-summit-north-america/) PyCon US-May 15-23, 2024-Pittsburgh, PA (https://us.pycon.org/2024/) Nadia Asparouhova (aka Nadia Eghbal) Website (https://nadia.xyz/) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/dp/0578675862/) Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure by Nadia Eghbal (https://www.fordfoundation.org/wp-content/uploads/2016/07/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf) CHAOSScast Podcast-Episode 77: Open Source Metrics at Microsoft (https://podcast.chaoss.community/77) Beat Saber (https://beatsaber.com/) True Detective-Season 4 (HBO max) (https://www.hbo.com/true-detective/season-4) BRAVO Hackathon Series (https://bravo.il2.afwerx.dso.mil/about) Demon Copperhead by Barbara Kingsolver (https://www.amazon.com/Demon-Copperhead-Novel-Barbara-Kingsolver/dp/0063251922) Special Guests: Aayat Ali, Isaac Milarsky, Natalia Luzuriaga, and Remy DeCausemaker.

[EN] Open Source Projects & Communities - Chris Holdgraf from 2i2c

Code for Thought

Play Episode Listen Later Feb 20, 2024 43:41

In this episode I talk to Chris Holdgraf, executive director of https://2i2c.org about what it takes to manage and run open source organisations. Open source projects come with unique challenges (and opportunities) and I think Chris brings important insights from his experience at 2i2c.Some links:https://chrisholdgraf.com Chris' home pagehttps://press.stripe.com/working-in-public 'Working in Public' by Nadia Eghbal, mentioned in this episodeSupport the Show.Thank you for listening and your ongoing support. It means the world to us! Support the show on Patreon https://www.patreon.com/codeforthought Get in touch: Email mailto:code4thought@proton.me UK RSE Slack (ukrse.slack.com): @code4thought or @piddie US RSE Slack (usrse.slack.com): @Peter Schmidt Mastadon: https://fosstodon.org/@code4thought or @code4thought@fosstodon.org LinkedIn: https://www.linkedin.com/in/pweschmidt/ (personal Profile)LinkedIn: https://www.linkedin.com/company/codeforthought/ (Code for Thought Profile) This podcast is licensed under the Creative Commons Licence: https://creativecommons.org/licenses/by-sa/4.0/

OSS Book Review: Nadia Eghbal's Working in Public - The Making and Maintenance of Open Source Software

The Virtual Coffee Podcast

Play Episode Listen Later Sep 26, 2023 44:48 Transcription Available

Join hosts Bekah and Dan in this episode with Nadia Eghbal's "Working in Public" enthusiasts Jessica Wilkins and Brian Meeker. We discuss the nuances of open source collaboration highlighted in the book, the challenges and rewards of being both a contributor and a maintainer, and the profound impact of individual contributions in the open source community. Dive into the transformative journey of participating in open source and redefining its true meaning with OpenSauced.LinksWorking in Public: The Making and Maintenance of Open Source Software by Nadia EghbalVirtual Coffee Book Club DiscussionThe left-pad storyEpisode Sponsor!We're grateful to be sponorsored by LevelUP Financial Planning, who understands the importance of finding balance between having an awesome life today, and being confident and excited about your future possibilities. If you want to take your financial confidence to the next level, check out levelupfinancialplanning.com.About JessicaJessica Wilkins is a self taught developer and technical writer from Los Angeles, California.In her previous career, she was a professional oboist, educator and owner of JDW Sheet Music.Jessica's interest in programming came during the pandemic when she wanted to build the Black Excellence Music Project which celebrates black artists from the jazz and classical fields.She now works for freeCodeCamp on the curriculum team.@jdwilkin4 on GitHub@codergirl1991 on Twitter@jessica-wilkins-developer on LinkedInAbout BrianBrian Meeker is a full stack engineer who occasionally leaves his basement in Indiana. Currently, he works as a Senior Engineer at Online Rewards. He works mostly in Elixir these days, but has a past littered with a wide variety of technologies and platforms. Outside of work, Brian is a devoted father, avid nerd, and lover of metal.brianmeeker.me@CuriousCurmudgeon on GitHub@CuriousCurmudge on Twitter@brianmeeker on LinkedInSponsor Virtual Coffee! Your support is incredibly valuable to us. Direct financial support will help us to continue serving the Virtual Coffee community. Please visit our sponsorship page on GitHub for more information - you can even sponsor an episode of the podcast! Virtual Coffee: Virtual Coffee: virtualcoffee.io Podcast Contact: podcast@virtualcoffee.io Bekah: dev.to/bekahhw, Twitter: https://twitter.com/bekahhw, Instagram: bekahhw Dan: dtott.com, Twitter: @danieltott

california los angeles public dive indiana maintenance github elixir bekah open source software senior engineer freecodecamp podcast contact nadia eghbal

Debugging the Internet with AI agents – with Itamar Friedman of Codium AI and AutoGPT

Latent Space: The AI Engineer Podcast â€” CodeGen, Agents, Computer Vision, Data Science, AI UX and all things Software 3.0

Play Episode Listen Later May 25, 2023 62:36

We are hosting the AI World's Fair in San Francisco on June 8th! You can RSVP here. Come meet fellow builders, see amazing AI tech showcases at different booths around the venue, all mixed with elements of traditional fairs: live music, drinks, games, and food! We are also at Amplitude's AI x Product Hackathon and are hosting our first joint Latent Space + Practical AI Podcast Listener Meetup next month!We are honored by the rave reviews for our last episode with MosaicML! They are also welcome on Apple Podcasts and Twitter/HN/LinkedIn/Mastodon etc!We recently spent a wonderful week with Itamar Friedman, visiting all the way from Tel Aviv in Israel: * We first recorded a podcast (releasing with this newsletter) covering Codium AI, the hot new VSCode/Jetbrains IDE extension focused on test generation for Python and JS/TS, with plans for a Code Integrity Agent. * Then we attended Agent Weekend, where the founders of multiple AI/agent projects got together with a presentation from Toran Bruce Richards on Auto-GPT's roadmap and then from Itamar on Codium's roadmap* Then some of us stayed to take part in the NextGen Hackathon and won first place with the new AI Maintainer project.So… that makes it really hard to recap everything for you. But we'll try!Podcast: Codium: Code Integrity with Zero BugsWhen it launched in 2021, there was a lot of skepticism around Github Copilot. Fast forward to 2023, and 40% of all code is checked in unmodified from Copilot. Codium burst on the scene this year, emerging from stealth with an $11m seed, their own foundation model (TestGPT-1) and a vision to revolutionize coding by 2025.You might have heard of "DRY” programming (Don't Repeat Yourself), which aims to replace repetition with abstraction. Itamar came on the pod to discuss their “extreme DRY” vision: if you already spent time writing a spec, why repeat yourself by writing the code for it? If the spec is thorough enough, automated agents could write the whole thing for you.Live Demo Video SectionThis is referenced in the podcast about 6 minutes in.Timestamps, show notes, and transcript are below the fold. We would really appreciate if you shared our pod with friends on Twitter, LinkedIn, Mastodon, Bluesky, or your social media poison of choice!Auto-GPT: A Roadmap To The Future of WorkMaking his first public appearance, Toran (perhaps better known as @SigGravitas on GitHub) presented at Agents Weekend:Lightly edited notes for those who want a summary of the talk:* What is AutoGPT?AutoGPT is an Al agent that utilizes a Large Language Model to drive its actions and decisions. It can be best described as a user sitting at a computer, planning and interacting with the system based on its goals. Unlike traditional LLM applications, AutoGPT does not require repeated prompting by a human. Instead, it generates its own 'thoughts', criticizes its own strategy and decides what next actions to take.* AutoGPT was released on GitHub in March 2023, and went viral on April 1 with a video showing automatic code generation. 2 months later it has 132k+ stars, is the 29th highest ranked open-source project of all-time, a thriving community of 37.5k+ Discord members, 1M+ downloads.* What's next for AutoGPT? The initial release required users to know how to build and run a codebase. They recently announced plans for a web/desktop UI and mobile app to enable nontechnical/everyday users to use AutoGPT. They are also working on an extensible plugin ecosystem called the Abilities Hub also targeted at nontechnical users.* Improving Efficacy. AutoGPT has many well documented cases where it trips up. Getting stuck in loops, using instead of actual content incommands, and making obvious mistakes like execute_code("writea cookbook"'. The plan is a new design called Challenge Driven Development - Challenges are goal-orientated tasks or problems thatAuto-GPT has difficulty solving or has not yet been able to accomplish. These may include improving specific functionalities, enhancing the model's understanding of specific domains, or even developing new features that the current version of Auto-GPT lacks. (AI Maintainer was born out of one such challenge). Itamar compared this with Software 1.0 (Test Driven Development), and Software 2.0 (Dataset Driven Development).* Self-Improvement. Auto-GPT will analyze its own codebase and contribute to its own improvement. AI Safety (aka not-kill-everyone-ists) people like Connor Leahy might freak out at this, but for what it's worth we were pleasantly surprised to learn that Itamar and many other folks on the Auto-GPT team are equally concerned and mindful about x-risk as well.The overwhelming theme of Auto-GPT's roadmap was accessibility - making AI Agents usable by all instead of the few.Podcast Timestamps* [00:00:00] Introductions* [00:01:30] Itamar's background and previous startups* [00:03:30] Vision for Codium AI: reaching “zero bugs”* [00:06:00] Demo of Codium AI and how it works* [00:15:30] Building on VS Code vs JetBrains* [00:22:30] Future of software development and the role of developers* [00:27:00] The vision of integrating natural language, testing, and code* [00:30:00] Benchmarking AI models and choosing the right models for different tasks* [00:39:00] Codium AI spec generation and editing* [00:43:30] Reconciling differences in languages between specs, tests, and code* [00:52:30] The Israeli tech scene and startup culture* [01:03:00] Lightning RoundShow Notes* Codium AI* Visualead* AutoGPT* StarCoder* TDD (Test-Driven Development)* AST (Abstract Syntax Tree)* LangChain* ICON* AI21TranscriptAlessio: [00:00:00] Hey everyone. Welcome to the Latent Space podcast. This is Alessio, Partner and CTO-in-Residence at Decibel Partners. I'm joined by my co-host, Swyx, writer and editor of Latent Space.Swyx: Today we have a special guest, Tamar Friedman, all the way from Tel Aviv, CEO and co-founder of Codium AI. Welcome.Itamar: Hey, great being here. Thank you for inviting me.Swyx: You like the studio? It's nice, right?Itamar: Yeah, they're awesome.Swyx: So I'm gonna introduce your background a little bit and then we'll learn a bit more about who you are. So you graduated from Teknion Israel Institute of Technology's kind of like the MIT of of Israel. You did a BS in CS, and then you also did a Master's in Computer Vision, which is kind of relevant.You had other startups before this, but your sort of claim to fame is Visualead, which you started in 2011 and got acquired by Alibaba Group You showed me your website, which is the sort of QR codes with different forms of visibility. And in China that's a huge, huge deal. It's starting to become a bigger deal in the west. My favorite anecdote that you told me was something about how much sales use you saved or something. I forget what the number was.Itamar: Generally speaking, like there's a lot of peer-to-peer transactions going on, like payments and, and China with QR codes. So basically if for example 5% of the scanning does not work and with our scanner we [00:01:30] reduce it to 4%, that's a lot of money. Could be tens of millions of dollars a day.Swyx: And at the scale of Alibaba, it serves all of China. It's crazy. You did that for seven years and you're in Alibaba until 2021 when you took some time off and then hooked up with Debbie, who you've known for 25 years, to start Codium AI and you just raised your $11 million seed rounds with TlB Partners and Vine. Congrats. Should we go right into Codium? What is Codium?Itamar: So we are an AI coding assistant / agent to help developers reaching zero bugs. We don't do that today. Right now, we help to reduce the amount of bugs. Actually you can see people commenting on our marketplace page saying that they found bugs with our tool, and that's like our premise. Our vision is like for Tesla zero emission or something like that, for us it's zero bugs.We started with building an IDE extension either in VS Code or in JetBrains. And that actually works alongside the main panel where you write your code and I can show later what we do is analyze the code, whether you started writing it or you completed it.Like you can go both TDD (Test-Driven Development) or classical coding. And we offer analysis, tests, whether they pass or not, we further self debug [00:03:00] them and make suggestions eventually helping to improve the code quality specifically on code logic testing.Alessio: How did you get there? Obviously it's a great idea. Like, what was the idea, maze? How did you get here?Itamar: I'll go back long. So, yes I was two and a half times a CTO, VC backed startup CTO where we talked about the last one that I sold to Alibaba. But basically I'm like, it's weird to say by 20 years already of R&D manager, I'm not like the best programmer because like you mentioned, I'm coming more from the machine learning / computer vision side, one, one of the main application, but a lot of optimization. So I'm not necessarily the best coder, but I am like 20 year R&D manager. And I found that verifying code logic is very hard thing. And one of the thing that really makes it difficult to increase the development velocity.So you have tools related to checking performance.You have tools for vulnerabilities and security, Israelis are really good at that. But do you have a tool that actually helps you test code logic? I think what we have like dozens or hundreds, even thousands that help you on the end to end, maybe on the microservice integration system. But when you talk about code level, there isn't anything.So that was the pain I always had, especially when I did have tools for that, for the hardware. Like I worked in Mellanox to be sold to Nvidia as a student, and we had formal tools, et cetera. [00:04:30] So that's one part.The second thing is that after being sold to Alibaba, the team and I were quite a big team that worked on machine learning, large language model, et cetera, building developer tools relate with, with LLMs throughout the golden years of. 2017 to 2021, 2022. And we saw how powerful they became.So basically, if I frame it this way, because we develop it for so many use cases, we saw that if you're able to take a problem put a framework of a language around it, whether it's analyzing browsing behavior, or DNA, or etc, if you can put a framework off a language, then LLMs take you really far.And then I thought this problem that I have with code logic testing is basically a combination of a few languages: natural language, specification language, technical language. Even visual language to some extent. And then I quit Alibaba and took a bit of time to maybe wrap things around and rest a bit after 20 years of startup and corporate and joined with my partner Dedy Kredo who was my ever first employee.And that's how we like, came to this idea.Alessio: The idea has obviously been around and most people have done AST analysis, kinda like an abstract syntax tree, but it's kind of hard to get there with just that. But I think these models now are getting good enough where you can mix that and also traditional logical reasoning.Itamar: Exactly.Alessio: Maybe talk a little bit more about the technical implementation of it. You mentioned the agent [00:06:00] part. You mentioned some of the model part, like what happens behind the scenes when Codium gets in your code base?Itamar: First of all, I wanna mention I think you're really accurate.If you try to take like a large language model as is and try to ask it, can you like, analyze, test the code, etc, it'll not work so good. By itself it's not good enough on the other side, like all the traditional techniques we already started to invent since the Greek times. You know, logical stuff, you mentioned ASTs, but there's also dynamic code analysis, mutation testing, etc. There's a lot of the techniques out there, but they have inefficiencies.And a lot of those inefficiencies are actually matching with AI capabilities. Let me give you one example. Let's say you wanna do fuzzy testing or mutation testing.Mutation testing means that you either mutate the test, like the input of the test, the code of the test, etc or you mutate the code in order to check how good is your test suite.For example, if I mutate some equation in the application code and the test finds a bug and it does that at a really high rate, like out of 100 mutation, I [00:07:30] find all of the 100 problems in the test. It's probably a very strong test suite.Now the problem is that there's so many options for what to mutate in the data, in the test. And this is where, for example, AI could help, like pointing out where's the best thing that you can mutate. Actually, I think it's a very good use case. Why? Because even if AI is not 100% accurate, even if it's 80% accurate, it could really take you quite far rather just randomly selecting things.So if I wrap up, just go back high level. I think LLM by themselves cannot really do the job of verifying code logic and and neither can the traditional ones, so you need to merge them. But then one more thing before maybe you tell me where to double click. I think with code logic there's also a philosophy question here.Logic different from performance or quality. If I did a three for in loop, like I loop three things and I can fold them with some vector like in Python or something like that. We need to get into the mind of the developer. What was the intention? Like what is the bad code? Not what is the code logic that doesn't work. It's not according to the specification. So I think like one more thing that AI could really help is help to match, like if there is some natural language description of the code, we can match it. Or if there's missing information in natural language that needs [00:09:00] to be asked for the AI could help asking the user.It's not like a closed solution. Rather open and leaving the developer as the lead. Just like moving the developer from, from being the coder to actually being like a pilot that that clicks button and say, ah, this is what I meant, or this is the fix, rather actually writing all the code.Alessio: That makes sense. I think I talked about it on the podcast before, but like the switch from syntax to like semantics, like developers used to be focused on the syntax and not the meaning of what they're writing. So now you have the models that are really good at the syntax and you as a human are supposed to be really good at the semantics of what you're trying to build.How does it practically work? So I'm a software developer, I want to use Codium, like how do I start and then like, how do you make that happen in the, in the background?Itamar: So, like I said, Codium right now is an IDE extension. For example, I'm showing VS code. And if you just install it, like you'll have a few access points to start Codium AI, whether this sidebar or above every component or class that we think is very good to check with Codium.You'll have this small button. There's other way you can mark specific code and right click and run code. But this one is my favorite because we actually choose above which components we suggest to use code. So once I click it code, I starts analyzing this class. But not only this class, but almost everything that is [00:10:30] being used by the call center class.But all and what's call center is, is calling. And so we do like a static code analysis, et cetera. What, what we talked about. And then Codium provides with code analysis. It's right now static, like you can't change. It can edit it, and maybe later we'll talk about it. This is what we call the specification and we're going to make it editable so you can add additional behaviors and then create accordingly, test that will not pass, and then the code will, will change accordingly. So that's one entrance point, like via natural language description. That's one of the things that we're working on right now. What I'm showing you by the way, could be downloaded as is. It's what we have in production.The second thing that we show here is like a full test suite. There are six tests by default but you can just generate more almost as much as you want every time. We'll try to cover something else, like a happy pass edge case et cetera. You can talk with specific tests, okay? Like you can suggest I want this in Spanish or give a few languages, or I want much more employees.I didn't go over what's a call center, but basically it manages like call center. So you can imagine, I can a ask to make it more rigorous, etc, but I don't wanna complicate so I'm keeping it as is.I wanna show you the next one, which is run all test. First, we verify that you're okay, we're gonna run it. I don't know, maybe we are connected to the environment that is currently [00:12:00] configured in the IDE. I don't know if it's production for some reason, or I don't know what. Then we're making sure that you're aware we're gonna run the code that and then once we run, we show if it pass or fail.I hope that we'll have one fail. But I'm not sure it's that interesting. So I'll go like to another example soon, but, but just to show you what's going on here, that we actually give an example of what's a problem. We give the log of the error and then you can do whatever you want.You can fix it by yourself, or you can click reflect and fix, and what's going on right now is a bit a longer process where we do like chain of thought or reflect and fix. And we can suggest a solution. You can run it and in this case it passes. Just an example, this is a very simple example.Maybe later I'll show you a bug. I think I'll do that and I'll show you a bug and how we recognize actually the test. It's not a problem in the test, it's a problem in the code and then suggest you fix that instead of the code. I think you see where I'm getting at.The other thing is that there are a few code suggestion, and there could be a dozen of, of types that could be related to performance modularity or I see this case there is a maintainability.There could also be vulnerability or best practices or even suggestion for bugs. Like if we noticed, if we think one of the tests, for example, is failing because of a bug. So just code presented in the code suggestion. Probably you can choose a few, for example, if you like, and then prepare a code change like I didn't show you which exactly.We're making a diff now that you can apply on your code. So basically what, what we're seeing here is that [00:13:30] there are three main tabs, the code, the test and the code analysis. Let's call spec.And then there's a fourth tab, which is a code suggestion, if you wanna look at analytics, etc. Mm-hmm. Right now code okay. This is the change or quite a big change probably clicked on something. So that's the basic demo.Right now let's be frank. Like I wanted to show like a simple example. So it's a call center. All the inputs to the class are like relatively simple. There is no jsm input, like if you're Expedia or whatever, you have a J with the hotels, Airbnb, you know, so the test will be almost like too simple or not covering enough.Your code, if you don't provide it with some input is valuable, like adjacent with all information or YAMA or whatever. So you can actually add input data and the AI or model. It's actually by the way, a set of models and algorithms that will use that input to create interesting tests. And another thing is many people have some reference tests that they already made. It could be because they already made it or because they want like a very specific they have like how they imagine the test. So they just write one and then you add a reference and that will inspire all the rest of the tests. And also you can give like hints. [00:15:00] This is by the way plan to be like dynamic hints, like for different type of code.We will provide different hints. So we can help you become a bit more knowledgeable about how to test your code. So you can ask for like having a, a given one then, or you can have like at a funny private, like make different joke for each test or for example,Swyx: I'm curious, why did you choose that one? This is the pirate one. Yeah.Itamar: Interesting choice to put on your products. It could be like 11:00 PM of people sitting around. Let's choose one funny thingSwyx: and yeah. So two serious ones and one funny one. Yeah. Just for the listening audience, can you read out the other hints that you decided on as well?Itamar: Yeah, so specifically, like for this case, relatively very simple class, so there's not much to do, but I'm gonna go to one more thing here on the configuration. But it basically is given when then style, it's one of the best practices and tests. So even when I report a bug, for example, I found a bug when someone else code, usually I wanna say like, given, use this environment or use that this way when I run this function, et cetera.Oh, then it's a very, very full report. And it's very common to use that in like in unit test and perform.Swyx: I have never been shown this format.Itamar: I love that you, you mentioned that because if you go to CS undergrad you take so many courses in development, but none of them probably in testing, and it's so important. So why would you, and you don't go to Udemy or [00:16:30] whatever and, and do a testing course, right? Like it's, it's boring. Like people either don't do component level testing because they hate it or they do it and they hate it. And I think part of it it's because they're missing tool to make it fun.Also usually you don't get yourself educated about it because you wanna write your code. And part of what we're trying to do here is help people get smarter about testing and make it like easy. So this is like very common. And the idea here is that for different type of code, we'll suggest different type of hints to make you more knowledgeable.We're doing it on an education app, but we wanna help developers become smarter, more knowledgeable about this field. And another one is mock. So right now, our model decided that there's no need for mock here, which is a good decision. But if we would go to real world case, like, I'm part of AutoGPT community and there's all of tooling going on there. Right? And maybe when I want to test like a specific component, and it's relatively clear that going to the web and doing some search and coming back, I don't really need to do that. Like I know what I expect to do and so I can mock that part of using to crawl the web.A certain percentage of accuracy, like around 90, we will decide this is worth mocking and we will inject it. I can click it now and force our system to mock this. But you'll see like a bit stupid mocking because it really doesn't make sense. So I chose this pirate stuff, like add funny pirate like doc stringing make a different joke for each test.And I forced it to add mocks, [00:18:00] the tests were deleted and now we're creating six new tests. And you see, here's the shiver me timbers, the test checks, the call successful, probably there's some joke at the end. So in this case, like even if you try to force it to mock it didn't happen because there's nothing but we might find here like stuff that it mock that really doesn't make sense because there's nothing to mock here.So that's one thing I. I can show a demo where we actually catch a bug. And, and I really love that, you know how it is you're building a developer tools, the best thing you can see is developers that you don't know giving you five stars and sharing a few stuff.We have a discord with thousands of users. But I love to see the individual reports the most. This was one of my favorites. It helped me to find two bugs. I mentioned our vision is to reach zero bugs. Like, if you may say, we want to clean the internet from bugs.Swyx: So debugging the internet. I have my podcast title.Itamar: So, so I think like if we move to another exampleSwyx: Yes, yes, please, please. This is great.Itamar: I'm moving to a different example, it is the bank account. By the way, if you go to ChatGPT and, and you can ask me what's the difference between Codium AI and using ChatGPT.Mm-hmm. I'm, I'm like giving you this hard question later. Yeah. So if you ask ChatGPT give me an example to test a code, it might give you this bank account. It's like the one-on-one stuff, right? And one of the reasons I gave it, because it's easy to inject bugs here, that's easy to understand [00:19:30] anyway.And what I'm gonna do right now is like this bank account, I'm gonna change the deposit from plus to minus as an example. And then I'm gonna run code similarly to how I did before, like it suggests to do that for the entire class. And then there is the code analysis soon. And when we announce very soon, part of this podcast, it's going to have more features here in the code analysis.We're gonna talk about it. Yep. And then there is the test that I can run. And the question is that if we're gonna catch the bag, the bugs using running the test, Because who knows, maybe this implementation is the right one, right? Like you need to, to converse with the developer. Maybe in this weird bank, bank you deposit and, and the bank takes money from you.And we could talk about how this happens, but actually you can see already here that we are already suggesting a hint that something is wrong here and here's a suggestion to put it from minus to to plus. And we'll try to reflect and, and fix and then we will see actually the model telling you, hey, maybe this is not a bug in the test, maybe it's in the code.Swyx: I wanna stay on this a little bit. First of all, this is very impressive and I think it's very valuable. What user numbers can you disclose, you launched it and then it's got fairly organic growth. You told me something off the air, but you know, I just wanted to show people like this is being adopted in quite a large amount.Itamar: [00:21:00] First of all, I'm a relatively transparent person. Like even as a manager, I think I was like top one percentile being transparent in Alibaba. It wasn't five out of five, which is a good thing because that's extreme, but it was a good, but it also could be a bad, some people would claim it's a bad thing.Like for example, if my CTO in Alibaba would tell me you did really bad and it might cut your entire budget by 30%, if in half a year you're not gonna do like much better and this and that. So I come back to a team and tell 'em what's going on without like trying to smooth thing out and we need to solve it together.If not, you're not fitting in this team. So that's my point of view. And the same thing, one of the fun thing that I like about building for developers, they kind of want that from you. To be transparent. So we are on the high numbers of thousands of weekly active users. Now, if you convert from 50,000 downloads to high thousands of weekly active users, it means like a lot of those that actually try us keep using us weekly.I'm not talking about even monthly, like weekly. And that was like one of their best expectations because you don't test your code every day. Right now, you can see it's mostly focused on testing. So you probably test it like once a week. Like we wanted to make it so smooth with your development methodology and development lifecycle that you use it every day.Like at the moment we hope it to be used weekly. And that's what we're getting. And the growth is about like every two, three weeks we double the amount of weekly and downloads. It's still very early, like seven weeks. So I don't know if it'll keep that way, but we hope so. Well [00:22:30] actually I hope that it'll be much more double every two, three weeks maybe. Thanks to the podcast.Swyx: Well, we, yeah, we'll, we'll add you know, a few thousand hopefully. The reason I ask this is because I think there's a lot of organic growth that people are sharing it with their friends and also I think you've also learned a lot from your earliest days in, in the private beta test.Like what have you learned since launching about how people want to use these testing tools?Itamar: One thing I didn't share with you is like, when you say virality, there is like inter virality and intra virality. Okay. Like within the company and outside the company. So which teams are using us? I can't say, but I can tell you that a lot of San Francisco companies are using us.And one of the things like I'm really surprised is that one team, I saw one user two weeks ago, I was so happy. And then I came yesterday and I saw 48 of that company. So what I'm trying to say to be frank is that we see more intra virality right now than inter virality. I don't see like video being shared all around Twitter. See what's going on here. Yeah. But I do see, like people share within the company, you need to use it because it's really helpful with productivity and it's something that we will work about the [00:24:00] inter virality.But to be frank, first I wanna make sure that it's helpful for developers. So I care more about intra virality and that we see working really well, because that means that tool is useful. So I'm telling to my colleague, sharing it on, on Twitter means that I also feel that it will make me cool or make me, and that's something maybe we'll need, still need, like testing.Swyx: You know, I don't, well, you're working on that. We're gonna announce something like that. Yeah. You are generating these tests, you know, based on what I saw there. You're generating these tests basically based on the name of the functions. And the doc strings, I guess?Itamar:So I think like if you obfuscate the entire code, like our accuracy will drop by 50%. So it's right. We're using a lot of hints that you see there. Like for example, the functioning, the dog string, the, the variable names et cetera. It doesn't have to be perfect, but it has a lot of hints.By the way. In some cases, in the code suggestion, we will actually suggest renaming some of the stuff that will sync, that will help us. Like there's suge renaming suggestion, for example. Usually in this case, instead of calling this variable is client and of course you'll see is “preferred client” because basically it gives a different commission for that.So we do suggest it because if you accept it, it also means it will be easier for our model or system to keep improving.Swyx: Is that a different model?Itamar: Okay. That brings a bit to the topic of models properties. Yeah. I'll share it really quickly because Take us off. Yes. It's relevant. Take us off. Off. Might take us off road.I think [00:25:30] like different models are better on different properties, for example, how obedient you are to instruction, how good you are to prompt forcing, like to format forcing. I want the results to be in a certain format or how accurate you are or how good you are in understanding code.There's so many calls happening here to models by the way. I. Just by clicking one, Hey Codium AI. Can you help me with this bank account? We do a dozen of different calls and each feature you click could be like, like with that reflect and fix and then like we choose the, the best one.I'm not talking about like hundreds of models, but we could, could use different APIs of open AI for example, and, and other models, et cetera. So basically like different models are better on different aspect. Going back to your, what we talked about, all the models will benefit from having those hints in, in the code, that rather in the code itself or documentation, et cetera.And also in the code analysis, we also consider the code analysis to be the ground truth to some extent. And soon we're also going to allow you to edit it and that will use that as well.Alessio: Yeah, maybe talk a little bit more about. How do I actually get all these models to work together? I think there's a lot of people that have only been exposed to Copilot so far, which is one use case, just complete what I'm writing. You're doing a lot more things here. A lot of people listening are engineers themselves, some of them build these tools, so they would love to [00:27:00] hear more about how do you orchestrate them, how do you decide which model the what, stuff like that.Itamar: So I'll start with the end because that is a very deterministic answer, is that we benchmark different models.Like every time this there a new model in, in town, like recently it's already old news. StarCoder. It's already like, so old news like few days ago.Swyx: No, no, no. Maybe you want to fill in what it is StarCoder?Itamar: I think StarCoder is, is a new up and coming model. We immediately test it on different benchmark and see if, if it's better on some properties, et cetera.We're gonna talk about it like a chain of thoughts in different part in the chain would benefit from different property. If I wanna do code analysis and, and convert it to natural language, maybe one model would be, would be better if I want to output like a result in, in a certain format.Maybe another model is better in forcing the, a certain format you probably saw on Twitter, et cetera. People talk about it's hard to ask model to output JSON et cetera. So basically we predefine. For different tasks, we, we use different models and I think like this is for individuals, for developers to check, try to sync, like the test that now you are working on, what is most important for you to get, you want the semantic understanding, that's most important? You want the output, like are you asking for a very specific [00:28:30] output?It's just like a chat or are you asking to give a output of code and have only code, no description. Or if there's a description of the top doc string and not something else. And then we use different models. We are aiming to have our own models in in 2024. Being independent of any other third party, like OpenAI or so, but since our product is very challenging, it has UI/UX challenges, engineering challenge, statical and dynamical analysis, and AI.As entrepreneur, you need to choose your battles. And we thought that it's better for us to, to focus on everything around the model. And one day when we are like thinking that we have the, the right UX/UI engineering, et cetera, we'll focus on model building. This is also, by the way, what we did in in Alibaba.Even when I had like half a million dollar a month for trading one foundational model, I would never start this way. You always try like first using the best model you can for your product. Then understanding what's the glass ceiling for that model? Then fine tune a foundation model, reach a higher glass ceiling and then training your own.That's what we're aiming and that's what I suggest other developers like, don't necessarily take a model and, and say, oh, it's so easy these days to do RLHF, et cetera. Like I see it's like only $600. Yeah, but what are you trying to optimize for? The properties. Don't try to like certain models first, organize your challenges.Understand the [00:30:00] properties you're aiming for and start playing with that. And only then go to train your own model.Alessio: Yeah. And when you say benchmark, you know, we did a one hour long episode, some benchmarks, there's like many of them. Are you building some unique evals to like your own problems? Like how are you doing that? And that's also work for your future model building, obviously, having good benchmarks. Yeah.Itamar:. Yeah. That's very interesting. So first of all, with all the respect, I think like we're dealing with ML benchmark for hundreds of years now.I'm, I'm kidding. But like for tens of years, right? Benchmarking statistical creatures is something that, that we're doing for a long time. I think what's new here is the generative part. It's an open challenge to some extent. And therefore, like maybe we need to re rethink some of the way we benchmark.And one of the notions that I really believe in, I don't have a proof for that, is like create a benchmark in levels. Let's say you create a benchmark from level one to 10, and it's a property based benchmark. Let's say I have a WebGPT ask something from the internet and then it should fetch it for me.So challenge level one could be, I'm asking it and it brings me something. Level number two could be I'm asking it and it has a certain structure. Let's say for example, I want to test AutoGPT. Okay. And I'm asking it to summarize what's the best cocktail I could have for this season in San Francisco.So [00:31:30] I would expect, like, for example, for that model to go. This is my I what I think to search the internet and do a certain thing. So level number three could be that I want to check that as part of this request. It uses a certain tools level five, you can add to that. I expect that it'll bring me back something like relevance and level nine it actually prints the cocktail for me I taste it and it's good. So, so I think like how I see it is like we need to have data sets similar to before and make sure that we not fine tuning the model the same way we test it. So we have one challenges that we fine tune over, right? And few challenges that we don't.And the new concept may is having those level which are property based, which is something that we know from software testing and less for ML. And this is where I think that these two concepts merge.Swyx: Maybe Codium can do ML testing in the future as well.Itamar: Yeah, that's a good idea.Swyx: Okay. I wanted to cover a little bit more about Codium in the present and then we'll go into the slides that you have.So you have some UI/UX stuff and you've obviously VS Code is the majority market share at this point of IDE, but you also have IntelliJ right?Itamar: Jet Brains in general.Swyx: Yeah. Anything that you learned supporting JetBrains stuff? You were very passionate about this one user who left you a negative review.What is the challenge of that? Like how do you think about the market, you know, maybe you should focus on VS Code since it's so popular?Itamar: Yeah. [00:33:00] So currently the VS Code extension is leading over JetBrains. And we were for a long time and, and like when I tell you long time, it could be like two or three weeks with version oh 0.5, point x something in, in VS code, although oh 0.4 or so a jet brains, we really saw the difference in, in the how people react.So we also knew that oh 0.5 is much more meaningful and one of the users left developers left three stars on, on jet brands and I really remember that. Like I, I love that. Like it's what do you want to get at, at, at our stage? What's wrong? Like, yes, you want that indication, you know, the worst thing is getting nothing.I actually, not sure if it's not better to get even the bad indication, only getting good ones to be re frank like at, at, at least in our stage. So we're, we're 9, 10, 10 months old startup. So I think like generally speaking We find it easier and fun to develop in vs code extension versus JetBrains.Although JetBrains has like very nice property, when you develop extension for one of the IDEs, it usually works well for all the others, like it's one extension for PyCharm, and et cetera. I think like there's even more flexibility in the VS code. Like for example, this app is, is a React extension as opposed that it's native in the JetBrains one we're using. What I learned is that it's basically is almost like [00:34:30] developing Android and iOS where you wanna have a lot of the best practices where you have one backend and all the software development like best practices with it.Like, like one backend version V1 supports both under Android and iOS and not different backends because that's crazy. And then you need all the methodology. What, what means that you move from one to 1.1 on the backend? What supports whatnot? If you don't what I'm talking about, if you developed in the past, things like that.So it's important. And then it's like under Android and iOS and, and you relatively want it to be the same because you don't want one developer in the same team working with Jet Brains and then other VS code and they're like talking, whoa, that's not what I'm seeing. And with code, what are you talking about?And in the future we're also gonna have like teams offering of collaboration Right now if you close Codium Tab, everything is like lost except of the test code, which you, you can, like if I go back to a test suite and do open as a file, and now you have a test file with everything that you can just save, but all the goodies here it's lost. One day we're gonna have like a platform you can save all that, collaborate with people, have it part of your PR, like have suggested part of your PR. And then you wanna have some alignment. So one of the challenges, like UX/UI, when you think about a feature, it should, some way or another fit for both platforms be because you want, I think by the way, in iOS and Android, Android sometimes you don't care about parity, but here you're talking about developers that might be on the same [00:36:00] team.So you do care a lot about that.Alessio: Obviously this is a completely different way to work for developers. I'm sure this is not everything you wanna build and you have some hint. So maybe take us through what you see the future of software development look like.Itamar: Well, that's great and also like related to our announcement, what we're working on.Part of it you already start seeing in my, in my demo before, but now I'll put it into a framework. I'll be clearer. So I think like the software development world in 2025 is gonna look very different from 2020. Very different. By the way. I think 2020 is different from 2000. I liked the web development in 95, so I needed to choose geocities and things like that.Today's much easier to build a web app and whatever, one of the cloud. So, but I think 2025 is gonna look very different in 2020 for the traditional coding. And that's like a paradigm I don't think will, will change too much in the last few years. And, and I'm gonna go over that when I, when I'm talking about, so j just to focus, I'm gonna show you like how I think the intelligence software development world look like, but I'm gonna put it in the lens of Codium AI.We are focused on code integrity. We care that with all this advancement of co-generation, et cetera, we wanna make sure that developers can code fast with confidence. That they have confidence on generated code in the AI that they are using that. That's our focus. So I'm gonna put, put that like lens when I'm going to explain.So I think like traditional development. Today works like creating some spec for different companies, [00:37:30] different development teams. Could mean something else, could be something on Figma, something on Google Docs, something on Jira. And then usually you jump directly to code implementation. And then if you have the time or patience, or will, you do some testing.And I think like some people would say that it's better to do TDD, like not everyone. Some would say like, write spec, write your tests, make sure they're green, that they do not pass. Write your implementation until your test pass. Most people do not practice it. I think for just a few, a few reason, let them mention two.One, it's tedious and I wanna write my code like before I want my test. And I don't think, and, and the second is, I think like we're missing tools to make it possible. And what we are advocating, what I'm going to explain is actually neither. Okay. It's very, I want to say it's very important. So here's how we think that the future of development pipeline or process is gonna look like.I'm gonna redo it in steps. So, first thing I think there do I wanna say that they're gonna be coding assistance and coding agents. Assistant is like co-pilot, for example, and agents is something that you give it a goal or a task and actually chains a few tasks together to complete your goal.Let's have that in mind. So I think like, What's happening right now when you saw our demo is what I presented a few minutes ago, is that you start with an implementation and we create spec for you and test for you. And that was like a agent, like you didn't converse with it, you just [00:39:00] click a button.And, and we did a, a chain of thought, like to create these, that's why it's it's an agent. And then we gave you an assistant to change tests, like you can converse it with it et cetera. So that's like what I presented today. What we're announcing is about a vision that we called the DRY. Don't repeat yourself. I'm gonna get to that when I'm, when I'm gonna show you the entire vision. But first I wanna show you an intermediate step that what we're going to release. So right now you can write your code. Or part of it, like for example, just a class abstract or so with a coding assistant like copilot and maybe in the future, like a Codium AI coding assistant.And then you can create a spec I already presented to you. And the next thing is that you going to have like a spec assistant to generate technical spec, helping you fill it quickly focused on that. And this is something that we're working on and, and going to release the first feature very soon as part of announcement.And it's gonna be very lean. Okay? We're, we're a startup that going bottom up, like lean features going to more and more comprehensive one. And then once you have the spec and implementation, you can either from implementation, have tests, and then you can run the test and fix them like I presented to you.But you can also from spec create tests, okay? From the spec directly to tests. [00:40:30]So then now you have a really interesting thing going on here is that you can start from spec, create, test, create code. You can start from test create code. You can start from a limitation. From code, create, spec and test. And actually we think the future is a very flexible one. You don't need to choose what you're practicing traditional TDD or whatever you wanna start with.If you have already some spec being created together with one time in one sprint, you decided to write a spec because you wanted to align about it with your team, et cetera, and now you can go and create tests and implementation or you wanted to run ahead and write your code. Creating tests and spec that aligns to it will be relatively easy.So what I'm talking about is extreme DRY concept; DRY is don't repeat yourself. Until today when we talked about DRY is like, don't repeat your code. I claim that there is a big parts of the spec test and implementation that repeat himself, but it's not a complete repetition because if spec was as detailed as the implementation, it's actually the implementation.But the spec is usually in different language, could be natural language and visual. And what we're aiming for, our vision is enabling the dry concept to the extreme. With all these three: you write your test will help you generate the code and the spec you write your spec will help you doing the test and implementation.Now the developers is the driver, okay? You'll have a lot [00:42:00] of like, what do you think about this? This is what you meant. Yes, no, you wanna fix the coder test, click yes or no. But you still be the driver. But there's gonna be like extreme automation on the DRY level. So that's what we're announcing, that we're aiming for as our vision and what we're providing these days in our product is the middle, is what, what you see in the middle, which is our code integrity agents working for you right now in your id, but soon also part of your Github actions, et cetera, helping you to align all these three.Alessio: This is great. How do you reconcile the difference in languages, you know, a lot of times the specs is maybe like a PM or it's like somebody who's more at the product level.Some of the implementation details is like backend developers for something. Frontend for something. How do you help translate the language between the two? And then I think in the one of the blog posts on your blog, you mentioned that this is also changing maybe how programming language themselves work. How do you see that change in the future? Like, are people gonna start From English, do you see a lot of them start from code and then it figures out the English for them?Itamar: Yeah. So first of all, I wanna say that although we're working, as we speak on managing we front-end frameworks and languages and usage, we are currently focused on the backend.So for example, as the spec, we won't let you input Figma, but don't be surprised if in 2024 the input of the spec could be a Figma. Actually, you can see [00:43:30] demos of that on a pencil drawing from OpenAI and when he exposed the GPT-4. So we will have that actually.I had a blog, but also I related to two different blogs. One, claiming a very knowledgeable and respectful, respectful person that says that English is going to be the new language program language and, and programming is dead. And another very respectful person, I think equally said that English is a horrible programming language.And actually, I think both of are correct. That's why when I wrote the blog, I, I actually related, and this is what we're saying here. Nothing is really fully redundant, but what's annoying here is that to align these three, you always need to work very hard. And that's where we want AI to help with. And if there is inconsistency will raise a question, what do, which one is true?And just click yes or no or test or, or, or code that, that what you can see in our product and we'll fix the right one accordingly. So I think like English and, and visual language and code. And the test language, let's call it like, like that for a second. All of them are going to persist. And just at the level of automation aligning all three is what we're aiming for.Swyx: You told me this before, so I I'm, I'm just actually seeing Alessio's reaction to it as a first time.Itamar: Yeah, yeah. Like you're absorbing like, yeah, yeah.Swyx: No, no. This is, I mean, you know, you can put your VC hat on or like compare, like what, what is the most critical or unsolved question presented by this vision?Alessio: A lot of these tools, especially we've seen a lot in the past, it's like the dynamic nature of a lot of this, you know?[00:45:00] Yeah. Sometimes, like, as you mentioned, sometimes people don't have time to write the test. Sometimes people don't have time to write the spec. Yeah. So sometimes you end up with things. Out of sync, you know? Yeah. Or like the implementation is moving much faster than the spec, and you need some of these agents to make the call sometimes to be like, no.Yeah, okay. The spec needs to change because clearly if you change the code this way, it needs to be like this in the future. I think my main question as a software developer myself, it's what is our role in the future? You know? Like, wow, how much should we intervene, where should we intervene?I've been coding for like 15 years, but if I've been coding for two years, where should I spend the next year? Yeah. Like focus on being better at understanding product and explain it again. Should I get better at syntax? You know, so that I can write code. Would love have any thoughts.Itamar: Yeah. You know, there's gonna be a difference between 1, 2, 3 years, three to six, six to 10, and 10 to 20. Let's for a second think about the idea that programming is solved. Then we're talking about a machine that can actually create any piece of code and start creating, like we're talking about singularity, right?Mm-hmm. If the singularity happens, then we're talking about this new set of problems. Let's put that aside. Like even if it happens in 2041, that's my prediction. I'm not sure like you should aim for thinking what you need to do, like, or not when the singularity happens. So I, [00:46:30] I would aim for mm-hmm.Like thinking about the future of the next five years or or, so. That's my recommendation because it's so crazy. Anyway. Maybe not the best recommendation. Take that we're for grain of salt. And please consult with a lawyer, at least in the scope of, of the next five years. The idea that the developers is the, the driver.It actually has like amazing team members. Agents that working for him or her and eventually because he or she's a driver, you need to understand especially what you're trying to achieve, but also being able to review what you get. The better you are in the lower level of programming in five years, it it mean like real, real program language.Then you'll be able to develop more sophisticated software and you will work in companies that probably pay more for sophisticated software and the more that you're less skilled in, in the actual programming, you actually would be able to be the programmer of the new era, almost a creator. You'll still maybe look on the code levels testing, et cetera, but what's important for you is being able to convert products, requirements, et cetera, to working with tools like Codium AI.So I think like there will be like degree of diff different type developers now. If you think about it for a second, I think like it's a natural evolution. It's, it's true today as well. Like if you know really good the Linux or assembly, et cetera, you'll probably work like on LLVM Nvidia [00:48:00] whatever, like things like that.Right. And okay. So I think it'll be like the next, next step. I'm talking about the next five years. Yeah. Yeah. Again, 15 years. I think it's, it's a new episode if you would like to invite me. Yeah. Oh, you'll be, you'll be back. Yeah. It's a new episode about how, how I think the world will look like when you really don't need a developer and we will be there as Cody mi like you can see.Mm-hmm.Alessio: Do we wanna dive a little bit into AutoGPT? You mentioned you're part of the community. Yeah.Swyx: Obviously Try, Catch, Finally, Repeat is also part of the company motto.Itamar: Yeah. So it actually really. Relates to what we're doing and there's a reason we have like a strong relationship and connection with the AutoGPT community and us being part part of it.So like you can see, we're talking about agent for a few months now, and we are building like a designated, a specific agent because we're trying to build like a product that works and gets the developer trust to have developer trust us. We're talking about code integrity. We need it to work. Like even if it will not put 100% it's not 100% by the way our product at all that UX/UI should speak the language of, oh, okay, we're not sure here, please take the driving seat.You want this or that. But we really not need, even if, if we're not close to 100%, we still need to work really well just throwing a number. 90%. And so we're building a like really designated agents like those that from code, create tests.So it could create tests, run them, fix them. It's a few tests. So we really believe in that we're [00:49:30] building a designated agent while Auto GPT is like a swarm of agents, general agents that were supposedly you can ask, please make me rich or make me rich by increase my net worth.Now please be so smart and knowledgeable to use a lot of agents and the tools, et cetera, to make it work. So I think like for AutoGPT community was less important to be very accurate at the beginning, rather to show the promise and start building a framework that aims directly to the end game and start improving from there.While what we are doing is the other way around. We're building an agent that works and build from there towards that. The target of what I explained before. But because of this related connection, although it's from different sides of the, like the philosophy of how you need to build those things, we really love the general idea.So we caught it really early that with Toran like building it, the, the maker of, of AutoGPT, and immediately I started contributing, guess what, what did I contribute at the beginning tests, right? So I started using Codium AI to build tests for AutoGPT, even, even finding problems this way, et cetera.So I become like one of the, let's say 10 contributors. And then in the core team of the management, I talk very often with with Toran on, on different aspects. And we are even gonna have a workshop,Swyx: a very small [00:49:00] meetingItamar: work meeting workshop. And we're going to compete together in a, in a hackathons.And to show that AutoGPT could be useful while, for example, Codium AI is creating the test for it, et cetera. So I'm part of that community, whether is my team are adding tests to it, whether like advising, whether like in in the management team or whether to helping Toran. Really, really on small thing.He is the amazing leader like visionaire and doing really well.Alessio: What do you think is the future of open source development? You know, obviously this is like a good example, right? You have code generating the test and in the future code could actually also implement the what the test wanna do. So like, yeah.How do you see that change? There's obviously not enough open source contributors and yeah, that's one of the, the main issue. Do you think these agents are maybe gonna help us? Nadia Eghbal has this great book called like Working in Public and there's this type of projects called Stadium model, which is, yeah, a lot of people use them and like nobody wants to contribute to them.I'm curious about, is it gonna be a lot of noise added by a lot of these agents if we let them run on any repo that is open source? Like what are the contributing guidelines for like humans versus agents? I don't have any of the answers, but like some of the questions that I've been thinking about.Itamar: Okay. So I wanna repeat your question and make sure I understand you, but like, if they're agents, for example, dedicated for improving code, why can't we run them on, mm-hmm.Run them on like a full repository in, in fixing that? The situation right now is that I don't think that right now Auto GPT would be able to do that for you. Codium AI might but it's not open sourced right now. And and like you can see like in the months or two, you will be able to like running really quickly like development velocity, like our motto is moving fast with confidence by the way.So we try to like release like every day or so, three times even a day in the backend, et cetera. And we'll develop more feature, enable you, for example, to run an entire re, but, but it's not open source. So about the open source I think like AutoGPT or LangChain, you can't really like ask please improve my repository, make it better.I don't think it will work right now because because let me like. Softly quote Ilya from Open AI. He said, like right now, let's say that a certain LLM is 95% accurate. Now you're, you're concatenating the results. So the accuracy is one point like it's, it's decaying. And what you need is like more engineering frameworks and work to be done there in order to be able to deal with inaccuracies, et cetera.And that's what we specialize in Codium, but I wanna say that I'm not saying that Auto GPT won't be able to get there. Like the more tools and that going to be added, the [00:52:30] more prompt engineering that is dedicated for this, this idea will be added by the way, where I'm talking with Toran, that Codium, for example, would be one of the agents for Auto GPT.Think about it AutoGPT is not, is there for any goal, like increase my net worth, though not focused as us on fixing or improving code. We might be another agent, by the way. We might also be, we're working on it as a plugin for ChatGPT. We're actually almost finished with it. So that's like I think how it's gonna be done.Again, open opensource, not something we're thinking about. We wanted to be really good before weSwyx: opensource it. That was all very impressive. Your vision is actually very encouraging as well, and I, I'm very excited to try it out myself. I'm just curious on the Israel side of things, right? Like you, you're visiting San Francisco for a two week trip for this special program you can tell us about. But also I think a lot of American developers have heard that, you know, Israel has a really good tech scene. Mostly it's just security startups. You know, I did some, I was in some special unit in the I D F and like, you know, I come out and like, I'm doing the same thing again, but like, you know, for enterprises but maybe just something like, describe for, for the rest of the world.It's like, What is the Israeli tech scene like? What is this program that you're on and what shouldItamar: people know? So I think like Israel is the most condensed startup per capita. I think we're number one really? Or, or startup pair square meter. I think, I think we're number one as well because of these properties actually there is a very strong community and like everyone are around, like are [00:57:00] working in a.An entrepreneur or working in a startup. And when you go to the bar or the coffee, you hear if it's 20, 21, people talking about secondary, if it's 2023 talking about like how amazing Geni is, but everyone are like whatever are around you are like in, in the scene. And, and that's like a lot of networking and data propagation, I think.Somehow similar here to, to the Bay Area in San Francisco that it helps, right. So I think that's one of our strong points. You mentioned some others. I'm not saying that it doesn't help. Yes. And being in the like idf, the army, that age of 19, you go and start dealing with technology like very advanced one, that, that helps a lot.And then going back to the community, there's this community like is all over the world. And for example, there is this program called Icon. It's basically Israelis and in the Valley created a program for Israelis from, from Israel to come and it's called Silicon Valley 1 0 1 to learn what's going on here.Because with all the respect to the tech scene in Israel here, it's the, the real thing, right? So, so it's an non-profit organization by Israelis that moved here, that brings you and, and then brings people from a 16 D or, or Google or Navon or like. Amazing people from unicorns or, or up and coming startup or accelerator, and give you up-to-date talks and, and also connect you to relevant people.And that's, that's why I'm here in addition to to, you know, to [00:58:30] me and, and participate in this amazing podcast, et cetera.Swyx: Yeah. Oh, well, I, I think, I think there's a lot of exciting tech talent, you know, in, in Tel Aviv, and I, I'm, I'm glad that your offer is Israeli.Itamar: I, I think one of thing I wanted to say, like yeah, of course, that because of what, what what we said security is, is a very strong scene, but a actually water purification agriculture attack, there's a awful other things like usually it's come from necessity.Yeah. Like, we have big part of our company of our state is like a desert. So there's, there's other things like ai by the way is, is, is big also in Israel. Like, for example, I think there's an Israeli competitor to open ai. I'm not saying like it's as big, but it's ai 21, I think out of 10.Yeah. Out. Oh yeah. 21. Is this really? Yeah. Out of 10 like most, mm-hmm. Profound research labs. Research lab is, for example, I, I love, I love their. Yeah. Yeah.Swyx: I, I think we should try to talk to one of them. But yeah, when you and I met, we connected a little bit Singapore, you know, I was in the Singapore Army and Israeli army.We do have a lot of connections between countries and small countries that don't have a lot of natural resources that have to make due in the world by figuring out some other services. I think the Singapore startup scene has not done as well as the Israeli startup scene. So I'm very interested in, in how small, small countries can have a world impact essentially.Itamar: It's a question we're being asked a lot, like why, for example, let's go to the soft skills. I think like failing is a bad thing. Yeah. Like, okay. Like sometimes like VCs prefer to [01:00:00] put money on a, on an entrepreneur that failed in his first startup and actually succeeded because now that person is knowledgeable, what it mean to be, to fail and very hungry to, to succeed.So I think like generally, like there's a few reason I think it's hard to put the finger exactly, but we talked about a few things. But one other thing I think like failing is not like, this is my fourth company. I did one as, it wasn't a startup, it was a company as a teenager. And then I had like my first startup, my second company that like, had a amazing run, but then very beautiful collapse.And then like my third company, my second startup eventually exit successfully to, to Alibaba. So, so like, I think like it's there, there are a lot of trial and error, which is being appreciated, not like suppressed. I guess like that's one of the reason,Alessio: wanna jump into lightning round?Swyx: Yes. I think we send you into prep, but there's just three questions now.We've, we've actually reduced it quite a bit, but you have it,Alessio: so, and we can read them that you can take time and answer. You don't have to right away. First question, what is a already appin in AI that Utah would take much longer than an sItamar: Okay, so I have to, I hope it doesn't sound like arrogant,

ceo american english israel google china master ai internet technology vision pr future san francisco research building partner spanish mit dna public write developing utah greek tesla run chatgpt silicon valley bs valley software airbnb android discord singapore ios israelis bay area vine logic cto stadiums icon vc react assistant demo self improvement residence openai repeat nvidia tel aviv qr cs python ui mm rsvp ml gpt linux alibaba github dry friedman profound apis mastodon blue sky vcs r d mutation google docs udemy reconciling copilot llm ast ides ide expedia relates frontend figma ilya benchmarking large language models alessio softly ui ux ux ui computer vision geni json jira v1 yama amplitude debugging github copilot tdd vs code itamar gpts jetbrains test driven development autogpt toran intellij langchain rlhf asts mellanox pycharm mosaicml podcast timestamps nadia eghbal connor leahy repeat yourself latent space tdd test driven development

Episode 175: Serkan Holat on Agile Public Funds

Play Episode Listen Later May 12, 2023 41:24

Guest Serkan Holat Panelists Richard Littauer | Leslie Hawthorn Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Richard and Leslie are hosting today, and they're very excited to welcome our special guest, Serkan Holat, who's a Freelance Software Developer, with over 20 years of experience in researching finance, open source ecosystems, and digital public goods. He advocates for financing open source software with public money and setting up dedicated public funds called Agile Public Funds. Today, we'll discuss with Serkan, the need to allocate funds to support and publish critical open source software, the importance of sustainability on open source software, and the lack of understanding of the industry's risk profile. Also, Serkan gives us all the details on an experiment he recently started to increase awareness about using public money to finance open source. Download this episode to hear much more! [00:01:47] We start off with Serkan telling us how the tax cause is going. He proposes introducing an open source tax on proprietary software sales, with the revenue going to public funds for distribution to the open source ecosystem. [00:06:11] Serkan explains how he's watched the space grow, and he talks about the Digital Public Goods Alliance that recognizes open source software as a new type of digital public good, and the Sovereign Tech Fund. [00:08:35] Serkan tells us why there shouldn't be any obligations on the developers and what we should do. [00:10:23] We hear Serkan's thoughts on the Sovereign Tech Fund in Germany, an excellent initiative that he supports as a blueprint for other nations to follow, but scalability will become an issue. [00:12:39] Free Software Foundation Europe has a fantastic campaign. Serkan's explains the idea of using public sector collaboration. [00:13:56] There's a discussion on the challenges of implementing public sector collaboration and there's a suggestion of creating a social contract to increase funding for open source software. [00:16:43] What's wrong with the market we currently have? Serkan elaborates on this. [00:20:19] The conversation shifts to Richard, Leslie, and Serkan touching on the role of security in financing open source software, they discuss the allocations of funds to support and publish open source software, the need for sustainability in open source software, and the lack of understanding of the industry's risk profile. [00:28:41] Serkan shares his thoughts on how he's trying to convince software companies to produce open source software. [00:30:31] Richard wonders how a tax on proprietary software to help out open source communities, is going to lead to a more equitable environment, or all people building open source software. [00:32:45] Serkan advocates for the creation of public funds to finance the open source ecosystem, and he's been experimenting with this approach for the past 15 months. He chooses three projects from Open Collective each month and distributes money based on their criticality score. [00:34:11] Find out where you can follow Serkan and all his writings on the web. Quotes [00:02:51] “My proposal on that area is to introduce an open source software tax on proprietor software sales.” Spotlight [00:37:13] Leslie's spotlight is the Chaos Computer Club. [00:38:22] Richard's spotlight is the Feminist Bird Club, Northern Vermont chapter. [00:39:04] Serkan's spotlight is an announcement made by Minister Alexandra van Huffelen, at the EU Open Source Policy Summit 2023. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Leslie Hawthorn Twitter (https://twitter.com/lhawthorn?lang=en) Serkan Holat Twitter (https://twitter.com/coni2k?lang=en) Serkan Holat LinkedIn (https://www.linkedin.com/in/serkanholat/) Serkan Holat Mastodon (https://mastodon.social/@coni2k) Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure by Nadia Eghbal (https://www.fordfoundation.org/work/learning/research-reports/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/) Digital Public Goods Alliance (https://digitalpublicgoods.net/) Sovereign Tech Fund (https://sovereigntechfund.de/en/) Open Source Project Criticality Score-GitHub (https://github.com/ossf/criticality_score) Open source public fund experiment by Serkan Holat (https://dev.to/coni2k/open-source-public-fund-experiment-lc8) Ecosyste.ms (https://ecosyste.ms/) If it's public money, make it public code!-FOSDEM'23 (https://fosdem.org/2023/schedule/event/public_money_public_code/) Public Money? Public Code! Free Software Foundation Europe (https://publiccode.eu/en/) Switch to open source alternatives in Munich (https://en.wikipedia.org/wiki/LiMux) Chaos Computer Club (https://www.ccc.de/en/) Northern Vermont Feminist Bird Club- Instagram (https://www.instagram.com/fbc.nvt/) Dutch Digitalisation Minister announces creation of an OSPO (https://joinup.ec.europa.eu/collection/open-source-observatory-osor/news/dutch-digitalisation-minister-announces-ospo-creation) Ministerial Address: Alexandra van Huffelen (YouTube) (https://www.youtube.com/watch?v=QTQEzKQFjXg&t=18080s) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Serkan Holat.

germany public open switch quotes roads munich edited funds spotlight agile sustain serkan chaos computer club public money fosdem open collective northern vermont nadia eghbal free software foundation europe ospo

Episode 157: Joel Wasserman on lessons learned with Flossbank

Play Episode Listen Later Mar 3, 2023 41:56

Guest Joel Wasserman 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 has been on this podcast before, and we are super excited to have him back on. Joining us is Joel Wasserman, co-founder and Founder of Flossbank and Software Engineer at Google. Today, we'll find out what happened to Flossbank and what's happening next as Joel tells the story of how the idea of Flossbank came about, and the challenges and lessons he's learned along the way. He goes in-depth about the need for funding, the ginormous difference between an open source author and an open source maintainer, and diversity in open source. Download this episode now to hear more! [00:01:23] What is Flossbank? [00:05:59] Onboarding can be difficult, and Joel fills us in on some lessons he's learned. [00:09:53] Richard brings up a point of finding the right person, and wonders what issues Joel had was because he was the middleman or something else, and if it's hard to find money for any project in open source. Joel mentions Nadia Eghbal's book as the best book he's ever read on the open source ecosystem. [00:12:58] Justin talks about a blog post Joel wrote last June on “The Flossbank Attempt,” where he made a comment “don't hesitate to reach out,” and he tells us what other projects are actively asking him for advice. [00:15:20] We hear what Joel thinks of the benefits of GitHub sponsors and Open Collective are in comparison to his and why they're able to garner some money, and his thoughts on that part of the ecosystem. [00:18:26] Joel tells us if there will be any sort of government grants going down the dependency tree and if he's thought about that kind of money coming into the system and if there are benefits. [00:22:26] We hear what Joel thinks about the idea the maybe Flossbank was never going to work because there's isn't as much altruism in the world from companies and that he's asking for something that's impossible. [00:29:38] Joel talks about payment mechanisms and something cool they did with Flossbank, working with a company called Coil that uses Interledger. [00:32:13] Joel details his realistic and optimistic view on people wanting to invest in open source and getting money off it, and about diversity in open source. [00:38:50] Find out where you can follow Joel on the web. Quotes [00:05:04] “What we didn't know and what we quickly found out is that a lot of companies want to have a relationship with the maintainer they are donating to.” [00:06:21] “Small companies, startups, are acutely aware of the open source they rely on.” [00:18:53] “People just take it for granted and they say, “Well, why should I fund it if the next person isn't funding it?” [00:22:48] “There's a ginormous rarely spoken difference between an open source author and an open source maintainer. An author chooses to put that license up. An author has given no promise to working on this, to securing it toward making sure that other companies get what they want, bug fixes, future maintenance, making sure their dependencies, no guarantees.” [00:24:00] “Open source maintainers are what I'm advocating to get paid and open source maintainers are the ones who are keeping code up to date, making sure it's secure, making sure the dependencies are up to date, making sure the dependencies are secure, those people are putting in work.” [00:28:09] “Maintainership is work. It's a triage of bugs, a triage of feature requests, it's actual improvements to a package, it's a long-term commitment, it's a dramatically different persona and role than author.” [00:32:26] “You should be giving to your entire open source dependency tree because you don't know what you depend on, or you don't know what maintainer needs that money to do their work, to keep their package secured, to keep their package up to date until it breaks.” Spotlight [00:39:01] Joel's spotlight is Nadia Eghbal's book, Working in Public: The Making and Maintenance of Open Source Software. [00:40:01] Justin's spotlight is the Open Technology Fund. [00:40:19] Richard's spotlight is the book, Sacred Economics: Money, Gift & Society in The Age of Transition by Charles Eisenstein. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Justin Dorfman Twitter (https://twitter.com/jdorfman?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Joel Wasserman Twitter (https://twitter.com/joel_wasserman_) Flossbank (https://flossbank.com/) Sustain Podcast-Episode 58: Joel Wasserman on Flossbank and Sustainability Giving Back to Dependencies (https://podcast.sustainoss.org/58) Feross-Introducing ‘funding' experiment (https://feross.org/npm-install-funding/) [Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal](https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862/ref=sr11?crid=2KZZFJPGJ6QPN&keywords=nadia+eghbal&qid=1675632306&sprefix=nadia+eg%2Caps%2C118&sr=8-1) The Flossbank Attempt by Joel Wasserman (https://medium.com/@joelwass/the-flossbank-attempt-de9d8ecc1dcf) Sustain Podcast-Episode 148-Ali Nehzat of thanks.dev and OSS Funding (https://podcast.sustainoss.org/148) Sustain Podcast-Episode 152-Dudley Carr and Wes Carr on StackAid (https://podcast.sustainoss.org/152) thanks.dev (https://thanks.dev/home) Stackaid (https://www.stackaid.us/) Coil (https://coil.com/) Interledger Foundation (https://interledger.org/) Open Technology Fund (https://www.opentech.fund/news/open-technology-fund-announces-free-and-open-source-software-sustainability-fund/) Sacred Economics: Money, Gift & Society in The Age of Transition by Charles Eisenstein (https://sacred-economics.com/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Joel Wasserman.

Episode 140: Courtney Miller and Hongbo Fang on Toxicity and Information Flow in Open Source Communities

Play Episode Listen Later Sep 30, 2022 45:55

Guest Courtney Miller | Hongbo Fang Panelists Richard Littauer | Eriol Fox Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. We are super excited to talk to our guests today on the topic of toxicity in open source. Today, we have joining us, Courtney Miller and Hungbo Fang, who are both PhD students at Carnegie Mellon University. We asked them to come on because we were curious about their work, and they came highly recommended by Bogdan Vasilescu. We'll hear more about Courtney's talk and her paper on her award-winning work exploring toxicity in open source communities, and we'll find out the work Hongbo has done focusing on information flow and where people talk about open source. Download this episode now to learn more! [00:02:49] Courtney tells us about the talk she gave at the Linux Open Source Summit on her work exploring toxicity in open source communities. [00:03:55] We find out if there was a data set that was used to find the information. [00:05:08] Hongbo focuses on information flow and where do people talk about open source, and he tells us what his involvement is with this work. [00:06:57] Courtney tells us what she saw within the hundred issues and how she broke them down and tagged them to get to the conclusions she had. [00:08:44] We hear how Courtney used the technical definition of toxicity introduced by Google's Perspective API tool to inform the decisions of what toxicity means. [00:12:01] Eriol wants to know whether Courtney's had thoughts or intentions of looking into the content moderation space to see if there's any similarities between what's happening there. [00:14:29] Richard wonders what we can do to improve the state of toxicity in open source and wonders if she has any future work that can make this better. [00:16:08] Hongbo shares his thoughts about the future and what we can do to solve this from a quantitative angle. [00:17:02] Based on Courtney's work, we find out if she thinks AI has improved, if she has hope, and Hongbo shares his thoughts as well. [00:19:20] Eriol wants to know how community members can help researchers by talking about things that are less referenced in the paper, and how Courtney thinks about tackling some of the harder to read parts of toxicity with new emerging spaces. [00:24:54] We find out if there's a place where open source could have a restorative justice around toxicity and what action is there for the open source community to move from talking about our experiences of toxicity to how we can heal. [00:27:40] Hongbo explains what his work is mainly focused on, how he's holding this space, and suggestions he has for the future on how we can improve information flow. [00:34:31] Richard talks about a paper called, The Tyranny of Structurelessness by Jo Freeman, and wonders if Hongbo has any suggestions for how to help open source projects with information gap issues. [00:39:33] Find out where you can follow Courtney, Hongbo, and their work online. Quotes [00:12:11] "Open source toxicity is not new, it's very old. The long-term effects of this toxicity, especially in open source, is why I was really moved to do this research.” [00:14:56] “If you can identify toxic comments, and deal with them, instead of making the maintainers spend the emotional labor every time dealing with this stuff – [that] can be very helpful.” [00:15:17] “Maintainers are often toxic in their own projects.” [00:15:40] “We have issue templates – what about issue response templates?” [00:25:47] “If a community has leadership that tolerates certain things, it's going to happen. If the community has leadership that does not tolerate certain things, it's not going to happen.” Spotlight [00:41:21] Eriol's spotlight is Digital Safety Snacks by Pen America. [00:41:58] Richard's spotlight is an article he read called, The Opposite of Rape Culture is Nurturance Culture by Nora Samaran. [00:42:40] Hongbo's spotlight is the book, Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure by Nadia Eghbal. [00:43:32] Courtney's spotlight is the book, Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal, and the tool, Betty. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Eriol Fox Twitter (https://twitter.com/EriolDoesDesign) Courtney Miller Twitter (https://twitter.com/courtneyelta?lang=en) Courtney Miller-GitHub (https://courtney-e-miller.github.io/) Courtney Miller LinkedIn (https://www.linkedin.com/authwall?trk=gf&trkInfo=AQGvhLpJ5bQFGAAAAYK81Q-A0uWlwtLgwE79a-9Evj7n8RNvlxcJ-ev6jmZWyxl-7O3juI8yF9SLUUwAQQ8Xs_d3Re5brEfG26DUUnt2ZH3YGYXmQGAaEhwNubkkw1Ilf5Ottjo=&original_referer=&sessionRedirect=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fcourtney-e-miller%2F) Hongbo Fang Twitter (https://twitter.com/fang_hongbo?lang=en) Hongbo Fang LinkedIn (https://www.linkedin.com/in/hongbo-fang-358ba615b) Sustain Podcast-Episode 40: How Open Source Maintainers Don't Get Rich with Bogdan Vasilescu (https://podcast.sustainoss.org/guests/bogdan-vasilescu) Perspective API (https://perspectiveapi.com/) Christian Kästner (https://www.cs.cmu.edu/~ckaestne/) Kat Lo Twitter (https://twitter.com/lolkat) Meedan Twitter (https://twitter.com/Meedan) Open Source Diversity (https://opensourcediversity.org/) The Tyranny of Structurelessness by Jo Freeman (https://www.jofreeman.com/joreen/tyranny.htm) “Did You Miss My Comment or What?” Understanding Toxicity in Open Source Discussions (paper) (https://www.cs.cmu.edu/afs/cs.cmu.edu/Web/People/ckaestne/pdf/icse22_toxicity.pdf) Roads and Bridges (https://www.roadsbridges.com/) Sustain Podcast-Episode 51: Working in Public: Nadia Eghbal and her new book about Making and Sustaining Open Source Software (https://podcast.sustainoss.org/guests/nadia) Nadia Asparouhova (Eghbal) Website (https://nadia.xyz/) Digital Safety Snacks by Pen America (https://pen.org/event-series/digital-safety-snacks/) The Opposite of Rape Culture is Nurturance Culture by Nora Samaran (https://norasamaran.com/2016/02/11/the-opposite-of-rape-culture-is-nurturance-culture-2/) Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure by Nadia Eghbal (https://www.fordfoundation.org/work/learning/research-reports/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://press.stripe.com/working-in-public) Betty (https://github.com/leopard-ai/betty) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guests: Courtney Miller and Hongbo Fang.

Episode 138: Ruth Cheesley, the Mautic Project Lead at Acquia, on Building and Growing Open Source Communities

Play Episode Listen Later Sep 16, 2022 39:41

Guest Ruth Cheesley Panelists Richard Littauer | Ben Nickolls | Eriol Fox | 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 excited to have as our guest, Ruth Cheesley, joining us from the UK. She is an open-source advocate and Project Lead for Mautic at Acquia. We invited Ruth on this podcast because we don't seem to have enough talks from people who are part of an actual community of coders. Today, Ruth tells us all about Mautic and her job there as Project Lead, she fills us in on Drupal and Acquia, and a tool they used in managing community health called, Savannah. We'll also hear Ruth's strategy when she helped with governance, why Open Source Friday is so important, she explains how she diversifies the contributor base, and we hear her ten-year vision for Mautic she's working on. Go ahead and download this episode now to learn more! [00:02:38] Ruth explains what Mautic is, how she became the Project Lead and being on the Community Leadership Team at Joomla. [00:04:48] Find out the difference between Joomla, Drupal, Acquia, and Mautic. [00:06:17] From someone that organizes open source communities at his job, Justin asks Ruth what tools she uses, and she tells us about one called, Savannah. [00:08:54] Ruth tells us about what her strategy was when she helped with governance. [00:12:47] Richard wonders if the assessment also applies to Mautic and if Mautic is just the same as every other open source project on the web. [00:16:03] Eriol asks Ruth to tell us some success stories or things that have been tricky between different kinds of functions within the open source. [00:19:14] We learn how Ruth sees her role or the roles of other people who are being paid as being part of a sustainable path for Mautic itself, and how money has a play in the ecosystem as well as attribution. [00:21:59] Ruth explains if Acquia pays for full-time engineers and for traditional coder roles for Mautic, and she tells us about Open Source Friday. [00:24:20] Eriol wonders if there's anything people can go read or listen to around how smaller organizations or individuals can make that kind of contribution sustainable and are there things we can implement. [00:27:09] Ruth tells us about a partner's program they created in Mautic. [00:29:27] How does Ruth manage to diversify the contributor base, given that not everyone has the access or time to do that sort of work? [00:32:01] Ruth shares a ten-year vision with a three-year strategy for Mautic. [00:34:10] Find out where you can follow Ruth online. Quotes [00:09:14] “There wasn't really a community empowerment process to set up workflows and training for people to take on the releases, so the project just sort of slowed down.” [00:32:28] “It's quite tricky during longer term plans when you have lots of businesses that are depending on your software, because what one business thinks the product should do is maybe different to what another business thinks the product should do.” Spotlight [00:35:27] Justin's spotlight is Tour de Source newsletter. [00:35:46] Eriol's spotlight is Fantasy Map Generator. [00:36:20] Ben's spotlight is Roden open source bike design. [00:37:02] Richard's spotlight is Richard Matthews and his Oyster Yachts, and the Royal Naval Tot Club of Antigua & Barbuda. [00:37:46] Ruth's spotlight is Ardour, a tool to compose music. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Ben Nickolls Twitter (https://twitter.com/BenJam?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Justin Dorfman Twitter (https://twitter.com/jdorfman?lang=en) Eriol Fox Twitter (https://twitter.com/EriolDoesDesign) Ruth Cheesley Twitter (https://twitter.com/RCheesley) Ruth Cheesley LinkedIn (https://uk.linkedin.com/in/ruthcheesley) Ruth Cheesley Website (https://www.ruthcheesley.co.uk/) Mautic (https://www.mautic.org/) Joomla (https://www.joomla.org/) Sustain Podcast-Episode 109: Dries Buytaert of Drupal on Balancing Makers and Takers to Scale and Sustain Open Source (https://podcast.sustainoss.org/guests/buytaert) Drupal (https://www.drupal.org/) Mautic Open-Source Marketing Automation Project (Open Collective) (https://opencollective.com/mautic) Savannah (https://www.savannahhq.com/) Mautic Community Manifesto (https://www.mautic.org/blog/community/mautic-community-manifesto) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://press.stripe.com/working-in-public) Google Season of Docs (https://developers.google.com/season-of-docs) Open Source Friday (https://opensourcefriday.com/) Acquia's Drupal Acceleration Team (https://dev.acquia.com/blog/acquias-drupal-acceleration-team) Acquia's response to the Mautic Community Manifesto (https://www.mautic.org/blog/press/acquias-response-to-the-mautic-community-manifesto) Mautic Community Governance Model (https://www.mautic.org/blog/press/mautic-community-governance-model) Response to Community Consultation on the Governance Model Proposal (https://www.mautic.org/blog/press/response-to-community-consultation-on-the-governance-model-proposal) Establishing an incentivised partners programme in an open source project (https://speaking.ruthcheesley.co.uk/uIAJxk/establishing-an-incentivised-partners-programme-in-an-open-source-project) Tour de Source (https://tourdesource.substack.com/) Fantasy Map Generator (https://github.com/Azgaar/Fantasy-Map-Generator) Roden (https://opencollective.com/roden) Oyster Yachts (https://en.wikipedia.org/wiki/Oyster_Yachts) Royal Naval Tot Club of Antigua & Barbuda (http://rntc.club/) Ardour (https://ardour.org/) Ardour-GitHub (https://github.com/Ardour) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Ruth Cheesley.

Episode 133: Sustain and CHAOSS: A Joint Podcast

Play Episode Listen Later Aug 12, 2022 40:46

Panelists Georg Link | Richard Littauer | Dawn Foster | Willem Jiang | Amanda Casari | Ben Nickolls Show Notes 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's episode is a shared podcast between Sustain and CHAOSS. We have six panelists to talk about maintaining open source and we'll also do a quick update from a previous episode and talk about what has changed and what maintaining open source looks like today. The panelists we have are Georg Link, Richard Littauer, Dawn Foster, Willem Jiang, Amanda Casari, and Ben Nickolls. 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:00:38] The six panelists introduce themselves. [00:04:04] Richard details more about what Sustain is, Georg and Dawn explain CHAOSS and what's going on there, and Amanda shares what she likes about CHAOSS. [00:13:15] Dawn talks about the kind of community members CHAOSS has, Willem tells us about the Asia community, and Ben shares his views on the Sustain community. [00:19:22] Georg asks if there's been any updates on the funding situation in open source and if anything has changed there and Ben updates us. [00:22:34] When thinking about resources, who gets paid, how money flows, and how we identify when help is needed, Amanda wonders how that's changed in the last few years in the CHAOSS community. [00:25:09] Richard shares from his angle what he's seen about what has changed in the past two years in open source. [00:27:09] Ben shares his views on the supply chain conversation about who is making money in open source. [00:29:06] Since security is such a hot topic, Georg asks if we're prepared in all the open source projects to really focus on this topic or if we have to upskill everyone, and we hear Ben's thoughts on this. [00:31:02] Richard explains how you can get involved in Sustain happenings that are going on, and Georg and Dawn inform us about some projects, working groups, and other things going on with CHAOSS. [00:39:17] Find out where you can get involved with Sustain and CHAOSS. Spotlight [00:34:21] Georg's pick is meeting with an online local group and doing cool things together. [00:35:06] Richard's pick is going on a super long hike and buying a hydration pack (CamelBak Pouch). [00:35:56] Dawn's spotlight is GraphiQL. [00:36:34] Ben's spotlights are taking care of Swifts on his roof, and the book, Swifts and Us: The Life of the Bird that Sleeps in the Sky. [00:36:55] Amanda's pick is the book, Burnout: The Secret to Unlocking the Stress Cycle. [00:38:03] Willem's pick is ApacheCon Asia 2022. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) Sustain Podcast (https://podcast.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) CHAOSS (https://chaoss.community/) CHAOSS Project Twitter (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) CHAOSS Community Participate (https://chaoss.community/participate/) podcast@chaoss.community (mailto:podcast@chaoss.community) Ford Foundation (https://www.fordfoundation.org/) Georg Link Twitter (https://twitter.com/georglink) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Dawn Foster Twitter (https://twitter.com/geekygirldawn) Willem Jiang Twitter (https://twitter.com/willemjiang) Amanda Casari Twitter (https://twitter.com/amcasari/) Ben Nickolls Twitter (https://twitter.com/BenJam?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Sustain Podcast-Episode 65: CHAOSS and Sustain: A Joint Podcast (https://podcast.sustainoss.org/65) Ecosyste.ms (https://ecosyste.ms/) xkcd (https://xkcd.com/2347/) Executive Order on Improving the Nation's Cybersecurity (The White House) (https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/) Sustain 2021 Event Report (https://sustainoss.org/assets/pdf/Sustain-In-2021-Event-Report.pdf) Mozilla-Open Source Archetypes: A Framework For Purposeful Open Source May 2018 (https://blog.mozilla.org/wp-content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf) SonarQube (https://www.sonarqube.org/) CamelBak Crux 3-Liter Water Reservoir (https://www.amazon.com/CamelBak-Crux-Reservoir-Set-Blue/dp/B01LA5FCJ2/ref=sr_1_2?gclid=Cj0KCQjw_7KXBhCoARIsAPdPTfjbp84atlITCdNAL5gP7kt8BFwPzg9TcouW3yKU019aOaPtTeB5wmkaAmvTEALw_wcB&hvadid=410016279262&hvdev=c&hvlocphy=9010767&hvnetw=g&hvqmt=e&hvrand=9439371394441572640&hvtargid=kwd-324558368114&hydadcr=9380_11541651&keywords=camelbak+pouches&qid=1659732626&sr=8-2) GraphiQL (https://www.gatsbyjs.com/docs/how-to/querying-data/running-queries-with-graphiql/) [Swifts and Us: The Life of the Bird that Sleeps in the Sky by Sarah Gibson](https://www.amazon.com/Swifts-Us-Life-Bird-Sleeps/dp/0008350663/ref=tmmpapswatch0?encoding=UTF8&qid=&sr=) Burnout: The Secret to Unlocking the Stress Cycle by Emily Nagoski, PhD and Amelia Nagoski, DMA (https://www.penguinrandomhouse.com/books/592377/burnout-by-emily-nagoski-phd-and-amelia-nagoski-dma/) ApacheCon Asia 2022 (https://www.apachecon.com/acasia2022/) [Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal](https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862/ref=sr11?crid=XK0VVY8QW60A&keywords=nadia+eghbal&qid=1659813710&sprefix=%2Caps%2C307&sr=8-1)

Episode 62: Maintaining Open Source Projects - a joint episode with the Sustain Podcast

Thoughts in Between: exploring how technology collides with politics, culture and society

Play Episode Listen Later Aug 12, 2022 42:07

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's episode is a shared podcast between Sustain and CHAOSS. We have six panelists to talk about maintaining open source and we'll also do a quick update from a previous episode and talk about what has changed and what maintaining open source looks like today. The panelists we have are Georg Link, Richard Littauer, Dawn Foster, Willem Jiang, Amanda Casari, and Ben Nickolls. 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:19] The six panelists introduce themselves. [00:04:45] Richard details more about what Sustain is, Georg and Dawn explain CHAOSS and what's going on there, and Amanda shares what she likes about CHAOSS. [00:13:56] Dawn talks about the kind of community members CHAOSS has, Willem tells us about the Asia community, and Ben shares his views on the Sustain community. [00:20:04] Georg asks if there's been any updates on the funding situation in open source and if anything has changed there and Ben updates us. [00:24:14] When thinking about resources, who gets paid, how money flows, and how we identify when help is needed, Amanda wonders how that's changed in the last few years in the CHAOSS community. [00:26:34] Richard shares from his angle what he's seen about what has changed in the past two years in open source. [00:28:33] Ben shares his views on the supply chain conversation about who is making money in open source. [00:30:36] Since security is such a hot topic, Georg asks if we're prepared in all the open source projects to really focus on this topic or if we have to upskill everyone, and we hear Ben's thoughts on this. [00:32:27] Richard explains how you can get involved in Sustain happenings that are going on, and Georg and Dawn inform us about some projects, working groups, and other things going on with CHAOSS. [00:40:42] Find out where you can get involved with Sustain and CHAOSS. Spotlights/Value Adds (Picks) of the week: [00:35:46] Georg's pick is meeting with an online local group and doing cool things together. [00:36:31] Richard's pick is going on a super long hike and buying a hydration pack (CamelBak Pouch). [00:37:21] Dawn's spotlight is GraphiQL. [00:37:59] Ben's spotlights are taking care of Swifts on his roof, and the book, Swifts and Us: The Life of the Bird that Sleeps in the Sky. [00:38:21] Amanda's pick is the book, Burnout: The Secret to Unlocking the Stress Cycle. [00:39:29] Willem's pick is ApacheCon Asia 2022. Panelists: Georg Link Richard Littauer Dawn Foster Willem Jiang Amanda Casari Ben Nickolls Sponsor: SustainOSS (https://sustainoss.org/) Links: CHAOSS (https://chaoss.community/) CHAOSS Project Twitter (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) CHAOSS Community Participate (https://chaoss.community/participate/) podcast@chaoss.community (mailto:podcast@chaoss.community) SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) Sustain Podcast (https://podcast.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Ford Foundation (https://www.fordfoundation.org/) Georg Link Twitter (https://twitter.com/georglink) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Dawn Foster Twitter (https://twitter.com/geekygirldawn) Willem Jiang Twitter (https://twitter.com/willemjiang) Amanda Casari Twitter (https://twitter.com/amcasari/) Ben Nickolls Twitter (https://twitter.com/BenJam?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Sustain Podcast-Episode 65: CHAOSS and Sustain: A Joint Podcast (https://podcast.sustainoss.org/65) Ecosyste.ms (https://ecosyste.ms/) xkcd (https://xkcd.com/2347/) Executive Order on Improving the Nation's Cybersecurity (The White House) (https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/) Sustain 2021 Event Report (https://sustainoss.org/assets/pdf/Sustain-In-2021-Event-Report.pdf) Mozilla-Open Source Archetypes: A Framework For Purposeful Open Source May 2018 (https://blog.mozilla.org/wp-content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf) SonarQube (https://www.sonarqube.org/) CamelBak Crux 3-Liter Water Reservoir (https://www.amazon.com/CamelBak-Crux-Reservoir-Set-Blue/dp/B01LA5FCJ2/ref=sr_1_2?gclid=Cj0KCQjw_7KXBhCoARIsAPdPTfjbp84atlITCdNAL5gP7kt8BFwPzg9TcouW3yKU019aOaPtTeB5wmkaAmvTEALw_wcB&hvadid=410016279262&hvdev=c&hvlocphy=9010767&hvnetw=g&hvqmt=e&hvrand=9439371394441572640&hvtargid=kwd-324558368114&hydadcr=9380_11541651&keywords=camelbak+pouches&qid=1659732626&sr=8-2) GraphiQL (https://www.gatsbyjs.com/docs/how-to/querying-data/running-queries-with-graphiql/) [Swifts and Us: The Life of the Bird that Sleeps in the Sky by Sarah Gibson](https://www.amazon.com/Swifts-Us-Life-Bird-Sleeps/dp/0008350663/ref=tmmpapswatch0?encoding=UTF8&qid=&sr=) Burnout: The Secret to Unlocking the Stress Cycle by Emily Nagoski, PhD and Amelia Nagoski, DMA (https://www.penguinrandomhouse.com/books/592377/burnout-by-emily-nagoski-phd-and-amelia-nagoski-dma/) ApacheCon Asia 2022 (https://www.apachecon.com/acasia2022/) [Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal](https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862/ref=sr11?crid=XK0VVY8QW60A&keywords=nadia+eghbal&qid=1659813710&sprefix=%2Caps%2C307&sr=8-1) Special Guests: Amanda Casari, Benjamin Nickolls, Richard Littauer, and Willem Jiang.

Nadia Asparouhova: Future Of Philanthropy, Science Funding, Creator Economy, Family Stories and Independent Research.

Ben Yeoh Chats

Play Episode Listen Later Jun 11, 2022 63:36

Nadia Asparouhova (previously writing under Nadia Eghbal) is an independent researcher with widely read essays on a range of topics most recently philanthropic funding including effective altruism and ideas machines, and recent ideas in funding science. She's written books about the open source community. She has worked in start ups and venture. She set up and ran Helium grants, a microgrant programme. She is an Emergent Ventures fellow. We speak about what she learned from microgranting and reviewing thousands of applications. We discuss what she thinks about EA influenced philanthropy, and why she is personally pro-pluralism. Nadia talks about why doesn't consider herself a creator and the downsides and upsides on he creator economy as currently formed. We discuss parallels with the open source community. We chat about Nadia's work as an independent researcher versus her work at start-ups and how they are fulfilling in different ways. Nadia examines what faith means to her now. We chat on the importance of intuition and the messiness of creative science and learning. We talk about science funding and how we might be the cusp of something new. Nadia expresses optimism about the future as we discuss possible progress stagnation. On a more personal note, we chat about how Nadia was a vegetarian and how and why she changed her mind. But also that she could not be a complete only carnivore either. We discuss the importance of family stories that shape us and the role the stories of her grandmother played in her life. We play over-rated under-rated: -Effective Altruism -Miami -Crowdfunding -Toulouse -Newsletters -Katy Perry Nadia talks briefly about a seed of an idea around anti-memetics. Nadia ends with her advice to others. Follow your curiosities. Transcript is available here. How are crypto billionaires most likely to change charitable giving Effective Altruism (EA) aside? “Broadly my worldview or thesis around how we think about philanthropy is that it moves in these sorts of wealth generations. And so, right now we're kind of seeing the dawn of the people who made a lot of money in the 2010s with startups. It's the “ trad tech” or startup kind of cohort. Before then you had people who made a lot of money in investment banking and finance and the early tech pioneers, they all formed their own cohort. And then you might say crypto is the next generation after that, which will eventually break down into smaller sub components for sure but we don't really know what those things are yet, I think, because crypto is still so early and they've sort of made money in their own way. ...When you have a group of people that have made money in a certain way that is almost by definition it's because it's a new wealth boom. They made their money in a way that's distinctly different from previous generations. And so, that becomes sort of like a defining theory of change or worldview. All the work that they are doing in this sort of philanthropic sense is finding a way to impose that worldview. …what will crypto's contribution to that be? ...I think in the crypto kind of generation you might see instead of thinking about the power of top talent, I think they're more about giving people tools to kind of build their own worlds..."

research creator economy independent ea philanthropy helium family stories nadia eghbal science funding effective altruism ea

Nadia Eghbal: Silicon Valley and the future of philanthropy

Play Episode Listen Later Mar 21, 2022 56:00

Nadia Eghbal is an independent researcher and writer. She's the author of Working in Public, which is an ethnographic study of how Open Source Software is made and maintained. She recently won an Emergent Ventures grant to study and write about technology wealth and philanthropy. In this conversation, we discussed how and why technology entrepreneurs think differently about philanthropy, what this means for the funding of science, how crypto is changing this space, and much more. Enjoy this conversation with Nadia Eghbal.-----------------Thanks to Cofruition for consulting on and producing the show. You can learn more about Entrepreneur First at www.joinef.com and subscribe to my weekly newsletter at tib.matthewclifford.com

business ai technology entrepreneur tech innovation public silicon valley philanthropy open source software entrepreneur first nadia eghbal

#33 - Nadia Eghbal

LABOSSIERE PODCAST

Play Episode Listen Later Jan 20, 2022 28:28

Nadia Eghbal is trying to understand how people work. She's a writer and researcher interested in infrastructure, governance, and the economics of the internet. Her latest book, Working in Public: The Making and Maintenance of Open Source Software, is about open source developers and what they tell us about the evolution of our online social spaces.Nadia interviewed hundreds of developers while working to improve their experience at GitHub, and argues that open source code is a form of public infrastructure. It requires maintenance, and that offers us a model through which to understand the challenges faced by online creators on all platforms.She's now deep in research mode, exploring a new topic about philanthropy and the 2010s tech wealth boom.She spent the last few years trying to understand parasocial communities and reputation-based economies, which she first explored as an independent researcher at Protocol Labs. Those ideas were put into practice when she joined Substack, where she worked until recently.

substack maintenance github open source software protocol labs nadia eghbal

Episode 50: Recognizing all Kinds of Labor in Open Source Ecosystems with Amanda, Katie, and John

substack nih unsolicited marginal revolution nadia eghbal

Play Episode Listen Later Jan 14, 2022 45:54

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 have three amazing guests with us, Amanda Casari, Katie McLaughlin, and John Meluso. Amanda is a Developer Relations Engineer and researcher at Google at the Open Source Programs Office, Katie is a Developer Relations Engineer at Google, and John is the OCEAN Postdoctoral Fellow at the University of Vermont. They are with us to talk about Project OCEAN (Open-Source Complex Ecosystems And Networks), how it came to be, where it is now, and what they hope to accomplish going forward. We also learn more about what they see as an open source ecosystem, and they go in depth about contributions and taxonomy. 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:44] John, Amanda, and Katie tell us their backgrounds and how they got involved in open source. [00:07:23] We learn more about OCEAN, how it came to be, and where it's at now. [00:11:25] Amanda and John explain a bit more about ecosystems. [00:15:52] Georg wonders what they have realized early on or over time that they want to make sure everyone who looks at open source takes away from their work. [00:19:59] Amanda brings up a question to the panelists concerning the idea of atomic information around software projects and balancing how much do they keep with a repo versus how do you allow for information to be distributed in many places that many people work, but it doesn't get lost and you don't lose somebody's attribution for the work they do. [00:28:58] Georg brings up the Types of Contributions metrics link CHAOSS uses that helps show how people can contribute to open source, and Katie shares her thoughts on it. [00:32:13] Sophie talks about “Which contributions count? Analysis of attribution in open source” report and what this research explores. John explains how they balance things by varying the kinds of methodologies they use. [00:38:49] Find out where you can follow Amanda, Katie, and John online. Value Adds (Picks) of the week: [00:39:45] Georg's pick is LifeTime wellness and fitness center. [00:40:31] Matt's pick is places to visit in Colorado: Rocky Mtn. National Park, Great Sand Dunes, and Gunnison National Park. [00:41:08] Sophia's pick is emergent property. [00:41:57] Amanda's pick is trading Vermont Golden Dome books with her oldest child. [00:43:10] Katie's pick is the book, CPython Internals by Anthony Shaw. [00:44:03] John's pick is the book, Data Feminism by Catherine D'Ignazio and Lauren F. Klein. Request from our Guests: Open Source Folks: Take (and share!) this anonymous survey about receiving credit for tasks in open source! Conducted by researchers at the University of Vermont in partnership with Google Open Source. [https://qualtrics.uvm.edu/jfe/form/SV_1zUs19oVcZJ0SPA](https://qualtrics.uvm.edu/jfe/form/SV_1zUs19oVcZJ0SPA) Panelists: Georg Link Sophia Vargas Matt Germonprez Guests: Amanda Casari Katie McLaughlin John Meluso Sponsor: SustainOSS (https://sustainoss.org/) 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) Project OCEAN (https://vermontcomplexsystems.org/partner/OCEAN/) Amanda Casari Twitter (https://twitter.com/amcasari?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Open Source Stories-Amanda Casari Website (https://www.opensourcestories.org/) Amanda Casari Linkedin (https://www.linkedin.com/in/amcasari/) Katie McLaughlin Twitter (https://twitter.com/glasnt) Katie McLaughlin Website (https://glasnt.com/) John Meluso Twitter (https://twitter.com/johnmeluso) John Meluso Linkedin (https://www.linkedin.com/in/jmeluso/) John Meluso, PhD Website (https://www.johnmeluso.com/) John Meluso Email (mailto:john.meluso@uvm.edu) ACROSS Taxonomy-GitHub (https://github.com/google/across) CHAOSS Types of Contributions metrics (https://chaoss.community/metric-types-of-contributions/) Which contributions count? Analysis of attribution in open source-Jean-Gabriel Young, Amanda Casari, Katie McLaughlin, Milo Z. Trujillo, Laurent Hébert-Dufresne, James P. Bagrow (https://arxiv.org/abs/2103.11007) Open source ecosystems need equitable credit across contributions-Amanda Casari, Katie McLaughlin, Milo Z. Trujillo, Jean-Gabriel young, James P. Bagrow, & Laurent Hébert-Dufresne (https://www.nature.com/articles/s43588-020-00011-w) Nadia Eghbal Website (https://nadiaeghbal.com/) Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure by Nadia Eghbal (https://www.fordfoundation.org/work/learning/research-reports/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862) A Place to Hang Your Hat- Leslie Hawthorn's Hat Rack blog post (https://hawthornlandings.org/2015/02/13/a-place-to-hang-your-hat/) Octohatrack-GitHub (https://github.com/LABHR/octohatrack) A tool for tracking non-code GitHub contributions-Katie McLaughlin (https://opensource.com/life/15/10/octohat-github-non-code-contribution-tracker) Recognize All Contributors (https://allcontributors.org/) CHAOSScast Podcast- Episode 39: Leaderboards and Metrics at Drupal.org with Matthew Tift and Tim Lehnen (https://podcast.chaoss.community/39) LifeTime (https://www.lifetime.life/) Rocky Mountain National Park (https://www.nps.gov/romo/index.htm) Great Sand Dunes (https://www.nps.gov/grsa/index.htm) Black Canyon Of The Gunnison (https://www.nps.gov/blca/index.htm) What Are Emergent Properties? (https://sciencing.com/emergent-properties-8232868.html) Vermont Golden Dome Books (https://libraries.vermont.gov/services/children_and_teens/book_awards/vtgdba) CPython Internals by Andrew Shaw (https://realpython.com/products/cpython-internals-book/) Data Feminism by Catherine D'Ignazio (https://www.amazon.com/Feminism-Strong-Ideas-Catherine-DIgnazio/dp/0262044005/) Special Guests: Amanda Casari, John Meluso, and Katie McLaughlin.

Apply For An ACX Grant

Slate Star Codex Podcast

Play Episode Listen Later Nov 12, 2021 9:08

https://astralcodexten.substack.com/p/apply-for-an-acx-grant What is ACX Grants? I want to give grants to good research and good projects with a minimum of paperwork. Like an NIH grant or something, only a lot less money and prestige. How is this different from Marginal Revolution's Fast Grants, Nadia Eghbal's Helium Grants, or EA Funds' grant rounds? Not different at all. It's total 100% plagiarism of them. I'm doing it anyway because I think it's a good idea, and I predict there are a lot of good people with good projects in this community who haven't heard about / participated in those, but who will participate when I do it. How much money are you giving out? ACX Grants proper will involve $250,000 of my own money, but I'm hoping to supplement with much more of other people's money, amount to be determined. See the sections on ACX Grants + and ACX Grants ++ below. Why do you have $250,000 to spend on grants? Unsolicited gifts from rich patrons, your generosity in subscribing to my Substack, and the second item here.

Episode 97: Anthony Ronda and the League of Extraordinary Foundry VTT Developers, games, and Open Source

Play Episode Listen Later Nov 12, 2021 34:40

Guest Anthony Ronda Panelists Richard Littauer | Eric Berry | Ben Nickolls | Eriol Fox Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Today, we have an amazing guest, Anthony Ronda, who is one of the leaders in the League of Extraordinary Foundry VTT Developers. Foundry Virtual Tabletop is a standalone application built for experiencing multiplayer tabletop RPGs, which helps you play games like Dungeons and Dragons and other games virtually. Anthony fills us in on the history of the League, the background of Foundry, and the open source module that was created. He also tells us about a really cool game he made, how he found it easier to make friends through the league, more about the Open Game License, and advice on how you can get started in this community. Go ahead and download this episode to find out more cool stuff! [00:01:40] Anthony explains Virtual Tabletop (VTT) and gives us the history and background of the League. [00:03:53] We find out the background of Foundry and how it's geared more towards Dungeons & Dragons and tabletop role-playing games, and Anthony tells us how the adoption has been over the past couple of years. [00:07:29] In talking about the API developer community, we learn how this relates to open source and what type of contributions exist. Anthony mentions a book by Nadia Eghbal that helped him make sense of what was going on, especially with making sure games run smoothly. [00:11:15] Anthony tells us about a cool game he made in Foundry. [00:14:30] The topic is gaming communities and Richard is curious to know more about Wizards of the Coast and what their involvement is with open source and Anthony explains how his league is doing newer novel things. He also explains the Open Game License. [00:19:05] Anthony shares his thoughts on the barriers to entry. [00:21:32] We learn from Anthony how he found it easier to make friends through the league than other open source communities. [00:22:47] We find out how many people in the open source gaming community are there on behalf of their company. [00:25:17] Anthony tells us how you can get started in this community. [00:29:24] Find out where you can follow Anthony online. Quotes [00:15:09] “First off, rules aren't protectable by copyright. However, a specific implementation of rules into texts are protected by our copyright.” [00:15:33] “Being a market leader doesn't necessarily mean that you're the best game, but it's the game that everyone knows the rules too.” [00:17:47] “You can at least see the correlation if not show causation, that open licensing allows your game to be more popular and go everywhere.” Spotlight [00:30:20] Eric's spotlight is an open source project called Voxelmade. [00:30:55] Ben's spotlight is an open source astronomy tool called Stellarium. [00:31:27] Eriol's spotlight is The Homebrewery, to turn pages into parchment and Dungeons & Dragons formatting. [00:32:19] Richard's spotlight is the computer game Commander Keen. Also, if you know John Carmack, who is one of the creators of this game, please let him know we are very interested to have him on this podcast! ☺ [00:32:57] Anthony's spotlight is Codidact. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) Anthony Ronda Twitter (https://twitter.com/nthonyronda) Anthony Ronda-GitHub (https://github.com/anthonyronda/) Foundry Virtual Tabletop (https://foundryvtt.com/) Foundry VTT Twitter (https://twitter.com/FoundryVTT) Foundry Virtual Tabletop YouTube (https://www.youtube.com/foundrynet) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862) Open Game License (https://en.wikipedia.org/wiki/Open_Game_License) Awesome OGL Projects-Anthony Ronda-GitHub (https://github.com/anthonyronda/awesome-ogl) Voxelmade (https://voxelmade.com/) Stellarium (https://stellarium.org/) The Homebrewery (https://homebrewery.naturalcrit.com/) Commander Keen (https://en.wikipedia.org/wiki/Commander_Keen) Codidact (https://codidact.org/) Special Guests: Anthony Ronda and Benjamin Nickolls.

Episode 92: Niels ten Oever on Human Rights, Open Source, and Digital Infrastructure

Play Episode Listen Later Sep 24, 2021 41:52

Guest Niels ten Oever Panelists Eric Berry | Justin Dorfman | Richard Littauer Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Our guest today is Niels ten Oever, who is a Postdoctoral Researcher at the University of Amsterdam, and recently published a really interesting report from the Ford Foundation on “Human Rights Are Not A Bug: Upgrading Governance for an Equitable Internet,” which we will learn more about. Today, Niels shares his thoughts on what the internet is, what human rights are, and how to make sure that we all work in the open. Niels tells us about the idea he had to build this powerful tool for the people in Ethiopia and what happened with that. He explains how he got interested in Internet Governance, his thoughts on 5G, working with the Guardian Project to develop the StoryMaker app, and more about his PhD report called, “Wired Norms.” Niels also shares great advice for open source developers on what they can do to make the world a better place. Download this episode now to hear so much more from Niels. [00:01:41] Niels tells us how he got into being a developer and working in open source, and tells us about working with the Guardian Project to develop the StoryMaker app. [00:04:25] Niels explains how he came up with this idea to build this powerful tool for the people in Ethiopia. He talks about his involvement with Tactical Tech and more about the report he wrote for the Ford Foundation on “Human Rights Are Not A Bug: Upgrading Governance for an Equitable Internet” and he goes in depth about infrastructural norm of interconnection.” [00:16:23] Since Niels is someone who is an open source developer and has worked with open tools, Richard asks him how he views the intersection between large unseen infrastructure, human rights, and open source as this whole idea of everything should be able to be used by anyone else and how does that work with him with the idea of privacy. [00:20:56] Niels talks about an article that he did along with Mallory Knodel, that the New York Times printed called, ‘Master,' ‘Slave' and the Fight over Offensive Terms in Computing. [00:26:06] Richard is curious to know how Niels personally chooses what level of the stack to approach to figure out how to be a better person. Niels shares his thoughts and advice for open source developers on what they can do to make the world a better place. He mentions Cloudflare as a company that has adopted a Human Rights Policy. [00:31:58] We find out from Niels about writing his PhD report called “Wired Norms,” why he came out with it, and the best part of it. [00:36:12] Find out where you can follow Niels online and learn more about things that he's writing. [00:36:27] Justin brings one final point about how Niels writes a lot of papers on 5G and how in America there a certain people that have this conspiracy theory that 5G is not secure, and since Niels works very closely in that community, he shares his thoughts. Quotes [00:03:18] “Then we develop different distros for the different parts of the radio station that have been in use ever since.” [00:03:52] “So we tend to think that you need the really fancy computers to do things, but Linux actually allowed me to reuse so much of the hardware and software there to enable freedom of expression.” [00:05:38] “I had also studied a year in Berlin and one of the quotes on top of the Humboldt University directly when you entered is in German and it means “Philosophers have always interpreted the world differently, but what really matters is to change it.” And that's what I actually wanted to do. I didn't want to be an armchair philosopher.” [00:08:42] “And then I thought like hey, but all these smartphones people carry around, they have as much computing power as my Linux boxes. Why don't we actually do editing on that?” [00:09:51] “So then I got really involved with technical tech and other organizations working on digital security issues, but also found out that like teaching people who were under the most stressful situation of their lives to do something else added on top and that the best possible outcome of that behavior is nothing happens is almost like the worst premise for behavior change.” [00:10:30] “So, then I started wondering, why don't we address this in the infrastructure itself?” [00:11:03] “So, that really confused me because my whole premise, freedom of expression plus access to information equals social change, clearly wasn't true.” [00:13:09] “What is so interesting about the internet, which consist of more than 70,000 independent networks, lots of different devices from different manufacturers, lots of networking stacks, operating systems, that are all working together, that is possible through what I call “infrastructural norm of interconnection.” [00:14:49] “But this is the nature of infrastructure, it hides itself, it only shows what it breaks.” [00:17:47] “But, as open source developers know, the most central part in this are actually people.” [00:18:35] “But, unfortunately, as the excellent researcher Corinne Cath shows, is that many of these governance bodies, such as the internet engineering task force, there is a total monoculture that is actually very resistant to change.” [00:19:09] “And there is nothing inherently wrong with that, but it is wrong if they set the rules for a global internet.” [00:20:56] “Together with Mallory Knodel, officer at the Center for Democracy and Technology, I made a really simple internet draft to request people to stop using “master,” “slave” and “blacklist”, “whitelist,” and that ended up being a huge route which ended up in the New York Times.” [00:23:22] “But what's the most important part I think is that it's never done, your human rights are like muscles, you need to keep training them or else you lose them.” [00:24:10] “If your code is used for a bad thing, that doesn't make you a bad person, but it makes you a bad person if you don't do anything about it and if you don't relate to that.” [00:24:37] “Our actions have consequences and people who work with computers have a disproportional impact on society.” [00:27:20] “Try to make the things a bit better, try to document your code better, try having discussions, try having people who are not just all CS white dudes on the developing team, but really do your best to bring more people in.” [00:28:43] “So, I do a lot of martial arts and I really enjoy it. And so, the first time you get punched in the face, you feel almost like insulted, right, like whoa, what, can you do this?” [00:29:35] “And I think that's what open source software is and can be really good for because we can fork, we can change, we can make iterative changes, discuss them in our meetings.” [00:30:41] “So like it's just another sign that says, “Club, need to comply to our methods, our tools, to be able to partake in this.” Spotlight [00:38:22] Eric's spotlight is news that he just heard that Nadia Eghbal got engaged! [00:38:52] Justin's spotlight is cosign, a container signing, verification storage application. [00:39:23] Richard's spotlight is Der Kleine Hobbit (The Hobbit in German) by J.R.R. Tolkien. [00:39:55] Niels spotlights are** **organizations that are active in Internet Governance: ARTICLE19 and the Center for Democracy and Technology. Also, great researchers such as Corinne Cath, and great pieces of software such as the Python community and Debian. He is also working on building 5G networks and has the Ettus B210. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) Niels ten Oever Twitter (https://twitter.com/nielstenoever?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Niels ten Oever Website (https://nielstenoever.net/) “Human Rights Are Not A Bug: Upgrading Governance for an Equitable Internet” by Niels ten Oever (https://www.fordfoundation.org/work/learning/research-reports/human-rights-are-not-a-bug-upgrading-governance-for-an-equitable-internet/) Wired Norms: Inscription, resistance, and subversion in the governance of the internet infrastructure by Niels ten Oever (https://nielstenoever.net/wp-content/uploads/2020/09/WiredNorms-NielstenOever.pdf) ‘Master,' ‘Slave' and the Fight Over Offensive Terms in Computing-New York Times (https://www.nytimes.com/2021/04/13/technology/racist-computer-engineering-terms-ietf.html) Guardian Project-StoryMaker (https://dev.guardianproject.info/projects/wrapp/) Tactical Tech (https://tacticaltech.org/) Dr. Corinne Cath-Speth Website (https://corinnecath.com/) Qalb (programming language) (https://en.wikipedia.org/wiki/Qalb_(programming_language)) Cloudflare-Human Rights Policy (https://www.cloudflare.com/resources/images/slt3lc6tev37/fdLHB1OGp8ZWwzCTVlM0n/e0a42a032592ded778bda8c31c6747b1/BDES-2133_Impact-Week-Human-Rights-Policy.pdf) ARTICLE19 (https://www.article19.org/) Python Software Foundation (https://www.python.org/psf/) Ettus-USRP B210 (https://www.ettus.com/all-products/ub210-kit/) Debian (https://www.debian.org/) Nadia Eghbal Twitter (https://twitter.com/nayafia?lang=en) cosign-GitHub (https://github.com/sigstore/cosign) [Der Klein Hobbit (The Hobbit in German) by J.R. Tolkien](https://www.amazon.com/Kleine-Hobbit-German-dp-0828811938/dp/0828811938/ref=mtother?encoding=UTF8&me=&qid=) [Harry Potter y la Piedra filosofal (Harry Potter and the Sorcerer's Stone in Spanish) by J.K. Rowling](https://www.amazon.com/Harry-Potter-piedra-filosofal-Sorcerers-Spanish/dp/1644732076/ref=sr11?dchild=1&keywords=harry+potter+in+spanish&qid=1629927272&s=books&sr=1-1) Center for Democracy & Technology (https://cdt.org/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Niels ten Oever.

Episode 85: Geoffrey Huntley and Sustaining OSS with Gitpod

head online passion entrepreneurship economy creators substack github parallels software development open source software nadia eghbal

Play Episode Listen Later Jul 16, 2021 45:44

Guest Geoffrey Huntley Panelists Eric Berry | Richard Littauer Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. We are super excited to be going “down under” with our guest today, Geoff Huntley, who works at Gitpod as part of a team that focuses on community and he works with the engineering team. He is also a long-time open source developer advocate, and general coder dude from Australia. We learn from Geoff how he got started in coding, how he loves to teach people coming into the field, and the importance of turning up, sticking around, and helping out in this industry. He tells us all about Gitpod, what he does there, why more people are adopting it, what beer money does for maintainers, and how he's using Gitpod to try to solve the problem of maintainers sustainability. Also, Geoff shares some awesome advice to help the sustainers out there, and his advice on how to use money, which you really need to hear! Download this episode now to find out much more from Geoff #vanlife! [00:01:45] Geoff tells us about the van he lives in and the project he maintains called ReactiveUI. [00:02:50] We learn how Geoff got started with coding and how he ended up willing to take over an open source project that takes a lot of maintenance. [00:06:00] Richard asks Geoff to talk about the amount of maintainers out there and any opinions he has about the engineering code versus the maintainer parable he just mentioned. [00:08:49] We learn more about Gitpod from Geoff. [00:10:49] Eric asks why people are adopting Gitpod, what makes that different between that and Codespaces, and Geoff tells us what the response has been so far. [00:14:40] Geoff talks about how he's using Gitpod to try to solve this problem of maintainers sustainability, and how it goes back to Nadia Eghbal with her Roads and Bridges and the pivotal work she did with the Ford Foundation. [00:17:43] Eric wonders what Geoff thinks that beer money does for the maintainers, and when he was talking to the guys, what kind of response was he getting. [00:21:18] Geoff tells us how many people were involved in the distribution and if he was able to bring in more community members to help decide where those funds were allocated. [00:23:13] We find out the background of the team at Gitpod, and what Geoff does there. [00:25:12] Richard wonders how Geoff is structuring partnerships and how is he making it easier for developers to know about the whole suite of tools that are at their disposal to try and get not just beer money, but sticker money, backer money, and eventually, hopefully things like UBI coming out of code. [00:26:46] Geoff shares his knowledge to the sustainers out there and that can help others. [00:33:00] Eric and Richard share their thoughts on what the next five years is going to be. [00:39:24] Geoff leaves us with a final thought on, “How to use money?” We also find out where you can find him online. Quotes [00:03:27] “Well, it was for personal development and learning. I found at the company I didn't really have a mentor as such, and I found in open source there is an unlimited supply of learning if you just turn up and say, “How can I help?” [00:04:12] “No other industry has that opportunity if you just do the one simple thing of just turning up, sticking around, and helping out.” [00:04:36] “So these are common problems in open source. We have a lot of focus on the code, but there's so many different ways people can contribute to open source even if you still don't understand the code base.” [00:07:22] “So, one thing to always remember is problems can be fixed, we'll pull requests. Open source software is as is.” [00:16:03] “Now, one of the things we've found in that is it's still too hard to give projects money.” [00:18:56] “People are very excited just to even know that you're using their software and how it's getting value.” [00:39:31] “I suppose I'd leave to everyone to think about when you do have money and beer money is coming in, consider maybe not paying your developers.” [00:40:12] “So, use your funds to bring yourself joy. Think about all the things you do as an open source maintainer and the things that don't bring you joy, that's what the funds should be used to do.” Spotlight [00:42:22] Eric's spotlights are github1s and GitHub Web IDE. [00:43:31] Richard's spotlight is the Vermont Commission on Native American Affairs. [00:44:30] Geoff's spotlight is the open source project pre-commit. Links Geoffrey Huntley Twitter (https://twitter.com/geoffreyhuntley) Geoffrey Huntley Linkedin (https://www.linkedin.com/in/geoffreyhuntley) Geoffrey Huntley Website (https://ghuntley.com/) Gitpod (https://www.gitpod.io/) Iron Ring (https://en.wikipedia.org/wiki/Iron_Ring) Open Source Maintainers on GitHub (https://github.com/maintainers) GitHub-open source (https://github.com/open-source) Geoff Huntley's personal monorepo-GitHub (https://github.com/ghuntley/ghuntley) Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure by Nadia Eghbal (Ford Foundation) (https://www.fordfoundation.org/work/learning/research-reports/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/) DevX Conf (https://devxconf.org/opensource) “DevX Conf wrap & distributing $10k of open-source funding” by Geoffrey Huntley and Christin Frohne (https://www.gitpod.io/blog/devxconf-wrap) Gitpod chat (https://gitpod.io/chat) Geoff Huntley Gitpod chat (https://discord.com/invite/ZZ8wxgHtc6) “Gitpod Open-Source Sustainability Fund” by Geoffrey Huntley (https://www.gitpod.io/blog/gitpod-open-source-sustainability-fund/) github1s (https://github.com/conwnet/github1s) GitHub Web IDE (https://github.com/zvizvi/Github-Web-IDE) Vermont Commission on Native American Affairs (https://vcnaa.vermont.gov/) pre-commit (https://github.com/pre-commit/pre-commit) Russell Keith-Magee-“If you're relying on open-source software for your business”-YouTube (https://www.youtube.com/watch?v=0t85TyH-h04) Sustain Podcast-Episode 50-Gitcoin, Quadratic Funding, and how Crypto can sustain Open Source with Kevin Owocki (https://podcast.sustainoss.org/50) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Geoffrey Huntley.

australia open crypto geoff quotes bridges roads edited spotlight open source sustaining github sustain geoffrey ubi ford foundation huntley bahr paul m eric berry gitcoin kevin owocki codespaces nadia eghbal native american affairs

#217 Use your cloud SSD for fast, cross-process caching

Python Bytes

Play Episode Listen Later Jan 19, 2021 38:38

Sponsored by Linode! pythonbytes.fm/linode Special guest: Ogi Moore Watch the live stream on YouTube. Michael #1: diskcache via Ian Maurer Python disk-backed cache (Django-compatible). Faster than Redis and Memcached. Pure-Python. The cloud-based computing of 2020 puts a premium on memory. Gigabytes of empty space is left on disks as processes vie for memory. Among these processes is Memcached (and sometimes Redis) which is used as a cache. Wouldn't it be nice to leverage empty disk space for caching? Features: Pure-Python Fully Documented Benchmark comparisons (alternatives, Django cache backends) 100% test coverage Hours of stress testing Performance matters Django compatible API Thread-safe and process-safe Supports multiple eviction policies (LRU and LFU included) Keys support "tag" metadata and eviction Developed on Python 3.8 Tested on CPython 3.5, 3.6, 3.7, 3.8 Tested on Linux, Mac OS X, and Windows Tested using Travis CI and AppVeyor CI Brian #2: TOML is 1.0.0 now. What does that mean for Python? Hopefully, some kind of toml parser will make it into Python core. Any Python access to 1.0.0? Mixed Implementations and TOML version support page lists: pytomlpp supports 1.0.0-rc.3, which is a wrapper around C++ tomlplusplus, which does support 1.0.0. Confusing tomlkit supports 1.0.0-rc.1, so that’s promising toml supports 0.5.0, great name. It’d be cool if it would support 1.0.0 What’s different between 0.5.0 and 1.0.0? Unless I’m mistaken, not much: CHANGELOG 1.0.0-rc1 Leading zeroes in exponent parts of floats are permitted. Allow raw tab characters in basic strings and multi-line basic strings. Allow heterogenous values in arrays. Other than that, lots of “Clarify …”, which I’m not sure how those all affect implementation. I’d love to hear more from people who know more about this Ogi #3: pyqtgraph pyqtgraph - plotting library, for when you need fast/interactive plots Uses qt5 (and soon qt6) bindings to generate plots within Qt applications Fills a niche role, want easy mouse interactivity, running locally on a machine Often used in engineering/scientific applications when looking at a lot of data, and wanting interactivity Michael #4: Parler + Python = Insurrection in public via Jim Kring and Mark Little According to Wikipedia: Parler (/ˈpɑːrlər/) is an American alt-tech microblogging and social networking service. Parler has a significant user base of Donald Trump supporters, conservatives, conspiracy theorists, and right-wing extremists. ArsTechnica article send in by Mark Little Ars: Parler’s amateur coding could come back to haunt Capitol Hill rioters Coding mess A key reason for her success: Parler’s site was a mess. Its public API used no authentication. When users deleted their posts, the site failed to remove the content and instead only added a delete flag to it. Oh, and each post carried a numerical ID that was incremented from the ID of the most recently published one. Another amateur mistake was Parler’s failure to scrub geolocations from images and videos posted online. Some 80 terabytes of posts, 1M videos, many already deleted, preserved for posterity. Catalog and Python pointed out by Shaun King. See the catalog (maybe, it’s the ugly side of people). The gist: https://gist.github.com/kylemcdonald/d8884da1a82ef50754ee49e0b6561071 Partially back online with Russian hosting service? Brian #5: Best-of Web Development with Python Suggested by Douglas Nichols Cool list with nice icons Covers Frameworks, HTTP Clients, Servers Auth tools, HTML Processing, URL utilities OpenAPI, GraphQL, Websocket RPC, Serverless, Content Management Web Testing, Web Forms, Markdown Third-party APIs Email, Web Scraping & Crawling, Monitoring Admin UI API Proxies Flask/FastAPI/Pyramid/Django Utilities Nice to see lots of FastAPI projects: fastapi-sqlalchemy - Adds simple SQLAlchemy support to FastAPI. fastapi-plugins - FastAPI framework plugins. fastapi_contrib - Opinionated set of utilities on top of FastAPI. starlette_exporter - Prometheus exporter for Starlette and FastAPI. fastapi-utils - Reusable utilities for FastAPI. fastapi-code-generator - This code generator creates FastAPI app from an.. slowapi - A rate limiter for Starlette and FastAPI. fastapi-versioning - api versioning for fastapi web applications. fastapi-react - Cookiecutter Template for FastAPI + React Projects. Using.. fastapi_cache - FastAPI simple cache. Ogi #6: Assorted Pyjion - https://github.com/tonybaloney/Pyjion a JIT extension for CPython that compiles python code using .NET 5 CLR CuPy - NumPy compatible multi-dimensional array on CUDA, uses _``*array_function_* (enabled with numpy 1.17) code using numpy to operate directly on CuPy arrays see NEP-18 and CuPy docs compatible with other libraries as well Extras: Michael: Trying Firefox + Brave + VPN Python Web Conf 2021 call for talks, due Jan 29, I’ll be speaking! PyCon US 2021 launched call for proposals: December 22, 2020 — Call for proposals opened February 12, 2021 — Proposals are due March 16, 2021 — Notifications will be sent to presenters March 23, 2021 — Deadline for speakers to confirm participation March 30, 2021 — Schedule is publicly released April 28, 2021 — Deadline to submit pre-recorded presentation (tutorials will be live) May 12-13, 2021 — Tutorial days May 15-16, 2021 — Conference days Apple launching Racial Equity and Justice Initiatives with partners across a broad range of industries and backgrounds — from students to teachers, developers to entrepreneurs, and community organizers to justice advocates Brian: PyCascades 2021 schedule https://2021.pycascades.com/program/schedule/ Ogi: Anthony Explains Video Series Learn X in Y minutes Reading Working in Public by Nadia Eghbal - provides some sanity checks for existing maintainers, might be a fantastic perspective for new contributors to open source Joke Tech Support, 2x Working at the help desk? Get the theme song: Here to help song And help by chat: "Running a successful open source project is just Good Will Hunting in reverse, where you start out as a respected genius and end up being a janitor who gets into fights." - Byrne Hobart

american donald trump apple science education running news reading performance cross russian public conference keys web software cloud id wikipedia windows mixed developers joke programming deadline capitol hill covers monitoring tested api parler open source coding python confusing data science tutorials developed adds thread linux proposals prometheus apis screenshots frameworks extras fills clarify benchmark cloud computing catalog django ide servers good will hunting ars notifications crawling partially racial equity qt software developers web development reusable serverless tech support assorted opinionated auth shaun king ars technica graphql mac os x nep markdown cuda redis jit gigabytes content management caching rpc implementations mark little clr changelog justice initiative linode websockets open api ogi tom l travis ci pycharm memcached starlette nadia eghbal cpython sqlalchemy python3 pycascades

#21 — Nadia Eghbal on the parallels between open-source software development and online creators

Means of Creation

Play Episode Listen Later Dec 15, 2020 52:16

This week on Means of Creation, we talked to Nadia Eghbal! Nadia’s work has focused on the reputation-based economies that drive creator and open-source developer communities. She currently is the Head of Writer Experience at Substack and previously helped build open-source developer experiences (independently and at GitHub).

Nadia Eghbal: The Making and Maintenance of our Open Source Infrastructure

Long Now: Seminars About Long-term Thinking

Play Episode Listen Later Nov 18, 2020 70:05

Tune in at 5:00pm PT on 11/17/20 to watch the public live stream of this talk on YouTube, Facebook, Twitter or Long Now Live. Nadia Eghbal is particularly interested in infrastructure, governance, and the economics of the internet - and how the dynamics of these subjects play out in software, online communities and generally living life online. Eghbal, who interviewed hundreds of developers while working to improve their experience at GitHub, argues that modern open source offers us a model through which to understand the challenges faced by online creators. Her new book, Working in Public: The Making and Maintenance of Open Source Software, is about open source developers and what they tell us about the evolution of our online social spaces. Eghbal sees open source code as a form of public infrastructure that requires maintenance, and that offers us a model through which to understand the challenges faced by online creators on all platforms.

infrastructure maintenance open source github open source software nadia eghbal

How the Future of Community Can Be Found in the History of Open Source with Nadia Eghbal

Masters of Community with David Spinks

Play Episode Listen Later Nov 17, 2020 66:33

Not often are experts in community deeply researching at a scholarly level how community works, our next guest Nadia Egbal does. She's the Head of Writer Experience at SubStack and the author of Working in Public, where she dives into the history and evolution of Open Source communities. They ended up laying the groundwork for how online communities outside of Open Source behaved and built culture. Not to mention, how that lead to people actually getting involved and becoming contributors (or not) in those communities. Even in the largest software projects or popular services like Wikipedia, a very small percentage of contributors make up most of the content available. She also discusses a rarer topic in the world of community, intensive research. Stemming from her work with the Ford Foundation “Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure”, Nadia has taken an approach of dissecting how community works through a more academic lens. She shares how she sees this kind of research so impactful and how companies, venture capital firms and other institutions might be able to empower more of this kind of research and what those roles might look like. She also shares how she has brought this approach to SubStack and her current community of writers and content creators and the trends she is seeing in the world of written content. Who is this episode for?: B2C, Online, Scaling Communities 3 key takeaways: - The stories and evolution of Open Source communities can tell us a lot about how our current online communities can evolve even outside the world of software. - The majority of contributions come from a small number of highly engaged users, even from the largest crowd sources communities projects like Wikipedia. - Implementing more research and research roles will help shape not only the communities of our companies but how we can build as a community industry.

history community head online public wikipedia substack implementing b2c open source stemming cmx nadia eghbal

How the Future of Community Can Be Found in the History of Open Source with Nadia Eghbal

Masters of Community with David Spinks

Play Episode Listen Later Nov 17, 2020 66:33

Not often are experts in community deeply researching at a scholarly level how community works, our next guest Nadia Egbal does. She's the Head of Writer Experience at SubStack and the author of Working in Public, where she dives into the history and evolution of Open Source communities. They ended up laying the groundwork for how online communities outside of Open Source behaved and built culture. Not to mention, how that lead to people actually getting involved and becoming contributors (or not) in those communities. Even in the largest software projects or popular services like Wikipedia, a very small percentage of contributors make up most of the content available. She also discusses a rarer topic in the world of community, intensive research. Stemming from her work with the Ford Foundation “Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure”, Nadia has taken an approach of dissecting how community works through a more academic lens. She shares how she sees this kind of research so impactful and how companies, venture capital firms and other institutions might be able to empower more of this kind of research and what those roles might look like. She also shares how she has brought this approach to SubStack and her current community of writers and content creators and the trends she is seeing in the world of written content. Who is this episode for?: B2C, Online, Scaling Communities 3 key takeaways: - The stories and evolution of Open Source communities can tell us a lot about how our current online communities can evolve even outside the world of software. - The majority of contributions come from a small number of highly engaged users, even from the largest crowd sources communities projects like Wikipedia. - Implementing more research and research roles will help shape not only the communities of our companies but how we can build as a community industry.

history community head online public wikipedia substack implementing b2c open source stemming cmx nadia eghbal

Working in Public with Nadia Eghbal

public silicon valley narrative village substack shifts governance nadia eghbal

Play Episode Listen Later Oct 24, 2020 50:52

Nadia Eghbal (@nayafia) of Substack joins Erik on this episode to discuss:- The background of her book, Working in Public, and the “why now” for it.- What she’s learned about open source that can be applied to other areas.- Shifts that she’d like to see in the internet.- The evolution of thinking around democracy in the world.- Governance in companies and countries.- Narratives in tech and the negative attention tech has received recently.Thanks for listening — if you like what you hear, please review us on your favorite podcast platform. Check us out on the web at www.villageglobal.vc or get in touch with us on Twitter @villageglobal.Want to get updates from us? Subscribe to get a peek inside the Village. We’ll send you reading recommendations, exclusive event invites, and commentary on the latest happenings in Silicon Valley. www.villageglobal.vc/signup

Working in Public with Nadia Eghbal

public silicon valley narrative village substack shifts governance nadia eghbal

Play Episode Listen Later Oct 24, 2020 50:52

Nadia Eghbal (@nayafia) of Substack joins Erik on this episode to discuss:- The background of her book, Working in Public, and the “why now” for it.- What she’s learned about open source that can be applied to other areas.- Shifts that she’d like to see in the internet.- The evolution of thinking around democracy in the world.- Governance in companies and countries.- Narratives in tech and the negative attention tech has received recently.Thanks for listening — if you like what you hear, please review us on your favorite podcast platform. Check us out on the web at www.villageglobal.vc or get in touch with us on Twitter @villageglobal.Want to get updates from us? Subscribe to get a peek inside the Village. We’ll send you reading recommendations, exclusive event invites, and commentary on the latest happenings in Silicon Valley. www.villageglobal.vc/signup

Episode 38: Community is Everything: Open Source with Henry Zhu (Part 3)

Enjoy the Vue

Play Episode Listen Later Oct 19, 2020 23:19

Welcome back to another episode of Enjoy the Vue. This concludes our three-part interview with Babel maintainer, Henry Zhu. Last time, we closed our discussion with what work maintainers of open source projects do that is not straight coding. In this episode, we continue talking with Henry about what do people count as maintenance work versus other tasks that definitely need to get done, but are perhaps less visible to the public eye. Henry also shares his approaches to taking care of himself and the pursuit of serendipity, and we discuss the inclusivity of the open source community, the relationship between in-person communities and open source culture, and we get into our picks of the week, so make sure not to miss this episode! Key Points From This Episode: Henry opens with the dichotomy between freedom and obligation for maintainers. Maintainers don’t see certain tasks as maintenance, such as answering user queries. What Henry does to take care of himself, like sport or playing music, and his musings on what serendipity looks like in an online setting. Spaces that promote serendipity, and why actively pursuing serendipity is not a paradox. There are communities like Google Summer of Code that promote open source involvement. Preferences are shaped through experiences of the communities, so it is important that they be inclusive, particularly for women. The relationship between in-person communities and open source culture. Ben’s picks this week include a ukulele, Azul, and Nadia Eghbal’s book, Working in Public. Veekas recommends Kim’s Convenience and Race After Technology by Ruha Benjamin. Henry’s picks include Tools for Conviviality by Ivan Illich, and a card game called The Mind. Tessa suggests Journey, the Reply series, and Conquer Your Critical Inner Voice. Tweetables: “How do we get people to have a higher sense of ownership so that we can lessen the burden on maintainers?” — @left_pad [0:02:37] “There's an aspect of serendipity involves risk, and involves trust and faith in something, in the future. Me putting myself out there is going to lead to something good.” — @left_pad [0:05:50] “I feel being more intentional, specifically reaching out to people, or getting involved in certain communities is probably better. There are formal versions of this, like Google Summer of Code. We've done that and Rails Girls, Summer of Code, stuff like that. Yeah, maybe we need more of that, instead of this blanket like, ‘Hey, anyone can get involved.’” — @left_pad [0:07:48] “For a tool, we want self-expression from the people that use it and I think coding is – or anything, [Illich] mentions education, and school, and medicine, and coding could be another thing where it's increasingly harder to learn how to code, even though now we have boot camps and stuff.” — @left_pad [0:17:46] Links Mentioned in Today’s Episode: - Henry Zhu on Twitter (https://twitter.com/left_pad?lang=en) - Henry Zhu on GitHub (https://github.com/hzoo) - Henry Zhu (https://www.henryzoo.com/) - Hope in Source Podcast (https://hopeinsource.com/) - Maintainers Anonymous Podcast (https://maintainersanonymous.com/) - Babel (https://babeljs.io/) - Google Summer of Code (https://summerofcode.withgoogle.com/archive/) - Rails Girls (http://railsgirls.com/) - Vue Vixens (https://www.vuevixens.org/) - Working in Public (https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862) - Kim’s Convenience on Netflix (https://www.netflix.com/title/80199128) - Race After Technology (https://www.amazon.com/Race-After-Technology-Abolitionist-Tools/dp/1509526404) - Tools for Conviviality (https://www.amazon.com/Tools-Conviviality-Ivan-Illich/dp/1842300113/ref=sr_1_1?dchild=1&keywords=Tools+for+Conviviality&qid=1601903637&s=books&sr=1-1) - Journey (https://thatgamecompany.com/journey/) - Conquer Your Critical Inner Voice (https://www.amazon.com/Conquer-Your-Critical-Inner-Voice/dp/1572242876/ref=sr_1_1?dchild=1&keywords=Conquer+Your+Critical+Inner+Voice&qid=1601904786&sr=8-1) - Enjoy the Vue on Twitter (https://twitter.com/enjoythevuecast?lang=en) - Enjoy the Vue (https://enjoythevue.io/) Special Guest: Henry Zhu.

Making is Show Business now – alexdanco.com

Josh on Narro

Play Episode Listen Later Oct 12, 2020 16:04

Nadia Eghbal’s new book, Working In Public: the Making and Maintenance of Open Source Software, may not have been on your short list of books to read this year. It’s admittedly a nerdy topic: it’s about open source projects, roles and... https://devonzuegel.com/post/making-is-show-business-now-alexdanco-com Devon Zuegel #clipping #cities #interpersonal #tools-for-thought #programming #travel podcast sponsor my work hereemail newsletter 💌the first heyday of open source in the 90sThe Mythical Man-Monthlearned how to accommodate hundreds of productive contributors"Eternal September"Get it in your inbox every week

maintenance show business open source software nadia eghbal eternal september devon zuegel

Episode 57: Mikeal Rogers on Building Communities, the Early Days of Node.js, and How to Stay a Coder for Life

Play Episode Listen Later Oct 10, 2020 38:46

Panelists Allen "Gunner" Gunn | Justin Dorfman | Richard Littauer Guest Mikeal Rogers Show Notes Hello and welcome to Sustain! Our special guest today is Mikeal Rogers, who works at Protocol Labs as IPLD Lead. We learn what Protocol Labs is, where they come from, and what Mikeal does there as the IPLD Lead (InterPlanetary Linked Data). We will find out what happened when io.js forked with Node.js, if there is a difference between the Project Manager and Developer Role, and Mikeal’s interests in design libraries, and building a community and ecosystem from scratch and how they interrelate. Download this episode now to learn more! [00:01:25] Mikeal tells us what he does at Protocol Labs. We also learn who Protocol Labs is and where they come from. [00:06:43] Mikeal talks about what he did in his previous jobs. [00:09:48] Richard asks Mikeal what separates his path and his ideal goal from being someone who ends up just working on algorithms full time for Microsoft in the back office. [00:14:15] Mikeal shares with us the io.js fork with Node.js. Justin wonders if there was a lot tension between the communities and Mikeal explains. [00:19:40] Richard wonders if Mikeal thinks the Project Manager Role and the Developer Role are similar. [00:24:18] Mikeal specializes in and worked on design libraries so they can grow entire ecosystems and communities and how to make the code itself actually enable and afford better sustainable practices, which he talks about here. He mentions the creation of the Buffer Interface. [00:32:51] Mikeal tells us where we can learn more about him and things he’s done with community and sustainability stuff and where we can find him on the internet. Spotlight [00:34:46] Justin’s spotlight is Into the Ether podcast. [00:35:06] Gunner’s spotlight is Save Internet Freedom. [00:35:33] Richard’s spotlight is a book called, Apprenticeship Patterns by Dave Hoover and Adewale Oshineye. [00:35:49] Mikeal’s spotlight is GitHub Actions. Quotes [00:08:10] “The whole industry is really pushing you towards do more, take on more responsibility, do a startup, take on executive roles, keep going. It’s just never enough to just write code or be a programmer.” [00:08:24] “I had a real kind of identity crisis a little bit when I was leaving the Node Foundation, because I was like what am I going to do? And it actually took me a little while, like I had a short stint in some venture capital stuff.” [00:22:30] “If you write code every day, you have a practice. Even if you’re just doing it for work, you have a practice, like you sit down, and you probably notice yourself taking a walk, or working on a problem in the shower or something. These are really subtle forms of meditation for you to take yourself in a different state and get all of the distractions away for a minute and just think about a problem.” Links Protocol Labs (https://protocol.ai/) IPLD (InterPlanetary Linked Data) (https://docs.ipld.io/) Medium-Mikeal Rogers (https://medium.com/@mikeal) Mikeal Rogers-GitHub (https://github.com/mikeal) Mikeal Rogers Twitter (https://twitter.com/mikeal?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) “Request for Commits explored different perspectives in open source sustainability”-podcast with Nadia Eghbal and Mikeal Rogers (https://changelog.com/rfc) Hope in Source podcast with Nadia Eghbal and Henry Zhu (https://hopeinsource.com/) Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman by Dave Hoover and Adewale Oshineye (https://www.amazon.com/Apprenticeship-Patterns-Guidance-Aspiring-Craftsman/dp/0596518382) Into the Ether- A podcast by EthHub (https://podcast.ethhub.io/) Save Internet Freedom (https://saveinternetfreedom.tech/) GitHub Actions (https://github.com/actions) GitHub Actions (GitHub Docs) (https://docs.github.com/en/free-pro-team@latest/actions) InfoWorld Tech Watch-“Why io.js decided to fork Node.js.” (https://www.infoworld.com/article/2855057/why-iojs-decided-to-fork-nodejs.html) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Mikeal Rogers.

Episode 36: Community is Everything: Open Source with Henry Zhu (Part 1)

Enjoy the Vue

Play Episode Listen Later Oct 5, 2020 23:02

Open source software has received both criticism and applause from the tech community all across the world. Today, we’re talking about open source with Henry Zhu, a New York City-based maintainer of the community-funded compiler, Babel. Previously at Adobe, he’s also a host of two podcasts that discuss the lives of maintainers, Hope in Source and Maintainers Anonymous. In this episode, Henry shares some the similarities between his faith and open source, and explains some of the assumptions people have about open source software, why we need to take a step back and reevaluate these assumptions, and why he believes we should be thinking about how to minimize options and make things simpler. After all, open source is about more than just the code. Tune in to find out more! Key Points From This Episode: Henry introduces himself, what he does, and his podcast, Hope in Source. Henry shares a bit more about his podcast and his conversations with Nadia Eghbal. The differences and similarities Henry sees between faith and open source. From code style checker in open source to core maintainer at Babel – the ideas are similar. We need to step back and reevaluate some of the assumptions we have about open source. Henry talks a bit about his co-host Nadia Eghbal’s new book, Working in Public. How to address the issue of over-participation – Henry thinks multiple solutions are needed. Maintaining both public and private personas – Henry says it’s better to have actual dialogue. Communicating in open source, membership, and assumptions about open source projects. Raising funding for open source projects using crowdfunding platforms like Kickstarter. Henry believes we should be thinking about how to remove options and make things simpler. Open source is not just about code, it's about other things too.

community new york city public open raising maintaining kickstarter communicating adobe babel open source vuejs nadia eghbal henry zhu

Episode 18: DevRel Metrics with Mary Thengvall

Play Episode Listen Later Sep 18, 2020 40:08

Panelists Matt Broberg | Nicole Huesman | Foundjem Armstrong Guests Mary Thengvall (https://podcast.chaoss.community/guests/mary-thengvall) Show Notes [00:01:48] Mary tells us all about herself and her job. [00:03:05] We find out from Mary what DevRel is. [00:05:20] Nicole asks Mary to talk the DevRel position being such a unique position and often people may want to apply traditional marketing metrics to the role and sometimes that doesn’t really work, so she explains why. [00:11:17] Matt wants to know how Mary handles the organization that is so used to trying to build these metaphorical engines everywhere and how do you try to explain DevRel from a data perspective if you don’t have the same easy metaphor available to you. She brings up the “Orbit Model.” [00:17:53] Armstrong asks Mary if this is a different kind of MetaMetrics that captures different forms of metrics and tries to present it to a different audience. [00:22:17] Mary tells us her thoughts on the whole notion of the unintended consequences of metrics or measurement, which is always a hot topic. [00:29:06] We learn how management measures Mary’s success and how does she evaluate her performance. [00:32:10] Mary tells us what she would like to see from the CHAOSS Project and how does she see the CHAOSS Project being helpful from a DevRel perspective. Picks [00:35:08] Mary has two picks: a book called, Working in Public, _by Nadia Eghbal and a video game, _Horizon Zero Dawn. [00:36:53 Armstrong’s pick is Ordy cartoon. [00:37:38] Nicole has two picks: I AM C-3PO and A Famous Dog’s Life (Audiobooks). [00:38:48] Matt’s pick is the research of George Lakoff and his book, _Metaphors We Live By. _ Sponsor Honeybadger (https://www.honeybadger.io/) Links CHAOSS Project (https://chaoss.community/) CHAOSS Project Twitter (https://twitter.com/chaossproj?lang=en) Mary Thengvall Website/Blog (https://www.marythengvall.com/) Mary Thengvall Twitter (https://twitter.com/mary_grace?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Mary Thengvall Instagram (https://www.instagram.com/candidcrafts) Camunda (https://camunda.com/) The Business Value of Developer Relations by Mary Thengvall (https://www.persea-consulting.com/book) The Orbit Model-GitHub (https://github.com/orbit-love/orbit-model) “DevRel Qualified Leads: Repurposing A Common Business Metric To Prove Value,” by Mary Thengvall (https://www.marythengvall.com/blog/2019/12/14/devrel-qualified-leads-repurposing-a-common-business-metrics-to-prove-value) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862) [Horizon Zero Dawn-Steam](https://store.steampowered.com/app/1151640/HorizonZeroDawnCompleteEdition/) Ordy Cartoon (https://en.wikipedia.org/wiki/M%C4%ABmu_Iro_Iro_Yume_no_Tabi) [I AM C-3PO (Audiobook)](https://www.amazon.com/I-Am-C-3PO-Anthony-Daniels-JJ-Abrams/dp/B07YSWW72T/ref=tmmaudswatch0?encoding=UTF8&qid=1600285679&sr=8-1-spons) [A Famous Dog’s Life (Audiobook)](https://www.amazon.com/Famous-Dogs-Life-Americas-Chihuahua/dp/B00DBD4F2W/ref=sr11?dchild=1&keywords=A+famous+dogs+life&qid=1600285744&s=audible&sr=1-1) Metaphors We Live By- George Lakoff (https://georgelakoff.com/books/metaphors-we-live-by/) George Lakoff Website (https://georgelakoff.com/) Special Guest: Mary Thengvall.

public maintenance armstrong metrics horizon zero dawn business value open source software developer relations devrel george lakoff nadia eghbal mary thengvall ordy

Episode 51: Working in Public: Nadia Eghbal and her new book about Making and Sustaining Open Source Software

Play Episode Listen Later Aug 28, 2020 43:49

Sponsored by: https://www.honeybadger.io/images/navbar_logo.svg?1597697989 (https://www.honeybadger.io/) Panelists Allen "Gunner" Gunn | Eric Berry | Justin Dorfman | Richard Littauer Guest Nadia Eghbal (https://nadiaeghbal.com/) Show Notes Hello and welcome to Sustain! Today, we have special guest. Nadia Eghbal, a writer and researcher, works for Substack, and has a new book out which we will be talking about today! We discuss Nadia’s book, what it’s all about, why she wrote it, and why Eric refers to it as the “Open Source Bible.” She also talks about the report she did called, “Roads and Bridges,” published by the Ford Foundation. Find out why she has been called the “Open Source Archaeologist.” Download this episode now! [00:01:43] Nadia tells us all about her book, what it’s about, and why she wrote it. [00:02:56] Justin asks Nadia what her expectations were of writing her report, Roads and Bridges. [00:05:01] Eric mentions a talk Nadia gave a few years back, and she used a “lobster” reference throughout it, so he wonders what her motivation was behind going so deep into creating a legacy of documentation and knowledge that very few people in the world have. [00:09:16] Richard brings up Mike McQuaid’s sticker funds and Nadia brings up an example of this. [00:11:40] Eric talks about Nadia’s book which he refers to as the “Open Source Bible,” and Gunner adds his viewpoint as well. [00:13:24] Gunner asks Nadia if this book leads to actions and does she have any thoughts about what actions she would like it to lead to on the part of readers. [00:15:36] Gunner has an archaeology question for Nadia and is curious to know if she has reflected on the idea that when you’re not downloading, when you’re not installing the idea of a license or the idea of a piece of technology, being more community created, as a more abstract or removed concept. [00:17:52] Justin brings up a previous podcast guest, Matt Asay from AWS, talking about Amazon working hand in hand with Redis and all these other open source companies, and he asks Nadia what she thinks about this. [00:22:03] Richard is curious to know what to do with projects that don’t have a charismatic leader where it hasn’t focused on who they are, which may have really good documentation. Is there any hope for any of those projects or they doomed to just continually wither and run out of steam? Nadia gives us the run down. [00:27:28] Richard wants to know what Nadia is doing at Sub Stack that is so interesting to her and following the research that you’ve learned from this book, why there? She tells us why she wrote the book. [00:32:37] Justin mentions a book he read called, Hate Inc. by Matt Taibbi, who has a Sub Stack thing. This is a great read! ☺ [00:35:08] Richard wants to know how Nadia can help people who write low-level software projects, who don’t have the power or the means or they are shy. What can we do to help those people? [00:38:22] Nadia tells us where you can find her on the internet, where you can find her book, and work. Spotlight [00:39:02] Gunner’s spotlight is Gosh science. [00:37:27] Justin’s spotlight is Nadia’s book, Working in Public (real world version). [00:39:30] Eric’s spotlight is also Nadia’s book, Working in Public and a quote from the book. [00:41:32] Richard’s spotlight is the concept of Antilibraries. [00:42:25] Nadia’s spotlight is Brendon Schlagel’s anti-library. Quotes [00:11:39] “I think what we’re seeing happen in all of this is we’re working toward building a shared vocabulary of the universe of this ecosystem, where each project is going to have its own arcane vocabulary over time.” [00:17:49] “Depending on who you talk to, the term open source just means so many things to different people.” Links Nadia Eghbal Website (https://nadiaeghbal.com/oss/) Nadia Eghbal Twitter (https://twitter.com/nayafia?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Nadia Eghbal Linux Conf AU 2017- Consider the Maintainer (YouTube) (https://www.youtube.com/watch?v=W2AR1owg0ao) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/dp/0578675862/) Substack (https://substack.com/) Gathering for Open Science Hardware (GOSH) (http://openhardware.science/) Antilibraries (https://www.antilibrari.es/) Hate Inc: Why Today’s Media Makes Us Despise One Another by Matt Taibbi (https://www.amazon.com/Hate-Inc-Todays-Despise-Another/dp/1949017257) Credits Produced by Richard Littauer (https://www.burntfen.com) Rebase.fm (https://rebase.fm/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Ad Sales by Eric Berry Special Guest: Nadia Eghbal.

How To Start and Grow a Newsletter with Lenny Rachitsky and Nadia Eghbal

public fellowship newsletter substack lenny nadia eghbal

Play Episode Listen Later Aug 27, 2020 49:47

Nadia Eghbal (@nayafia), of Substack, and author of Working in Public, and Lenny Rachitsky (@lennysan), author of a newsletter on product and growth and former Airbnb PM, join Erik on this episode to discuss:- The On Deck Writer’s Fellowship in partnership with Substack.- The evolution of newsletters as a medium over time.- Nadia and Lenny’s journeys on Substack.- Their advice for people who want to get started writing their own newsletters.- How they think about what to write about and the right cadence for their newsletters.- How to improve as a writer.- How to think about pricing.Thanks for listening — if you like what you hear, please review us on your favorite podcast platform. Check us out on the web at villageglobal.vc or get in touch with us on Twitter @villageglobal.

How To Start and Grow a Newsletter with Lenny Rachitsky and Nadia Eghbal

public fellowship newsletter substack lenny nadia eghbal

Play Episode Listen Later Aug 27, 2020 49:47

Nadia Eghbal (@nayafia), of Substack, and author of Working in Public, and Lenny Rachitsky (@lennysan), author of a newsletter on product and growth and former Airbnb PM, join Erik on this episode to discuss:- The On Deck Writer’s Fellowship in partnership with Substack.- The evolution of newsletters as a medium over time.- Nadia and Lenny’s journeys on Substack.- Their advice for people who want to get started writing their own newsletters.- How they think about what to write about and the right cadence for their newsletters.- How to improve as a writer.- How to think about pricing.Thanks for listening — if you like what you hear, please review us on your favorite podcast platform. Check us out on the web at villageglobal.vc or get in touch with us on Twitter @villageglobal.

290 - AMA with Nadia Eghbal (Writer Experience @ Substack) On All things Substack

Forward Thinking Founders

Play Episode Listen Later Aug 27, 2020 42:44

Nadia Eghbal is the Head of Writer Experience at Substack. In this Forward Thinking City AMA, we ask Nadia questions on all things Substack.

head writer substack nadia eghbal

Nadia Eghbal: Open-Source Software

North Star Podcast

Play Episode Listen Later Aug 17, 2020 67:01

My guest today is Nadia Eghbal, an independent researcher and the author of Working in Public: The Making and Maintenance of Open Source Software. She currently works on the writer experience team at Substack. She did a lot of her research at Protocol Labs where she studied the production and economics of open source. Before that, she worked on the open source team at GitHub. One of the core theses of her work is that open-source software projects don't have zero marginal cost. Maintenance can be expensive, even if the code itself is free to distribute. In this episode, we spoke about how sharing ideas on different platforms helps you express different sides of your personality, why GitHub is the center of the open source community, and what she learned running a grant program. Please enjoy my conversation with Nadia Eghbal. ____________________________ Shownotes 2:07 - Why the personal projects of a coder can unexpectedly turn into a massive public responsibility. 4:36 - The temporal nature of creating code aside from any other art form. 8:24 - How creators can become enslaved by their own systems. 12:37 - How Github differs from social media platforms, and why it might be that way on purpose. 14:54 - The similarities and differences of open source code and organized religion. 20:48 - How to efficiently externalize information to make more open source type projects possible. 24:29 - Why Nadia feels compelled to write everything down, even though to her it sometimes feels like a problem. 31:00 - How the bystander effect comes into play in the world of open source software development. 35:17 - Why Nadia believes that the way open source was started made it "set up to fail." 38:46 - The importance of granularity and modularity in maintenance, throughout people's personal and professional lives. 43:54 - What the consequences are to accepting code that causes problems downstream. 46:22 - Why Nadia chose to write and publish this book instead of going through the process of getting a PhD. 49:05 - What microgrants are, and how their different aspects play into research and development. 54:06 - How creative people can share their knowledge with each other better through story sharing. 57:28 - How Nadia focuses the scope of her projects from being too overly broad. 1:00:40 - The danger of thinking you ever know enough about any field that's not your own.

phd substack maintenance github open source software protocol labs nadia eghbal

Working in Public: Open Source Software with Nadia Eghbal

Hanselminutes - Fresh Talk and Tech for Developers

Play Episode Listen Later Aug 13, 2020 35:16

Nadia Eghbal is the author of Working in Public: The Making and Maintenance of Open Source Software. She is a writer and researcher who likes to understand how people work. She is currently interested in parasocial communities and reputation-based economies.https://nadiaeghbal.com/

public maintenance open source software nadia eghbal

Nadia Eghbal, "Working in Public: The Making and Maintenance of Open Source Software" (Stripe Press, 2020)

New Books in Technology

Play Episode Listen Later Aug 12, 2020 67:35

Open source is the once-radical idea that code should be freely available to everyone. Open-source software was once an optimistic model for public collaboration, but is now a near-universal standard. But most open-source code is not developed by big teams or equitable collaborations; it’s maintained by unseen individuals who work tirelessly to write and publish code that's consumed by millions. In Working in Public: The Making and Maintenance of Open Source Software (Stripe Press), Nadia Eghbal takes an inside look at modern open source software development and its evolution over the last two decades. The book draws from hundreds of interviews with developers, and serves as a first-of-its-kind anthropological investigation of the open source community. Eghbal examines the role of GitHub as a platform for hosting code, the way software developers are (and often aren’t) compensated for their work, and the complex dynamics between maintainers, contributors, and users of open-source software. Nadia Eghbal is a writer and researcher who explores how the internet enables individual creators. From 2015 to 2019, she focused on the production of open source software, working independently and at GitHub to improve the open source developer experience. Matthew Jordan is a professor at McMaster University, where he teaches courses on AI and the history of science. You can follow him on Twitter @mattyj612 or his website matthewleejordan.com. Learn more about your ad choices. Visit megaphone.fm/adchoices

ai public open press maintenance github stripe mcmaster university open source software matthew jordan nadia eghbal

Working in Public

The Changelog

Play Episode Listen Later Aug 12, 2020 75:14 Transcription Available

Nadia Eghbal is back and this time she’s talking with us about her new book Working in Public. If you’re an old school listener you might remember the podcast we produced with Nadia and Mikeal Rogers called Request for Commits. If you weren’t listening then, or can’t remember…don’t worry…the back catalog of Request for Commits is still online and subscribe-able via all the podcast ways. That podcast is still getting listens to this very day! Obviously we go way back with Nadia…and having a chance to now talk with her through all the details of her new book Working in Public, this was a milestone for this show and Jerod and I. We talked through the reasons she wrote the book in the first place, Nadia’s thoughts on the future of the internet and the connection of creators to the platforms they build their followings on, and we also talk about the health of projects and communities and the challenges we face internet-at-large as well as right here in our backyard in the open source community.

development public code software hackers programming open source commits software engineering jerod changelog nadia eghbal mikeal rogers

Nadia Eghbal, "Working in Public: The Making and Maintenance of Open Source Software" (Stripe Press, 2020)

New Books Network

Play Episode Listen Later Aug 12, 2020 67:35

Open source is the once-radical idea that code should be freely available to everyone. Open-source software was once an optimistic model for public collaboration, but is now a near-universal standard. But most open-source code is not developed by big teams or equitable collaborations; it’s maintained by unseen individuals who work tirelessly to write and publish code that's consumed by millions. In Working in Public: The Making and Maintenance of Open Source Software (Stripe Press), Nadia Eghbal takes an inside look at modern open source software development and its evolution over the last two decades. The book draws from hundreds of interviews with developers, and serves as a first-of-its-kind anthropological investigation of the open source community. Eghbal examines the role of GitHub as a platform for hosting code, the way software developers are (and often aren’t) compensated for their work, and the complex dynamics between maintainers, contributors, and users of open-source software. Nadia Eghbal is a writer and researcher who explores how the internet enables individual creators. From 2015 to 2019, she focused on the production of open source software, working independently and at GitHub to improve the open source developer experience. Matthew Jordan is a professor at McMaster University, where he teaches courses on AI and the history of science. You can follow him on Twitter @mattyj612 or his website matthewleejordan.com. Learn more about your ad choices. Visit megaphone.fm/adchoices

ai public open press maintenance github stripe mcmaster university open source software matthew jordan nadia eghbal

Nadia Eghbal, "Working in Public: The Making and Maintenance of Open Source Software" (Stripe Press, 2020)

New Books in Anthropology

Play Episode Listen Later Aug 12, 2020 67:35

Open source is the once-radical idea that code should be freely available to everyone. Open-source software was once an optimistic model for public collaboration, but is now a near-universal standard. But most open-source code is not developed by big teams or equitable collaborations; it’s maintained by unseen individuals who work tirelessly to write and publish code that's consumed by millions. In Working in Public: The Making and Maintenance of Open Source Software (Stripe Press), Nadia Eghbal takes an inside look at modern open source software development and its evolution over the last two decades. The book draws from hundreds of interviews with developers, and serves as a first-of-its-kind anthropological investigation of the open source community. Eghbal examines the role of GitHub as a platform for hosting code, the way software developers are (and often aren’t) compensated for their work, and the complex dynamics between maintainers, contributors, and users of open-source software. Nadia Eghbal is a writer and researcher who explores how the internet enables individual creators. From 2015 to 2019, she focused on the production of open source software, working independently and at GitHub to improve the open source developer experience. Matthew Jordan is a professor at McMaster University, where he teaches courses on AI and the history of science. You can follow him on Twitter @mattyj612 or his website matthewleejordan.com. Learn more about your ad choices. Visit megaphone.fm/adchoices

ai public open press maintenance github stripe mcmaster university open source software matthew jordan nadia eghbal

Nadia Eghbal, "Working in Public: The Making and Maintenance of Open Source Software" (Stripe Press, 2020)

New Books in Science, Technology, and Society

Play Episode Listen Later Aug 12, 2020 67:35

Open source is the once-radical idea that code should be freely available to everyone. Open-source software was once an optimistic model for public collaboration, but is now a near-universal standard. But most open-source code is not developed by big teams or equitable collaborations; it’s maintained by unseen individuals who work tirelessly to write and publish code that's consumed by millions. In Working in Public: The Making and Maintenance of Open Source Software (Stripe Press), Nadia Eghbal takes an inside look at modern open source software development and its evolution over the last two decades. The book draws from hundreds of interviews with developers, and serves as a first-of-its-kind anthropological investigation of the open source community. Eghbal examines the role of GitHub as a platform for hosting code, the way software developers are (and often aren’t) compensated for their work, and the complex dynamics between maintainers, contributors, and users of open-source software. Nadia Eghbal is a writer and researcher who explores how the internet enables individual creators. From 2015 to 2019, she focused on the production of open source software, working independently and at GitHub to improve the open source developer experience. Matthew Jordan is a professor at McMaster University, where he teaches courses on AI and the history of science. You can follow him on Twitter @mattyj612 or his website matthewleejordan.com. Learn more about your ad choices. Visit megaphone.fm/adchoices

ai public open press maintenance github stripe mcmaster university open source software matthew jordan nadia eghbal

Working in Public (The Changelog #408)

community managing public software maintenance participation open source oss open source software nadia eghbal

Play Episode Listen Later Aug 12, 2020 75:14 Transcription Available

Nadia Eghbal is back and this time she’s talking with us about her new book Working in Public. If you’re an old school listener you might remember the podcast we produced with Nadia and Mikeal Rogers called Request for Commits. If you weren’t listening then, or can’t remember…don’t worry…the back catalog of Request for Commits is still online and subscribe-able via all the podcast ways. That podcast is still getting listens to this very day! Obviously we go way back with Nadia…and having a chance to now talk with her through all the details of her new book Working in Public, this was a milestone for this show and Jerod and I. We talked through the reasons she wrote the book in the first place, Nadia’s thoughts on the future of the internet and the connection of creators to the platforms they build their followings on, and we also talk about the health of projects and communities and the challenges we face internet-at-large as well as right here in our backyard in the open source community.

development public code software hackers programming open source commits software engineering jerod changelog nadia eghbal mikeal rogers

16: Managing Over-Participation (Working in Public)

Hope in Source

Play Episode Listen Later Aug 4, 2020 46:37

Is more (information, people, code) always better? Nadia Eghbal joins Henry to chat about her new book, Working in Public: The Making and Maintenance of Open Source Software, a deep-dive into the of open source community and how it may paint a picture of online communities in general. They talk about her 2x2 model of communities, the public web (Twitter) to private groups (group chat), the turn to individual creators, and the importance of moderation and boundaries. Transcript at https://hopeinsource.com/overparticipation Henry: https://twitter.com/left_pad Nadia: https://twitter.com/nayafia The Book: Working in Public: The Making and Maintenance of Open Source Software

Working, Making, Creating in Public... and Private

a16z

Play Episode Listen Later Aug 2, 2020 47:06

We're living in an unprecedented era of online collaboration, coordination, and creation. All kinds of people are coming together -- whether in an open source project or company, an R&D initiative, a department in a company, a club or special interest group, even a group of friends and family -- around some shared interest or activity. But the word "members" is faceless, and doesn't help us really understand, support (and better design for) these communities.So in this special book launch episode of the a16z Podcast, Nadia Eghbal -- author of the new book Working in Public: The Making and Maintenance of Open Source Software published by Stripe Press -- shares with a16z editor in chief Sonal Chokshi the latest research and insights from years of studying the health of open source communities (for Ford Foundation), working in developer experience (at GitHub), researching the economics and production of software (at Protocol Labs), and now focusing on writer experience at Substack.Eghbal offers a new taxonomy of communities -- including newer phenomena such as "stadiums" of open source developers, other creators, and really, influencers -- who are performing their work in massive spaces where the work is public (and not necessarily participatory). So what lessons of open source communities do and don't apply to the passion economy and creator communities? How does the evolution of online communities -- really, social networks -- shift the focus to reputation and status as a service? And what if working in public is also about sharing in private, given the "dark forest theory of the internet", the growing desire for more "high-shared context" groups and spaces (including even podcasts and newsletters)? All this and more in this episode.

Episode 25: Understanding nextTick

Enjoy the Vue

Play Episode Listen Later Jul 13, 2020 36:24

Sponsored By: Show Notes [00:01:11] Ari tells us what nextTick is and Tessa tells us about the differences between local and global versions. [00:03:43] Ari and Tessa tell us scenarios they’ve run into as far as needing nextTick. [00:08:26] Ben is curious about “chaining” in nextTick. Tessa explains this and she also mentions her talk she did at VueConf US 2019, where she broke down a bunch of different ways to nest nextTick. [00:13:06] As far as nextTick goes, Ben wants to know if this is something that Ari and Tessa would recommend people only reach out to when things start to be inconsistent or when should someone use this? [00:18:55] Ben wants to know if nextTick is used improperly can it cause performance issues or not quite? [00:23:54] Tessa wonders if Vue3 comes out, if she follows the style where her JS is at the top of her single file component and open it, she will see at the top what props it accepts and also what events that she has decided this component will emit? [00:26:20] Ari and Tessa give some final tips about nextTick stuff. Sponsor: Linode (https://promo.linode.com/vue/) Picks of the week: [00:28:53] Tessa has two picks: Douglas by Hannah Gadsby on Netflix and Managing Up by Mary Abbajay. [00:30:55] Ari has two picks: Queer Eye-Season 5 on Netflix and Queer Eye-We’re in Japan! on Netflix. [00:33:26] Ben’s has three picks: An OXO Good Grips Silicone Pastry Mat, Tessa, who has provided some really great picks and finds for him this week which is Hey.com and Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal. Resources mentioned: VueConf US 2019-Back to the Vueture: Stuck in the Event Loop by Tessa (https://www.vuemastery.com/conferences/vueconf-us-2019/back-to-the-vueture-stuck-in-the-event-loop) nextTick (https://vuejs.org/v2/api/#Vue-nextTick) Douglas-Hannah Gadsby (https://www.netflix.com/title/81054700) Managing Up: How to Move Up, Win at Work, and Succeed with Any Type of Boss by Mary Abbajay (https://bookshop.org/books/managing-up-how-to-move-up-win-at-work-and-succeed-with-any-type-of-boss/9781119436683) Queer Eye-Netflix (https://www.netflix.com/title/80160037) Queer Eye: We’re in Japan!-Netflix (https://www.netflix.com/title/81075744) OXO Good Grips Silicone Pastry Mat (https://www.oxo.com/silicone-pastry-mat.html) Hey.com (https://hey.com/) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://nayafia.substack.com/p/22-working-in-public)

netflix work japan boss succeed maintenance javascript js frontend vue move up open source software hannah gadsby managing up linode javascript frameworks queer eye season mary abbajay any type nadia eghbal event loop queer eye netflix vueconf us

Episode 44: Crossing The Chasm with Tobie Langel

Play Episode Listen Later Jul 10, 2020 40:54

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 (https://twitter.com/tobie?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) UnlockOpen (https://unlockopen.com/) Sustain Podcast-Episode 41: The Donut Diet, Commitments. and More Awesomeness with Dave Gandy (https://fireside.fm/s/fxw-Bcan+HH3L5owT) Open Technology Fund (https://www.opentech.fund/) Aral Balkan (https://ar.al/) [Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal](https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862/ref=sr12?dchild=1&keywords=working+in+public%3A+the+making&qid=1592942530&sr=8-2) [Accelerate: The Science of Lean Software and DevOps:Building and Scaling High Performing Technology Organizations by Nicole Forsgren, PhD](https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339/ref=sr12?dchild=1&keywords=accelerate&qid=1592942345&sr=8-2) Credits Produced by Justin Dorfman (https://www.justindorfman.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Ad Sales by Eric Berry Special Guest: Tobie Langel.

What Nadia Eghbal Thinks About Basically Everything

global status substack village global shamelessness erik torenberg nadia eghbal venture stories

Play Episode Listen Later Jan 18, 2020 117:41

Nadia Eghbal (@nayafia) of Substack joins Erik on this episode.They discuss:- How the internet changes how we find meaning and why new religions haven’t emerged from the internet yet.- The future of newspapers and publishing, and what happens if people can go direct to the reporters they trust via tools like Substack and others.- Her interest in the economics of content creators on the internet.- Shamelessness as a strategy.- Status on the internet and whether it’s really zero sum.- Global cooperation and local versus global impacts.Thanks for listening — if you like what you hear, please review us on your favorite podcast platform. Check us out on the web at villageglobal.vc or get in touch with us on Twitter @villageglobal.Venture Stories is brought to you by Village Global and is hosted by co-founder and partner, Erik Torenberg. Grace Chen is our audio engineer and the show is produced by Brett Bolkowy.

What Nadia Eghbal Thinks About Basically Everything

global status substack village global shamelessness erik torenberg nadia eghbal venture stories

Play Episode Listen Later Jan 18, 2020 117:41

Nadia Eghbal (@nayafia) of Substack joins Erik on this episode.They discuss:- How the internet changes how we find meaning and why new religions haven’t emerged from the internet yet.- The future of newspapers and publishing, and what happens if people can go direct to the reporters they trust via tools like Substack and others.- Her interest in the economics of content creators on the internet.- Shamelessness as a strategy.- Status on the internet and whether it’s really zero sum.- Global cooperation and local versus global impacts.Thanks for listening — if you like what you hear, please review us on your favorite podcast platform. Check us out on the web at villageglobal.vc or get in touch with us on Twitter @villageglobal.Venture Stories is brought to you by Village Global and is hosted by co-founder and partner, Erik Torenberg. Grace Chen is our audio engineer and the show is produced by Brett Bolkowy.

SOS 016: Changing Open Source Culture With Serkan Holat

Sustain Our Software

Play Episode Listen Later Oct 29, 2019 55:24

Serkan is a freelance software developer who has been developing web applications since 2001. Lately he has been working with Angular and ASP.NET. He shares that he has been studying sustainability of open source issues since 2014 and also shares the abridged version of how he came to be involved with the open source community. Richard then asks Serkan to share more details on how he as a developer became interested in open source. He shares how as a developer working on proprietary software he often found himself working on similar solutions in different companies and he realized that he was building the same software solutions over and over. From this he concluded that open sourcing these types of projects would reduce the need to keep creating these projects by sharing the solutions between those that need them. Serkan points out the problem with the way open source works now is that it’s difficult to make money in it and as such he started looking for ways to fix this problem. He has the desire to find ways to move money from proprietary solutions into open source. Serkan asserts that the only real difference between proprietary software and open source software is licensing and furthermore that any software could be open source. The next topic discussed by the panelists is the changes they’ve seen in the last five years for funding open source. Serkan highlights that he believes that many companies are coming to understand that the future is positive with open source and those companies are beginning to move that way. Richard responds by sharing the importance of building structures around funding developers who decide to open source their software. Serkan moves the conversation to a deeper analysis of proprietary rights. The panelists discuss a survey of developers taken by Tidelift that shows that many professionals prefer open source software over proprietary software. The panelists then have a deeper discussion on what the reasons and drawbacks are for proprietary companies to turn open source. They also discuss how to create a tax of sorts that starts funding proprietary solutions turned open source and who would start that process. The open source experts then discuss how it is difficult to convince individual companies to go open source because their focus is on growing their business and making their own software prosper. Serkan responds to this by saying that open source is an investment that can pay dividends in the long run. They also share ideas on how working with governments and individuals could help to facilitate the transition to greater worldwide involvement in open source and propel the software industry forward to supporting open source. Serkan closes by reiterating some thoughts he shared earlier that governments are already involved in a wide range of programs that benefit all of its citizens. He shares how the sustaining of open source could be another program that is added to a government’s agenda and the opportunities that a government has to be of help in contrast to companies and individuals. Panelists Richard Littauer Pia Mancini Eric Berry Guest Serkan Holat Sponsors iPhreaks Adventures in Angular Adventures in .NET Links Angular ASP.NET Chad Whitacre Medium Catching Up w/ Nadia Eghbal Changelog.com sustainoss.org Tidelift Survey Tragedy of the Commons Picks Richard Littauer NPM Tools The Access Fund Pia Mancini Asymmetry by Lisa Halliday Emahoy Tsegué-Maryam Guébrou Eric Berry Airpods Case Oscoin Codefund Serkan Holat License Zero Marcin Jakubowski Ted Talk The Egg In a Nutshell

culture adventures tragedy catching up open source commons egg panelists nutshell angular asp asymmetry serkan eric berry changelog access fund pia mancini tidelift nadia eghbal lisa halliday codefund iphreaks

SOS 016: Changing Open Source Culture With Serkan Holat

Devchat.tv Master Feed

Play Episode Listen Later Oct 29, 2019 55:24

Serkan is a freelance software developer who has been developing web applications since 2001. Lately he has been working with Angular and ASP.NET. He shares that he has been studying sustainability of open source issues since 2014 and also shares the abridged version of how he came to be involved with the open source community. Richard then asks Serkan to share more details on how he as a developer became interested in open source. He shares how as a developer working on proprietary software he often found himself working on similar solutions in different companies and he realized that he was building the same software solutions over and over. From this he concluded that open sourcing these types of projects would reduce the need to keep creating these projects by sharing the solutions between those that need them. Serkan points out the problem with the way open source works now is that it’s difficult to make money in it and as such he started looking for ways to fix this problem. He has the desire to find ways to move money from proprietary solutions into open source. Serkan asserts that the only real difference between proprietary software and open source software is licensing and furthermore that any software could be open source. The next topic discussed by the panelists is the changes they’ve seen in the last five years for funding open source. Serkan highlights that he believes that many companies are coming to understand that the future is positive with open source and those companies are beginning to move that way. Richard responds by sharing the importance of building structures around funding developers who decide to open source their software. Serkan moves the conversation to a deeper analysis of proprietary rights. The panelists discuss a survey of developers taken by Tidelift that shows that many professionals prefer open source software over proprietary software. The panelists then have a deeper discussion on what the reasons and drawbacks are for proprietary companies to turn open source. They also discuss how to create a tax of sorts that starts funding proprietary solutions turned open source and who would start that process. The open source experts then discuss how it is difficult to convince individual companies to go open source because their focus is on growing their business and making their own software prosper. Serkan responds to this by saying that open source is an investment that can pay dividends in the long run. They also share ideas on how working with governments and individuals could help to facilitate the transition to greater worldwide involvement in open source and propel the software industry forward to supporting open source. Serkan closes by reiterating some thoughts he shared earlier that governments are already involved in a wide range of programs that benefit all of its citizens. He shares how the sustaining of open source could be another program that is added to a government’s agenda and the opportunities that a government has to be of help in contrast to companies and individuals. Panelists Richard Littauer Pia Mancini Eric Berry Guest Serkan Holat Sponsors iPhreaks Adventures in Angular Adventures in .NET Links Angular ASP.NET Chad Whitacre Medium Catching Up w/ Nadia Eghbal Changelog.com sustainoss.org Tidelift Survey Tragedy of the Commons Picks Richard Littauer NPM Tools The Access Fund Pia Mancini Asymmetry by Lisa Halliday Emahoy Tsegué-Maryam Guébrou Eric Berry Airpods Case Oscoin Codefund Serkan Holat License Zero Marcin Jakubowski Ted Talk The Egg In a Nutshell

culture adventures tragedy catching up open source commons egg panelists nutshell angular asp asymmetry serkan eric berry changelog access fund pia mancini tidelift nadia eghbal lisa halliday codefund iphreaks

Episode 16: Changing Open Source Culture With Serkan Holat

Grey Mirror: MIT Media Lab’s Digital Currency Initiative on Technology, Society, and Ethics

Play Episode Listen Later Oct 29, 2019 55:28

Serkan is a freelance software developer who has been developing web applications since 2001. Lately he has been working with Angular and ASP.NET. He shares that he has been studying sustainability of open source issues since 2014 and also shares the abridged version of how he came to be involved with the open source community. Richard then asks Serkan to share more details on how he as a developer became interested in open source. He shares how as a developer working on proprietary software he often found himself working on similar solutions in different companies and he realized that he was building the same software solutions over and over. From this he concluded that open sourcing these types of projects would reduce the need to keep creating these projects by sharing the solutions between those that need them. Serkan points out the problem with the way open source works now is that it’s difficult to make money in it and as such he started looking for ways to fix this problem. He has the desire to find ways to move money from proprietary solutions into open source. Serkan asserts that the only real difference between proprietary software and open source software is licensing and furthermore that any software could be open source. The next topic discussed by the panelists is the changes they’ve seen in the last five years for funding open source. Serkan highlights that he believes that many companies are coming to understand that the future is positive with open source and those companies are beginning to move that way. Richard responds by sharing the importance of building structures around funding developers who decide to open source their software. Serkan moves the conversation to a deeper analysis of proprietary rights. The panelists discuss a survey of developers taken by Tidelift that shows that many professionals prefer open source software over proprietary software. The panelists then have a deeper discussion on what the reasons and drawbacks are for proprietary companies to turn open source. They also discuss how to create a tax of sorts that starts funding proprietary solutions turned open source and who would start that process. The open source experts then discuss how it is difficult to convince individual companies to go open source because their focus is on growing their business and making their own software prosper. Serkan responds to this by saying that open source is an investment that can pay dividends in the long run. They also share ideas on how working with governments and individuals could help to facilitate the transition to greater worldwide involvement in open source and propel the software industry forward to supporting open source. Serkan closes by reiterating some thoughts he shared earlier that governments are already involved in a wide range of programs that benefit all of its citizens. He shares how the sustaining of open source could be another program that is added to a government’s agenda and the opportunities that a government has to be of help in contrast to companies and individuals. Panelists Richard Littauer Pia Mancini Eric Berry Guest Serkan Holat Sponsors iPhreaks Adventures in Angular Adventures in .NET Links Angular ASP.NET Chad Whitacre Medium Catching Up w/ Nadia Eghbal Changelog.com sustainoss.org Tidelift Survey Tragedy of the Commons Picks Richard Littauer NPM Tools The Access Fund Pia Mancini Asymmetry by Lisa Halliday Emahoy Tsegué-Maryam Guébrou Eric Berry Airpods Case Oscoin Codefund Serkan Holat License Zero Marcin Jakubowski Ted Talk The Egg In a Nutshell Special Guest: Serkan Holat.

culture adventures tragedy catching up open source commons egg panelists nutshell angular asp asymmetry serkan eric berry changelog access fund pia mancini tidelift nadia eghbal lisa halliday codefund iphreaks

7.05: Chattanooga, China, and Subsidiarity

Winning Slowly

Play Episode Listen Later May 22, 2019 35:27

Localism is great! …but it is no panacea. Show Notes We look at everything from American racial history to the differences between Chattanooga’s and China’s “local” internets. Stephen gesticulating wildly! Links The New Sewer Socialists, Evan Malmgren, Logic An alternate ending to the tragedy of the commons, Nadia Eghbal, on Elinor Ostrom’s Governing the Commons: The Evolution of Institutions for Collective Action Ostrom noticed there are many situations where common resources are allocated efficiently, without intervention from the market or state. She explores, through a series of case studies, why this occurred, and under what conditions we could recreate these situations. Music Bali” by Ryan Dugré “Winning Slowly Theme” by Chris Krycho. Sponsors Many thanks to the people who help us make this show possible by their financial support! This month’s sponsors: Daniel Ellcey Jake Grant Jeremy W. Sherman Marnix Klooster Nathaniel Blaney Spencer Smith If you’d like to support the show, you can make a pledge at Patreon or give directly via Square Cash. Respond We love to hear your thoughts. Hit us up via Twitter, Facebook, or email!

american china institutions chattanooga governing localism elinor ostrom subsidiarity square cash nadia eghbal chris krycho

Nadia Eghbal, Protocol Labs: Why Give Away Money and How to Fund Digital Infrastructure

Play Episode Listen Later Jan 7, 2019 37:28

Nadia Eghbal, a researcher at Protocol Labs. We chat about her grant program to give people money on the internet and her current mindset towards funding digital infrastructure.

money fund giveaways digital infrastructure protocol labs nadia eghbal

Episode 50: Your First Open Source Contribution with VM Brasseur

Tech Done Right

Play Episode Listen Later Nov 28, 2018 39:39

Your First Open Source Contribution with VM Brasseur TableXI offers training for developers and product teams! For more info, email workshops@tablexi.com or go to http://tablexi.com/workshops. Guest VM Brasseur (https://twitter.com/vmbrasseur): Open Source consultant, Vice President of Open Source Initiative (https://opensource.org/), and Author of Forge Your Future with Open Source (https://pragprog.com/book/vbopens/forge-your-future-with-open-source). vmbrasseur.com (https://www.vmbrasseur.com/). Summary The Open Source world is large. It’s also complex and difficult to manage, especially for a novice. Our guest this week is VM Brasseur, who is the Vice President of the Open Source Initiative and the author of a new book from Pragmatic called Forge Your Future With Open Source. We talk how Open Source is different from free software, and how to get started in Open Source, how to pick a project, how to navigate a new project to make your first submission. We’ll also look at it from the other side, and talk about open source projects can make themselves more contributor-friendly. And we talk about the state of Open Source in general. We want to hear from you. What was your first open source experience like? Or, how do you handle new contributors on your project? Notes 03:40 - Misconceptions Keeping People From Contributing to Free and Open Source Software 05:27 - Overcoming Impostor Syndrome (https://en.wikipedia.org/wiki/Impostor_syndrome) 08:27 - Why Contribute to Open Source? 10:15 - What Project Do I Start With? - Valentia (https://valentinaproject.bitbucket.io) - Free Sewing (https://freesewing.org) 12:32 - Why NOT To Start With Documentation 14:24 - Getting Started With Your First Contribution - Code Triage (https://www.codetriage.com/) 20:20 - Advice For Navigating the Open Source Community 22:40 - The Importance Codes of Conduct 24:44 - The Evolution of Open Source - Open Source Initiative (https://opensource.org) - Open Source Definition (https://opensource.org/osd-annotated) - Updating GitHub From Rails 3.2 to 5.2 (https://githubengineering.com/upgrading-github-from-rails-3-2-to-5-2/) 35:29 - Join VM at the Seattle GNU/Linux Conference (https://seagl.org/) on November 9th & 10th! 36:33 - Advice For Maintainers Wanting to Make Projects Welcoming Related Episodes 20 Years of Web Development with Avdi Grimm and Sarah Mei (https://www.techdoneright.io/46) Open Source and Companies with Nell Shamrell-Harrington (https://www.techdoneright.io/28) The Social Responsibility of Coding with Liz Abinante (https://www.techdoneright.io/25) Open Source: The Big Picture with Nadia Eghbal (https://www.techdoneright.io/16) Open-Source Community Management and Safety With Coraline Ada Ehmke and Yana Carstens (https://www.techdoneright.io/8) Special Guest: VM Brasseur.

evolution vice president companies open source coding impostors contribution social responsibility pragmatic web development overcoming impostor syndrome open source initiative nadia eghbal avdi grimm nell shamrell harrington forge your future sarah mei vm brasseur

#31 - Sustaining the Underfunded: Nadia Eghbal

Future of Coding

Play Episode Listen Later Oct 12, 2018 88:37

Two years ago, Nadia Eghbal "stumbled onto the internet's biggest blindspot": sustainability of open-source. Her Ford Foundation report "Roads and Bridges" became an instant classic. She shined a light on the underappreciated roles of maintainers and how difficult it was for even vital projects to get enough funding for a single person full time. In this conversation, we discuss how she found "stumbled onto" this problem initially, and her road from the Ford Foundation to GitHub and now Protocol Labs. We discuss the challenges of indepdendent research and remote work... and how being able to find amazing friends and co-conspirators on Twitter somehow makes it all better. Nadia lays out her vision for the future of open source, and how we can tackle the human side of scaling open-source development. She also gives us a sneak preview of her current work on a new economic model for understanding how open-source software consumption scales. It doesn't scale costlessly, because "you have to make continual changes to it, either because people are submitting changes back to it, but also because software degrades over time. Knowledge degrades over time. You can't just release something once and be done with it." Notes and transcript at futureofcoding.org/episodes/31

bridges roads sustaining github ford foundation underfunded protocol labs nadia eghbal

PG Vlog #187 - benefits of the university-based research system

Play Episode Listen Later Aug 18, 2018

Support these videos: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Vlog-187-university-research-system.htm- [PG Podcast - Episode 41 - Steve Krouse on becoming an independent researcher](http://pgbovine.net/PG-Podcast-41-Steve-Krouse.htm)- [The independent researcher](https://nadiaeghbal.com/independent-research), by Nadia Eghbal- [Formal vs. informal software research](https://www.youtube.com/playlist?list=PLzV58Zm8FuBINl1vnkO_gA43jh6wVOZPE) (YouTube playlist)Recorded: 2018-08-19

university research benefits system vlog formal nadia eghbal pg podcast

PG Vlog #165 - formal vs. informal software research (Part 5) - the F-word: Funding

research software funding vlog f word informal nadia eghbal

Play Episode Listen Later Jul 2, 2018

Support these videos: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Vlog-165-formal-vs-informal-research-5.htm[YouTube playlist for this video series](https://www.youtube.com/playlist?list=PLzV58Zm8FuBINl1vnkO_gA43jh6wVOZPE)- [Unicorn Jobs](http://pgbovine.net/unicorn-jobs.htm)- [The independent researcher](https://nadiaeghbal.com/independent-research) by Nadia Eghbal- [My Twitter thread that inspired this video series](https://twitter.com/pgbovine/status/1013895004438200320) (see my webpage for archived version)(actual recording date was 2018-07-05)Recorded: 2018-07-02 (6)

PG Vlog #164 - formal vs. informal software research (Part 4) - unicorns are rare

research software unicorns rare vlog informal nadia eghbal

Play Episode Listen Later Jul 2, 2018

Support these videos: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Vlog-164-formal-vs-informal-research-4.htm[YouTube playlist for this video series](https://www.youtube.com/playlist?list=PLzV58Zm8FuBINl1vnkO_gA43jh6wVOZPE)- [Unicorn Jobs](http://pgbovine.net/unicorn-jobs.htm)- [The independent researcher](https://nadiaeghbal.com/independent-research) by Nadia Eghbal- [My Twitter thread that inspired this video series](https://twitter.com/pgbovine/status/1013895004438200320) (see my webpage for archived version)(actual recording date was 2018-07-04)Recorded: 2018-07-02 (5)

PG Vlog #163 - formal vs. informal software research (Part 3) - bootstrapping independent research

research software independent vlog bootstrapping informal nadia eghbal

Play Episode Listen Later Jul 1, 2018

Support these videos: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Vlog-163-formal-vs-informal-research-3.htm[YouTube playlist for this video series](https://www.youtube.com/playlist?list=PLzV58Zm8FuBINl1vnkO_gA43jh6wVOZPE)- [The independent researcher](https://nadiaeghbal.com/independent-research) by Nadia Eghbal- [My Twitter thread that inspired this video series](https://twitter.com/pgbovine/status/1013895004438200320) (see my webpage for archived version)(actual recording date was 2018-07-03)Recorded: 2018-07-02 (4)

PG Vlog #162 - formal vs. informal software research (Part 2) - alternatives to formal papers

Play Episode Listen Later Jul 1, 2018

Support these videos: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Vlog-162-formal-vs-informal-research-2.htm[YouTube playlist for this video series](https://www.youtube.com/playlist?list=PLzV58Zm8FuBINl1vnkO_gA43jh6wVOZPE)- [The independent researcher](https://nadiaeghbal.com/independent-research) by Nadia Eghbal- [The differences between tinkering and research](http://togelius.blogspot.com/2016/04/the-differences-between-tinkering-and.html) by Julian Togelius- [My Twitter thread that inspired this video series](https://twitter.com/pgbovine/status/1013895004438200320) (see my webpage for archived version)(actual recording date was 2018-07-03)Recorded: 2018-07-02 (3)

research software alternatives papers vlog informal nadia eghbal julian togelius

PG Vlog #161 - formal vs. informal software research (Part 1) - the role of research papers

Play Episode Listen Later Jul 1, 2018

Support these videos: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Vlog-161-formal-vs-informal-research-1.htm[YouTube playlist for this video series](https://www.youtube.com/playlist?list=PLzV58Zm8FuBINl1vnkO_gA43jh6wVOZPE)- [DS.js paper from my lab](http://pgbovine.net/dsjs-paper.htm) (an example of academic software research)- [The independent researcher](https://nadiaeghbal.com/independent-research) by Nadia Eghbal- [The differences between tinkering and research](http://togelius.blogspot.com/2016/04/the-differences-between-tinkering-and.html) by Julian Togelius- [My Twitter thread that inspired this video series](https://twitter.com/pgbovine/status/1013895004438200320) (see my webpage for archived version)(actual recording date was 2018-07-02)Recorded: 2018-07-02 (2)

software vlog ds informal research papers nadia eghbal julian togelius

PG Vlog #160 - formal vs. informal software research (Part 0) - what's this series about?

research software vlog informal nadia eghbal

Play Episode Listen Later Jul 1, 2018

Support these videos: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Vlog-160-formal-vs-informal-research-0.htm[YouTube playlist for this video series](https://www.youtube.com/playlist?list=PLzV58Zm8FuBINl1vnkO_gA43jh6wVOZPE)- [The independent researcher](https://nadiaeghbal.com/independent-research) by Nadia Eghbal- [My Twitter thread that inspired this video series](https://twitter.com/pgbovine/status/1013895004438200320) (see my webpage for archived version)(actual recording date was 2018-07-07)Recorded: 2018-07-02 (1)

PG Podcast - Episode 37 - Henry Zhu on humans of open-source software

Play Episode Listen Later Jun 12, 2018

Twitter: https://twitter.com/pgbovineSupport with Patreon, PayPal, or credit/debit: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Podcast-37-Henry-Zhu.htm- [Things You Should Never Do, Part I - Netscape rewriting their entire codebase](https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/) by Joel Spolsky- [Google and HTTP](http://this.how/googleAndHttp/) by Dave Winer- [#SmooshGate FAQ](https://developers.google.com/web/updates/2018/03/smooshgate)- [Diligence, Patience, and Humility](https://www.oreilly.com/openbook/opensources/book/larry.html) by Larry Wall- [Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure](https://www.fordfoundation.org/library/reports-and-studies/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/) by Nadia Eghbal- [PG Podcast - Episode 35 - Audrey Boguchwal + Nadia Eghbal on sustainable online communities](http://pgbovine.net/PG-Podcast-35-Audrey-Boguchwal-and-Nadia-Eghbal.htm)Recorded: 2018-06-13 (2)

google humility humans paypal roads diligence open source software dave winer joel spolsky nadia eghbal henry zhu larry wall pg podcast

PG Podcast - Episode 35 - Audrey Boguchwal + Nadia Eghbal on sustainable online communities

Play Episode Listen Later Feb 24, 2018

Support with Patreon, PayPal, or credit/debit: http://pgbovine.net/support.htmTwitter: https://twitter.com/pgbovinehttp://pgbovine.net/PG-Podcast-35-Audrey-Boguchwal-and-Nadia-Eghbal.htm- [Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure](https://www.fordfoundation.org/library/reports-and-studies/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/)- [Nadia's articles on sustainability and open source](http://nadiaeghbal.com/oss/)- [Nadia's writing on Medium](https://medium.com/@nayafia)- [Python Core Mentorship](https://www.python.org/dev/core-mentorship/)- [Don't just open the door, welcome people through it](https://snarky.ca/dont-just-open-the-door-welcome-people-through-it/)- [Brett Cannon: Setting Expectations for Open Source Participation](https://www.youtube.com/watch?v=-Nk-8fSJM6I)- [MIT Squadbox project](http://squadbox.org/)Recorded: 2018-02-25

medium sustainable paypal roads online communities nadia eghbal pg podcast

Episode 28: Open Source and Companies with Nell Shamrell-Harrington

Tech Done Right

Play Episode Listen Later Jan 16, 2018 39:32

Open Source and Companies with Nell Shamrell-Harrington Follow us on Twitter! @techdoneright (https://twitter.com/tech_done_right) Also, please leave us a review on Apple Podcasts (https://itunes.apple.com/us/podcast/tech-done-right/id1195695341?mt=2)! Guest Nell Shamrell-Harrington (https://twitter.com/nellshamrell): Senior Software Development Engineer at Chef (https://www.chef.io/), CTO of Operation Code (https://operationcode.org/). nellshamrell.com (http://www.nellshamrell.com/) Summary What's it like to run an Open Source project as part of your day job? How does open source change when it's backed by a company? Why is it useful for a company to run open source projects? Nell Shamrell-Harrington, who runs the Habitat project for Chef is on the show to talk about open source contributing and maintenance. You'll come away with some ways to be a better contributor and maintainer. Notes 01:57 - Nell’s History Working on Open Source - gibbon (https://github.com/amro/gibbon) 03:37 - Open Source Governance - The FreeBSD Project (https://www.freebsd.org/) 07:07 - Chef, Having Community Discussions, and Handling RFCs and Contributions - Chef Compliance (https://docs.chef.io/chef_compliance.html) - Habitat (https://www.habitat.sh/) 13:48 - Being Involved in DevProgress (https://devprogress.us/) and Campaign Volunteering as a Developer 20:57 - Closed Source vs Open Source Development 25:48 - Advice for Getting Started in Open Source and Emphasis on Defined Codes of Conduct 27:44 - Accepting & Reviewing Pull Requests and Being Clear on What Tools Are For and Looking For in Contributions 32:29 - Common Mistakes Among Contributors and Maintainers - RailsConf 2017: Teaching RSpec to Play nice with Rails by Sam Phippen (https://www.youtube.com/watch?v=jyPfrK1y1nc) 34:55 - Keeping Open Source Projects Sustainable Related Episodes Software, Open Source, and Rails With Eileen Uchitelle and Andrew Horner (http://www.techdoneright.io/7-rails-with-eileen) Open-Source Community Management and Safety With Coraline Ada Ehmke and Yana Carstens (http://www.techdoneright.io/8) Open Source: The Big Picture with Nadia Eghbal (http://www.techdoneright.io/16) Special Guest: Nell Shamrell-Harrington.

advice chefs companies accepting cto getting started open source habitat emphasis rails looking for nadia eghbal being involved operation code being clear nell shamrell harrington sam phippen

PG Podcast - Episode 31 - Nadia Eghbal on fostering sustainable creativity

diversity medium worse hopes best practices roads big picture mid open source github researching standardization maintainers nadia eghbal

Play Episode Listen Later Nov 13, 2017

Support these videos: http://pgbovine.net/support.htmhttp://pgbovine.net/PG-Podcast-31-Nadia-Eghbal.htmRecorded: 2017-11-14

creativity sustainable fostering nadia eghbal pg podcast

Episode 16: Open Source: The Big Picture with Nadia Eghbal

Tech Done Right

Play Episode Listen Later Jul 26, 2017 36:58

Open Source: The Big Picture with Nadia Eghbal Follow us on Twitter @techdoneright (https://twitter.com/tech_done_right), leave us a review on Apple Podcasts (https://itunes.apple.com/us/podcast/tech-done-right/id1195695341?mt=2), and please sign up for our newsletter (http://www.techdoneright.io/newsletter)! Guest Nadia Eghbal (https://twitter.com/nayafia): Works on Open Source Initiatives at GitHub (https://github.com/), Author of Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure (https://www.fordfoundation.org/library/reports-and-studies/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/); Read her essays on Open Source on Medium (https://medium.com/@nayafia) Summary The Internet runs on Open Source. Open Source runs on maintainers and contributors. Is that sustainable? We talk to Nadia Eghbal about her work documenting and analyzing the Open Source ecosystem. How did we get here, and how did GitHub change Open Source? Nadia answers why Open Source makes economic sense, and discusses what can make projects more sustainable (hint: it's not just money). Notes 01:22 - Researching the Open Source Community 03:14 - How the Relationship Between Open Source and the Rest of Technology Changed in the Mid-2000s 07:22 - Where is Open Source going? How will it evolve? 09:28 - What do successful projects do that others can learn from? 12:34 - Standardization of Funding 13:33 - As Projects Mature 17:26 - The Open Source Ecosystem: Excludable and Non-Excludable 21:42 - The Reputational Economy 25:20 - “Worse is Better”: Sharing Between Ecosystems; Fragmentation 30:03 - Diversity and Being New in the Open Source Community 34:16 - Hopes for the Future: Better Tooling for Maintainers, Shared Understanding of Best Practices, Supporting Open Source

GitHub's Open Source Survey (2017) (The Changelog #252)

Play Episode Listen Later Jun 9, 2017 78:26 Transcription Available

On Friday, June 2, 2017 – GitHub announced the details of their Open Source Survey – an open data set on the open source community for researchers and the curious. Frannie Zlotnick, Nadia Eghbal, and Mikeal Rogers joined the show to talk through the backstory and key insights of this open data project which sheds light on the broader open source community’s attitudes, experiences, and backgrounds of those who use, build, and maintain open source software.

development code software hackers survey programming open source github software engineering changelog nadia eghbal mikeal rogers

GitHub's Open Source Survey (2017)

The Changelog

Play Episode Listen Later Jun 9, 2017 78:26 Transcription Available

On Friday, June 2, 2017 – GitHub announced the details of their Open Source Survey – an open data set on the open source community for researchers and the curious. Frannie Zlotnick, Nadia Eghbal, and Mikeal Rogers joined the show to talk through the backstory and key insights of this open data project which sheds light on the broader open source community’s attitudes, experiences, and backgrounds of those who use, build, and maintain open source software.

development code software hackers survey programming open source github software engineering changelog nadia eghbal mikeal rogers

a16z Podcast: The Changing Culture of Open Source

a16z

Play Episode Listen Later Apr 8, 2017 39:48

The culture of open source has changed across generations, from previous ones that had to fight for the brave new way -- to the current "GitHub generation" that not only accepts open source, but expects it as the default. Which makes sense given that open source powers so much of the software world today... and by the way, that's not just tech companies but hospitals and banks; it touches everyone. Open source culture has also moved away from cults of personality and top-down models to drive the vision for open source projects, to decentralized individual contributor identities and more micro-sized projects within projects. So what does that mean for the governance of open source, whether it's by institution or foundation, or a "healthy" or "popular" project? Should we invert, always invert to make sure open source code "lands" and is committed by default -- as opposed to going through a cabal of gatekeepers first? This episode of the a16z Podcast -- featuring Nadia Eghbal (who formerly researched the sustainability of open source projects for Ford Foundation, and is now in community programs at GitHub) and Mikeal Rogers (community manager and more at Node.js Foundation) in conversation with Sonal Chokshi -- covers all this and more. Is open source simply too loaded a term? Is there no sense of ownership? How best to manage a project or resolve conflicts? After all, at the end of the day, it's about people, not just code... The views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. This content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments and certain publicly traded cryptocurrencies/ digital assets for which the issuer has not provided permission for a16z to disclose publicly) is available at https://a16z.com/investments/. Charts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.

foundation open references charts open source github node andreessen horowitz ford foundation community management a16z enterprise software changing culture nadia eghbal sonal chokshi mikeal rogers

#104: Navigating the Open Source Galaxy

The New Stack Analysts

Play Episode Listen Later Aug 16, 2016 52:02

In this episode of The New Stack Analysts, we explore the ways in which open source projects interconnect with one another, how open source communities can both increase and improve their contributions, and the issues facing open source projects hoping to operate at scale. The New Stack Founder Alex Williams spoke with Cisco CTO Ken Owens along with GitHub Community Programs researcher Nadia Eghbal to hear their thoughts on these topics and more. Learn more at: https://thenewstack.io/navigating-open-source-galaxy/ Watch on YouTube: https://www.youtube.com/watch?v=FJVtJyDEDT0

navigating galaxy open source nadia eghbal new stack analysts

Open Source, Then and Now (Part 1) (Request For Commits #1)

Play Episode Listen Later Aug 4, 2016 76:31 Transcription Available

Nadia Eghbal and Mikeal Rogers kick off Season 1 of Request For Commits with a two part conversation with Karl Fogel — a software developer who has been active in open source since its inception.

community sustainability software open source commits oss changelog nadia eghbal mikeal rogers karl fogel

Open Source, Then and Now (Part 2) (Request For Commits #2)

Hanselminutes - Fresh Talk and Tech for Developers

Play Episode Listen Later Aug 4, 2016 64:38 Transcription Available

Nadia Eghbal and Mikeal Rogers kick off Season 1 of Request For Commits with a two part conversation with Karl Fogel — a software developer who has been active in open source since its inception.

community sustainability software open source commits oss changelog nadia eghbal mikeal rogers karl fogel

Open Source, Then and Now (Part 1)

Request For Commits

Play Episode Listen Later Aug 4, 2016 76:31 Transcription Available

Nadia Eghbal and Mikeal Rogers kick off Season 1 of Request For Commits with a two part conversation with Karl Fogel — a software developer who has been active in open source since its inception.

community sustainability software open source oss changelog nadia eghbal mikeal rogers karl fogel

Open Source, Then and Now (Part 2)

Request For Commits

Play Episode Listen Later Aug 4, 2016 64:38 Transcription Available

Nadia Eghbal and Mikeal Rogers kick off Season 1 of Request For Commits with a two part conversation with Karl Fogel — a software developer who has been active in open source since its inception.

community sustainability software open source oss changelog nadia eghbal mikeal rogers karl fogel

Funding Open Source with Nadia Eghbal

Play Episode Listen Later Apr 28, 2016 33:30

Former VC Nadia Eghbal is exploring the world of open source and how tech gets funded. Her investigative work is currently supported by The Ford Foundation as she explores the way that the public infrastructure of the Internet gets built. She talks with Scott about how Open Source Software gets funded!

internet funding open source ford foundation open source software nadia eghbal

The Past, Present, and Future of Open Source

Open Source – Software Engineering Daily

Play Episode Listen Later Apr 8, 2016 19:39

Nadia Eghbal joins us as the host of today’s show to discuss the past, present, and future of open-source software. This monologue was adapted from Nadia’s article, We’re in a brave, new post open source world. In this episode, Nadia describes the origins of open-source in the Free software movement, its rise to popularity, and The post The Past, Present, and Future of Open Source appeared first on Software Engineering Daily.

future past present open source software engineering daily nadia eghbal

Ep. #17, Open Source Economics

To Be Continuous

Play Episode Listen Later Apr 5, 2016 78:03

In this episode of To Be Continuous, Edith and Paul are joined by Sean Byrnes, CEO of Outlier.ai, and Nadia Eghbal. The group discusses open source economics, and examines several potential evolutions of adding money to the open source equation.

ceo economics open source outliers nadia eghbal sean byrnes

Ep. #17, Open Source Economics

To Be Continuous

Play Episode Listen Later Apr 5, 2016 78:03

In this episode of To Be Continuous, Edith and Paul are joined by Sean Byrnes, CEO of Outlier.ai, and Nadia Eghbal. The group discusses open source economics, and examines several potential evolutions of adding money to the open source equation. The post Ep. #17, Open Source Economics appeared first on Heavybit.

ceo economics open source outliers nadia eghbal heavybit sean byrnes

Funding open source (The Changelog #193)