Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Semelhante a Open Source: What’s this all about?
Semelhante a Open Source: What’s this all about? (20)
Último
Último (20)
Open Source: What’s this all about?
- 1. Open Source Software What’s this all about? Brad Montgomery @bkmontgomery
- 2. IANAL I am not a lawyer
- 3. Do you write code?
- 4. Do you help create software?
- 5. Do you use software?
- 6. What is Software? in no particular order Mobile Software Desktop Software Operating Systems Embedded Systems SaaS/Web-based Software Software Libraries/Components
- 7. What is Open Source?
- 8. ...a development method for software that harnesses the power of distributed peer review and transparency of process. - The OSI
- 9. ...a development method for software that harnesses the power of distributed peer review and transparency of process. - The OSI
- 10. ...a development method for software that harnesses the power of distributed peer review and transparency of process. - The OSI
- 11. “Open Source” is a process.
- 12. “Open Source Software” is created through this process.
- 13. How about an example?
- 15. Building in Public Actual Code is Public
- 16. Building in Public Contributors are public
- 17. Building in Public Edits are Public!
- 18. Open Source These people work together, but they are not employed by the same organization.
- 19. ...people work together, but they are not employed by the same organization.
- 20. Open Source is a Framework for Collaboration
- 22. Software is Intellectual Property Someone owns it.
- 24. Software is owned by the original author
- 25. Software is owned by the original authors
- 26. Software is owned by the original author’s employer
- 27. Software is owned by the original authors’ employers
- 28. :-(
- 29. Software ownership is Complex.
- 30. Software is not (usually) sold.
- 33. Don’t get sued.
- 34. How does Open Source foster Cooperation?
- 35. Types of Licenses 1. Academic 2. Permissive 3. Reciprocal 4. Partially Closable
- 36. Academic To paraphrase: “You can do whatever you want with this code” Examples: BSD, MIT
- 37. Permissive • Grant substantial Permissions • May contain Patent or Trademark provisions • Provide additional protection to authors Example: Apache 2.0
- 38. Reciprocal “Share-Alike” • Permission to modify & distribute must be granted • Specifies Restrictions on Distribution/Use • Source code must be included • Modifications must be released under the same license Example: GNU GPL
- 39. Partially Closable • Require some sharing • Allow some proprietary use • Often a software library or component Examples: LGPL, MPL
- 40. Why “give away” your code?
- 41. “Given enough eyeballs, all bugs are shallow” Eric S. Raymond
- 42. OR... “Why not let people at NASA, Google, and Twitter help you build stuff?”
- 43. Smart people working on a solution to the same problem == Better Software
- 44. How can this help me? Start using open source software!
- 45. Caution! “Read the Label” when using Open Source Software!
- 46. Developers: Save time Don’t reinvent the wheel.
- 47. Managers:Save money Encourage research & evaluation. Lean on proven solutions.
- 48. Students:Learn from Pros Get some real-world experience!
- 49. Contributing? Make sure you’re allowed!
- 50. Developers: Read your employers’ PIA. They may own your code/ideas.
- 51. Developers: Get permission. In writing.
- 52. Questions? Feedback: brad@workforpie.com
- 53. Thanks!
Notas do Editor
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- The OSI: Open Source Initiative (a non-profit 501c3); Advocates/educators of open source and the body that approves licenses.\n\nhttp://www.opensource.org/about\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Collaborators can be individuals, employees of organizations, live in other countries, have be held to different contract/copyright laws.\n\nNo (well, sort of) contract negotiation among companies.\n\n
- \n
- Who owns it? The original author, an employer, public domain?\n
- at least in the US; All rights reserved! You cannot copy/modify/or even use it without permission.\n
- \n
- \n
- \n
- \n
- \n
- \n
- When you buy software, you do not become the owner. The same is true if you acquire freely available software.\n
- You have given explicit permission to (and probably *how*) use the software.\n
- \n
- Amidst this complexity, how do people (working for different companies; maybe even competitors) avoid getting sued?\n\nTech companies LOVE litigation! (Read any recent news about Google, Apple, Oracle, or Microsoft)\n
- \n
- \n
- These are very simple; easy to use; \n
- Essentially make it harder to sue the original authors; provisions may revoke rights in the case of a lawsuit;\n\nMay also require that all contributing authors verify that they have permission to contribute! (e.g. requiring employers to “sign off” on contributions).\n
- Often described as Viral. If you incorporate this code into your own project, your entire project MUST adhere to the terms.\n
- Part of the code can be “closed” (used in proprietary development; not shared). Part *must* be shared.\n\ne.g. A Library can be incorporated into a closed-source product, but changes to the library must be published.\n
- \n
- ESR: An early open source advocate\nhttp://en.wikipedia.org/wiki/Eric_S._Raymond\n\nThe Cathedral and the Bazaar\nhttp://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/\n
- There are a lot of smart people that need to solve the same problems. You get a better solution when you work together.\n
- In *my* opinion, stable, useful, working software (or components) is the greatest benefit of open source collaboration.\n
- Try out “packaged” desktop software; Use open source tools/libraries if you’re a developer; Release your own software!\n
- \n
- There are thousands of software components/libraries for hundreds of languages that solve generic problems & are available under various licenses. \n
- \n
- \n
- \n
- PIA: Proprietary Information agreement. Many employees sign over rights to all IP upon employment... even for things created “off the clock”. \n
- HOWEVER, this can often be overcome if you get permission (in writing from someone authorized to grant it!) for a project or OSS contribution BEFORE doing any work.\n
- \n
- \n