text stringlengths 0 2.46k |
|---|
• Comparison of CHAOSS and Augur tools for project metrics and dashboards |
• Four key metrics used by Dr. Dawn Foster's team: response time, change request closure ratio, release frequency, and contributor risk |
• Importance of contributor metrics and throughput in measuring project health |
• Use of CHAOSS tools by big companies with open source program offices |
• Challenges and limitations of scoring project health and comparing different projects |
• Need for project-specific interpretation of metrics and consideration of external factors affecting project health |
• Metrics for improving open source projects and identifying areas for improvement |
• Recruiting outside contributors to open source projects |
• Governance models for open source projects and how they vary by project |
• CHAOSS (Community Health Analytics for Open-Source Systems) and its governance templates |
• Drupal's shift towards ambitious digital experiences and its current use cases |
• Angie Byron's transition from the Drupal community to working with data platforms |
• Angie Byron's current role in the Drupal community is focused on strategic decisions and big-picture thinking, rather than day-to-day involvement. |
• She aims to empower new leaders and provide mentorship to incoming product managers for Drupal. |
• Angie is involved in documenting the governance structure and process for Drupal, but acknowledges that more documentation is needed. |
• She discusses the challenges of repeating herself and the importance of putting process into written form. |
• The conversation touches on the idea of using AI-powered tools to turn transcribed conversations into documentation. |
• Angie Byron explains her interest in data platforms and community management, and how she is drawn to cracking the code of how different language frameworks can work together. |
• Open source data infrastructure governance |
• Comparison of open source projects, including MySQL, Postgres, and MongoDB |
• SSPL and BSL licenses and their implications for open source projects |
• Challenge of sustaining open source projects without stable funding models |
• Spectrum of open source approaches, from OSI-compatible to copyleft licenses |
• OSI needs to address the issue of companies profiting from open source software while maintainers struggle to make a living |
• Angie Byron suggests expanding the definition of open source or creating a new license model that allows for maintainers to thrive in situations where they are profiting |
• The OSI's stance on the SSPL and BSL licenses has not changed, and they have not addressed the issue further |
• Ivan's approach to open source aligns with Angie Byron's values, as they use open source technologies and do not try to lock customers into proprietary solutions |
• The conversation touches on the need for a spectrum of licenses that allow for different levels of profiting from open source software |
• Companies like Redpanda and Ivan are seen as positive examples of open source companies that align with the values of the maintainers. |
• Role of Director of Community at an open source organization |
• Community engagement and events, such as meetups and forums |
• Interaction with OSPO (Open Source Program Office) and its role in supporting open source projects |
• Maintainer succession planning and finding ways to step back |
• Provisional maintainers and progression model for commit access |
• Term limits for committers and forced vacation concept to prevent burnout |
• Prioritizing community well-being and preventing over-reliance on individual maintainers |
• Analogies for being a "linchpin" vs. a "cog" in a team or system |
• Discussion of pressure and responsibility that comes with being a linchpin |
• Argument that being a purposeful cog is a more desirable role |
• Use of drummer in a band as an analogy for being a cog |
• Reference to Seth Godin's book "Linchpin" and its emphasis on being a linchpin |
• Critique of the linchpin concept and its potential drawbacks |
**Adam Stacoviak:** GitHub Sponsors... What is the state of GitHub Sponsors? |
**Stormy Peters:** So GitHub Sponsors is now generally available for companies, as well as individuals, to donate money to maintainers. Or give money to maintainers, not donate. |
**Adam Stacoviak:** Yeah. It's been a journey. You've had a couple people in charge of it, and the last time we talked to Jessica Lord, she was -- just about a year and a half ago, was it? |
**Jerod Santo:** Probably... |
**Adam Stacoviak:** She came back to GitHub. She was a boomerang. |
**Stormy Peters:** Yeah. |
**Adam Stacoviak:** She loves GitHub so much... |
**Stormy Peters:** I'm glad that she came back. |
**Jerod Santo:** Yeah. She's awesome. |
**Adam Stacoviak:** She's not still in charge of GitHub Sponsors, right? |
**Stormy Peters:** She's not doing Sponsors now. |
**Adam Stacoviak:** Okay. Is anyone in charge of it? Who is in charge of it? How does it work? |
**Stormy Peters:** We actually have an open job rec right now. If you would like to be in charge of it, you could apply. |
**Adam Stacoviak:** Gosh... I could slay that. |
**Stormy Peters:** But it's actually for a team that's going to be looking at how to change the open source ecosystem so that we fund maintainers in ways that aren't just a paycheck. |
**Adam Stacoviak:** Yeah. It's a tough job. Who could do that job well? what would they have done beforehand to do that job well? |
**Stormy Peters:** It's been kind of fun trying to recruit. We really want someone who's passionate about open source software, who has some kind of background in it. |
**Adam Stacoviak:** We love open source. You know that, right? |
**Stormy Peters:** Yeah. |
**Adam Stacoviak:** We could pair up on that job, Jerod. |
**Jerod Santo:** We've got jobs... |
**Stormy Peters:** I've also interviewed people who were in insurance before, and so just in insurance models... I've interviewed people that were in venture capital money... We're just kind of experimenting with who can bring new ideas to this space. |
**Adam Stacoviak:** It has to begin with the desire. What is GitHub optimizing for when it comes to sponsors? What does GitHub want with Sponsors in general? What are the possibilities? |
**Stormy Peters:** \[06:11\] Our ultimate goal is to make open source software successful. So that means providing ways for maintainers to have time and energy to invest in open source software. But part of that solution is helping companies understand what dependencies they have, and making sure that software is secur... |
**Jerod Santo:** Right. That sounds like a challenge. So you said it is now available to companies... |
**Stormy Peters:** It was always available to companies, but until recently, they had to pay via credit card, which - how many people at a company can put a couple hundred thousand dollars on their credit card? So we added things like invoices, and normal corporate things. |
**Adam Stacoviak:** POs, and stuff like that, right? |
**Jerod Santo:** I see. So you greased the kids, as they say, for companies to be able to actually give at a higher clip than they could with some sort of corporate credit card. |
**Stormy Peters:** Yeah. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.