I’m excited to share that I’ll be contributing to the Swift runtime as part of Google Summer of Code 2026, working on concurrency runtime improvements around task visibility and diagnostics.
Before diving in, I’d like to properly onboard into how the runtime team and wider Swift contributors coordinate day-to-day.
I’d really appreciate guidance on a few practical things:
Where does most discussion happen? From what I know, it's meant to be here most of the time.
(maybe GitHub issues, mailing lists, Slack, Discord, real-time chat, etc. also exist?)
Is there a preferred place and methodology for GSoC contributors to stay in sync with mentors and other contributors?
Are there recommended docs or prior discussions I should absolutely read?
I want to make sure I integrate into existing discussions rather than duplicating work or missing important stuff.
Mentors will be @Mike_Ash and @al45tair, whom I really look forward to talking more to.
I will post regularly about my work and ideas during GSoC and I would deeply appreciate any and all feedback from everyone interested.
Can't wait to learn from the community and contribute.
Hi Ege, and congratulations on being selected for GSoC 2026 :-)
The forums and Swift Open Source Slack are the two main places we use to communicate. Personally I think Slack works better for real-time/near-real-time communication and collaboration, while the forums are a bit slower. The advantage of the forums, mind, is that they're more public, and the Swift Open Source Slack doesn't archive messages. Mike and I are both in that Slack, so I'd suggest joining that instance and giving us a ping to say hello :-)
It might be a good idea for us to have a regular meeting (i.e. video call) to talk about progress and hash out any ideas. I'll see if I can set something up.
I don't think so. I think it's important that we stay in touch and talk about the project. Otherwise I think we can organise ourselves how we wish.
I suppose familiarising yourself with the documentation on the Swift website, particularly the parts about contributing to the project, is a good start. I think it's also a good idea to get yourself set up so that you can build and test the Swift compiler and so that you're familiar with how to do that on your machine.
Otherwise, I think you'd already looked over the Concurrency source code while writing your proposal; you might also want to take a glance at swift-inspect so you can see what that currently does to enumerate tasks if you haven't already looked. Ideally we'll be replacing that with the work you'll be doing over the summer.