Hey all! I'm working on putting together an extra option in APRS settings to allow for better APRS VOX through one of the classic Baofeng cables.
Anyway, while I can mostly work out the actual code part, I figured I should first ask about how to merge things upstream? Is there any kind of procedure, or more of just the code-over-the-wall technique?
Anyway, fantastic software! Thanks for putting in the legwork and keeping it all together.
(also, please do consider a git repo; i understand you've had problems with support requests for main branch builds, but i feel there are ways around that and the benefits outweight the problems.)
-Parker KJ5DFL
Upstreaming procedure
Re: Upstreaming procedure
It would be useful if you can describe what functionality you intend to add, because we use a common codebase for all radios, but this causes limitations for all hardware platforms becuase of limited storage space and limited code space on the older radios.KJ5DFL wrote: ↑Sun Jun 16, 2024 10:20 pmHey all! I'm working on putting together an extra option in APRS settings to allow for better APRS VOX through one of the classic Baofeng cables.
Anyway, while I can mostly work out the actual code part, I figured I should first ask about how to merge things upstream? Is there any kind of procedure, or more of just the code-over-the-wall technique?
Anyway, fantastic software! Thanks for putting in the legwork and keeping it all together.
(also, please do consider a git repo; i understand you've had problems with support requests for main branch builds, but i feel there are ways around that and the benefits outweight the problems.)
-Parker KJ5DFL
Adding additional settings would require additional on screen texts and additional voice prompts etc, so its not just a question of adding code for additional settings.
AFIK, we now have very limited code space available on the MK22 based radios e.g. GD77, RD5R, DM1801V1 etc and therefore do not normally accept code submissions which only would only be useful to a very small number of people.
Branching the code base so that its separate for the STM32 radios, would make lots of additional support work and the devs are already very short of free time, so I don't know if thats likely to every happen.
If there are minimal changes the functionality would have a large user base, then possibly it could be included, but we have other higher priority functionality being researched by several people, which would probably take all remaning ROM space