Vscodium: Cooperate with com.visualstudio.code.oss from flathub

[G-Ray]

@amtlib-dot-dll is doing a great job packaging the open source version of vscode to flathub.org (https://flathub.org/apps/details/com.visualstudio.code.oss).

Maybe vscodium contributors can merge efforts with him to avoid confusion between various OSS versions.

I propose to:

• Use the same project name. We could rename vscodium to CodeOSS, the contrary or pick another neat name.
• Merge doc and code if necessary, under the same repo, and indicate that a flatpak build is available on flathub.org.
• Create a static site to showcase the product and link to installation packages

[amtlib-dot-dll]

@G-Ray Thank you

@stripedpajamas Awesome for your project

• "Code - OSS" is the name used in the upstream, and I don't know why Microsoft put this name rather than "Visual Studio Code" in the publically available repository. Naming is unimportant
• IMHO, codes here are far less than my recipe to build the Flatpak package because Flathub requires offline builds. It's awesome for you to add a link mentioning that there is a Flatpak build of the open source version of Visual Studio Code
• We don't need Wine or something else to build the Windows package. There is a free service called AppVeyor and it is what Microsoft use to test the Windows build of Visual Studio Code some time ago
• I noticed that NODE_ENV=production is used in the build script. Long time ago when I tried to build it, this environment variable disrupts the build. Perhaps someone fixed it
• This line should be a secret for Microsoft but they leaked it by accident so you will see it everywhere. I prefer scraping it from here
• Welcome for discussion if you have any more questions

[stripedpajamas]

@amtlib-dot-dll thank you for the notes. I am working on the AppVeyor build now, so hopefully we will have the Windows build pretty soon.

I will link to the Flatpak package in the README for anyone who wants that.

@G-Ray I will go ahead and close this issue as I don't plan on merging the projects, but I will be sure to make it clear in the README where the Flatpak magic lives. If you feel that this issue warrants more discussion let me know and I'll reopen.

[rugk]

I will link to the Flatpak package in the README for anyone who wants that.

It's still not linked or did I miss something? @stripedpajamas

[stripedpajamas]

@rugk sorry! Forgot to update the README. I'll reopen this until a PR is merged that closes it