If you're techie, your homepage should be GitHub, not Instagram!
summary
Argues that a techie’s homepage should be GitHub not Instagram and gives concrete steps: start by fixing a typo or filing bug reports, post even tiny projects (first PHP calculator), aim for pull requests that get merged to prove impact, and use README, MIT license, CONTRIBUTING, CODE_OF_CONDUCT, issue/PR templates, labels like good first issue to attract contributors. Recommends GitHub Pages, Actions/CI, tests, branching strategy and profile README; cites ~20 million public repos and programs like GSoC, Hacktoberfest and GirlScript SoC.
AI-written summary · about
chapters (32)
- 0:00Intro
- 5:27Title
- 5:40Introduction
- 6:35Thank you
- 6:49My journey
- 9:33Open source has given me a family
- 10:25How to contribute
- 14:34Readme
- 16:24Licenses
- 16:53Engage with community
- 19:06Label your resource properly
- 20:01Engage with the community via issue threats
- 20:33Maintain quality of code
- 21:27Relevant topics
- 22:21GitHub Pages
- 23:13Integration Tests
- 24:39Branching Strategy
- 26:02Profile Readme
- 27:56Google Summer of Code
- 28:56How to apply for GSO
- 30:12ForceX
- 30:54GirlScript Summer
- 32:46Google Outreaches
- 33:08Open Source Organizations
- 34:33Maintain a Strict
- 35:15Stop People on GitHub
- 36:23Audience Questions
- 37:14Feature Requests
- 38:55Open Source Libraries
- 43:49Scope for improvement
- 45:36Learn how to consume
- 47:42Conclusion
related talks
47mThe Art of Documentation and Readme.md
32mGit yourself a leg up for student projects
39mSharing Your Side Projects Online and Making Your Github the Best Résumé It Ca
35mThe Art of Documentation and Readme.md for Open Source Projects
14mAn always upto date Developer's CV
44mLeveling up on GitHub: Tips + Tricks for Beginners to...
31mTelling a Great Story on GitHub
25mHi, my name is README!