text stringlengths 0 2.46k |
|---|
[4742.76 --> 4743.10] Cool. |
[4743.50 --> 4744.18] Anything else? |
[4744.84 --> 4748.24] Future, is the project mature in terms of feature set? |
[4748.34 --> 4750.78] Or is it, like, you got huge plans for Dapr? |
[4750.96 --> 4751.28] Yeah. |
[4751.42 --> 4752.28] And you feel like it's kind of done? |
[4752.34 --> 4753.18] We have huge plans. |
[4753.32 --> 4755.86] We've recently added workflows, which is really nice. |
[4755.86 --> 4766.34] So very, you know, 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 it'll be reliable and secure. |
[4766.92 --> 4771.90] And we're adding cryptography APIs, blob streaming APIs, document store APIs, SQL APIs. |
[4772.28 --> 4774.22] There's a whole world of APIs getting added to Dapr. |
[4774.22 --> 4778.16] We have eight today and we're going strong on 12, I want to say, in the next year. |
[4778.70 --> 4778.96] Awesome. |
[4779.50 --> 4779.98] Very cool. |
[4780.44 --> 4780.80] Thanks, Jaron. |
[4781.16 --> 4781.64] Thank you. |
[4781.84 --> 4782.54] Thanks for having me. |
[4782.70 --> 4783.22] Thank you. |
[4783.90 --> 4784.18] Jaron. |
[4784.72 --> 4785.16] Jaron. |
[4785.36 --> 4785.76] Jaron. |
[4786.16 --> 4786.62] My bad. |
[4786.70 --> 4787.12] Thanks, Jaron. |
[4787.18 --> 4787.72] My bad, Jaron. |
[4790.98 --> 4793.88] Okay, that completes our transition to Apple. |
[4794.08 --> 4795.42] I mean, well, that's the wrong announcement. |
[4795.48 --> 4795.82] My bad. |
[4795.82 --> 4803.86] That completes our Open Source Summit North America 2023 in Vancouver, Canada coverage. |
[4804.30 --> 4815.84] Big, big, big thank you to our friends over at GitHub for sponsoring our efforts to get there and get all this awesome hallway track coverage and bring it back. |
[4815.86 --> 4818.04] Cut it up and make it awesome. |
[4818.04 --> 4821.28] And then share it with you because, well, we love you. |
[4821.28 --> 4826.22] Okay, so if you want to give us some feedback on this episode, the link is in the show notes. |
[4826.34 --> 4828.40] But one more thing. |
[4828.46 --> 4834.54] Coming up next, speaking of Apple coverage, we have our Friday show coming up. |
[4834.54 --> 4837.08] The next change log and friends. |
[4837.08 --> 4842.34] We have Mike McQuaid joining us for WWDC coverage. |
[4842.68 --> 4845.74] Vision Pro, all the updates, everything. |
[4845.74 --> 4850.22] And then next week on this show, we're talking pass keys. |
[4850.46 --> 4852.96] It's going to be such a fun conversation. |
[4853.12 --> 4856.14] If you want to know about pass keys, come back next week. |
[4856.62 --> 4857.48] We've got something for you. |
[4858.00 --> 4858.56] But that's it. |
[4858.56 --> 4859.40] This show is done. |
[4859.52 --> 4866.38] Big thank you to our friends over at Fastly, over at Fly, and also our friends at TypeSense. |
[4866.92 --> 4874.28] And of course, the infamous and also famous brake master cylinder because those beats, well, they're banging. |
[4874.82 --> 4875.40] That's it. |
[4875.62 --> 4876.32] This show's done. |
[4876.78 --> 4877.32] We'll see you tomorrow. |
[4877.32 --> 4877.38] We'll see you tomorrow. |
• Maintainer Month series by the Linux Foundation's Open Source Summit North America 2023 |
• Issues with open source software maintainers, including finding balance, understanding project health, and getting funding |
• GraphQL API by Square, currently in OpenAlpha, seeking feedback |
• GitHub Sponsors, now generally available for companies and individuals to support maintainers |
• Job opening for a team to change the open source ecosystem to fund maintainers beyond just a paycheck |
• GitHub is experimenting with new insurance models and venture capital funding to support open-source software |
• Sponsors are a key part of GitHub's business model, with a goal of making open-source software successful by providing maintainers with time and energy to invest in their projects |
• GitHub offers tools to help companies understand and manage their dependencies, and has made it easier for companies to sponsor open-source projects by adding invoicing and corporate payment options |
• The new sponsor feature has led to increased interest and participation from companies, with $30 million in flow-through in the beta program and new companies signing up for it |
• Companies are looking for ways to support open-source software, but may be hesitant to give too little or not enough, and GitHub is trying to establish norms for corporate sponsorship of open-source projects |
• A suggested guideline for corporate sponsorship is $2,000 per engineer per year, but there are multiple ways to calculate sponsorship amounts. |
• Pricing pages for SaaS companies and the concept of fairness in funding open source projects |
• Difficulty in determining fair funding levels for open source projects |
• Maintainer guilt and the challenges of succession planning |
• Nonprofits as potential models for open source project management and succession planning |
• Importance of having a plan in place for succession and maintaining community trust |
• Potential for community-driven approaches to solve succession planning challenges |
• Clear role definitions and expectations for maintainers |
• Importance of documentation and writing out problem solutions |
• GitHub Sponsors features and future plans, including accelerator programs and contributing dependencies with one click |
• GitHub funds open-source projects with startup potential |
• GitHub accelerator program is an application process for select projects |
• GitHub sponsors allows users to support their favorite projects directly |
• The 1% of repositories with the most activity are a key focus for GitHub |
• Proactive outreach to high-activity projects is a potential future direction for GitHub sponsors |
• The GitHub accelerator and sponsors teams are being reorganized with a new lead |
• Discussing potential ways to provide funding to open-source projects through bug bounties |
• Exploring the possibility of integrating bug bounties into GitHub's issue system |
• The importance of leadership and finding a new leader for a team |
• The potential benefits of an accelerator program for open-source projects |
• The existence of a dashboard for maintainers to access GitHub Sponsors and related resources |
• A list of free software available for open-source contributors and maintainers |
• The concept of a "maintainer dashboard" is discussed, where maintainers can find available resources to sustain their projects |
• The dashboard should also help maintainers identify contributors, their activity level, and the origin of contributions (e.g. individual or organization) |
• The discussion highlights the need for a platform that helps developers and maintainers focus on their core work (writing code) rather than administrative tasks |
• The current model of open source projects often requires developers to take on business and marketing responsibilities in addition to coding |
• A dependency graph is mentioned as a way to track the distribution and usage of open source libraries and frameworks, allowing creators to receive compensation for their work. |
• Discussion of GitHub Sponsors and monetizing open-source projects |
• Use of bots to simplify interactions with GitHub Sponsors |
• Payment and tax implications for maintainers using GitHub Sponsors |
• Partnerships with other funding methods to expand options |
• Acquisition of CodeCov by Sentry and its impact on the Sentry platform |
• Combination of CodeCov and Sentry to improve developer experience and reduce bugs |
• Process for teams to get started with CodeCov and integrate it into their workflow |
• CodeCov's role is to analyze code coverage reports and provide feedback to developers and teams |
• CodeCov overlays code coverage on top of a code base and integrates with CICD |
• CodeCov provides actionable feedback to developers and teams on code coverage |
• CodeCov's goal is to make code coverage a team effort, not just a developer's responsibility |
• Dawn Foster from VMware discusses her experience attending conferences and reconnecting with people in the industry |
• Dawn Foster mentions her PhD research on the Linux kernel, specifically on network analysis of people within the kernel |
• The speaker spent 3.5 years studying the Linux kernel, gathering data on collaboration within the kernel. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.