Learn open source by working on a real project, with two mentors beside you.
gsoc.elixpo.com ·
Project ideas ·
Get involved ·
gsoc@elixpo.com
This repository is the home of Elixpo's Google Summer of Code (GSoC) programme. It holds everything a prospective contributor needs to read before applying: the project ideas, the codebases they belong to, how to get involved, how to write a proposal, how we select contributors, our AI policy and the people who mentor.
Status: Elixpo is applying to be a mentoring organisation for Google Summer of Code 2027. Google announces accepted organisations after the application period. In 2027 we plan to mentor one contributor, so every accepted contributor gets two mentors' full attention.
Short contributions bring people into open source, but they rarely turn newcomers into maintainers. Our aim for GSoC is the longer path:
newcomer → first contribution → understands one part of a project → designs and ships it with review → helps review others → keeps it running
Everything in this programme is built around that path:
- One problem per idea. Each idea is one clear problem in one codebase, with what is in and out of scope written down.
- Two mentors per idea. A primary mentor is the main contact; a backup mentor knows the project and can step in.
- Proof, not promises. Every idea says how success is measured, usually with tests anyone can run.
- No private keys. Every project can be set up from its public repository.
- Ownership after the summer. The contributor is invited to keep reviewing and maintaining the part they built.
| # | Idea | Project | Theme | Size | Difficulty |
|---|---|---|---|---|---|
| 1 | LixBlogs read-access policy and offline conformance harness | LixBlogs | Security | 175 h | Hard |
| 2 | Accessible LixSketch canvas | LixSketch | Accessibility | 175 h | Intermediate |
| 3 | Crumb connector contract and offline conformance kit | Crumb | Rust, agent security | 175 h | Hard |
| 4 | Explainable contest-scoring engine | Elixpo Open Source | Community, data | 90 h | Intermediate |
| 5 | Oreo badge simulator and CLI test bench | Oreo | Embedded, open hardware | 175 h | Intermediate |
| 6 | LixBlogs CLI automation contract v1 | LixBlogs | Developer tools | 90 h | Easy |
The full descriptions, warm-up tasks and mentors are on
gsoc.elixpo.com/ideas. The source text is in
content/ideas/.
| Codebase | What it is | Repository |
|---|---|---|
| LixBlogs | A collaborative publishing platform with an API and a CLI | elixpo/blogs.elixpo |
| LixSketch | A shared canvas for sketches, diagrams and documents | elixpo/sketch.elixpo |
| Crumb | A self-hosted agent harness and terminal, written in Rust | elixpo/crumb.elixpo |
| Elixpo Open Source | A platform for running open-source contests and mentorship programmes | elixpo/opensource.elixpo |
| Oreo | An open MicroPython OS and hardware platform for an ESP32-S3 badge | elixpo/oreo |
| Person | Role |
|---|---|
| Anwesha Chakraborty (@anwe-ch) | Programme coordinator, programme point of contact |
| Ayushman Bhattacharya (@Circuit-Overtime) | Lead organisation administrator, mentor, founder of Elixpo |
| Vivek Yadav (@ez-vivek) | Organisation administrator, mentor, programme point of contact |
| Divyanshu (@divyanshuj91) | Mentor |
How Elixpo will run the programme, from selection to after the final
evaluation, is summarised at
gsoc.elixpo.com/operations. The full
handbook is in operations/:
- Communication: weekly cadence, response times and how to raise a blocker.
- Weekly report template.
- Mentor handbook: primary and backup duties, absence cover, review standards and notes.
- Evaluations: what they are based on and the early-warning process.
- Escalation: who to contact, in order, and how conduct reports are handled.
- Retention: what happens after the programme.
Elixpo has run open contribution in public since 2024. Maintainers took part in Hacktoberfest in October 2024 and October 2025: preparing work for outside contributors, reviewing their pull requests and merging them. In October 2025 the Chapter repository merged 47 Hacktoberfest-labelled pull requests from 24 GitHub accounts. The dated record, with links to the evidence, is on gsoc.elixpo.com/about.
- Read the project ideas and pick one or two.
- Set up the project from its repository and try a warm-up task.
- Introduce yourself and ask questions at gsoc@elixpo.com. GitHub Discussions for GSoC 2027, where applicants will introduce themselves and ask about the ideas, opens soon.
- Write your proposal with our template and submit it through the official Google Summer of Code website.
Programme questions and private matters: gsoc@elixpo.com.
Spotted a mistake or have a suggestion for an idea? Open an issue or a pull request; see CONTRIBUTING.md. Developer notes (building, checks and deployment) are in docs/DEVELOPMENT.md. This project follows the Elixpo Code of Conduct; report security issues as described in SECURITY.md.
- Site code: MIT. See LICENSE.
- Site text (
content/): Creative Commons Attribution 4.0. See LICENSE-CONTENT and LICENSES/CC-BY-4.0.txt. - Names and logos are not covered by either licence. See TRADEMARKS.md and NOTICE.
Google Summer of Code and the GSoC logo are trademarks of Google LLC. Elixpo is applying as a mentoring organisation and is not affiliated with or endorsed by Google.
