Download as PDF, PPTX
Uploaded byAnoop Thomas Mathew
Let's Contribute
The document discusses contributing to open source projects. It begins by asking participants about their experience with coding and git. It then lists many ways one can contribute such as documentation, bug reports, reviews, development, and translations. The rest of the document outlines an activity where participants are split into groups to collaboratively develop a calculator application implementing various math functions over multiple tasks. It provides guidance on development practices like coding style, testing, and using git. It concludes by discussing the open source development process and encouraging participants to get involved in a project.
More Related Content
Let's Contribute
- 1. Let's Contribute ANOOP THOMASMATHEW @atmb4u CTO @ Profoundis Labs (one day workshop) FOSSMeet 2014 NIT, Calicut
- 2. ➢Who Am I ➢QuickHands Up! ➢ project contributors ? ➢ git users ? ➢ coders – python/C/C++/javascript/java ? Welcome!
- 3. Contributing to Community weneed to be producers; not just consumers!
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. Contribution Options Tutorials andCode Samples
- 16.
- 17. philosophical methodologies of open source Weare gonna play a GAME !
- 18. philosophical methodologies of open sourceno more boring! We are gonna play a GAME !
- 19. we'll create acalculator
- 20.
- 21. Rules ●Create personal githubaccount.
- 22. Rules ●Choose your comfortablelanguage
- 23.
- 24.
- 25. Rules ●write Tests foreverything you write
- 26. Rules ●Each one ofyou should be involved
- 27.
- 28. Rules ●push to therepo allocated to you
- 29. Rules ●It must beextensible else might have to redo it!
- 30. Rules ●one task willbe given every 15 mins
- 31. Learn some git try.github.io QuickReference git init git status git add <filename> git commit -m “Message” git remote add origin <url> git remote -v git push origin master git pull origin master git merge git rm <filename>
- 32.
- 33. SimpleCalculator Add Subtract Divide Multiply Review #1 Documented? Test casesadded? Committed? Pushed? Who is idle in team?
- 34.
- 35. ●Coding Style –GNU C/ Python PEP8 ●Testing Frameworks ●Tickets/Issues/Bugs INTERMISSION
- 36.
- 37. ➢tan ➢add History tothe calcuator Task #4
- 38.
- 39. Polynomial Solver x2 +x+1 =0 Task #6
- 40. ➢Polynomial Solver ➢ anysecond degree polynomial ➢Expression Evaluator ➢Paranthesis Task #7
- 41. ➢Polynomial Solver ➢ Any nth degreepolynomial Task #8
- 42. Good News EveryOne! Let'sreview some code
- 43.
- 44. Development Process ➢ pickany open source project ➢ pick one which you use or want to use ➢ any of it you find interesting
- 45. Development Process ➢ clonecode ➢ find location from the website ➢ use git or other version control system
- 46. Development Process ➢ installit from source code
- 47. Development Process ➢ getit running; use it ➢ Might need some external libraries. ➢ Look at README, INSTALL or Installation Guide
- 48. Development Process ➢ translateproject to mother tongue transifex.com
- 49. Development Process ➢ readdocumentation
- 50. Development Process ➢ writedocumentation
- 51.
- 52. Development Process ➢ browsebug tracker/issues/tickets
- 53. Development Process ➢ subscribeto mailing list; chat over IRC
- 54. Development Process ➢ discusswith the community
- 55. Development Process ➢ findpriorities for the community; talk.
- 56. Development Process ➢ findtickets to work on tickets tagged: 'low hanging fruit', 'easy pickings'
- 57. Development Process Let's makethe world a better place!
- 58. https://leanpub.com/opensourcebook/ A Code Explorer'sGuide to Open Source Jungle
- 59. reach me at 99953 44 675 @atmb4u atm@profoundis.com
- 60. This is theend. or is this the begining? Your Choice ! Ideas ● talk to people – group on every week ● use time more effectively ● find opportunities to contribute ● let other's see your code
- 61. Thank You @atmb4u Feedback @bit.do/quickfeedback