I’m Ansh Verma, a computer science student from India, and I’m excited to start contributing to Joplin. I’ve been actively exploring open source and am looking to work on a project with real users and long-term impact—Joplin feels like a great fit.
My interests are mainly around full-stack development and DevOps, and I enjoy understanding how products work end to end, from code to deployment and maintenance. I’m currently getting familiar with the Joplin codebase and contribution process and plan to start with small, meaningful contributions.
I’m also interested in learning more about GSoC 2026 ideas within the Joplin ecosystem and growing through consistent contributions.
Looking forward to contributing, learning from the community, and collaborating with fellow developers.
Thanks, and happy to be here!
I’ve made many contributions to the Joplin code over the last couple of years, many of which I’d describe as small, meaningful contributions. Feel free to have a look through my merged PRs here Pull requests · laurent22/joplin · GitHub if you think it might benefit to get some context of where features align with the code.
I’ve also raised a load of issues on GitHub and some feature requests on the forum. I can think of a couple which have a clear course of action which should be easy enough to pick up and could be good first issues:
Or if you are interested in something more of a challenge and front-end heavy, and have some ideas for how to make good UI, this is a task I started and gave up on, as front-end isn’t really my strong suit, and I wasn’t quite sure about the best way to implement the feature in a way that provides a good user experience:
I attempted having arrow up and arrow down buttons to move notes through the list, but the FlatList was re-rendering every time a note was moved, meaning it would be really slow to move a note a long way through a list.
