Fork announcement: VEY

[zh-jq]

Hi all,

I’m the original author of G3.

I still have write permission on this repository, but I no longer have the admin permission needed for long-term project maintenance and future development here. Because of that, I have forked G3 into a new project named VEY and will continue active development there.

Project link:
VEY-OSS/vey

Why this fork exists:

• I do not have the repository permissions needed for long-term stewardship in this org
• I want to continue developing the project actively
• VEY will be the place where I continue my work on the codebase

What VEY is:

• a fork of G3 created by the original author
• the project where future development from me will happen
• an independently maintained continuation of the codebase

Compatibility:

• the codebase remains broadly compatible in design and behavior
• however, application names have changed from G3 to VEY
• because service names, executable names, and configuration directories under /etc use the application name, migration requires some system-level renaming

What users should expect:

• new development from me will happen in VEY rather than in this repository
• documentation, issue tracking, and future changes will gradually move to VEY
• VEY should be treated as its own actively maintained project

New contributors are very welcome in VEY.

If you are interested in contributing code, documentation, testing, packaging, or design discussions, please join the new project there. I would be glad to work with both existing G3 users and new contributors in VEY.

Simple migration notes:

• replace old G3 executable names with the corresponding VEY executable names
• update systemd unit files and service names if they include the old application names
• migrate configuration paths under /etc/<old-app-name>/ to /etc/<new-app-name>/
• review any hard-coded paths in deployment scripts, container files, and monitoring configs
• review log paths, runtime directories, and PID or socket paths if they include the old names
• verify service users, permissions, and startup arguments after the rename

I’m posting this here so anyone following G3 can easily find the continuation project.

Thanks to everyone who used, tested, and contributed to G3.

Note: this announcement text was co-authored with GPT-5.4.