pvarki / pvarki/python-tak-rmapi

[Feature Request] Addition to automatic Callsign to specify different devices

Open
#76 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
0
Forks
0
Avg merge
1d 19h
Merged PRs (30d)
12

Description

All Rasenmaeher packages provide users callsign-info for TAK-products. In TAK if multiple logged in users have the same callsign the usability of the users is compromised. Usually users are told to make one Rasenmaeher user per used tool, but we could fix this with additional tag at the end of Rasenmaeher packages provided callsign.

Example. User downloads Client Package for TAK Tracker
Package is otherwise same, but callsign information contains "-tracker" to notify other users that this user is TAK Tracker and isn't available to chat and receive packages.

"{{ client_cert_name }}-tracker"

Problems with adding information to callsign are lengthening the callsing-tracker and makes it harder to read if the users callsign is already long. Also iTAK and WinTAK are currently not supporting defining Callsign in connection package.

This would be best suited for TAK Tracker as that is the general way of having multible same callsign at the same time. TAK Trackers use case is to have ATAK shut on device when not needed to conserve battery and only use TAK Tracker, when the need for ATAK rises user can open it and use it immediately. TAK Tracker most likely will be in the background if the users doesn't close it manually.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the package-generation code for Rasenmaeher client packages and the callsign entry shown in the issue. Compare how TAK Tracker packages are produced with the stated iTAK and WinTAK limitations, then define how a device-specific callsign should be represented without making callsigns unreadably long. Done means the selected package can distinguish TAK Tracker users with clear behavior and coverage for the supported package variants.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.