Mike,

Obviously, you have a lot of relevant experience. Before even trying to understand your suggestions I am going to have to google things like "CARLA region sets" and "GitHub templates".

Even though it's my idea. I'm not sure implementing it is worth the trouble. Especially, since someone said the "Duplex off" does not work on most radios. If it's true it's a show stopper.

But, it sounds like you are saying if you use the right templating tools it may not be that much trouble.

I don't want to think about the phrase "infinite number of use cases". I have enough trouble with just one.

I suggested MediaWiki as a possibility because I know it can handle crowdsourcing tables that describe license, region, organization, frequency, modes, etc.

I've never looked at the parts of GitHub you are discussing. Googling "github templates" returns a whole lot of stuff that does not appear to be what you are talking about.

On Sun, Mar 12, 2017 at 10:38 PM M Noivad <noivad@mac.com> wrote:

From: Drew Einhorn <drew.einhorn@gmail.com>
The point is to make it easier for licensed folks to avoid mistakes that
violate the law, not to make it impossible for folks who intend to violate
the law.

It's easy to accidentally press the TX button. I would prefer to easily
configure the radio to limit the damages. Duplex off is nice. But, I'd
prefer to set my country to US and license to Amateur Technician and
automatically have Duplex set correctly for all frequencies outside the
amateur bands.

From: John Wilkerson <jl_wilkerson@att.net>
The suggestions should be posted at the Chirp website, if you'd ever
want them considered.

If sounds like you’re requesting more of an additive template system with importable sets of preference templates based on license/region/organization that only overwrite specified fields, or open a new document with those fields set. This would allow you to save different presets in groups for different use cases/clients as well as combine sets (with the latest template added taking precedence). For instance that would allow a person to start with a “Technician,” “Extra,” template overlay a “CARLA region set” of channels, and then import their groups sets. Numerical collisions could either automatically add to the end or give the user a remap to # option per channel or per group. That system could be group sourced, and maintain the flexibility for an infinite number of use cases.

From: David <weather@lightingunlimited.com>
What is MediaWiki?

From: Drew Einhorn <drew.einhorn@gmail.com>
MediaWiki is the very powerful wiki software that runs the Wikipedia and
many other well-known wikis. It is not the easiest to work with, but it can
do just about anything wiki related, and do it well. Casual users are
frequently overwhelmed by its complexity. So, it is often not the best
choice.

I’ve been running a MediaWiki installation for over 10 years now. While MediaWiki is great for crowdsource, for file exchange, security & safety can be problematic. Instead I would probably crowdsource templates, suggested above, on github.

For crowdsourced information, MediaWiki is great. Setup complexity is dependent on your server environment. For some it’s as simple as downloading a package and running the setup wizard, while for others it’s compiling from source, etc. If you need advice, I’d be happy to help.

Thanks for Chirp.

Mike
KF6FGE
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Drew Einhorn at drew.einhorn@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com