Is this extension still developed?

[sewbacca]

There has been no activity on @tomblind's profile for over a year now, so I wonder if the author has abondoned this project or even GitHub completly. It's a great extension and works reliable for the most part. There are some issues here and there, but also PRs available to fix them, so it would be great if they'd be merged.

Also if someone knows @tomblind directly, could he or she post that he is ok? I am a little bit concerned.

[tomblind]

I appreciate the concern, but I am doing well.

Unfortunately, real-life obligations have been taking up my time and I've had very little bandwidth for my OS stuff. But, the extension is still alive and I'll do my best to keep it from breaking down. Bigger updates will have to wait for awhile until my time frees up, though.

[sewbacca]

Glad to hear, that you are doing well, and thanks for the update! Life happens, so it's perfectly understandable to not have time for your other projects. Honestly, this is a bit of a lesson for me, not to read too much into profile activity. Anyways, I gonna be excited if any updates happen. Untill then, have a great time!

[treahard]

I too completely rely on this fantastic tool. The Symmetry Tax Engine is written in Lua and this extension is a life saver.

Thank you Tom.

-- Tom Reahard

On June 4, 2023 at 3:29:04 PM, Tom @.***) wrote:

I appreciate the concern, but I am doing well.

Unfortunately, real-life obligations have been taking up my time and I've had very little bandwidth for my OS stuff. But, the extension is still alive and I'll do my best to keep it from breaking down. Bigger updates will have to wait for awhile until my time frees up, though.

— Reply to this email directly, view it on GitHub https://github.com/tomblind/local-lua-debugger-vscode/issues/80#issuecomment-1575756766, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2RUGKYELZQM5CATYA7EELXJUD3BANCNFSM6AAAAAAY2EGDIU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Ismoh]

What do you think about adding a collaborator to this repo to keep it up to date and maintained, @tomblind ? Someone who can maintain PRs and release creation?

I know that there are more important things in life than maintaining a github repo, but would be awesome, if someone can assist as long as you can't.

[Ismoh]

I hope @tomblind won't be mad, but I really need all the PRs in your extension and decided to do so in my fork, until this repo is maintained again. I additionaly add a huge hint, that your the author of this extension.

[sewbacca]

I hope @tomblind won't be mad, but I really need all the PRs in your extension and decided to do so in my fork, until this repo is maintained again. I additionaly add a huge hint, that your the author of this extension.

Thank you for your efforts in maintaining the PRs. I genuinely appreciate it, especially considering how frequently I rely on this extension. Would it be feasible for you to deploy the merged extension on the VSCode Marketplace? This would greatly simplify the process of installing updates for all users.

[capacic]

The new repo does not have issues enabled.

I installed it on M3 Mac. Trying to start debugging gives an error: "Failed to find extension path".

[Ismoh]

I hope @tomblind won't be mad, but I really need all the PRs in your extension and decided to do so in my fork, until this repo is maintained again. I additionaly add a huge hint, that your the author of this extension.

Thank you for your efforts in maintaining the PRs. I genuinely appreciate it, especially considering how frequently I rely on this extension. Would it be feasible for you to deploy the merged extension on the VSCode Marketplace? This would greatly simplify the process of installing updates for all users.

Edit:
I think this doesn't work as you might imagine.
I can only publish as publisher ismoh and not as tomblind. I don't think anyone will get any notification in VSCode, that there is a newer version. I would need @tomblind's vscode marketplace PAT.

Otherwise it would feel like 100% stealing code.

This is why I initially wanted to wait for an answer from @tomblind. @tomblind please give me a chat!

[Ismoh]

The new repo does not have issues enabled.

I installed it on M3 Mac. Trying to start debugging gives an error: "Failed to find extension path".

Issues are enabled now.

[Ismoh]

Failed to find extension path

Should be fixed in v0.3.5 now.

[sewbacca]

Thank you for your efforts in maintaining the PRs. I genuinely appreciate it, especially considering how frequently I rely on this extension. Would it be feasible for you to deploy the merged extension on the VSCode Marketplace? This would greatly simplify the process of installing updates for all users.

Edit:
I think this doesn't work as you might imagine.
I can only publish as publisher ismoh and not as tomblind. I don't think anyone will get any notification in VSCode, that there is a newer version. I would need @tomblind's vscode marketplace PAT.

Otherwise it would feel like 100% stealing code.

This is why I initially wanted to wait for an answer from @tomblind. @tomblind please give me a chat!

I wouldn't consider a reupload stealing, especially considering the LICENSE of this project. As I understand it, you are free to copy, modify, publish and redistribute the software, as anyone else is allowed to.

On the other hand I completely understand why it feels like stealing. Yet I still think a reupload would be justified for three reasons:

1. As I said earlier, the marketplace allows for convinient updates, once new PRs roll in.
2. This extension has not been developed for almost two years now, which is discouraging for people who want to create PRs, but don't, because they don't see it being merged any time soon.
3. There are already good PRs available and unless people are actually looking for a fork where they are maintained, only few people will be able to benefit from the changes. A new published extension might not get all the attention from long time users, but from new users and users who are looking for another Lua debugger.

In my opinion, adding an info somewhere, that the reupload maintains some new features and PRs, untill further notice from the original dev, would suffice as not stealing.

I do agree though that a better solution would be if @tomblind added some active maintainers to their project. However this solution is not mutually exclusive with a maintained new extension at the marketplace.

[ogsadmin]

A suggestion for a temporary solution (until @tomblind surfaces again): Maybe @Ismoh could publish a *.vsix file in his GitHub fork as a release download?

• This will make it pretty easy to install/update the extension (just download, then in VSCode go to extensions and install from file) - no need to compile it yourself
• The metadata could have publisher as ismoh or tomblind - in case of ismoth as a seperate extension (would require uninstalling tomblinds extension first - I've done it in this way to keep the debug configuration identical) or with tomblind as an update.
• This could be "advertised" in this issue here (I would expect people downloading from the public VSCode Marketplace and later running into troubles would visit the @tomblind's GitHub page and therefore getting a link to @Ismoh's updates)

I think, we all agree about what a fantastic debugger extension @tomblind created for Lua - we should make it available to other Lua users! I feel that clearly stating this was originally developed by Tom Blind, but then improved by the community, is the way to go forward.

[Ismoh]

I think, I'll publish local-lua-debugger-vscode 2.0 soon, but I only will do if there are four volunteer collaborators. I don't want a unmaintained fork 2.0..

Take a look on: https://github.com/Ismoh/local-lua-debugger-vscode/discussions/6

[Ismoh]

FYI: https://marketplace.visualstudio.com/items?itemName=ismoh-games.second-local-lua-debugger-vscode