text stringlengths 0 2.46k |
|---|
• Amazon's role in bridging the open source community with the company |
• Historical reputation issues with open source at Amazon |
• Efforts to change Amazon's approach to open source |
• Amazon's approach to contributing to open source, including community participation and supporting maintainers and projects |
• Challenges in justifying the business case for open source adoption |
• Role of the Open Source Programs Office (OSPO) in streamlining policies and making it easier for developers to use and contribute to open source |
• Longevity and history of the Amazon OSPO, with discussion of its origins and evolution. |
• Open source program offices (OSPOs) should go beyond compliance and focus on contributing to the community. |
• OSPOs have been around for 10-15 years and have evolved to share best practices and support each other. |
• Scaling OSPO efforts across a large company is a significant challenge. |
• Open source security is a major concern and involves collaboration with multiple teams. |
• The role of open source in AI is a growing area of interest and requires standardization. |
• Finding good people to build and lead an OSPO is difficult due to the specialized skills required. |
• The speaker has 25 years of experience in open source and previously held OSPO director roles at Silicon Graphics, SanDisk, and Comcast. |
• Coordination challenges of working with multiple divisions and understanding their engagement with open source |
• Lack of resources and team for open sourcing |
• Guidance for open sourcing library at Amazon, including approval process and documentation requirements |
• Role of the Open Source Program Office in reviewing and approving open source projects |
• Considerations for open sourcing, including maintenance, liability, and business alignment |
• Case of using company resources to open source code, and the company's stance on permitting individuals to do so |
• Amazon's involvement in various open source projects and initiatives, including the Linux Foundation |
• Amazon open source projects such as Bottle Rocket and Finch |
• Contribution to open-source projects like OpenJDK and Coreto |
• VJ Raji, CEO and founder of Statsig, and the inception story of the company |
• Statsig's mission to bring sophisticated tools to companies outside of the big tech firms |
• Jordan Harband, open-source maintainer, and his work on 400-450 npm packages |
• Temporal, a TC39 proposal, and its current status and potential issues |
• Date object in JavaScript has been criticized for its poor API, mutability, and lack of support for localization and time zones. |
• Temporal proposal aims to provide a more robust and reliable way to work with dates and times in JavaScript. |
• The proposal is inspired by the Java library Joda Time and provides seven new globals under the Temporal object for performing date and time operations. |
• Temporal is currently in stage 3 of the TC39 process and has been stable for two years, with no normative changes in the last TC39 meeting. |
• The speaker is a polyfill maintainer and believes Temporal is ready for implementation as a polyfill, which would make it stable and available for use in production. |
• Temporal is expected to replace libraries like Moment.js, which announced its deprecation two years ago. |
• The speaker plans to migrate their own library to Temporal as soon as it's usable, and is expecting a "big JS party" when it happens. |
• The speaker has enough money to work on open source full-time, but not enough to cover bills with their current income. |
• The speaker believes that profitable corporations using open source packages should contribute to their maintainers. |
• The speaker thinks that the lack of regulation and the absence of a capital incentive are the main reasons corporations don't contribute to open source maintainers. |
• The speaker suggests that a capital incentive is invisible and hard to quantify, but still has a significant impact on the bottom line. |
• The speaker discusses the difference between the most used and most supported packages, attributing it to the fact that most of their packages are transitive dependencies. |
• The speaker praises sites like Tidelift and Thanks.dev for surfacing and filtering money to transitive dependencies. |
• The speaker wishes to be better known to users of transitive dependencies and recognizes that promoting oneself is a distinct skill set. |
• Difficulty of becoming a full-time influencer in the niche of Askeenama |
• Heavy-handed approach to promoting the creator of Askeenama |
• Sponsorship and monetization, including the importance of corporate support |
• Impact of the current sponsorship situation on the creator's ability to work on open-source projects |
• Potential consequences if the situation doesn't change, including having to get part-time jobs to sustain open-source work |
• Personal commitment to maintaining GitHub and contributing to open-source projects daily since 2014 |
• Developers can use platforms like tide and thanks.dev to receive funding based on their dependencies and the value they provide to other developers. |
• The speaker has a large number of dependencies in his projects and has received funding through these platforms. |
• The speaker discusses the benefits and limitations of each platform, including the ability to receive granular control over funding distribution with thanks.dev. |
• The speaker notes that tide has a more enterprise-focused goal and is more of a patronage model. |
• The speaker considers implementing a sponsorship model, such as sponsorware, but notes that it may not be effective for his specific situation and type of packages. |
• The speaker mentions the challenges of implementing a sponsorship model, including the need to invest time and effort into developing a compelling offering. |
• Contradiction between open source philosophy and capitalist models |
• Company offers sponsorship in exchange for exclusive access to new feature |
• Developer's concerns about violating open source ethos |
• Model of withholding changes until a certain threshold of sponsors is reached |
• Discussion of potential sponsors and income streams for open source projects |
• Comparison of different sponsorship platforms and their effectiveness |
• Challenges of monetizing open source projects and compensating developers |
• Problem of "influencers" sitting on top of other projects and not contributing enough to the original project. |
• Problem of disrupted lives for public value providers |
• Tie Lift and GitHub's profit-driven models |
• Proposal for regulation: 1% of profit to open source infrastructure |
• Regulation as a solution to pipeline problem |
• Companies' reluctance to donate to open source |
• GitHub and Tie Lift's potential to do more |
• Staffing and funding challenges at GitHub and npm |
• Discussion about a booth and a panel on the impact of AI on developers |
• Acknowledgement of collaboration with Todd Lewis and team at All Things Open |
• Thanks to Fastly, Fly, Typesense, and Breakmaster Cylinder |
• Promotion of Changelog Beats' music on Spotify |
• Introductions of various individuals, including Jackenc and Kurz, and their respective roles or affiliations |
[0.00 --> 18.12] this week on the change law we're going back to the hallway track of all things open 2023 |
[18.12 --> 23.96] in raleigh north carolina today's episode features matthew sanabria former engineer |
[23.96 --> 31.04] at hashi corp who worked on terraform enterprise nithya ruff chief open source officer and head |
[31.04 --> 36.50] of the open source program office at amazon and last up today is jordan hardband open source |
[36.50 --> 42.84] maintainer at large with dependencies in most javascript apps out there there has been many |
[42.84 --> 49.16] changes this year in open source and each of these perspectives lends insight into the challenging |
[49.16 --> 55.58] and changing waters happening right now in open source and we have to give a tremendous thank |
[55.58 --> 61.70] you to todd lewis the organizer behind all things open it is one of our favorite conferences and |
[61.70 --> 68.28] todd lewis and team does a tremendous job leading that conference of course a big thank you to our |
[68.28 --> 74.90] friends and our partners at fastly and fly this podcast got you fast because fastly they are super |
[74.90 --> 81.10] fast globally check them out at fastly.com and our good friends at fly will help you put your app |
[81.10 --> 88.16] and your database in 30 plus regions on six continents with no ops check them out at fly.io |
[88.16 --> 104.78] what's up friends i'm here with james cowling co-founder |
[104.78 --> 110.56] and cto at convex they're one of our new sponsors and they're building a full stack platform for the |
[110.56 --> 118.20] typescript era so james in your main navigation you link to a page called convex versus firebase how |
[118.20 --> 124.22] similar is convex to firebase and if someone is quickly trying to grok what convex is is that a |
[124.22 --> 129.12] good comparison i think it's a good starting point for sure i mean firebase has been very impactful and |
[129.12 --> 135.08] the people we speak to who use firebase often love it and they often lament the time they have to move |
[135.08 --> 140.60] off of firebase because it's kind of failed to meet their needs as a growing company so firebase falls |
[140.60 --> 147.82] short in a few ways one is in terms of like a fully relational document model one is in terms of having |
[147.82 --> 154.20] strong type system one is in terms of having this full end-to-end consistency story where you write |
[154.20 --> 159.94] functions that run on an api server on the data that you can subscribe to and so one thing i think |
[159.94 --> 165.90] we see in the the firebase style development model is that you have web applications talking directly to |
[165.90 --> 171.42] a database in a cloud fire store with convex what is different is you have your code talking to actual |
[171.42 --> 176.96] fully fledged typescript functions running on your data that you can subscribe to but i think that the |
[176.96 --> 182.54] the firebase's comparison is fairly apt and if someone is a firebase user i think you will love |
[182.54 --> 186.90] convex and it's certainly designed to fill that niche in the market it's people who want to build |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.