[chirp_devel] What is the policy about radio clones being NOT listed by it's own brand/model?

[Pavel Milanes (CO7WT)]

Ho to all,

What is the policy about radio clones being NOT listed by it's own 
brand/model?

Scenario:

A new user must come to Chirp because some friend told him about it, and 
that Chirp support his Baofeng "X" radio, he come into Chirp's web page 
and his mind only search for the "download" link: "got it"

Downloading... installing... opening.

WTF! My radio is not listed.

Call/email to the friend, search the internet /{time wasted and user 
confused}/  just to know that his radio is not *directly* listed in the 
software: it must use the model Z from Baofeng.

Sure, users "has" to read the front page for the Chirp's site to realize 
that, but...

It's only me thinking this is wrong?

The actual situation with the Baofeng is a weekly issue on the 
site/email list. And now I have a issue with the "mobile Baofengs" aka 
BTECHS and family.

Actually the  JetStream JT2705M is supported but not listed directly on 
chirp, in the page it's showed as a clone of the QYT KT-UV980, but a 
user may be confused by this.

The Juentai JT-6188 Mini is also in the same case (listed as a clone of 
the QYT KT8900), but it's getting more complicated; now I may have found 
a new variant for it (and entire new radio with it's own ids) and 
Juentai also released the JT-6188 Plus, and dealers in internet keep 
saying just JT-6188 confusing users...

I have changed the supported models wiki page to show Juentai JT-6188 
*Mini *to avoid confusion.

Now the question:

It's correct/safe to just create adn register a class for this clones by 
instantiating the correct class but overriding the vendor/model?

I think this will help the users a lot, and it's a simple hack, also 
applicable to the baofengs...

73 Pavel CO7WT




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20160414/ede43c8d/attachment-0001.html