[chirp_users] Template & MediaWiki

[Tom Hayward]

On Tue, Mar 14, 2017 at 1:55 PM, M Noivad <noivad at 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.py

Tom KD7LXL