[hpsdr] Proposal for a new Software project.

[Bob Cowdery]

I think you have hit the proverbial nail on the head Alberto. Flex for
example have to have a software product and if they don't have a clear
idea of where they are headed and a clear architecture they will
flounder. There has to be an 'architect' who gives that direction and is
strong enough to maintain a position on all the important aspects. I've
never found architecture design by committee works too well as there
will never be a consensus.

As for hobbyists there are parts that they will take with open arms like
DttSp as a component of an SDR that is pretty hard for most of us to
write. But to swallow a whole architecture is asking a lot as I think
many want to be free to try new things, new tools, new languages and to
experiment with different ways to do things.

IMHO some SDR component ware, which would do the difficult things like
DSP and provide efficient, simple, and robust interfaces to audio
streams and SDR hardware would be a real help to many if at the right
level of granularity. Components should be cross platform and be
language, and infrastructure agnostic (or at least hide any
infrastructure they use). The wiring up and presentation can be left to
individual taste.

Just my opinion of course and not meant to deter anyone from doing what
they think is right.

73's
Bob
G3UKB


Alberto I2PHD wrote:
> ***** High Performance Software Defined Radio Discussion List *****
> 
> 
> 
> ------------------------------------------------------------------------
> 
> May I give a very personal comment on what I have recently read about a
> proposed new SDR architecture,
> be it modeled along the FSM document or similar lines ?
> 
> Who is the average hobbyist developer of an SDR program ? More often
> than not, he is what could be
> called a 'lone wolf'... he develops things according to his personal
> vision of how things should be developed...
> it is not easy to force him into a pre-built structure and architecture...
> 
> This can be done instead easily in the commercial world, where
> developers are paid, and work not for their own
> intimate pleasure, but to earn their salary...  the perspective is
> different.... if the specs of the project say :
> "You must implement a message-passing architecture, where the client and
> server talk to each other using
> the Occam protocol (...)", then he will do it, because he is paid to do it.
> 
> But it takes much more to have him implement such a thing if the
> motivation behind his work is that of self
> accomplishment, and personal rewarding when he admires the product of
> his efforts....
> 
> He will do that only if he himself is convinced that that is that right
> way to do it, not because someone else
> decided it, but because that decision happens to be coincident with his
> personal decision....
> 
> Hobbyist, open source project cannot and should not, IMHO, managed as it
> would be right to do for a
> commercial project... otherwise they are doomed to failure....
> 
> But, as said, these are just my personal feelings, which, probably, are
> all wrong.
> But I just wanted to expose them....
> 
> 73  Alberto  I2PHD
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/


 1259689906.0