I’m Harsh, a developer interested in getting involved with the Learning Equality/Kolibri community and contributing consistently over the coming months.
I’ve previously contributed to Jaeger across both the frontend and backend repositories, so I have some experience working with a large existing open-source codebase, understanding unfamiliar components, implementing changes, and going through the review process.
I’ve also been exploring systems/AI-related work and recently placed 2nd in the KubeEdge pre-test on speculative decoding.
I’m particularly interested in Kolibri because of the combination of frontend, backend and the engineering challenges around building an offline-first platform.
I’ve started going through the contribution/developer documentation and would like to understand the codebase properly before jumping into larger changes.
I’d really appreciate some guidance on:
• whether Kolibri, Kolibri Studio or the Design System would be the best starting point for my background
• which part of the codebase I should study first
• any good first issues or smaller contributions that would help me understand the architecture
• what you’d recommend I work towards if I want to become a long-term contributor
I’m starting this well ahead of the next GSoC cycle because I’d like to genuinely contribute to the project and understand the community rather than only preparing an application.
Looking forward to contributing and learning from everyone here!
Thank you for reaching out. Please send an email to contributors@learningequality.org requesting to be added to Learning Equality’s developer community slack channel so you can get started with contributing.