Move into `EmmyLuaLs` GH Organization ?

[alek13]

As for now, there are 2 organizations:

• EmmyLua
• EmmyLuaLs

This is "slightly" (actually huge) confusing for everyone — both users and contributors.
I got confused myself by all these versions/copies/variants.

I suggest making the first small step towards unification:

• Move this repository to EmmyLuaLs.
  In fact, this extension already uses the new emmylua_ls, which is located in emmylua-analyzer-rust, which is hosted under the EmmyLuaLs organization.
  • No Breaking Changes: GitHub automatically handles redirects for the repository URL, clones, stars, and forks,.. so on...

The migration will solve several problems:

1. Unified Naming & Publishers (Marketplace / Open VSX)
   The naming and publishers situation is currently a mess: in the VS Code Marketplace, the extension is under the personal account of tangzx (tangzx.emmylua), related plugins (like EmmyLuaCodeStyle) are under CppCXY, and on Open VSX, third parties are publishing their own forks (like theo.emmylua or xuhuanzy.emmylua-luals).
   Consolidating under EmmyLuaLs is the perfect opportunity to set up official, unified organization publishers/namespaces (e.g., emmyluals.emmylua) across the MS Marketplace, Open VSX Registry, and so on... This ensures brand safety, ownership continuity, and trust.

2. The Documentation Mess
   The documentation issue is critical: right now, the old emmylua.github.io website is hosted by the old organization and leads to the Java version, while the docs for the new Rust version are hidden deep inside the emmylua-analyzer-rust repository.
   Moving the repo to EmmyLuaLs will help users understand that it's all part of the same project, and they will actually know what is relevant for the modern extension.

Note

Here also I would like to help to make new modern website with docs. (something like our: https://voxrame.dev/ , https://voxrame.dev/utils/helpers , but in Emmy Style ) -- with search through docs/annotations/..., with translations into several languages, and so on...

3. Scattered Issue Tracking
   Users frequently open issues regarding the Rust language server directly in this VSCode-EmmyLua repository just because it's the client they use. Having them in separate organizations makes triaging and transferring issues between the extension and the core LSP server unnecessarily annoying.

4. CI/CD and Release Automation
   Additionally, this will allow us to easily build a streamlined CI/CD pipeline where an update or a tag in the Rust LSP core can automatically trigger automated testing or a release candidate preview for the VSCode extension.

---

PS: cant register in QQ. :( @CppCXY , have you Discord ? (cc: @tangzx)

[CppCXY]

I think many of the points you made are very good, but I don't agree with the migration. Some people had advised me about it before you, and I turned them all down. The conclusion is simple: unification is right, but I'm not willing to do it. This might touch on sentimental notions, and I firmly hold that the emmylua plugin belongs in the emmylua repository, whereas emmyluals is merely a language server (even though it has grown beyond that) and a specialized organization at that.

By the way, I'm not actually have discord, because it's very difficult for Chinese people to register for these services, and my English is very poor, so all our chats are conducted through translation.