The group works cooperatively with major industrial and community contributors to F# to facilitate open-source contributions to the F# core components. For example:
We cooperate with the Debian packaging team to see F# packaged on Debian.
Goals and Remit
See our Goals and Remit document.
To get involved:
Our mission is to maintain the excellent quality of the core F# implementation across these platforms, and to extend the tooling available for F# across your favorite platforms.
This technical guide discusses the FSharp.Core library.
Naming, Engineering and General Advice
How Your Contributions to the F# Language, Compiler and Core Library Are Delivered Cross-Platform
An Update on the F# Compiler Services, Visual F# Power Tools and more
Our first blog entry
Most group discussion happens in other forums. To contact the group, please either:
- Ask questions on StackOverflow
- Post to our Google Group
- Propose or discuss an F# language feature - please check for duplicates first
- Contribute an issue to the F# compiler and library
- Contribute an issue to other core repositories
- Contribute an issue to other F# community incubation projects
If using the Xamarin, Microsoft or Intellifactory professional tooling for F#, you should use the support contacts for those products. They may also refer you to the above forums for some issues.
The convenors of the F# Core Engineering Group are Michael Newtown, Dave Thomas, Tomas Petricek and Don Syme. You can contact them directly, though it is better to use one of the public forums above.
- Notes and Guidance on FSharp.Core
- Recommended Guidelines for F# Projects, Packages and Namespaces
- Online meeting notes, 18 September 2014
- Contributing to the F# Language and Compiler
- Some Recent F# Core Engineering Highlights
- Introducing the F# Core Engineering Group
- Online meeting notes, 02 July 2013
- The F# Core Engineering Group Goals, Remit and Activities