text stringlengths 0 2.46k |
|---|
**Yaron Schneider:** Correct. |
**Adam Stacoviak:** ...no corporate overlord necessarily... |
**Yaron Schneider:** Yeah. |
**Adam Stacoviak:** Okay. How has that benefited Diagrid? How has that benefited your company in terms of commercializing this open source, your journey to get venture-backed funding? How has that helped in all ways the business angle of -- has it been a lot easier, I suppose, to go this route? |
**Yaron Schneider:** So there's a lot of commercial entities that back open source projects that are not CNCF projects. I can name many. But I think the one major benefit of being in the CNCF was looking at the contributor growth since we joined, because Dapr picked up a lot of new contributors ever since we joined in.... |
**Adam Stacoviak:** Right. What's the license of Dapr itself, and is there anybody else who can do a Diagrid? |
**Yaron Schneider:** Yes, everyone can. |
**Adam Stacoviak:** Could Jerod and I be like "Hey, we're leaving here today and we're gonna compete." |
**Yaron Schneider:** Yes, you can definitely do that. Dapr is Apache 2. That's mandated by the CNCF. So all CNCF projects are under an Apache 2 license, which is very flexible in how you commercialize it. You can do whatever you want, you can start your own service around it, Dapr and any other project in the CNCF. |
**Adam Stacoviak:** So you're competing on, I guess, your ability to do the managed service the best, right? |
**Yaron Schneider:** Yes. |
**Adam Stacoviak:** So if somebody competes with you, they have the same Dapr core, or whatever it might be. They can spin up a version of that. Now, it wouldn't be cool necessarily to do that, but they could. It's possible. |
**Yaron Schneider:** They could. Yeah, definitely. And we welcome competition. Look what's happening with Argo. It's a CNCF project that picked up a lot of traction \[unintelligible 01:15:49.03\] there's multiple companies trying to commercialize it today. Microsoft is commercializing Dapr. I actually built Dapr into a... |
\[01:16:10.05\] But yes, we believe that in Diagrid, because Mark and I, my co-founder, created the Dapr project, and we're core maintainers of the project, and we're also on the Dapr steering committee, alongside Alibaba, Intel and Microsoft, then we have a very good overview into the project, and we have a very good ... |
**Jerod Santo:** But you didn't name yourself Dapr Inc. |
**Yaron Schneider:** Yes, yes. We didn't. For two reasons. One is - well, a legal requirement. We can't, because Dapr is under trademarks of CNCF. So that limits you. But even if it didn't have that limitation, we still wouldn't do that, because we don't want to tie the fate of our company to one single project. At som... |
**Jerod Santo:** Is there a parallel to Dapr, or a comparable that people may know about? |
**Yaron Schneider:** Yeah, so Dapr is really polyglot, in that you can talk to it from any language. I think if you look at individual programming languages, you'll find equivalents, like Spring, for example, for Java. Or Spring Cloud. So it's like a Java framework that gives you all of these developer primitives. It's... |
**Jerod Santo:** Okay. That helps. So are there drawbacks to the polyglot style, versus -- I mean, I'm sure there are, but HTTP works pretty well, so... |
**Yaron Schneider:** Yeah, it does. I mean, if you're writing an extremely low-latency application, Dapr might not be for you, because you still have an extra network \[unintelligible 01:18:18.26\] |
**Jerod Santo:** Right. |
3:And so if you're writing a trading application, and you need microseconds of latency, Dapr might not be a fit for you. But we do believe that in terms of performance, it's good for 90% plus of use cases. Another reason why Dapr might not be for you is if you need really, really specific features from like Kafka or AW... |
**Jerod Santo:** That makes sense. The lowest common denominator across what you're trying to do. |
**Yaron Schneider:** Yeah. |
**Jerod Santo:** Cool. Anything else? Future? Is the project mature in terms of feature set, or is it like you've got huge plans for Dapr? Do you feel like it's kind of done? |
**Yaron Schneider:** We have huge plans. We've recently added workflows, which is really nice... So a workflow as code type of programming model where you can tell your code "Hey, sleep for 100 years and then kick off this process", and that'll be reliable and secure. And we're adding cryptography APIs, blob streaming ... |
**Jerod Santo:** Awesome. |
**Adam Stacoviak:** Very cool. Thanks, Yaron. |
**Yaron Schneider:** Thank you for having me. Thank you. |
• GitHub Sponsors is now generally available for companies and individuals to support maintainers |
• Previous challenges with corporate credit cards are resolved with new payment options such as invoices and POs |
• Open job position for team to change open source ecosystem to fund maintainers beyond just a paycheck |
• GitHub is experimenting with diverse backgrounds and ideas to bring new perspectives to the role |
• Ultimate goal is to make open source software successful by providing ways for maintainers to invest time and energy |
• New companies are signing up for Sponsors, but there is no established norm for corporate giving |
• GitHub is working to establish norms and provide tools for companies to understand and support dependencies |
• Typical corporate giving is still uncertain, but $2k per engineer is a suggested starting point |
• Pricing models for open source projects, including the need for an on-ramp to fair funding |
• Maintainer guilt and the challenges of succession planning for open source projects |
• The importance of community building and trust in open source project management |
• Lessons from nonprofits in terms of succession planning and community building |
• Establishing clear roles and responsibilities within open source projects to ensure non-breakage and ease of transition |
• Strategies for growing and sustaining open source projects, including documenting problem-solving processes and promoting knowledge sharing among contributors |
• GitHub Sponsors and Accelerator program |
• Challenges of funding open source projects |
• GitHub Fund partnership with Microsoft's M12 venture capital fund |
• Accelerator program application process |
• Outreach and support for maintainers with high activity on GitHub |
• Future plans for GitHub Sponsors and Accelerator program |
• Hiring a new lead for the Sponsors and Accelerator teams |
• Exploring additional funding options, such as bug bounties |
• Ideas for GitHub Sponsors' future development |
• Accelerator program and its benefits for open source projects |
• Maintainer dashboard for open source contributors and maintainers |
• Centralizing resources and services for open source maintainers |
• Business and administrative tasks for open source project management |
• Tools and support for developers and maintainers to sustain their projects |
• Dependency graph and its role in distributing funds to open source creators |
• Trickle-down compensation for creators based on their project's usage and impact |
• Discussion of GitHub Sponsors and its potential for scaling with more companies |
• Strategies for maintainers to promote and use GitHub Sponsors, including using bots |
• Challenges and considerations for maintainers in receiving donations through GitHub Sponsors, including tax implications and alternative funding methods |
• Interview with Dr. Dawn Foster about her Ph.D. research on the Linux Kernel, including her study on collaboration and communication within the kernel community |
• Discussion of the benefits of open source and public data for research, including the CHAOSS project and its focus on Community Health Analytics for Open Source Software |
• Overview of the CHAOSS project and its goals, including defining metrics and developing software for open source community analysis |
• Augur and GrimoireLab are software projects that gather data from various sources, including GitHub and Slack, to analyze project health. |
• Dr. Dawn Foster advocates for looking at trends in project health metrics, rather than assigning a score, due to the complexity of individual project workflows. |
• Understanding the context of project metrics is crucial, as automated processes like bots can skew data and mislead interpretation. |
• The goal of analyzing project health is to identify areas for improvement and provide actionable insights for maintainers and contributors. |
• CHAOSS (a project mentioned in the transcript) provides tools to collect and analyze project data, including Augur and GrimoireLab, which use different approaches to store and display data. |
• The end users of project health metrics include maintainers, contributors, and individuals considering participation in a project, each with different goals and priorities. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.