Reviewing Octave Forge packages

More than one person can review a package, in fact that would be great.

The reviewing procedure in short:

1. Pick a package at https://sourceforge.net/p/octave/package-releases/
2. Copy the check-list below and fill it out, marking each box:
   • [x] for successfully passed
   • [ ] for not done / error (please give below the checklist a brief reason)
3. Paste your filled in check-list as a comment on the issue above
4. An Octave Forge Admin will try to look over your review and hopefully release the package.

Checklist

# Repository / Metadata

- [ ] release commit/changeset specified and present in repository
- [ ] `generate_package_html` / `make html` works without errors and warnings
- [ ] generated HTML documentation looks sane

# pkg-tool runs without errors or warnings

- [ ] `pkg install   foo`
- [ ] `pkg load      foo`
- [ ] `pkg unload    foo`
- [ ] `pkg uninstall foo`
- Above steps were run on Octave and OS versions:
  -  ________
  -  ________

# Package tests

- [ ] ran `pkg test foo`
- [ ] ran `doctest` 

# Package files in release candidate tarball

- [ ] `DESCRIPTION` version and release date updated
- [ ] `DESCRIPTION` minimum Octave tested
- [ ] `DESCRIPTION` all dependencies are listed
- [ ] `NEWS` version and date match
- [ ] `NEWS` big changes announced
- [ ] `INDEX` all (new) functions are listed
- [ ] version numbers in help text and function body (e.g., banners) updated
- [ ] license specifications in help text and function body agree `licensecheck -r`
- [ ] file permissions are readable/executable by all users
- [ ] junk files are removed (hidden dot files, backup files, results of configure runs, etc.)
- [ ] (optional if present) `src/configure.ac` version updated

Admin tasks

1. Upload release tarball to Individual Package Releases
2. Update https://octave.sourceforge.io/
   1. Upload new package HTML documentation to /home/project-web/octave/htdocs/packages/foo/
   2. Update index
      1. Add entry in htdocs/news.html