We are always looking for help on our projects. If you would like to volunteer, please reach out to us at volunteer@haskell.foundation, or join the Haskell Foundation Slack. If you have a proposal, we'd love to hear it!
The Security Response Team maintains the Haskell Security Advisory Database. This database can serve as the basis for Haskell-aware tooling, and it is exported to OSV, the industry-standard data source, for use in multi-language tooling.
The Haskell Error Index is a community-driven repository of detailed documentation for Haskell errors and warnings.
To decrease the cost of maintaining Haskell tools, the Haskell Foundation is leading the development of a stable API to GHC by facilitating conversations between tooling developers and GHC maintainers.
Bryan Richter is working full-time for the Haskell Foundation to improve GHC’s CI implementation, focusing on reliability and observability
The Haskell CI group meets monthly to discuss the effective use of CI with Haskell. It is a forum in which professionals can share experiences, ask each other for advice, and produce materials for the community on best practices and useful techniques.
Haskell language extensions are the mechanism by which language research and innovation are made optional. However, it is not always easy to see which extensions are expected to change and develop, and which are finished. The Haskell Foundation’s Stability Working Group is working on a simple, understandable classification that allows teams to make informed decisions about the tradeoffs between stability and innovation and to have their stability policy reflected in compiler warnings.
This book on writing fast Haskell code, including a detailed treatment of profilers and other measurement tools as well as optimization techniques that enable action based on profiles, was contributed to the HF by IOG, who continue to sponsor its writing. In addition to a describing tools and techniques, the book also provides case studies, showing how to dramatically improve the performance of real Haskell programs.
The Haskell Foundation is in the process of taking over the hosting of Stackage, a widely-used repository of Haskell packages that have all been tested to work well together that was developed and hosted for many years by FPComplete.
In order to make it easier for new contributors to get involved with GHC, the Haskell Foundation worked with OST Eastern Switerland University of Applied Sciences and the GHC developers to organize a three-day hands-on introduction, which was attended by 43 in-person participants, nine speakers from the GHC project, and six additional volunteers from the HF, OST, and the GHC project. This hybrid-online event was recorded, and the videos are available on YouTube, where they can be a continuing resource for new GHC developers and intermediate Haskellers who want to learn more about how GHC compiles their code.
The Haskell Foundation coordinated a process of making nightly builds of the latest development version of GHC conveniently available in GHCUp, making it much easier for the GHC team to gather feedback, especially from closed-source applications. With nightly builds available, projects can schedule a regular CI job that checks whether recent changes with the compiler are still compatible with the codebase, allowing developers to notify the GHC team much earlier in a development cycle. Additionally, it is now much easier for the GHC team to seek feedback regarding changes to the compiler. An example repository has been created by the HF’s Stability Working Group to demonstrate the use of nightlies with scheduled jobs on CI.
The Haskell Foundation assisted the GHC developers with getting feedback about short- to medium-term development priorities through a deliberative process, resulting in a list of priorities. The Haskell Foundation took care of contacting the users, clarifying their answers, sorting them by topic, and summarizing and analyzing the results. The HF then worked closely with the leadership of the GHC project to produce a report detailing their plans.
The UTF-8 character set encoding is the industry standard. Haskell Foundation drove the effort behind the migration of the core text libraries to use UTF-8 as a default. This will have a positive effect on text performance of many Haskell programs.
