[Mep-dev] OHL and informal requirements review

[Art Botterell]

I've looked at the HPSDR project a couple of times, but was deterred  
by what struck me as overly complex interfaces and excessive  
functional dependencies among the various boards.  I'm sure that  
structure has a valid rationale from the point of view of the  
developers, but from a project-coordination point of view it looks a  
bit scary.

I'd suggest that simple interfaces, loosely coupled modules and rapid  
prototyping... more like the way modern software is built... might  
prove more manageable for a project like MEP, at least in its early  
phases.

There'll be time for refinements and optimizations later, provided the  
team can maintain its momentum long enough to get some early wins so  
as to attract sustaining energy from a larger community.  That's  
especially crucial, I think, in a diverse and distributed community- 
based project.

(And Michelle, for my part I think that first list of requirements is  
pretty much on the mark.  Enough to start designing some prototypes  
around, not so heavily-crafted that we'll be reluctant to revise them  
in future cycles.)

- Art KD6O