Closed dsyme closed 6 months ago
We were talking about this on our private Slack channel last week - none of the maintainers have any problem with making this change, any concerns were around branding/perception only. While @Krzysztof-Cieslak, @TheAngryByrd and I are the core maintainers nowadays, the project didn't start as part of Ionide and I don't want to give the impression that we made this thing out of whole cloth.
In terms of branding / perception, is the "ionide" brand ready to claim itself outside of VSCode, towards editors FSAC is currently used in?
I'm not sure there is any strong upside, but to get more contributors under the ion IDE umbrella, while fsprojects is more of a catch all, reach many more areas than F# language tooling.
Yes. Please
We've reached out to @ReedCopsey to confirm that there's no problem with this, so we're going to proceed with the move to the Ionide org.
Functionally there should be no change in maintainership, permissions, or procedures - FSAC will continue to be maintained by @Krzysztof-Cieslak, @TheAngryByrd, myself, and the other Ionide maintainers. There may be a brief disruption in CI/CD pipelines as the code moves over, and we may have to make small alterations to the build scripts, but we don't anticipate any large problems as a result of this move.
Closing this issue as the repository has now been transferred to https://github.com/ionide/FsAutoComplete.
Version
x
Dotnet Info
Looking over the repos in fsharp org, this is the last active engineering repo - the org is otherwise for FSSF and F# lang design topics
So I'm wondering if we should move this to fsprojects? Or ionide?
It's no big deal, but may make sense.
It could also theoretically merge with dotnet/fsharp long term as part of a mono repo for core F# engineering assets
Steps to reproduce
na
Details
Na
Logs
Na
Checklist