247
edits
Online Developer Meeting (2024-11-26): Difference between revisions
Jump to navigation
Jump to search
→Today's topics: Add notes from meeting
m (Update items that are completed) |
(→Today's topics: Add notes from meeting) |
||
| Line 8: | Line 8: | ||
* "Code sprint" for new terminal widget? | * "Code sprint" for new terminal widget? | ||
** not discussed | |||
* buildbot: broken synchronization for stable branch? | * 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? access permissions for organization members? | * 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. | |||
* load path and PKG_ADD issues | * load path and PKG_ADD issues | ||
** Keep allowing arbitrary code execution in <code>PKG_ADD</code> scripts. Try to avoid the use-after-free when <code>addpath</code> is used in <code>PKG_ADD</code>scripts. | |||
* future of octave-cli (also: FLTK, and gnuplot graphics) | * 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 <code>octave-cli</code> 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* call <code>octave-cli</code> (but <code>octave</code>, potentially calling <code>octave --no-gui</code>) in the vast majority of cases. | |||
** After the "original" <code>octave-cli</code> has been renamed, potentially, add a new wrapper executable named <code>octave-cli</code> that essentially just forwards to <code>octave --no-gui</code> (to avoid potential issues with hard-coded executable names in build scripts or Makefiles). | |||
== Previous topics == | == Previous topics == | ||