Hi!
I’m a first year university student interested in participating in GSoC 2026 with Swift. I am proficient in C/C++ and have been using Swift for roughly 2 months now, and I’m eager to start contributing to the codebase early to build a strong foundation. I have some questions for GSoC 2026:
Should I focus on the main repo (apple/swift) or other repos projects like swift-syntax also in the mix?
Apart from good first issues, are there any specific subsystems that are recommended for new comers to understand the compiler better?
This might be kind of stupid but any tips on increasing my chances at actually getting GSoC 2026 for Swift? Like, what do mentors look for in a candidate?
Really excited to join the swift community and thanks in advance for your guidance!
(Based on my experience till now) - I am also a second year student
It’s great to see a first-year student starting this early. Proficiency in C++ is a massive advantage for the Swift project. Here is some general advice on how to structure your path:
Repository Strategy: Don't feel restricted to one repo. While apple/swift is the C++ core, SourceKit-LSP is an excellent place to see immediate impact on developer tools. I recommend exploring both to see which subsystem fits your interests best.(sourcekit-lsp-issues)
The "Mark" System: Instead of chasing one giant project, focus on a series of incremental "Marks."
Mark 1: A localized fix (like a good first issue) to learn the PR and CI workflow.
Mark 2: A structural improvement, such as refactoring legacy logic or improving diagnostics. Building this "pulse" of activity shows you can handle the daily rhythm of a professional codebase.
Find Your Dopamine in the Code: While GSoC is a great goal, try to find the "dopamine" in the true open-source experience. There is a unique satisfaction in fixing a bug that has been bothering you or adding a feature that helps thousands of other developers. If you approach this with genuine curiosity rather than just a checklist, you’ll naturally build the "ownership" mindset that mentors look for.
Subsystems to Watch: For the compiler, look into Lexing/Parsing (C++ heavy). For tooling, prioritise SwiftSyntax and Swift Concurrency. Understanding how the compiler "sees" code is essential for any high-impact contribution.
The 2026 cycle is still far out, so the best thing you can do now is pick a small issue, get your first green checkmark, and enjoy the process of learning. Looking forward to seeing your work!
Best of luck brother
