What problem would this solve?
Herald's naming is currently tied to "ASL3" throughout — the repo name (ASL3-Herald), install paths (/etc/asterisk/scripts/asl3-herald, /var/www/html/asl3-herald, /usr/local/bin/asl3-herald), the systemd service (asl3-herald.service), the main script (asl3-herald.py), the CLI, etc. This doesn't match the naming convention used by the rest of my AllStarLink tooling (e.g. ar-news, lnkact-monitor — not asl3-lnkact-monitor), and bakes a version-specific name into the project. If AllStarLink ever moves to ASL4, "ASL3-Herald" becomes a stale/misleading name baked into every path and file, forcing a much bigger migration later than if it's just called "Herald" now.
What would you like to see?
Scrub "ASL3" from the project's naming wherever it's just a naming convention rather than an actual technical dependency — repo name, install paths, config paths, systemd unit name, script/binary names, internal identifiers, etc. — and rename to just "Herald" (matching the ar-news / lnkact-monitor style).
The README should keep stating that Herald is currently built for/tested against ASL3, and can call that out explicitly if/when ASL4 support is added later — but that should be a documentation update, not a repo-wide rename.
Notes / open questions for planning
- Needs a plan for existing installs: renaming
/etc/asterisk/scripts/asl3-herald, /var/www/html/asl3-herald, the systemd service name, etc. means install.sh needs a migration path (move config/state, disable old service, re-point Allmon3/Supermon integration links) so existing users don't lose their config or end up with duplicate installs.
- GitHub repo rename (
ASL3-Herald → Herald or similar) has implications for existing clones, the install.sh one-liner URLs, and any external links (README badges, wiki, this very issue tracker).
- Not being tackled immediately — filed to track scope and pick back up when there's time to plan it properly.
Alternatives considered
Leave the ASL3 naming as-is until ASL4 actually exists, and do a larger rename/migration at that point instead of preemptively. Rejected for now in favor of avoiding a bigger rename later once more is built on top of the ASL3-specific naming.
What problem would this solve?
Herald's naming is currently tied to "ASL3" throughout — the repo name (ASL3-Herald), install paths (
/etc/asterisk/scripts/asl3-herald,/var/www/html/asl3-herald,/usr/local/bin/asl3-herald), the systemd service (asl3-herald.service), the main script (asl3-herald.py), the CLI, etc. This doesn't match the naming convention used by the rest of my AllStarLink tooling (e.g.ar-news,lnkact-monitor— notasl3-lnkact-monitor), and bakes a version-specific name into the project. If AllStarLink ever moves to ASL4, "ASL3-Herald" becomes a stale/misleading name baked into every path and file, forcing a much bigger migration later than if it's just called "Herald" now.What would you like to see?
Scrub "ASL3" from the project's naming wherever it's just a naming convention rather than an actual technical dependency — repo name, install paths, config paths, systemd unit name, script/binary names, internal identifiers, etc. — and rename to just "Herald" (matching the
ar-news/lnkact-monitorstyle).The README should keep stating that Herald is currently built for/tested against ASL3, and can call that out explicitly if/when ASL4 support is added later — but that should be a documentation update, not a repo-wide rename.
Notes / open questions for planning
/etc/asterisk/scripts/asl3-herald,/var/www/html/asl3-herald, the systemd service name, etc. means install.sh needs a migration path (move config/state, disable old service, re-point Allmon3/Supermon integration links) so existing users don't lose their config or end up with duplicate installs.ASL3-Herald→Heraldor similar) has implications for existing clones, the install.sh one-liner URLs, and any external links (README badges, wiki, this very issue tracker).Alternatives considered
Leave the ASL3 naming as-is until ASL4 actually exists, and do a larger rename/migration at that point instead of preemptively. Rejected for now in favor of avoiding a bigger rename later once more is built on top of the ASL3-specific naming.