Using Generative AI to Develop Open Source Code - Practical Guidance for Managing Lega...
summary
Practical legal guidance on using generative AI for open source code: copyright requires human authorship so edits matter, training data can be reproduced and trigger infringement, and pending cases like GitHub Copilot and Getty v Stability AI raise liability concerns. Use tools that surface provenance such as GitHub Copilot and AWS CodeWhisperer, run snippet scanners like Black Duck, turn on code referencing, add provenance by tag AI-generated commits, avoid pasting secrets in prompts, and prefer self-host and fine tune models when possible.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:03Copyright basics for AI
- 3:56AI tools and copyright
- 5:47Licensing with AI output
- 7:56Open source vs AI terms
- 10:46Developer Certificate of Origin
- 12:10AI laws and regulations
- 13:56Trade secret risks with AI
- 16:08Best practices for open source
- 21:44Compliance strategies
- 26:03AI compliance approaches
- 29:33Minimizing trade secret risks
- 30:17Summary and Q&A
related talks
38mContributing AI-Generated Content to OSS Projects - Navigating Legal, Copyright, &...
29mAI-Generated Code: Legal Risks and How to Reduce Them
43mBest Practices for AI-Assisted Code Generation Tools (Like CoPilot)
37mNavigating the Future of Open Source Development: Opportunities, Risks, Best Practices...
38mWhat Should OSPOs Think About Github CoPilot?
47mPanel Discussion: Open...
48mOpen Source: What's Next
10mThe Next Era Of Open Source: Humans + AI, Not Humans vs AI