“F# Core Engineering Activities” is a loose term for activities by the people who maintain and contribute to the repositories of The F# Software Foundation. There are not many “meetings”, most work is coordinated via github issues.
These people - both maintainers and contributors - work cooperatively with major industrial and community contributors to F# to facilitate open-source contributions to the F# core components.
Each Monday we aspire to hold an “F# Compiler and Core Engineering Office Hours” chat on the #compiler channel of the F# Software Foundation. Normally hosted by Don Syme, we’re also looking for volunteers to act as host when he’s not available.
The activities include:
Working with the Mono team to see F# packaged as part of standard Mono distributions.
Working with the Debian packaging team to see F# packaged on Debian.
Please join in the fun!
Goals and Remit
F# Core Engineering Activities dates back to 2013. The FSSF board assigns permissions and conducts oversight of the activities through a board resolution in 2015.
See our Goals and Remit document.
The FSSF board appoint a “chairperson” who has responsibility for assigning permissions and arranging a degree of oversight. The last chairperson appointed was Tomas Petricek for 2015-16, a new chaiperson is currently being sought.
Maintainer (pull-request) permissions for various repositories is listed below.
Some specific people with maintainer permissions are as follows:
- fsharp - Don Syme, Enrico Sada, Tomas Petricek and http://github.com/fsharp/FSharp.Compiler.Service
- FSharp.Compiler.Service Don Syme, Enrico Sada, Tomas Petricek
- fsharp.github.io - Don Syme, Dave Thomas, Tomas Petricek and http://github.com/fsharp/FSharp.Compiler.Service
- fslang-design and fslang-suggestions - Don Syme, Chester Husk III, Jared Hester, Kurt Schelfthout, Marcus Griep - Language Design, Suggestion, RFC Curation and other contributions
To get involved:
The aim is to maintain the excellent quality of the core F# implementation across these platforms, and to extend the set of tools available for F# across your favorite platforms.
If you are working in some particular area and would like to update your activity/responsibility, please submit an edit to this page.
Guides and Posts
Group focused to improve the F# story on .NET Core and integration in the .NET Core SDK
A link to the F# RFC process
This technical guide discusses the F# Compiler.
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 discussion happens in other forums. Please use any of the following:
- 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 you are using an F# package from Xamarin, Microsoft or another company then you should contact them via their support for any issues or questions. They may refer you to one of our forums for some specific issues.
- Core Engineering online meeting notes, 19 November 2018
- Starting an F# + .NET Core Development Group
- The F# Language and Core Library RFC Process
- F# Compiler Technical Overview
- 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