REPO NO LONGER MAINTAINED - USE LINKED FORK INSTEAD - STOP LOGGING ISSUES

[shyal]

Thanks @yishanhe for finding a good and maintained fork:

Really appreciate that @skygragon contributed such a great tool.
But since it is not got maintained for more than half year.
I drilled down the fork network and found https://github.com/leetcode-tools/leetcode-cli is
very active and is maintained by the @jdneo who is the author of vscode-leetcode.
Maybe it is time to move on. But it is always better if we can avoid divergence.

#173

[skygragon]

@shyal sorry for my reply lately... the truth is, I got a new job last year and honestly it does cost all my energy and time due to the well-known 996 pressure...
However I'm glad you guys like @jdneo are helping around during my absence. Also I'm thinking of a better way to keep this project more active/responsive. I guess friends here are students mostly or working guys that seeking a job, eventually they will have new focus and move on. While I'd like to keep this project alive forever, and sincerely welcome more maintainers to make this happen.

[jdneo]

Echo for @skygragon. So far I was just making some workaround to the leetcode-cli in the fork. But it's not recommended to take that fork as a final solution. I'm still hoping the vscode-leetcode can directly use the original cli to provide features to the users.

It will be great if anyone is volunteer to be a maintainer for this great project.

[shyal]

@skygragon great to hear from you. My suggestion is to designate a team of maintainers to evaluate and approve pull requests. In my case, i've fixed issues in my branch that already have pull requests that were never merged.

It's totally understandable that you're busy with your job. My guess is this repo will remain is good health if some maintainers are allowed to merge into it.

[peterschussheim]

Can we close this issue or at least modify the title so it is not so misleading?