Re: [Gnucap-devel] about updating ideas page

[al davis]

On Friday 06 February 2015, al davis wrote:
> If you are thinking "summer of code" and where to get
> started,  you should first get familiar with what is here
> and how we work. You should try to make some contributions
> and show at least a basic familiarity with how we work, what
> is here, what it is used for, and why.
> 
> Something you (or anyone) can do to get in is to work on the 
> help system by writing the help text for as much as you can.

Another way to jump in, to learn about the gnucap project, is to 
make test cases.  The "tests" directory has a lot of test files, 
but it is not 100%.  You can study the code and look for where 
it says untested() or itested(), figure out how getting there 
might happen, and create test inputs to exercise that code.

If there is no way to get there, that code should be considered 
for removal, unless it is needed for some other known reason, in 
which case it should be marked unreachable().

These suggestions, help text and testing, are not suggestions 
for summer-of-code projects.  It's something we need that can be 
done in small pieces to get familiar with the project, and get 
you to the point where you can make real original contributions.