What Open Source projects should our scholarship recipient work on?



Outreachy Diversity Program & FSharp

The F# Software Foundation Board has recently voted YES to tentatively beginning a foray into Outreachy, the 501©(3) nonprofit under The Software Freedom Conservancy, as a diversity initiative to bring talented junior developers into F# Open Source Software. To read more about the program click here.

We need your help.

We are looking to get feedback from the community on what projects would be good and appropriate to present to a mentee. Remember, they will have a mentor from the community helping them on their contribution(s) and will work for 3 months on it. These projects should be somewhat “hype”-worthy as a deliverable for the mentee is blogging about their work.

Where to begin?

The board has some ideas about what would be good, but what do you think? Fable? Paket? Giraffe? Ionide? Most desired language feature? Reply below and start the conversation.

If you’re interested in becoming a mentor, please reach out on FSSF Slack and definitely check out Selketjah’s post.

F# Weekly #3, 2019 – Category Theory for (dotnet) Programmers & Fabulous 0.3


If someone would be interested in editor tooling, I’d recommend working on FsAutoComplete or Forge rather than Ionide itself - those utilities used by Ionide (and other editors) are the places where most of the interesting things happen.


While I can’t suggest specific projects, I’d say that one of the most asked-for pieces in the F# ecosystem is better IDE support.

These days, I realise that people come to F# from many different backgrounds, but AFAICT, a large proportion are still C# developers who are curious about F#.

C# developers are used to astoundingly good IDE support. Given that the C# language itself is what it is, it’s amazing what Visual Studio can do with it. Not only syntax highlighting, but refactoring support, code snippets, code lens, static code analysis, all of that.

When C# developers realise how little of that is available for F#, they’re already put off by the language. F# could really use better IDE support.

I’m not only talking about more features, but just as much features that are as reliable, as robust, as the corresponding features are for C#.


One topic that our local meetup has discussed working on together is increasing the overall helpfulness/friendliness of error messages from the compiler. Perhaps a specific subset of error messages — e.g. ones that might be daunting to new F# devs — would be a sufficiently narrow focus for a mentor/mentee pair over the course of 3 months?

At the very least, I would be up for working on and blogging about error messages (though I’ll probably end up applying regardless of the particular project FSSF chooses) ^^


How about something around missing = after a let…?