1. Aaron Williamson & Karen M. Sandler July 28, 2011 OSCON Legal Basics for Developers: A (AN?) FAQ

2. Do I need to put copyright notices on my code to get a copyright?

3. What's the difference between free software and open source? Is there a legal distinction?

4. If I find some code and the header says it's open source, can I use it?

5. Why are there so many licenses?

6. Sounds complicated. Can I just put my code in the public domain?

7. My project is GPL'd, and some company is using it in its product, but not providing source. What should I do?

8. Can I sue them?

9. I'm signing an employment/contractor agreement, and it says the company owns all my work. How can I keep my copyrights to free software I develop on the side?

10. I submitted a patch to a project, and they want me to assign my copyrights. What does this mean? Should I do it?

11. I'm starting a free software project. Are there legal issues I should consider when choosing a name?

12. I hear that there are patents in the field I'm writing software for. Should I be concerned? Should I study the patents to make sure I'm not infringing?

13. What can I do to protect myself and my users from patents?

14. Should I incorporate a nonprofit for my software project?

15. Can you compare the abstraction-filtration-comparison test to the analytic dissection test?

16. The GNOME Foundation and SFLC are 501(c)(3) charities in the USA – make a donation! These slides, this talk, and audio/video recordings thereof are licensed under the Creative Commons Attribution-ShareAlike 3.0 United States License! help@softwarefreedom.org Become a Friend of GNOME! help@softwarefreedom.org