https://arkid15r.dev/tags/open-source/Recent content in Open-Source on Arkadii Yakovetsen© Arkadii YakovetsMon, 28 Sep 2026 13:15:00 -0700https://arkid15r.dev/slack-community-etiquette/Thu, 17 Sep 2026 11:00:00 -0700https://arkid15r.dev/slack-community-etiquette/Communities get the Slack they tolerate. Large communities drown less often in obvious scam posts or clear code of conduct violations than in everyday attention tax. Wrong channel posts, top-level replies that should have been threads, and the `Also send to #channel` checkbox quietly multiply unread counts for people who never asked for the ping. This post is a practitioner etiquette essay from Slack-lived experience: pick the right room, consolidate before you hit Enter, trim link previews, prefer reactions over thanks-noise, and remember that deleted messages still leave footprints. It ends with a short checklist you can pin.https://arkid15r.dev/open-source-contributions-career/Mon, 14 Sep 2026 09:00:00 -0700https://arkid15r.dev/open-source-contributions-career/A reflective note for contributors and mentees on three hats in open source -- maintainer, mentor, and manager -- learned in that order, with sponsorship as an optional bridge when someone is ready and the program is not. It sketches a soft maturity ladder from Foundations through Hire-ready, and when personal funding keeps a track record growing between cycles. It includes a sponsorship path after a GSoC rejection so the work does not pause for a calendar, and another where a consistent public track record leads through sponsorship to an internship and a permanent role. Organization stipends can become GitHub Sponsors support when orgs pass them through. The numbers are a funnel: hundreds of contributors, dozens of mentees and sponsored people, and a rare hire.https://arkid15r.dev/psf-board-candidates-2026/Sat, 12 Sep 2026 11:53:44 -0700https://arkid15r.dev/psf-board-candidates-2026/The 2026 PSF Board election fills four seats under Approval Voting through September 15. This post walks every nominee A-Z with links to nomination statements, AMAs, and PSF blog interviews, plus a short evaluative paragraph on each. I have no personal affiliation with any candidate. Facts and links are a best-effort snapshot from those public sources and may be incomplete or wrong. Read the primary materials before you vote, and contact me if something needs a correction.https://arkid15r.dev/google-summer-of-code-complete-guide-to-success-part-3/Wed, 09 Sep 2026 14:00:00 -0700https://arkid15r.dev/google-summer-of-code-complete-guide-to-success-part-3/Parts 1 and 2 covered preparation, contribution, and communication. This part is about the proposal itself -- the document mentors use to judge whether you can finish the work. It starts with strategy for your three slots, including why one or two strong proposals beat three thin ones. From there it covers structure: background, motivation, technical approach, timeline, deliverables, risks, collaboration, and responsible AI use while writing. The goal is a proposal that shows readiness, not just enthusiasm.https://arkid15r.dev/gsoc-2026-projects-top-50/Thu, 03 Sep 2026 12:00:00 -0700https://arkid15r.dev/gsoc-2026-projects-top-50/Google Summer of Code 2026's 12-week timeline wrapped final evaluations at the end of August, with shorter projects finishing earlier. This post reads the official projects page and Google's program announcements for scale, acceptance rates, and what is marked complete versus still active. It then ranks mentoring organizations by volume and highlights where the largest slots landed. The centerpiece is a personal list of 50 completed projects from orgs including Apache, Debian, Django, Git, the Linux Foundation, OWASP, and PSF. Bias is declared up front: security-related work, hardware, frameworks I use, and communities I am close to.https://arkid15r.dev/google-summer-of-code-complete-guide-to-success-part-2/Tue, 25 Aug 2026 13:00:00 -0700https://arkid15r.dev/google-summer-of-code-complete-guide-to-success-part-2/Part 1 covered preparation and choosing an organization. This part focuses on contribution and communication -- the habits that make technical skill visible to maintainers. It covers Git and GitHub Flow, keeping forks current, and pull-request hygiene that respects review bandwidth. There is also guidance on reading project guidelines, handling feedback, and using AI responsibly without dumping unowned volume on mentors. The closing thread is how to talk to communities clearly so your work gets noticed for the right reasons.https://arkid15r.dev/google-summer-of-code-complete-guide-to-success-part-1/Mon, 10 Aug 2026 12:00:00 -0700https://arkid15r.dev/google-summer-of-code-complete-guide-to-success-part-1/Over a few years of mentoring for OWASP and the Python Software Foundation, I have watched contributors succeed and stall in Google Summer of Code. This first part starts with what GSoC really is -- remote open-source work under mentors, not a traditional internship -- and what evaluations actually reward. It then covers how to choose and research an organization, including why smaller orgs can be a smarter bet than the most competitive names. From there it walks through joining the community early, making real contributions before proposals are due, and shaping a standout application. The through-line is preparation and relationships, not last-minute proposal writing alone.