3 ms·

This post only mentions Roslyn, but the F# project will also be moved over. :)

by Permit 12y ago

kodablah 12y ago
I believe it has always been there: https://github.com/fsharp/fsharp https://github.com/fsharp/fsharp
- Permit 12y ago
  That's actually just a clone of the codeplex project. As mentioned in the README contributions first go (went?) through codeplex.
  - ghuntley 12y ago
    Correct but this is purely for legacy reasons - all changes currently go through Microsoft's full intensive testing process/suite due to shipping with Visual Studio/F# being a product whereby you can involve the call centres/invoke enterprise incident resolution process etc. Don Syme did a presentation over at http://www.meetup.com/fsharpsydney/events/204864872/ http://www.meetup.com/fsharpsydney/events/204864872/ last week which went into this in detail. This will all be changing with migration of development to GitHub first, codeplex will disappear in time as the language further continues on the path of seperation from Microsft - http://fsharp.org/ http://fsharp.org/
  - latkin 12y ago
    This is not quite accurate. fsharp/fsharp is the F# Open Edition repo, and has existed since long before the current (well, obsolete as of this week) Microsoft Visual F# repo on Codeplex. The F# Open Edition repo targets Linux/Mac/Mono explicitly. Compared to the Visual F# repo, it's quite close, but has a handful of tweaks to account for mono/xplat, plus has a bunch of xplat packaging capabilities. Before the VF# repo opened for business earlier this year, Open Edition was maintained based on the per-release F# code drops that constituted the old open source strategy for F#. Anyways, Visual F# (i.e. owned by MSFT, targeting windows/VS) is now at https://github.com/microsoft/visualfsharp https://github.com/microsoft/visualfsharp. There is even a [doc](https://github.com/Microsoft/visualfsharp/wiki/Code-Flow-to-Open-Edition https://github.com/Microsoft/visualfsharp/wiki/Code-Flow-to-...) explaining how the code flows to Open Edition from there.

This post only mentions Roslyn, but the F# project will also be moved over. :)

by Permit 12y ago

This post only mentions Roslyn, but the F# project will also be moved over. :)

kodablah 12y ago

I believe it has always been there: https://github.com/fsharp/fsharp https://github.com/fsharp/fsharp

Permit 12y ago
That's actually just a clone of the codeplex project. As mentioned in the README contributions first go (went?) through codeplex.
- ghuntley 12y ago
  Correct but this is purely for legacy reasons - all changes currently go through Microsoft's full intensive testing process/suite due to shipping with Visual Studio/F# being a product whereby you can involve the call centres/invoke enterprise incident resolution process etc. Don Syme did a presentation over at http://www.meetup.com/fsharpsydney/events/204864872/ http://www.meetup.com/fsharpsydney/events/204864872/ last week which went into this in detail. This will all be changing with migration of development to GitHub first, codeplex will disappear in time as the language further continues on the path of seperation from Microsft - http://fsharp.org/ http://fsharp.org/
- latkin 12y ago
  This is not quite accurate. fsharp/fsharp is the F# Open Edition repo, and has existed since long before the current (well, obsolete as of this week) Microsoft Visual F# repo on Codeplex. The F# Open Edition repo targets Linux/Mac/Mono explicitly. Compared to the Visual F# repo, it's quite close, but has a handful of tweaks to account for mono/xplat, plus has a bunch of xplat packaging capabilities. Before the VF# repo opened for business earlier this year, Open Edition was maintained based on the per-release F# code drops that constituted the old open source strategy for F#. Anyways, Visual F# (i.e. owned by MSFT, targeting windows/VS) is now at https://github.com/microsoft/visualfsharp https://github.com/microsoft/visualfsharp. There is even a [doc](https://github.com/Microsoft/visualfsharp/wiki/Code-Flow-to-Open-Edition https://github.com/Microsoft/visualfsharp/wiki/Code-Flow-to-...) explaining how the code flows to Open Edition from there.