Skip to content

Fleet? #7

@Littleaton

Description

@Littleaton

Not sure if fleet is a good name for groups of repeaters.. but your call :)

“Fleet” feels a bit… naval/vehicle-oriented, which doesn’t quite match a fixed mesh repeater network. You’re not moving assets around—you’re building coverage and infrastructure.

A better name depends on the vibe you want (technical, radio-centric, community, etc.). Here are some stronger options with why they work:

More accurate / infrastructure-focused
Cluster – Common in networking; implies grouped nodes working together
Grid – Feels like coverage and structure (nice for mapping too)
Mesh – Simple and on-brand (e.g., “Wasatch Mesh”)
Array – Slightly technical, works well for RF systems
Network – Straightforward, no confusion
Radio / RF culture vibes
Net – Ham-radio style (“Utah North Net”)
System – Classic repeater naming (“Wasatch System”)
Linked System – If they’re interconnected
Backbone – Implies core infrastructure nodes
More unique / branded feel
Zone – Good if you divide regions
Sector – Works well if directional or geographic
Region – Clean and scalable (you were already leaning this way)
Fabric – A bit more modern/techy (like “network fabric”)
Layer – If you’re thinking in architecture terms

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions