1,072
edits
Online Developer Meeting (2022-06-28): Difference between revisions
Jump to navigation
Jump to search
m
Add GSOC Openlibm topic
ArunGiridhar (talk | contribs) (Launch page) |
m (Add GSOC Openlibm topic) |
||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 3: | Line 3: | ||
== Today's topics == | == Today's topics == | ||
* Octave 7.2 | |||
* VM updates | |||
* Fosshost and hosting updates? | * Octave 7.2 | ||
** jwe indicated a release is imminent | |||
* VM updates | |||
** Presentations by mnabipoor and Petter | |||
** Both efforts will move forward | |||
** Need to define VM language | |||
* Fosshost and hosting updates | |||
** Kai presented details of migration and documentation of the migration process | |||
* [https://github.com/gnu-octave/MinusForge MinusForge] to finally move to Octave Packages with <code>pkg install -forge</code> | |||
** Timeline to deprecate https://octave.sourceforge.org. | |||
** Kai presented this new mechanism to obtain "pkg install -forge" functionality for GitHub packages in addition to SourceForge, en route to leaving SourceForge | |||
* GSOC status/progress check-in | |||
** Openlibm support from Julia team may be faltering. Is it worth continuing to try and integrate this cross-platform library? | |||
*** See discussion at [https://octave.discourse.group/t/point-of-openlibm-project-or-if-even-julia-wants-to-shift-away-from-openlibm-do-we-want-to-use-it/2980] | |||
** What about other workarounds in Octave for cross-platform issues (e.g., gnulib, Autoconf tests + workarounds in Octave code)? How much should Octave do versus relying on programmer to have a reasonable environment? | |||
* Follow up on implementing classdef classes in C++ | |||
** jwe presented updates on the classdef functionality. | |||
== Previous topics == | == Previous topics == | ||
| Line 13: | Line 29: | ||
* Drop "native" MXE Octave builders from buildbot configuration? | * Drop "native" MXE Octave builders from buildbot configuration? | ||
** [https://octave.discourse.group/t/drop-native-builds-from-mxe-octave/2689 Discourse thread] | ** [https://octave.discourse.group/t/drop-native-builds-from-mxe-octave/2689 Discourse thread] | ||
*** Drop the builder from the buildbot configuration. | |||
*** Don't '''actively''' remove support for native builds from MXE Octave. But don't spend too much time maintaining it. Maybe at some later time, someone will step up to maintain it again. | |||
* Timeframe for Octave 7.2 release? | * Timeframe for Octave 7.2 release? | ||
** Important fixes (among others possible loss of .m file content on exit) | ** Important fixes (among others possible loss of .m file content on exit) | ||
| Line 20: | Line 38: | ||
** Buildbot worker on ARM hardware? | ** Buildbot worker on ARM hardware? | ||
*** No, see below | *** No, see below | ||
*** Maybe, at a later point ask again for access to their AARCH64 server farm. | |||
** Possible to run a Mercurial server? With mirror(?), forks for GSoC students(?), ... | ** Possible to run a Mercurial server? With mirror(?), forks for GSoC students(?), ... | ||
*** Possible, needs setup 😇 | *** Possible, needs setup 😇 | ||
*** For the time being, GSoC students should use a public service for their fork. | |||
** Short summary: Octave got one x86_64 server instance '''(2 cores, 4 GB memory, 500 GB HDD)''', useful as webserver probably?! | ** Short summary: Octave got one x86_64 server instance '''(2 cores, 4 GB memory, 500 GB HDD)''', useful as webserver probably?! | ||
<syntaxhighlight lang="bash> | <syntaxhighlight lang="bash> | ||
| Line 75: | Line 95: | ||
** https://octave.discourse.group/t/implementing-unimplemented-m/2706/5 | ** https://octave.discourse.group/t/implementing-unimplemented-m/2706/5 | ||
** Need clarity about the purpose: Helping search vs. Motivate to join Octave community. | ** Need clarity about the purpose: Helping search vs. Motivate to join Octave community. | ||
* How to implement a classdef class in C++ code only? | |||
** Why is the classdef implementation so complicated? Does it need to be? | |||
** @carandraug and @Maged will look into this for their GSoC project. Pointers welcome. | |||
** Maybe, some kind of documentation could be a result of the GSoC project. | |||
== See also == | == See also == | ||