Re: [chirp_users] Template & MediaWiki
CARLA is a California Amateur Radio Linking Association. They have a series of 20-smthing linked repeaters throughout the SF Bay Area. If you transmit at a local frequency only the repeater you hit relays the message, if you use another frequency, it repeats your message throughout the CARLA relay system. Sorry, I should have specified this as an example of a set of different frequencies that would only be useful to Bay Area HAMs.
Github itself is shared repository that is much more suited for file exchange. Github doesn’t have any templates, but it will host any type of file. So, if your app could import and export sets (not complete files that only work on 1 radio as now) as files in whatever internal format you wish, having sets available as a file others could download from Github would allow for add security. But this wouldn’t be all on you.* As far as github, it can be used to share applications, documentation, bugs, etc. Github is free to use for open exchange and there is a paid tier for pro use. (Free should work fine though)
*Users could make a file of their channel sets & defaults ( I’m calling it a templates—though technically they’re more like an overlay since you can add them together ) and then post them to Github where other Hams can look at sets, such as the examples previously mentioned.
As far as the “infinite number” of possible combinations, that meant the community could take some of the burden off you simple by making sets for groups or regions, etc. and share them. That way if someone wants a repeater channel set with a + or - offset, they can define that for the whole set & tweak individual exceptions.
M
On Tue, Mar 14, 2017 at 1:55 PM, M Noivad noivad@mac.com wrote:
Github itself is shared repository that is much more suited for file exchange. Github doesn’t have any templates, but it will host any type of file. So, if your app could import and export sets (not complete files that only work on 1 radio as now) as files in whatever internal format you wish, having sets available as a file others could download from Github would allow for add security. But this wouldn’t be all on you.* As far as github, it can be used to share applications, documentation, bugs, etc. Github is free to use for open exchange and there is a paid tier for pro use. (Free should work fine though)
Chirp has an established system for source code management (or file exchange, as you call it). It is called Mercurial, and for the discussed use case it works identically to Git.
http://chirp.danplanet.com/projects/chirp/wiki/DevelopersProcess
Chirp has an established templating and overlay system for band plans. This is nearly the same as what's being discussed, except it doesn't have a "transmit allowed" flag. If one were going to add this feature, that's where I would start.
http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/bandplan.py http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/bandplan_na...
Tom KD7LXL
participants (2)
-
M Noivad
-
Tom Hayward