GSoC 2026 Ideas

[LaurentRDC]

Dear Cabal maintainers,

Haskell.org will be applying to Google Summer of Code 2026 (GSoC 2026)..

Are there some ideas by the maintainers for projects? Even if you don't have the capacity to mentor or write a proposal, it would be nice to track ideas. That might inspire others to join in.

[ulysses4ever]

We discussed this a little bit on today's Cabal meeting. There's not many ideas so far but we asked people on our Matrix channel to submit ideas.

In the past, @gbaz did a great job at proposing/mentoring GSoC project, so pinging him just in case.

I personnly think reviving the work on store GC would be a great project but I'm not sure about a good mentor for it (the original author hasn't been active in this repository for a while):

• RFC: Store garbage collection #10126

Other than that what I can think of is grouping several smaller feature requests (of which we have many!) into an artificial group and submit it. For instance,

More robust and user-friendly Cabal project setup (cabal.project files)

including:

• overriding constraints, especially important for imports (think importing LTS) RFC: Cabal support for LTS Snapshots #7556 (comment)
• don't trip on unrelated cabal.project files living up the directory tree, and do a smarter thing instead: "Error: cabal: There is no <pkgname>.cabal package file or cabal.project file." in directory with .cabal file #9353 (comment)
• cabal cannot find cabal.project or *.cabal unless packages is defined #5850
• confusing build messages about optimization Confusing -O1 in build profile #6221 (stretch but is related to the optimization field in cabal.project)

[ulysses4ever]

on ghc-devs, there was some more info posted just now:

If anything comes to mind, please submit an idea proposal using the instructions found here: https://summer.haskell.org/ideas.html.

and also

We are hoping to have ideas submitted prior to February 1st.