InnoSetup packages need new maintainer(s)

[idleberg]

I do not plan to continue work on any of the following InnoSetup-related packages:

• atom-language-innosetup
• sublime-innosetup
• vscode-innosetup → chouzz.vscode-innosetup

Why?

In the past couple of years, I enjoyed working on these projects even though I have never used InnoSetup myself. This joy has worn of considerably in the last couple of month, when I had to realize I have less and less time for "fun" projects like these.

How?

I'm looking for maintainers for any of the mentioned projects. Ideally, these repositories would be handled by a group of enthusiasts, since they are somewhat related:

1. Because Sublime Text was my go-to editor some years ago, it all started with this package. The original language syntax and auto-completions were created for Sublime Text. With the introduction of a new syntax format in Sublime Text 3, things got more complicated, but I did my best to keep the old TextMate and the new Sublime Text format en par.
2. Next up was Atom. The language system was converted with apm and the auto-completions were converted into snippets using atomizr. On top of that, I added a build-system using plain JavaScript. The task of converting the language-syntax is easy, as long as the TextMate format from the Sublime Text package is still maintained.
3. As with Atom, the Visual Studio Code package is largely based on the Sublime Text package. The language syntax is a verbatim copy from the Sublime Text package, the auto-completions were converted into snippets using atomizr. Again, this task is easy as long as the TextMate syntax from the Sublime Text package is maintained.

I understand that it's unlikely to find maintainers that will keep all three packages synchronized, especially since all editors (except VSCode) have introduced their own custom language format. However, this would be the ideal. Apart from that, maintainers should at least try to consider issues and PRs from the other packages. These decisions, of course, are not in my domain anymore.

More importantly, I want a possible transition to go forth as transparent as possible. Users need to be aware that a package is now maintained by somebody else.

So, that's all I can think of from the top of my head. I'm looking forward to see where this is going.

[chouzz]

Hi, @idleberg I would like to become a maintainer for vscode-innosetup, as for Atom and Sublime Text, I can take a look for their issues. I have 2 years experiences with Typescript and vscode extension development, but still a new comer for open source project, I am intersting in vscode extension, I have developed serval extensions in my company, and I am sorry to see such good extension archived, I would like to contribute my part on vscode-innosetup.

[idleberg]

Hi @chouzz, thanks for getting in touch. I've been thinking about to do this properly and I've come to the conclusion that it's probably a bit intransparent/untrustworthy to just hand a package to somebody else. How do you feel about forking and publishing the package under your name and I will put out one final release notifying users of available options?

[chouzz]

Thanks for reply. I am ok maintain a fork version, but I would like to maintain vscode version of Inno-setup, since I am not familiar with Sublime Text extension development and Atom is sunset.

BTW, you don't need to put final release, vscode provide a way to mark extension deprecated, if you think it is ok, I can release my version on marketplace and comment in discusstion, so microsoft team will mark deprecated and users can migrate easily.

WDYT? :)

[idleberg]

Took a while: microsoft/vscode-discussions#1 (comment)

🙏

[pzhlkj6612]

Thank you all for the hard work!