docs: add proposed JS8Call @GROUP standard (issue #29) - #38
Open
nisfeb wants to merge 1 commit into
Open
Conversation
Draft JS8Call @group standard in response to issue s2underground#29. Automated traffic from companion software (TC2-BBS, JS8Spotter) currently shares the @ghostnet group, which spams manual operator inboxes. Define a small set of topic groups (subscribe by interest) and software groups (keep automation out of manual inboxes), with naming rules that fit the JS8Call callsign field. Ship a readable spec (js8call-groups.md) and a machine-importable registry (js8call-groups.csv) so software like TC2-BBS can import the list. Marked as a proposal pending S2 Underground ratification.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #29 (proposal for ratification).
What
Adds a draft JS8Call
@GROUPstandard so automated traffic stops sharing@GHOSTNETand spamming manual operators' inboxes.js8call-groups.mdis the human-readable spec: why, naming rules that fit the JS8Call callsign field, a set of topic groups (subscribe by interest), a set of software groups (keep automation out of manual inboxes), and usage and subscription guidance.js8call-groups.csvis the same registry in importable form (Group,Category,Purpose,Automated), which the issue calls for so TC2-BBS can import the group list directly.Design
@GHOSTNETstays as-is for manual calling, SNR, and heartbeat traffic.@EMERG,@WEATHR,@INFRA,@SUPPLY,@HEALTH,@CIVDEF,@SECRPT,@NUCDET,@NEWS.@SPOTTR(JS8Spotter),@TC2BBS(TC2-BBS).A-Zand0-9, max 6 characters, one purpose per group, no collision with JS8Call built-ins. This matches the example tags in issue Standardize JS8Call @GROUPS #29.Status
Marked in the document as a proposal pending S2 Underground ratification. The tag names and categories are a starting point for discussion, deliberately kept to a small set so operators actually monitor them. Happy to adjust the taxonomy to match your intent.