Hello everyone,
Here's a general call for help on the GNU Radio project if you are so
inclined. If you've wanted to contribute back to the code, but weren't sure
how to make a difference, there are lots of little things to look at. We've
set up a Jenkins continuous integration server that keeps track of the code
issues, including enumerating all "TODO" and "FIXME" comments through the
source code. It also tests and graphs the test code we've put in there. You
can see these results here:
http://www.gnuradio.org/jenkins/job/GNURadio-master/
What we want to see is the red and yellow graph lines going down and the
blue lines going up. The blue graph is the number of QA tests run. Any more
QA tests for a) blocks that do not currently have any QA code or b) more
corner cases for blocks already being tested would be most welcome.
The red and yellow lines mostly represent compiler warnings and TODO/FIXMEs.
Many of these might be very quickly resolvable with a few lines changed.
Some of them are probably more complex to know what the right answer is, so
if you have some ideas, start a thread on the mailing list to discuss what
the right fix might be.
Keep in mind on the warnings that libusrp and libusrp2 seem to be the cause
of most of them. I wouldn't worry about fixing these because those have been
deprecated and will be removed from the code when we release the next
version.
So while many of these bugs/issues/warnings/todo's have been around for a
while and haven't seemed to hurt anything, any time we remove one of these,
we've made the code better, more robust and reliable, and less likely to
cause headaches in the future. Every little bit helps.
Thanks!
Tom
_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio