Looking for New Maintainers

[petertzy]

First of all, I want to sincerely thank everyone who has contributed to this project.

I want to be transparent about something: I am not a strong programmer. My main strength has always been reviewing code, coordinating work, and defining the project's direction. Nearly all of the project's most difficult technical challenges have been solved by contributors and AI agents. In fact, I have not personally written any of the project's code from start to finish.

As the project has grown, it has also become significantly more complex. At this point, I hope the community can continue maintaining and improving it, with the long-term goal of bringing it to a commercial-quality standard.

Current Priorities

The most urgent tasks are:

• Simplify the project by removing obsolete and redundant files left over from previous refactoring efforts.
• Continue improving the codebase and polishing existing features. Several parts of the project still provide a suboptimal user experience and need further refinement.

Temporary Maintainer

Because I am currently too busy with work to continue actively maintaining the project, I have invited @lwu1822 to serve as the temporary maintainer.

I truly appreciate their willingness to help move the project forward.

If @lwu1822 is no longer able to maintain the project in the future, I will continue looking for another suitable maintainer.

If you are interested in taking on this responsibility, please feel free to introduce yourself. I would be happy to consider adding dedicated long-term maintainers to the list of project owners.

Long-Term Vision

My long-term goal is to see this project eventually reach a commercial standard.

If the project is commercialized in the future, my current plan is to grant project contributors broad authorization for their work, and for project owners to share any potential profits equally. While this is only a long-term vision at this stage and not a legal commitment, I want to make my intentions clear from the beginning.

Finally, thank you to everyone who has contributed, tested, reported issues, reviewed code, or simply supported this project. None of this would have been possible without the community.

[lwu1822]

Thank you so much for the kind words! I'm really honored you thought of me, and I'd be very glad to help take this on.

Your priorities make a lot of sense to me. Starting with the cleanup feels right. Once the old files from the earlier refactors are cleared out, I think everything after it gets a lot easier. Alongside that, I'll make sure to keep issues triaged and labeled so it's easy for people to find a good place to jump in, and to keep PRs moving so no one's work sits waiting.

For the UX edges, I'll open issues as I go so everyone can see what's in progress and what's still up for grabs.

Two things whenever you get a chance:

• Could you please grant me merge permissions, along with anything else I'd need on the maintainer side? Thank you very much!
• If any starting points come to mind on what was left behind intentionally versus accidentally during the refactors, that would be a big help in making sure the cleanup doesn't remove anything the community still relies on!

Thank you @petertzy again, and thank you to everyone here who's contributed, tested, reported issues, and stuck with this project. Really looking forward to working with you all!

[petertzy]

Thank you for accepting the invitation. I've already sent you the collaborator invitation. Once you accept it, you should have the necessary permissions.

For safety, I've made a complete backup of the entire project in a separate repository. I also created a branch called archive, which contains a backup of all the code.

I feel that everyone is quite busy these days, so I think we should move this project forward at a comfortable pace. There's no need to put ourselves under any time pressure.

I originally created this repository as a hobby about two years ago. About a year ago, with the help of AI tools and the valuable programming experience I gained during my first year working in my company's IT department, I was able to significantly improve the quality of the project. That's how it gradually started attracting attention from more people.

Since I've already put the strongest safeguards in place, you can feel free to delete, refactor, or improve the code without worrying about losing anything. If something turns out to be a mistake, we can always recover it from the backups.

My current goal is simple: even if this project never becomes commercially successful, I hope it can still become a useful tool that makes everyday life easier for myself and for at least a small group of people.

Regarding the parts you mentioned that could be removed, I think all of the pre-refactoring code can be deleted. I intentionally kept it isolated from the new implementation, treating it only as a reference during the refactoring process. At this point, it has already served its purpose, so I don't think it needs to be kept anymore and can be removed entirely.

[lwu1822]

Thank you very much for the info and setting up the backups and the archive branch! Knowing there's a safety net makes the cleanup a lot less nerve-wracking, and it's really thoughtful of you to have done that before handing things over.

That's very helpful context on the pre-refactoring code, thank you. Since it was kept isolated and has already served its purpose as a reference, I'll plan to remove it entirely. I'll still open an issue listing what's going so it's on the record and anyone who wants to weigh in has the chance.

I really appreciate you saying there's no time pressure. That's a nice way to run things, and I agree, steady progress at a comfortable pace will probably serve the project better than rushing anyway.

I also think that's a lovely goal for the project. Something genuinely useful for you and a handful of other people is worth building, whether or not anything commercial ever comes of it. And it's clearly already resonated with more than a few people, which says a lot about what you've built over these years.

Thanks again for trusting me with this! I'll dive in and reach out if anything comes up.