esoc2026 is the rulebook for a European stipend programme, not a codebase

Stipends are matched through hubs, not through a central committee

European Summer of Code funds stipends for contributors who are new to open source, and its stated purpose is to match open source projects with applied projects across Europe. The programme is explicitly indebted to Google Summer of Code for inspiration, and it sets out three goals: opportunities for junior developers to engage with open source worldwide, a link between the worldwide open source community and private and public sector projects throughout Europe, and support for the wider open source ecosystem. The applied side is the distinguishing part. The README says ESoC expressly helps applied projects connect with relevant open source, open source projects connect with applied projects and sponsors, and applicants work on open source directly in an applied context. That framing is why an organisation whose work is not itself open source can appear in a programme built around open source contributions.

Three hubs carry the matching, and more are wanted

The programme is described as organised in a decentral and distributed fashion, by hubs, and three are named. France is served by probabl, described as the scikit-learn company. Germany is served by the German Center for Open Source AI. Italy is served by Fondazione Bruno Kessler. The operational consequences are worth spelling out for anyone considering participation. Participants apply for projects with open source libraries or applied partners, sponsors from the public and private sector submit projects, open source projects apply for support, and the hubs throughout Europe carry out the matching process. A hub is therefore the route through which funding and project relationships are arranged, and the README says the network is actively being expanded, with contact through LinkedIn for details. If your project is outside those three countries, the practical first step is finding which hub would cover you rather than contacting the programme directly.

The affiliated project list is where to look for a project to join

Affiliation is the mechanism that connects an existing project to the programme, and the repository lists who is in. The current affiliated projects are AI-on-Demand, openML, pixi, pgmpy, pykalman, pytorch-forecasting, pytorch-tabular, pyaptamer, rattler, scikit-base, shap, skpro and sktime, with a further group under an Incubating heading that lists dsip-ts, Gradient-Free-Optimizers, hyperactive and prophetverse by name only. Two observations. The affiliated list is heavily weighted toward the Python and machine learning ecosystem, with several entries from the sktime family, so a project outside that space is less likely to find an established route in. And the incubating entries carry no links, unlike the affiliated ones, so their status and maintainers have to be established separately. Projects that want in fill out the open source project onboarding form, and the README says the network of affiliated projects is actively being expanded as well.

Two batches, each with a narrow application window

The 2026 cycle is scheduled in two larger batches, on February 18 and April 1, with projects released on a rolling basis in between. An information event for applicants and interested organisations takes place on January 30 from 11 to 14 UTC, hosted in the AI-on-Demand Discord events channel, and it covers general programme information, the applicant guide, the organisation and sponsor guide, and advice from previous mentors and successful applicants. Batch 1 opened applications on February 18 at 18:00 UTC with a submission deadline of March 19 at 18:00 UTC, followed by evaluation, reviews and interviews, with projects starting on April 15. Batch 2 opened on April 1 at 18:00 UTC with a deadline of April 30 at 18:00 UTC and projects starting on May 25. The changelog records how this moved in practice: the applicant and sponsor guides were published on 2026-01-05, batch 1 was released on 2026-02-18, the batch 2 release was moved to April 1 on 2026-03-18, and batch 2 was released on 2026-04-01.

Applicants register once, then follow the project card

The application procedure has two halves and the second one is where applicants get caught out. You register for ESoC through the ESoC applicant registration form, and you also follow any additional how to apply steps listed on the project card of the projects you are interested in. A card may require a second form or an extra task, and it may simply say that the ESoC form is enough provided you mention the project. There is no limit and no penalty for the number of projects you apply to, but the recommendation is to focus on at most three, because applying to too many reduces the time per application and hurts the quality of each. Both the ESoC form and the project specific steps must be complete by the project application deadline, which varies by project and is specified on the card. The practical advice in the FAQ section is unglamorous and worth following: use a correct email address, keep the same name and email across every form, note the relevant periods in advance, and check your email during them. Most forms allow updating a submission until the deadline, and where they do not, a second application under the same name works, with the last submission received before the deadline counting.

What is actually in the repository: one README and a folder of cards

The top level of the repository contains a .gitignore, the README, a cards directory and an esoc2025 directory that holds the projects from the previous year. There is no code, no build system and no published licence, and the primary language field is empty. The README is the product, and the changelog section inside it is the closest thing to a release history, since the repository has no GitHub releases either. Two practical consequences. If you want the current state of the programme, the README is the authoritative copy you can diff over time, and the 2025 directory gives you a template for what a year of project pages looked like. If you want to reuse or embed this content in your own tooling, the absence of a licence means there is no stated grant to do so, so check with the programme or the hub before scraping or redistributing the project cards.

Running your own contributor programme is the alternative

For an open source project that simply wants help, the alternative to ESoC is to run a call for contributors directly, with your own issue labels, a good first issue list and a private channel for questions. The difference in approach is not the work, which is the same, but who carries the process. Doing it yourself means you write the mentoring plan, do the screening and track the stipend yourself. Going through ESoC means the hub handles the matching between applied partners and open source projects, applicants go through a shared evaluation and review round, and the funding is arranged through the programme. That arrangement is worth the constraints when the project is outside the affiliated list or outside the three current hub countries, because affiliation and matching are the parts you cannot easily do alone. For a project that is already affiliated, or an applicant who wants the shared evaluation and a funded context, the ESoC route is the cheaper one, and for everyone else the direct route remains open.

Editorial conclusion

Use esoc2026 when you are applying to European Summer of Code 2026, when you are an open source project considering affiliation with a hub, or when you want to understand how the stipend, the hub matching and the evaluation windows fit together in one place. It is not a repository to fork, extend or depend on, since it holds a README and a cards directory with no published licence and no releases. Before you act on it, read the specific project card for your deadline rather than the batch dates, since project deadlines vary and individual projects may add their own conditions, and confirm current details with the hub or the programme site at esoc.dev, given that the last push here was on 2026-06-07.

Frequently asked questions

Official sources

1. european-summer-of-code/esoc2026 on GitHub
2. Issues
3. README