replace all instances of 'ln' with 'lightning' in README.md

[shea256]

No description provided.

[Roasbeef]

Changing this without changing the name of the repo will cause future go get ... calls to fail.

[Roasbeef]

Hey @shea256, thanks for the PR!

Changing the name of the project isn't as simple as changing a few lines in the README. As I pointed out in the comments above, changing the instructions for go get ... will break the installation command for users. In order to change the project name, while maintaining links circulating, we'll have to create a new repo, and edit the README of this repo pointing over to the new one.

As this change may be a bit involved, I'm closing this PR for now. We'll handle the steps required to make a smooth switchover.

[shea256]

@Roasbeef I realize that, I'm not a noob 😄

My point was to demonstrate how the language could be much better and how it would improve the branding / developer aesthetics, so I made some quick edits to the README.md file.

I figured someone on the team would have to go through and make edits to variable names and such and multiple commits would be required for the update.

Also I don't see why you'll need to create a new repo. Are you having people install directly from GitHub? I'm not quite familiar with go but surely it must have a package manager.

And sounds good RE the switchover.

[shea256]

It seems you should be able to do this without creating a new repo, but I could be mistaken.

[Roasbeef]

Yep, Go has a package manager. Go source code stored locally in a special "workspace". Within this workspace, packages are partitioned (under $GOPATH/src/) according to which version source control software each project uses. So if we change the name, then all go get ... pointers, and the folder structure locally would need to change also. Users could either re-name everything, or just nuke then start over.

A new repo would be required in order to avoid killing any active links to lnd on the net. Links to github.com/LightningNetwork/lnd would be broken since Github doesn't set up redirects if a repo name is changed.

[Roasbeef]

Actually, I'm wrong: Github does in fact redirect old links

[shea256]

Yes of course, I knew that. I rename repos all the time.