Why you should contribute to Open Source.

  • 2,982 views
Uploaded on

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.

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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,982
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
26
Comments
0
Likes
6

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. #!/usr/bin/env python import sys def main(): print ' You should contribute to Open Source ' sys.exit(0) if __name__ == "__main__": main()
  • 2. Who am I?
  • 3. Why work in OSS?
    • Work on what you like, when you like
    • 4. Development in the ”real” world
    • 5. Learn from the best
    • 6. Build a publicly verifiable resume
    • 7. Companies will find you!
  • 8. What you like, when you like
    • Millions of open source projects
    • 9. Big names – Linux, MySql, Apache projects
    • 10. Pick and choose
    • 11. No schedules, no deadlines
    • 12. No boss!
  • 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 - Mailing lists & Forums
  • 19. Learn from the best
    • Rock star coders!
    • 20. Linux Kernel - Linus Torvalds, Ingo Molnar, …
    • 21. Python - Guido Van Rossum, …
    • 22. Mono – Miguel De Icaza
    • 23. Lucene/Hadoop – Doug Cutting, Michael McCandless, Yonik Seeley, …
    • 24. Thousands of very talented individuals
  • 25. What you tell in a resume?
  • 32. The company wants to know...
    • How good are your design skills?
    • 33. How well can you write code?
    • 34. Do you have experience on ”real” projects?
    • 35. Can you work in a team?
    • 36. Do you have focus and patience?
  • 37. A publicly verifiable resume
    • I've worked on this for two years
    • 38. I wrote features X, Y, Z in Project P
    • 39. I've over a hundred posts on the user forum
    • 40. I have commit access to the project
    • 41. I'm the expert because I ”wrote” it!
  • 42. Companies will find you!
    • Project X will save us money. Who works on it?
    • 43. We should have in-house expertise on the Project X.
    • 44. Hiring open source developers is free publicity
    • 45. Wow, you work on X, you must be really good!
  • 46. Requirements
  • 52. Choosing the right project
    • Filter by your interest area
    • 53. Filter by language
    • 54. Something you use
    • 55. Something you want to learn
    • 56. Using the project is very important
  • 57. How do I start?
    • Choose your project
    • 58. Join the mailing list or forum
    • 59. Check out the code
    • 60. Find open issues and feature requests
    • 61. Ask the developers on what you can work on
  • 62. Contributing
  • 67. Do's and Don'ts
    • dnt rite sms lingo!
    • 68. Be courteous
    • 69. Don't be an island. Collaborate.
    • 70. Learn from your mistakes
    • 71. Persevere. It takes time.
  • 72. Questions? Shalin Shekhar Mangar shalin [at] apache [dot] org http://twitter.com/shalinmangar http://shalinsays.blogspot.com