Looking for contributors to keep this project alive

[fvarrui]

For many years, I have dedicated time and effort to this open-source project, and it has been amazing to see how it has grown and how many people have found it useful. However, due to a lack of time, I am finding it increasingly difficult to keep it up to date, manage issues, and respond to all requests.

To ensure the project remains alive and continues to evolve, more people need to get involved in its maintenance. I am looking for contributors who can help with tasks such as:

• Reviewing and managing issues.
• Evaluating and merging pull requests.
• Improving documentation.
• Implementing new features and fixing bugs.
• If you’ve used this project and would like to contribute to its sustainability, any help is welcome. No full-time commitment is required; even small contributions can make a difference.

If you are interested in getting involved or want more details, please comment.

Thank you to everyone who has supported this project over the years!

[maths22]

As the primary maintainer for the build and distribution toolchain for the FIRST Tech Challenge scoring system (https://ftc-scoring.firstinspires.org/local), which is built on top of this project, I would be happy to contribute to the maintenance of this project as time allows.

[fvarrui]

Hi Jacob! Thanks so much for offering yourself as a collab

[fvarrui]

I've created a new organization on GitHub, with the idea of ​​moving JP to this organization, so that it no longer belongs to me, but to the community.

This will facilitate the management of permissions on the project, being able to create teams, as well as also maintain auxiliary projects, such as the projects that I use to test JP or any other new project.

This move would cause a change in the Maven coordinates of the project (new groupId=io.github.javapackager):

<dependency>
    <groupId>io.github.javapackager</groupId>
    <artifactId>javapackager</artifactId>
    <version>x.y.z</version>
</dependency>

but I don't think this will affect too much, since I don't think there are other projects built on top of JP, but rather make use of the plugin.

And then we should register it as a new artifact in sonatype. I could take care of the necessary arrangements at https://oss.sonatype.org/ to release the plugin to Maven Central. And if it's possible, which I think it is, we could also automate the publication of new versions of JP using GitHub Actions.

[fvarrui]

@maths22 What do you think?

[maths22]

A new org would seem like a good idea, as would using actions for publishing. I'd imagine the mac stub launcher would also be a good candidate to move over. I would also imagine usage would almost entirely be with the plugin, so a readme/callout in release notes for the first version at the new coordinates would seem adequate.