Online Developer Meeting (2022-02-22)

From Octave
(Redirected from Meet)
Jump to navigation Jump to search

Todays topics[edit]

  • Meet and greet 5 minutes before meeting (audio testing).

Previous topics[edit]

The following items were not discussed. Just some links to progress on those items are displayed.

Release process of Octave 7.1[edit]

  • Blocking issues: 9 bugs targeting 7.0.90 (see Savannah overview on
  • Most important ones (in no particular order):
    • bug #61788: arrays of type int16 contain wrong numbers]
      • Will probably be reverted before Octave 7.
    • bug #61813: memory management bug when calling MEX that returns an output]
      • Issue if Octave is compiled with C++17, while the mex file not. @jwe checks on this.
      • maybe also: malloc-delete[] combination in the .mex interface
    • bug #61821: segfault using tree_parameter_list in oct file]
      • Lower priority, only conditionally reproducible.
    • bug #61898: subsref: Error when field syntax is used on non-scalar @class object]
      • Needs reproducible example without interval package. Similar bug #61843 reported.
  • A few package releases with fixes for Octave 7 were pushed to mxe default, e.g. (ga, control, communications)
    • Should those changes be applied to the "release" branch? -YES.
  • Revisit load path caching:
    • Improving the caching strategy is the way to go.

C++17 features in Octave API?[edit]

  • Timeframe?
    • When qt6 is distributed? - Probably bad strategy (Debian/Ubuntu and even Arch have trouble with qt6).
    • Regarding stable=stale Linux distributions.
  • Should we announce that possible requirement for some time in the future with the release of Octave 7?
  • See also: Should Octave switch to C++17? If so, when? on Discourse.

GSOC 2022 opening soon[edit]

  • GSOC 2022 Timeline (Feb 7-21 is Org application window, acceptances announced Mar 7.)
  • 2022 changes - after shifting to shorter projects in 2021, GSOC now allows flexible project/time commitments from 10-22 wks (12 standard, org/mentor flexibility on milestone dates).
  • GSOC FAQ (took note that the organization does get a small stipend for participating... helping a bit to offset yearly infrastructure costs)
  • Past projects at other orgs ranged quite widely in scope, especially with change to smaller projects in 2021:
    • some were often a part of big tasks. Are there bigger octave goals that could be parted out for a GSOC task? parts of classdef, or graphics handles, or a new command window, or dare we suggest JIT?
    • Some amounted to "tackle all the bugs related to X". Are there bug categories or unimplemented function categories (that might require particular coding or mathematical knowledge) worth directing particular focus on? 'the unimplemented interpolant classes/functions' or 'unimplemented image package functions related to feature recognition' or ...
    • "complete this unfinished thing" tasks (prior gsoc? pkg related? the 'did you mean' feature?)
  • Thinking ahead, 'Google Season of Docs' has typically announced/opened their program in Feb-March. Are there small/large doc projects worth getting into GSOD so a paid freelance technical writer/coder can take it on for 6-9 months? Successful examples ranging from document creation to doc infrastructure - 2021 2020 2019
  • Please find small / partial contributions (also m-files) that help you with your current projects on Octave.
    • HDF5 project?
    • Time to specify the task lacks...

See also[edit]