Panel: Open Source, Standards, and Economics
summary
Discussion explains that standards groups enforce royalty-free patent policy reciprocity, projects use developer certificate of origin or contributor license agreements to track provenance, and companies adopt procurement-friendly standards hosted on GitHub. Tidelift’s model pays original maintainers to improve security and reliability of hundreds of small libraries, Node.js updates an IPR/disclosure policy, and watchers warn of growing ethical source licenses and regulator attention to platform liability and critical-security cleanups.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:26Wendy Seltzer
- 10:39Identifying Common Themes
- 10:59Clearly Defined Boundaries
- 11:55Mozilla Public License
- 15:54Web Accessibility
- 16:24The History of Procurement of Open-Source
- 20:25Importance of Having Multiple Stakeholders
- 20:40What Does a Developer Need To Know about Their Open Source License
- 36:55Contributor License Agreement
- 55:21Predictions
related talks
32mSOS: Sustainable Open Source
36mPanel: Openwashing – How Do We Handle (and Enforce?) OSS Policies in Products?
29mNavigating the Open Source Policy Labyrinth: Unraveling Global Policy Efforts for a Secure Future
25mWhat Makes Open Source Work: Licensing and Beyond
36mFreedom vs Sustainable Business: A Candid Necessary Debate
32mPanel Discussion: Contribute with Clarity: Choosing Your...
38mPanel: Open Source Management Based on Open Source
26mPanel Discussion: Open Source Licensing