GSoC 2025: projects, proposals and other information

Community GSoC
1

Welcome prospective GSoC 2025 participants!

This post aims to provide some guidance about the program in 2025.

  1. Projects
    Please take a look on list of projects at: The LLVM Compiler Infrastructure Project. Projects also have topics below on the Discourse, so you can ask mentors about details of the project, skills required, etc. Also, please watch this forum for important announcements.
  2. Proposal & application process
    We encourage you to discuss your proposal before submitting to GSoC system. Having your proposal discussed ensures that your proposal will be well aligned with the project. Please do not hijack other threads (e.g. with mentor Q&A) and create a separate new thread to discuss your proposal. The ideal proposal will contain:
  • A descriptive title
  • Information about you, including contact information. Please do not forget to include:
    • Your prior compiler and compiler-related experience, if any (e.g. studies at the University, prior contributions)
    • Whether you have any prior contributions to LLVM. If yes, please provide links to these contributions.
    • Your past open source participation and contributions, if any
    • Your knowledge of programming languages (e.g. C, C++, Python, Rust, etc.) and your estimate of your level of experience
  • Information about your proposed project. This should be fairly detailed:
    • Synopsis
    • Benefits to Community
    • Deliverables
    • Timeline
    • Related Work
  • Include your answers to the following questions:
    • Why are you interested in our organization?
    • Why are you interested in this particular project?
    • What makes you a good candidate to work on this project?
    • What do you expect to get out of this GSoC program?
  • Information about other commitments that might affect your ability to work during the GSoC period (exams, classes, holidays, other jobs, weddings, etc.) . Also, if the project allows both medium- and large-size participation, indicate the intended size of the project and the timeframe of your participation.

Double check before your submission that you’re eligible for participation. If in doubt, contact GSoC support. Some useful information could be found in FAQ; essentially the program is open to beginners in open source or students. If you’re a professional software engineer or had similar experience, then you’re not eligible and your application will be rejected.

Please note that proposals generated using Large Language Models (LLMs) will not be accepted. We expect original work and thoughtful responses. Correcting grammar and spelling errors with the help of technology is acceptable, but we draw a clear line at using LLMs to create content.

  1. Important LLVM + GSoC details.
    LLVM organization adds the following to the GSoC process. By submitting your proposal you agrees with the following:
  2. LLVM organizes midterm GSoC conference where program participants present their projects. Participation in this conference is required for midterm evaluation.
  • Final project report should be presented and submitted as LLVM blog post prior to final evaluation and is a prerequisite to it.
  1. Useful links
  1. Deadlines
  • Submission to GSoC system opens on March 24th at 18:00 UTC.
  • Submission to GSoC system ends on April 8th at 18:00 UTC.
  • Results to be announced on May 8th at 18:00 UTC.

Welcome to 21th Summer of Code!

5 Likes
LLVM Weekly - #584, March 10th 2025
3

I’m a bit confused by this. We normally only use Discourse threads for discussion of (mentor-proposed) projects in general. Specific proposals from students are reviewed privately (e.g. via Discourse PMs, email, etc), not in public Discourse threads.

Are you saying that the blog post itself is going to act as the final report this year? How will you handle scheduling in this case? Are we okay with two dozen GSoC blog posts going up on the official LLVM blog in a span of a couple of days before the submission deadline?

1 Like
4

It is enough to submit a PR before the submission deadline. Then we can schedule, say, one blog post per week. We did something like this this year and it worked quite nice.

The final report still should be submitted to GSoC system. But the intention is to have PR with blog post submitted before the final submission deadline, so we won’t have long tail of participants who “forgot to submit” or “sorry, was very busy”, etc. Overall, we always were very flexible with blog post provided that they are submitted within reasonable time frame and structured reasonably. If someone does e.g. blog diary with weekly progress report, we used to happily link this as well.

5

What we do not want is to have multiple proposals to be discussed within the same thread. Certainly it is fine to discuss the proposal via email, etc.

1 Like
8

Hi @akorobeynikov,

I’m considering a couple of GSoC 2025 project ideas related to improving LLVM support in Haskell. Would it be alright if I send my proposals to your email for initial feedback?

Thanks!
Diego Antonio Rosario Palomino

9

I would suggest you to find the mentor who might be willing to mentor these projects. Then you’d work with this mentor and in the meantime let them contact me.

1 Like
10

Thanks so much for replying so quickly!

Just to clarify, I’m still deciding between the two project ideas and would focus on one or the other depending on how discussions evolve.

I do have a couple of people in mind who might be willing to mentor the project. However, they’re not official LLVM developers — they just use the LLVM toolchain. Are there any specific requirements for mentors, such as needing to be part of the LLVM developer community?

Thanks again!

11

Sorry for the delay. I sent you an email at anton@korobeynikov.info in case there is still time for my application

12

Hello,
I’m getting married in May and will be on my honeymoon for a week. Do you think this will be easy to accommodate and should I mention it in my proposal?

Thanks