Opportunities

 

19th February, 2017

Srijan Agarwal

srijan@wikitolearn.org

$whoamI

def show_off(self):

  • CSE Sophomore at Amrita University

  • Active FOSS@Amrita member

  • Develops in JS, PHP and Python

  • Appreciable amount of bug fixes (~around 50) since 2015

  • Google Summer of Code'16 student with WikiToLearn -> Core Developer at WikiToLearn

  • Google Code-In Mentor'16 for WikiToLearn

  • Invited to talk at FUDCon Conference 2016 Cambodia, FOSSASIA Summit 2017 Singapore, and many national conferences.

  • Developer Advocate at ThinkFOSS and Product Engineer at Scapic.

My goal for this talk : 

  • What really is Open Source? And why should I care?

  • Get more people contribute to Open Source

  • Educate students about GSoC/Outreachy.

  • freely used

  • changed

  • shared by anyone 

software that can be

through access to the source code

is Open Source

Why should I even care?

Loads of ways to contribute

 

Fixing code, Documentation, Quality Assurance, Translation, Design etc etc

I code, How can I contribute technically?

GSoC

Outreachy

  1. All University Students

  2. Has projects in all languages

  3. You need to start early

  4. 178 organisations

  5. next round (?) March, 2017

  1. Only for non males

  2. Has projects in all languages

  3. You need to start early

  4. 12 organisations

  5. next round (?) March, 2017

  • Stipend of $5500 (?) sent out in 3 (?) intervals.

  • Wonderful technical mentors

  • Working in a technical community in a real time huge project!

Only GSoC and Outreachy? o.O

  • Season of KDE

  • OWASP SOC

  • Mozilla Winter of Security

  • Rails Girls Summer of Code

  • TOR Summer of Privacy (Security)

  • Open DayLight Summer Internship

  • Radare Summer of Code (Security)

  • DataOne Summer Internship

  • Free Software Foundation Internship

Google Code-In

13-17 years of age

Pros :

 

  • small bugs, easy to fix, helping mentors

  • Tshirts, swags, trip to SFO with parents

Cons :

 

  • Anxiety

What if I want to start *now*?

Common terms you'll come across

  • ​Git - a version control system for collaborative development

  • IRC - Internet Relay Chat, where devs hangout

  • Bug - issue in code which needs a patch

  • Patch - code change that fixes something

"Do I have to find bugs of my own?"
"How can others know I am working on this bug?"
"How can someone review my work and test if something is wrong?"

Phabricator

  • Bug Tracker
  • Developed by Facebook
  • Some orgs simply use Github, Gitlab, etc.

Gerrit

  • Code Review Tool


  • Developed by Google

Phabricator/Issue Tracker

Find bug

Fix it

Send patch

Get it reviewed

Good

Bad

Merged

That's it.

Time for some Q&A

Made with Slides.com