- This is a collection of small projects to start contributing to Octave. Projects of long duration are listed in the Projects page.
Review and fix existing bugsEdit
- Review bugs that catch your interest on the Octave bug tracker on GNU Savannah.
- A modern interface to the Octave bug tracker is given by SavannahAPI.
- Discuss with the developers there how to fix that bug or upload a patch there.
- Some bugs have already patches attached.
- Help testing those patches.
- Help updating outdated patches to the latest development version (this requires some Mercurial knowledge).
Implement missing Matlab functionsEdit
- Use the Savannah patch tracker for submissions unrelated to an existing bug.
Test Octave functions for proper input handlingEdit
- Many functions either do insufficient input checking or the input requirements have changed over time.
- Contributors can try to break Octave function behavior with different types of input, and document the results.
- Users can check expected behavior according to the Octave help and, if applicable, expected compatible behavior according to public facing Matlab documentation.
- Inputs to test can be:
- different numeric types - double, single, integer.
- non-numeric types - logical, string, cell, struct
- different input shapes - scalar, row/column vectors, 2D, 3D, & nD arrays, zero size arrays (, 1x0, and 1x3x0 are all empty but may require different handling).
- char/string parameters: different case handling, partial matching behavior, invalid/nonsense parameters.
- For the input items above, does function behave acceptably? Are numerical or graphical outputs as expected? Is output consistent? Is any error message intelligible/meaningful to the user?
- Optionally the behavior above can be tested against Matlab function output if it is available. If needed but not available, tests can be submitted to other developers for output checking.
- Note 1: There is much undocumented Matlab behavior. Because this has the possibility of changing with little notice, fixing incompatibilities related to such undocumented behavior is considered on a case-by-case basis by the developer team. Documentation of such cases is always beneficial, however.
- Note 2: Only Matlab public documentation and function output may be compared. Internal Matlab code, even if available, should never even be looked at by a contributor. Contributions will be discarded if it is determined such action occurred.
- Contributors can submit bug reports to the Octave Bug Tracker documenting their findings.
- An example can be see in bug #64078 comment #10 of looking through the /plot/draw functions for how they handle integer and logical inputs to numeric fields.
Write Built-In Self Tests (BISTs)Edit
Writing BISTs improves Octave's regression testing and ensures that we don't break anything when we add new features.
Work on Octave packagesEdit
- Take a look at https://gnu-octave.github.io/packages/ if you would like to work on some package there.
Below is a non exhaustive list of bugs which should be looked at and appear to be easy. Completed scrub using 6.1 as non expert. Status column provides notes from last review to facilitate addressing each bug. (Reviewing and updating status of items in this list as well as adding new ones are themselves good beginner tasks.)
- The last full scrub came from hardy for v4.2
- Suspect many java bugs could be closed.
- Appears plotting bugs have been fixed, but not have been reviewed for 5 years.
- Did not include most documentation bugs.
- Experts: rik5, nrjank, etc. will be able to find significantly more to close.
|#36954||datenum / datevec convert date-time string incorrectly during hour lost to DST||siko1056 suggests closing as won't fix. nrjank reverted from Postponed to Confirmed / removed Assigned To tag after dormant for 2 years.|
|#40357||OOM when converting from sparse double to sparse logical||hardy thinks this might be a DUPLICATE, nrjank changed to Need Info, needs better test to determine if the OOM comes from known sparse indexing issue or something else.|
|#48088||document that issquare, iscolumn, isempty, etc operate on cell arrays||documentation patch candidate submitted and needs review.|
|#49886||ezplot: octave does not warn when function not vectorized||Rik states This would be easy to fix if #42691 was first solved. That bug was closed as fixed in August 2021, so supposedly this one should now be easier manageable. nrjank marked as Needs Info to determine if desired output is just adding a warning, or also matching matlab output.|
|#49360||odeset lacks documentation for solver options||Needs someone to review and make a to-do list.|
|#53214||area.m needs update to implement ShowBaseline and other properties||nrjank states last remaining task is adjusting the axis limits to fit the data. This has been pushed for area.m. Left remaining is whether to do the same for plot.m which would require checking on/fixing failing tests in other functions.|
|#54437||optimset missing documentation for 5 options||Documentation task. rik states AutoScaling, ComplexEqn, and Updating can be copied from fsolve.m so this would be an improvement.|
|#55065||Implement uiopen and uisave||both a patch and m-file versions of the two functions have been separately submitted. they both need to be evaluated for fitness.|
|#56208||GUI Editor autocomplete list could show variables from current workspace||suggested it might be fixed, but appears to still not be meeting summary requst. marked as Needs Info|
|#57352||text height for blank line should approximate that of ordinary character||initial patch suggestion provided but still needs some trial and error to get good height behavior|
|#58530||missing functions: xline() and yline()||initial patch submitted in 2022, needs rework according to rik's comments|
The equivalent suggestions for patches.
A list of patch reports with attachments not marked "Done or Cancelled" can be viewed in the SavannaAPI, sorted by oldest first or sorted by "longest since last comment" first. While some of these older submissions may still be viable and just need a patch refresh to the current code base, many will have become out of date or rendered inapplicable due to code or function changes, and could be closed as 'Wont Fix'.