Making open source my new year’s resolution

My motivation for making contributing to open source software my new year’s resolution in 2017. Hopefully, this will motivate people to do the same thing.

Transcript

1. MAKING OPEN SOURCE MY NEW YEAR’S RESOLUTION @KENNETH_SKOVHUS TECHFESTIVAL AT ISSUU, SEPTEMBER 2017
3. OPEN SOURCE SOFTWARE (OSS) SOFTWARE WITH SOURCE CODE THAT ANYONE CAN INSPECT, MODIFY, AND ENHANCE. OPPOSED TO CLOSED SOURCE / “PROPRIETARY”. OSS OFTEN USED AS BUILDING BLOCKS FOR PROPRIETARY SOFTWARE
5. HI! I'M KENNETH.
6. DEPENDING ON OSS TO DO MY JOB AT
8. *NIX APPIUM ATOM BABEL BASH BSD CHROME DOCKER EXPRESS FABRIC FIREFOX FLOW GIT JEST MYSQL NGINX NODE NPM OPEN SSH OPEN SSL POSTGRESQL PYTHON REACT REACT NATIVE RUBY SCALA TYPESCRIPT VARNISH VIM V8 VS CODE WEBPACK YARN ZSH …
10. MAKING OPEN SOURCE MY NEW YEAR’S RESOLUTION
11. MAKING OPEN SOURCE YOUR NEW YEAR’S RESOLUTION
12. CONTRIBUTE TO OSS ! MEETUPS & CONFERENCES
13. WHY CONTRIBUTE TO OSS? GIVE BACK TO THE COMMUNITY TO HAVE FUN TO LEARN
14. HOW TO START CONTRIBUTING? THINGS TO KEEP IN MIND “FIGURING OUT HOW TO CONTRIBUTE TO OPEN SOURCE” JULIA EVANS @B0RK
16. OSS CODE CONTRIBUTIONS REQUIRES SAME DEV SKILLS YOU USE EVERY DAY AT WORK
17. SOFTWARE DESIGN DEBUGGING TESTING DOCUMENTATION MAKING CLEAR PULL REQUEST ASK QUESTIONS OSS CODE CONTRIBUTIONS REQUIRES SAME DEV SKILLS YOU USE EVERY DAY AT WORK
18. WHAT MAKES IT DIFFICULT? CODEBASE / CONVENTION IS UNKNOWN HOW IS THE CODE CONSUMED?
19. MAINTAINERS = STRANGERS DIFFERENT GOALS / DIRECTION IS THE CHANGE BROADLY APPLICABLE? WHAT MAKES IT DIFFICULT?
20. MAINTAINING OSS IS TOUGH BE RESPECTFUL WHAT MAKES IT DIFFICULT?
21. HOW TO START CONTRIBUTING? FIRST STEPS
22. 1) EXPLORE THE SOURCE CODE OF TOOLS YOU USE EVERY DAY
23. 2) FIND BUG / LIMITATION IN OSS PACKAGE
24. 2) FIND BUG / LIMITATION IN OSS PACKAGE
25. 2) FIND BUG / LIMITATION IN OSS PACKAGE
26. 2) FIND BUG / LIMITATION IN OSS PACKAGE
27. 2) FIND BUG / LIMITATION IN OSS PACKAGE
28. 2) FIND BUG / LIMITATION IN OSS PACKAGE COMMENT ON (GITHUB) ISSUES HELP WITH DOCUMENTATION PUSH FIXES / FEATURES UPSTREAM
29. 2) FIND BUG / LIMITATION IN OSS PACKAGE GOOD START = SMALL DOCS PULL REQUEST
30. 3) WRITE BLOG POSTS SHARE IF YOU LEARN SOMETHING NEW (LANGUAGE, TOOL, LIBRARY)
31. 4) OPEN SOURCE SOMETHING!
33. 1) DIVE INTO THE SOURCE CODE, BE CURIOUS 2) HELP OUT OSS YOU USE (DOCS, ISSUES, BUGS, FEATURES) 3) WRITE BLOG POSTS (NEW TOOLS, LANGUAGES, EXPERIENCES) 4) OPEN SOURCE *SOMETHING* HOW TO START CONTRIBUTING
34. “BUT I HAVE NO TIME FOR OSS CONTRIBUTIONS AT MY DAY JOB!”
35. USING OPEN SOURCE SOFTWARE => CONTRIBUTE BACK (CONVINCE YOUR MANAGER IF NEEDED!)
36. USING OPEN SOURCE SOFTWARE => CONTRIBUTE BACK (STILL NO TIME? DONATIONS )
37. USING OPEN SOURCE SOFTWARE => CONTRIBUTE BACK (CLARIFY THIS AT JOB INTERVIEWS)
38. USING OPEN SOURCE SOFTWARE => CONTRIBUTE BACK (ADDING ADDITIONAL SPARE TIME GETS YOU FURTHER)
40. WHAT OSS CONTRIBUTIONS GIVES ME DIVERSITY IN TASKS (OSS VS PRODUCT/CLIENT WORK) PART OF SOMETHING BIGGER (GLOBAL NETWORK) INSIGHTS INTO TOOLS I USE EVERY DAY
41. WHAT OSS CONTRIBUTIONS GIVES ME GITHUB.COM/SKOVHUS/JEST-CODEMODS
43. MAKING OPEN SOURCE YOUR NEW YEAR’S RESOLUTION @KENNETH_SKOVHUS TECHFESTIVAL AT ISSUU, SEPTEMBER 2017