Online Developer Meeting (2023-05-23): Difference between revisions

From Octave
Jump to navigation Jump to search
Tags: Mobile edit Mobile web edit
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
* Date: Tuesday, May 23, 2023 @ 18:00 UTC  '''[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023&month=4&day=25&hour=18&min=0&sec=0&p1=263&p2=37&p3=248&p4=202&p5=26 Convert timezones here!]'''
* Date: Tuesday, May 23, 2023 @ 18:00 UTC  '''[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023&month=5&day=23&hour=18&min=0&sec=0&p1=263&p2=37&p3=248&p4=202&p5=26 Convert timezones here!]'''
* Location: https://meet.jit.si/octave-dev
* Location: https://meet.jit.si/octave-dev


== Today's topics ==
== Today's topics ==
* GSoC updates
* GSoC updates
** '''Andreas and Nick described initiation so far. Students start work next week.'''
* VM update and planning:
* VM update and planning:
** Add to default by Jun 30, giving 5-6 months of wider testing?
** Add to default by Jun 30, giving 5-6 months of wider testing?
** '''jwe will review in next 3-4 weeks. If he doesn't do it by the next meeting, the VM is to be pushed. Set default runtime compilation setting to false but configuration can be left enabled by default.'''
* [https://octave.discourse.group/t/4440 New warnings from GCC 13.1] (GUI threading issue?)
** '''Others will try to replicate as they get gcc 13 on their machines. No obvious bugs came to mind but some things may need to be reworked to avoid intermediates.'''
* Status of coding community events?
** '''No updates. Polls haven't been made yet.'''
* Discourse policy on AI bots.
** '''Agreed that bots are bad as of now, spread bogus answers, cause much extra work for moderators. One user was already suspended. The FAQ will be updated so that "post your own stuff" precludes AI copy-paste.'''


== Previous topics ==
== Previous topics ==

Latest revision as of 01:09, 24 May 2023

Today's topics[edit]

  • GSoC updates
    • Andreas and Nick described initiation so far. Students start work next week.
  • VM update and planning:
    • Add to default by Jun 30, giving 5-6 months of wider testing?
    • jwe will review in next 3-4 weeks. If he doesn't do it by the next meeting, the VM is to be pushed. Set default runtime compilation setting to false but configuration can be left enabled by default.
  • New warnings from GCC 13.1 (GUI threading issue?)
    • Others will try to replicate as they get gcc 13 on their machines. No obvious bugs came to mind but some things may need to be reworked to avoid intermediates.
  • Status of coding community events?
    • No updates. Polls haven't been made yet.
  • Discourse policy on AI bots.
    • Agreed that bots are bad as of now, spread bogus answers, cause much extra work for moderators. One user was already suspended. The FAQ will be updated so that "post your own stuff" precludes AI copy-paste.

Previous topics[edit]

  • Octave 8.2.0 released
    • Release process went pretty smoothly.
    • If no specific extraordinary motivation, we won't need release candidates for future bug-fix releases.
    • @jwe will try to provide existing helper scripts and instructions for release process.
  • Coding Community Events
    • OctConf 2023?
      • @jwe proposed to do that in the form of a developer summit for a couple of days.
      • @Rik offered to open a poll for dates/venue/... on the discourse forum.
      • Probably, at least 6 months lead time.
    • Online coding sprints?
      • Maybe in the form of a loose online meeting for the duration of a weekend?
      • @Rik offered to open a poll for dates/tools/... on the discourse forum.
  • GSoC discussion
    • Process for evaluation of student applications has started.
    • Some promising candidates.
  • Possible version 9 projects:
    • Qt6 (does that force us to require a C++17 compiler?)
      • Only enablement patches have landed so far. Further integration and bug fixes are still needed.
    • new terminal widget
    • arguments blocks
    • improved breakpoint handling
    • experimental stack-based virtual machine
    • MException object
    • string object (separate from having double-quoted characters create string objects)
    • HDF5-based save and load compatible with Matlab's file format
    • refactor octave_function and classes derived from it
    • broadcasting for sparse
    • make graphics and GUI event processing in the interpreter independent from readline
  • Status of Octave Forge
    • should the Octave bug tracker continue to be used for reporting bugs in external packages?
      • Propose package maintainers to move to own trackers.
    • if not, how can we make it easy to find the location to report bugs for a package/package function? How do other systems like Python, R, etc., handle this problem?
  • Some old bug reports have been closed recently - thanks!
    Current stats by year:
2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 total
Octave 1 16 16 41 79 101 160 129 180 201 132 126 117 54 1353
Octave Forge 3 9 19 27 38 28 39 54 44 49 16 326

See also[edit]

Retrieved from "https://wiki.octave.org/wiki/index.php?title=Online_Developer_Meeting_(2023-05-23)&oldid=14808"