If you're targeting GSoC 2027, learn to read pull requests.
Read recently merged PRs.
You'll learn:
- how maintainers review code
- what changes they accept
- what “good enough to merge” actually looks like
This is one of the fastest ways to understand a new open-source project.
If you're targeting GSoC 2027, here's something nobody wants to hear:
Your proposal won't save you if nobody in the community knows who you are.
Contribute early. Communicate. Be useful.
By application time, you shouldn't be introducing yourself.
#GSoC2027#OpenSource
Google says Android will remain an open ecosystem for innovation, without a central point of control or failure.
Now, Google wants more control over which apps you can install on your own Android device.
Keep Android open: https://t.co/XdC9TTqd70
#KeepAndroidOpen#Android
If you're preparing for GSoC 2027, stop asking:
“Which organization is easiest to get into?”
Ask:
“Which project can I still see myself contributing to even if GSoC didn't exist?”
That answer will take you much further.
#GSoC2027#OpenSource
The GSoC advice pipeline:
1. Never get selected for GSoC
2. Post “How to crack GSoC” content
3. Tell everyone to “start early”
4.Refuse to elaborate
I got selected for GSoC 2026.
Let’s talk about what actually works.
#GSoC2027#OpenSource
Just submitted a 44 questions and 25 page written assessment for the Canonical Microservices Engineer role.
At some point, I stopped answering questions and started writing a book 😭
Now we wait.
Everyone asks: “I know I should start for GSOC rn but how?”
Here’s my take:
Pick a project you can actually open, run and use right now.
If you can test it, break it, and open it daily - you’ll understand the code deeply and contribute way better. #GSOC2026#larpmaxxing
One GSoC mistake I made early:
Trying to understand the entire codebase before contributing.
You don’t need to.
Pick one issue. Trace one feature. Understand one small part deeply.
Your map of the codebase grows with every contribution.
#GSoC2027#GSoC#OpenSource