Consider moving the repo to tree-sitter-grammars

[amaanq]

Hey @eonpatapon, I hope you've been well. We at nvim-treesitter (and potentially more folks from other teams interested in an ecosystem-wide effort to maintain grammars) have decided to move all of our own grammars collectively into one org, to make it easier for us all to fix bugs or keep things up to date (scanner crashes, regenerating with the latest abi, etc.) without having to rely on one sole maintainer (you).

This is 100% optional, and please don't feel pressured or feel like you have an obligation of moving the grammar to the org, but it will help everyone a lot, us at nvim-treesitter, other users downstream, to know that a grammar won't ever die should a maintainer call it quits or go MIA. We also have org-wide actions that we maintain (out of sight, out of mind for you) and a grammar template (soon for newbies) in place to ensure authors have a better experience with working on and fixing tree-sitter grammars. It also enables anyone looking to find grammars for a specific language to only have to search in one spot

Our org is here: https://github.com/tree-sitter-grammars

If you want to participate (and don't worry, you'll still have full write perms to your repo, just no admin access), that'd be great! All you have to do is transfer the repo to me in the repository settings and I'll handle it from there. Thanks a lot, and again no worries if the answer is no!

[myitcv]

I had previously discussed with @eonpatapon moving this repo to https://github.com/cue-lang, the home organisation of the open source CUE project: cue-lang/cue#1921

That would still seem to be a better place for @eonpatapon's excellent work, and as part of the current work on cuepls it feels even more like the right decision to move it under https://github.com/cue-lang. Not least because there we will logically group editor plugins, grammars etc, but also so that we can more naturally manage access control as part of the CUE project, delegating to folks like @eonpatapon who have the expertise, but still guided by the actual changes being made to the language.

@eonpatapon - it was on my TODO list to message you regarding the transfer because it seems like there is a lot we can leverage from this project for the auto-generation of syntax highlighting grammars, IntelliJ plugin work, and more. So this issue served as a timely reminder to ping you. If you are still up for moving the repo to the CUE project, we can pick up conversation in cue-lang/cue#1921.