InnoSetup packages need new maintainer(s) #2
idleberg
announced in
Announcements
Replies: 1 comment 4 replies
-
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. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I do not plan to continue work on any of the following InnoSetup-related packages:
vscode-innosetup→ chouzz.vscode-innosetupWhy?
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:
apm
and the auto-completions were converted into snippets usingatomizr
. 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.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.
Beta Was this translation helpful? Give feedback.
All reactions