[chirp_users] Image frequency policy

[Dean Gibson AE7Q]

I've sent this privately to avoid "polluting" the public thread.  I 
haven't followed this very closely, but:

 1. As I understand it, this guy doesn't really understand "image"
    frequency reception.
 2.  From his last message, I think he will "continue the fight",
    perhaps on other forums.

So, I'd suggest a policy statement on your web site, something like:

/Chirp will not accept or support modifications that may cause a radio 
to actually operate (including receive) on a frequency or in a mode that 
is different than the frequency or mode displayed. Such modifications 
may cause users to operate on a frequency or in a mode that they do not 
intend.  Discussions on this matter are considered "off-topic" for the 
mailing list./

Sincerely, Dean

On 2013-04-02 08:39, Dan Smith wrote:
> Hi Andre,
>
> I hope this can be our last discussion on this topic.
>
>> The only problem I "see" is the fact that despite chirp allows us
>> to "unlock" baofeng, for example (I can set the range from 1 to
>> 1000mhz), it won't allow me to save those freqs in memory!
> At this point, the mainline version of CHIRP will not gain support for
> programming frequency ranges that the hardware is known not to support.
> I have seen no compelling evidence that any version of the hardware is
> capable of anything outside the range that CHIRP currently supports
> (aside from the 220MHz variant). Until I do, the current functionality
> will remain.
>
> You have brought this up multiple times in multiple places and we
> have repeatedly explained that we have no interest in features
> that may be at best useless and at worst damaging. Please, lets put
> this topic to rest.
>
> Thanks!
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20130402/08d20eee/attachment.html