Update README to include information on correct package and usage

[michaeloyer]

I discovered this library through a tweet, but realized when I went to install this package in a NuGet explorer the referenced tweet was installing a deprecated and unlisted package and the repo didn't mention the current package. It also didn't add the additional namespace in the simple example making discoverability harder. The updates to the README should make the next new person attempting to use this to not have to jump through as many hoops as I did.

FWIW, I liked the NuGet package better as FsHttp because it's harder to find in a nuget explorer (looking up just FsHttp didn't show up until after I installed the package, and I have a harder time trying to remember what your last name is when I just want use it in an F# script) though I do understand the convention and it's nice to have something cool with your name on it.

Nice library! 👍

[dsyme]

Possibly we should move to "fsprojects" and try yo get the rights to the old package name?

[SchlenkR]

@michaeloyer thank you very much for your PR and for the comments, and please excuse the husstle :)

I see the point with package naming, and I was always uncertain if it's a good idea including the owner's name. Since I'm a freelancer, it's indeed some kind of advertisement. But in the end - who cares, and it's propably a better thing increasing convenience and accessibility for the users (see #81). BTW I'm the owner of the "FsHttp" package on NuGet, and I could easily reactivate this.

@dsyme I'm sure fsprojects is not "dotnet", but are there some brief hints on the impact / upsides / downsides for the original owner / the community of moving a project to fsprojects? Who is in charge of it, is copyright transfered beyond the granted rights in the project's license, etc.? If there are some statements, resources, or others, it would be helpful. If the opinion is that it's a benefit for the F# community, I'm open for moving it (Reed Copsey says it has nothing to do with FSSF).

Thank you, and hava a nice day.

[dsyme]

@ronaldschlenker The policies are here: https://github.com/fsprojects/fsprojects-admin. Happy to have feedback on them.

Reed and I chat from time to time and I guess we think of "fsprojects" as "FSSF-compatible" - not an actual activity of the foundation in any sense, but Sergey Tihon and I try to achieve alignment with the FSSF goals for education and community enablement through running the project space.

No copyright is transferred. No rights to code are granted beyond those in the project license. I'll make that clear in the policies.

It's more like a joint working space, with some loose shared goals, and if you abandon the project the backup maintainers have some rights to do things to the github project itself.

[SchlenkR]

Thank you @dsyme for pointing me to the document.

Ok, so why not move to fsprojects... I just want to clean up some things, remove some flaws and implement breaking changes, and then I create an issue in fsprojects for transfer :)