Looking for active Maintainer to support Atom-Beautify / Unibeautify related projects

[Glavin001]

Hello and thank you for your interest in Atom-Beautify / Unibeautify!

I am not personally using Atom editor at this time and do not have much time available to actively maintain these projects at the current time. However, I recognize many of you would benefit from continued support. I would love to have someone assist me / share the load!

First priority is going through the backlog of Pull Requests and then looking through open Issues for the most important features / bug fixes up next.

Please let me know if you're interested in becoming a more active contributor.

Thank you!

[seahsky]

Hi @Glavin001 , are you still looking for maintainer on this project? I might help out during my off-work hours

[16amattice]

@Glavin001 Is this something you are still looking for?? I would definitely like to help contibute on this.

[Glavin001]

The Atom editor is not longer supported: https://github.blog/2022-06-08-sunsetting-atom/

Therefore, next steps would be to determine which editor(s) most people are moving to (e.g. VSCode?) and contribute to Unibeautify core and extensions for those editors, which will replace Atom-Beautify.

Thoughts?

What editors are each of you migrating to? I'm using VSCode now.

[16amattice]

@Glavin001 I mean I recently switched over from Visual Studio to VSCode myself. Personally I like the layout and think its heading in the right direction compared to Visual Studio. Is Unibeautify already to the point of ready to use in VSCode, or what needs to be completed/updated?

[16amattice]

@Glavin001 so I'm looking more into this.
So is unibeutify the core of the application and atombeautify and other ones are extensions? If so I'm assuming we could go ahead and archive this project. Or do we need to directly edit unibeautify core to add support for other applications. Some cleanup is probably in order. I would love to help, just want to know where this is at and what the goals are.

[marc-medley]

What editors are each of you migrating to?

VSCodium where extensions are provided via the Open VSX Registry. Open VSX is an Eclipse Foundation open-source registry for VS Code See github.com/eclipse/openvsx.

[SilentGlasses]

Would be nice to get code editors to connect via API or some other integration method than have a direct plugin that needs to get extra maintenance outside of this project?

[SilentGlasses]

I am deciding between Pulsar (successor to Atom) and Zed

Leaning more toward Pulsar as it's not a huge learning curve from Atom.

[SilentGlasses]

I am not a dev but I can certainly help with keeping the issues clean and discussing why they are there to determine priority...

I would even suggest closing out all existing issues since Atom has been EOL and focus on Pulsar to start with since that is the successor to Atom.

[16amattice]

I am not a dev but I can certainly help with keeping the issues clean and discussing why they are there to determine priority...

I would even suggest closing out all existing issues since Atom has been EOL and focus on Pulsar to start with since that is the successor to Atom.

I definitely agree with this. I'm assuming the original dev doesn't have much time to work on this sadly.

[16amattice]

I am deciding between Pulsar (successor to Atom) and Zed

Leaning more toward Pulsar as it's not a huge learning curve from Atom.

Pulsar seems like a good idea, but it is also in an "earlier" stage of development, so it is possible that upcoming changes could affect things that would have to be kept track of.