Panduan untuk mempublikasikan kode ke publik

Membahas berbagai keuntungan dari berkontribusi ke open source, bagaimana cara memulainya bahkan bila kamu tidak bisa menulis kode.

1. Publishing Your Code: A Guide Irfan Maulana Principal SDE - Web @ GovTech Edu Indonesia Open Tech Summit Indonesia 25-26 Nov 2024
2. dub.sh/mzp.x dub.sh/mzp.gh dub.sh/mzp.adp
3. Public Projects
4. From: indogithubers.com
5. Open source is a software development model where the source code is freely accessible, allowing anyone to view, modify, and distribute it.
6. Is not only about the public availability, it’s also about the collaborative & transparent philosophy.
7. Dan banyak lagi…
8. #OpenSource Is Everywhere.
10. Learn from the best. Observe public code from another developer, get involved in their thought process, follow how they write the code, see how they work, and collaborate — all without needing to work in the same company. BENEFITS
11. Build your professional network. Collaborating with many people with diverse backgrounds gives you a unique experience, working with them in the same codebases, will eventually grow your professional network. BENEFITS
12. Polish your reputation. As "they" are trying to "climb" in social media, you can also polish your professional branding and build public trust through the open-source contributions that are available for everyone. BENEFITS
13. Improve your communication skills Not just writing code, we may need to ask questions, explain the problem, propose a solution, and discuss many things. By that time, your communications will also get better. BENEFITS
14. Public feedback. Software will getting better when getting more feedback. By opening to public, you unlock opportunities to make continuous improvement in your software. BENEFITS
15. Code & Software Quality Public software will have more pressure to always keeping the quality high. You have more reasons to write a better code, easy to read and setup, easy to be tested. BENEFITS
16. 💪 Challenges 🔶 Sustainability 🔶 Funding 🔶 Security Risk 🔶 License Problem
17. User / Consumer Sponsor / Supporter / Patron Maintainer / Contributor Author / Creator 󰢨 Positions
18. Start to take more responsibility.
19. Find the project you’re interested Observe, get to used with their workflow. Learn the tools, e.g: Git Read the docs It’s not always new feature, fixing bug is also welcomed Do not add unnecessary changes 󰝋 Where to start
20. Involve in the discussion, help to answer related questions. Write & improve docs, translate to your local Create external tutorial/article/video Bug/issue triage. Create or help local communities Organize offline/online event 󰠇 More than just a code
21. summerofcode. withgoogle.com
22. hacktoberfest.com
23. 🔷 Start from the closest and familiar. 🔷 Extract ‘the helpers’ to be more generic. 🔷 Porting to other language or framework 🔷 Starter/project template. 🔷 Theme/plugin/extension 󰩃 Start your own
24. 🔷 License 🔷 Versioning & Changelog 🔷 Installation/Local setup 🔷 Demo page/Documentation 🔷 Bug report, Feature request & Discussion 👀 Things to consider
25. “Little progress is better than no progress at all. Success comes in taking many small steps. If you stumble in a small step, it rarely matters. Don't gift wrap the garbage. Let little failures go.” — John C. Maxwell, Failing Forward: Turning Mistakes into Stepping Stones for Success
26. Get the slide dub.sh/mzp.deck
27. CREDITS: This presentation template was created by Slidesgo, and includes icons by Flaticon and infographics & images by Freepik Thanks! mazipan.space Please keep this slide for attribution