Set up ElixirLS fork for Visual Studio Marketplace

In an effort to get this project revitalized, I am setting things up for publishing to the marketplace before I start trying to merge in any fixes or features. I want the published extension to be clearly labeled as a fork of Jake’s work but I also want to be set up so that, if we end up being viable long term, we don’t have code and settings littered with fork for example. Here is what I propose.

1. We use elixir-lsp (display name Elixir Language Server Protocol) as the publisher. Sticking with this as our org name and publisher name feels like consistent branding that should help users understand where it came from. Alternatively we switch to just ElixirLS (I grabbed the elixir-ls org if needed) since this is the language server not the protocol, but that’s not super important.
2. We use elixir-ls for the package name, making the full package id be elixir-lsp.elixir-ls or elixir-ls.elixir-ls if we dropped the P.
3. We use something like “ElixirLS Fork: …” as the display name of the extension, so that anyone who finds us in the marketplace knows right away that this is a fork and isn’t misled if they were trying to find Jake’s extension.
4. We ensure that the README as displayed on the extension’s entry in the marketplace clearly calls out Jake’s great work and the reason for the fork, and points people to Jake’s extension if that is what they were looking for.
5. We use ElixirLS for the langId as opposed to Jake’s elixirLS. This is very similar I know, but it is different enough to not squash config people are using from his extension and doesn’t require that fork or similar be left in settings for users of this fork.
6. We use “ElixirLS” and not “ElixirLS Fork” in the UI labels. It seems unlikely that someone will have both extensions installed at the same time so it doesn’t feel necessary to call out fork in those labels.

@JakeBecker I’d love to hear your opinion on this if you can spare the time. I don’t want to do anything disrespectful to your work and hope to help this thrive for the sake of the community.

Anyone else have an opinion? @axelson? @msaraiva?

[axelson]

Okay, I think we are on the same page. Thanks for taking the screenshots, it’s helpful to see what it will look like visually.

[axelson]

@JakeBecker Congrats on getting married! That’s very exciting, and very busy 😃 I hope you get that job and get paid to work on ElixirLS, that would be awesome 🎉