Online Developer Meeting (2024-12-17): Difference between revisions
Jump to navigation
Jump to search
(Create page) |
m (Fix links to previous and next meeting) |
||
Line 32: | Line 32: | ||
== See also == | == See also == | ||
* Next meeting: [[ | * Next meeting: [[Online_Developer_Meeting_(2025-01-28)]] | ||
* Prev meeting: [[ | * Prev meeting: [[Online Developer Meeting (2024-11-26)]] | ||
[[Category:2024]] | [[Category:2024]] | ||
[[Category:Meetings]] | [[Category:Meetings]] |
Latest revision as of 13:27, 29 November 2024
- Date: Tuesday, December 17, 2024 @ 18:00 UTC Convert timezones here!
- Location: https://meet.jit.si/octave-dev
Today's topics[edit]
Previous topics[edit]
- Release of Octave 9.3.0?
- Rik volunteered to shadow jwe while he makes release to learn the process. Markus and NickJ may also shadow event if the timing works out.
- "Code sprint" for new terminal widget?
- not discussed
- buildbot: broken synchronization for stable branch?
- Might have fixed itself by restarting the Digital Ocean server. (The server load was above 100 before the restart. Mainly Python and Apache processes again. Still suspecting the Mercurial web interface.) Will monitor the situation.
- GitHub mirror:
- broken synchronization for stable branch?
- Fixed by Kai on Nov. 25th.
- access permissions for organization members?
- Base access permission for organization members has been changed from "write" to "read". Higher access permissions should be added on a per-repository level if required.
- broken synchronization for stable branch?
- load path and PKG_ADD issues
- Keep allowing arbitrary code execution in
PKG_ADD
scripts. Try to avoid the use-after-free whenaddpath
is used inPKG_ADD
scripts.
- Keep allowing arbitrary code execution in
- future of octave-cli (also: FLTK, and gnuplot graphics)
- Look into moving FLTK and gnuplot graphics toolkits into Octave packages (if that is easy)
- Eventually remove them from core Octave (regardless of whether they can be moved to packages).
- Rename
octave-cli
to something that indicates that the main difference is that it doesn't link to the Qt libraries. Users of Octave with the CLI should *not* calloctave-cli
(butoctave
, potentially callingoctave --no-gui
) in the vast majority of cases. - After the "original"
octave-cli
has been renamed, potentially, add a new wrapper executable namedoctave-cli
that essentially just forwards tooctave --no-gui
(to avoid potential issues with hard-coded executable names in build scripts or Makefiles).
See also[edit]
- Next meeting: Online_Developer_Meeting_(2025-01-28)
- Prev meeting: Online Developer Meeting (2024-11-26)