When1: December 12th, 14:00 UTC.
When2: Darmstadt (15:00), London (14:00), Philadelphia
(09:00), San Francisco (06:00)
Where: Octave IRC channel, #octave. See
http://wiki.octave.org/IRC
A code sprint is an opportunity for programmers to get together
for both coding and socializing.
We will have some goals, the sprint topics shown below, to guide
our sprint, but anyone is welcome to hang out and work on their
own special topic.
There will be multiple Octave Maintainers attending so this is
also a good chance to get introduced to the Octave code base and
how to make patches for it.
In order to contribute you should have installed Mercurial,
fetched the development sources, and have successfully built your
own local copy of Octave.
See http://www.gnu.org/software/octave/get-involved.html. For
further information, see the wiki page
http://wiki.octave.org/2015_Code_Sprint, and add your name to the
list of attendees there if you can join.
Sprint Topics
- Refactor C++ code that uses print_usage() and error() to
resemble m-files (http://wiki.octave.org/Refactor_C%2B%2B_code_that_uses_print_usage()_and_error()_to_resemble_m-files)
- Add BIST tests for octave functions written in C++
(http://wiki.octave.org/wiki/index.php?title=Add_BIST_tests_for_octave_functions_written_in_C%2B%2B)
- Remove class of function from documentation strings
- Move some ODE package functions from Octave-Forge to core