Downloaded 37 times
Uploaded byShalin Shekhar Mangar
Why you should contribute to Open Source.
Presented at Indian Institute of Information Technology (IIIT) Allahabad on 21 Oct 2009 to students on the benefits of contributing to open source projects. The target audience was freshmen.
Why you should contribute to Open Source.
- 1. #!/usr/bin/env python importsys def main(): print ' You should contribute to Open Source ' sys.exit(0) if __name__ == "__main__": main()
- 2.
- 3. Why work inOSS? Work on what you like, when you like
- 4. Development in the”real” world
- 5. Learn from thebest
- 6. Build a publiclyverifiable resume
- 7.
- 8. What you like,when you like Millions of open source projects
- 9. Big names –Linux, MySql, Apache projects
- 10.
- 11. No schedules, nodeadlines
- 12.
- 13. Development in the”real” world ”Other” people use it
- 14. Build system -Makefile, Ant, Maven
- 15. Source control –CVS, SVN, Git
- 16. Bug tracker –Bugzilla, Jira, Launchpad
- 17. Documentation – Manuals,Wiki, Books!
- 18. Support - Mailinglists & Forums
- 19. Learn from thebest Rock star coders!
- 20. Linux Kernel -Linus Torvalds, Ingo Molnar, …
- 21. Python - GuidoVan Rossum, …
- 22. Mono – MiguelDe Icaza
- 23. Lucene/Hadoop – DougCutting, Michael McCandless, Yonik Seeley, …
- 24. Thousands of verytalented individuals
- 25. What you tellin a resume? Contact info
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32. The company wantsto know... How good are your design skills?
- 33. How well canyou write code?
- 34. Do you haveexperience on ”real” projects?
- 35. Can you workin a team?
- 36. Do you havefocus and patience?
- 37. A publicly verifiableresume I've worked on this for two years
- 38. I wrote featuresX, Y, Z in Project P
- 39. I've over ahundred posts on the user forum
- 40. I have commitaccess to the project
- 41. I'm the expertbecause I ”wrote” it!
- 42. Companies will findyou! Project X will save us money. Who works on it?
- 43. We should havein-house expertise on the Project X.
- 44. Hiring open sourcedevelopers is free publicity
- 45. Wow, you workon X, you must be really good!
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52. Choosing the rightproject Filter by your interest area
- 53.
- 54.
- 55. Something you wantto learn
- 56. Using the projectis very important
- 57. How do Istart? Choose your project
- 58. Join the mailinglist or forum
- 59. Check out thecode
- 60. Find open issuesand feature requests
- 61. Ask the developerson what you can work on
- 62.
- 63. Features & Bugfixes
- 64.
- 65.
- 66.
- 67. Do's and Don'tsdnt rite sms lingo!
- 68.
- 69. Don't be anisland. Collaborate.
- 70. Learn from yourmistakes
- 71. Persevere. It takestime.
- 72. Questions? Shalin ShekharMangar shalin [at] apache [dot] org http://twitter.com/shalinmangar http://shalinsays.blogspot.com