Online Developer Meeting (2022-04-26): Difference between revisions

From Octave
Jump to navigation Jump to search
(Create page.)
 
Line 35: Line 35:
=== GSoC 2022 ===
=== GSoC 2022 ===


* [Maintainers of symbolic package unresponsive](https://octave.discourse.group/t/gsoc-2022-symbolic-package-project/2396/3).  If no communication gets established by the weekend, this project will be dropped to avoid applicants putting energy in this.
* [https://octave.discourse.group/t/gsoc-2022-symbolic-package-project/2396/3 Maintainers of symbolic package unresponsive].  If no communication gets established by the weekend, this project will be dropped to avoid applicants putting energy in this.


=== Package problems ===
=== Package problems ===

Revision as of 05:25, 23 March 2022

Todays topics

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


Previous topics

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

Octave 7 RC 2

  • No major bugs remain, next will be final release.
  • Bug #62207 "segfault in bug-35881/bug-35881.tst in 32-bit ARM and MIPS" appeared. But maybe not a blocker, as only 32-bit ARM and MIPS seems affected. No Octave maintainer can reproduce due to missing hardware.

NumFOCUS

Bus factor problem, revisited

  • Any infrastructure changes to make in 2022? Web hosting?
    • We are looking for options to become less independent on private sponsored web servers, but not need to rush.
  • FossHost accepting applications again [1]
    • Arun will reach out for them.

Octave 8

  • Would it be worthwhile to look into Sergio Burgos' gui editor?
    • The authors of the software did not get in contact with the Octave developers.
    • The creator of this item did not attend the meeting, thus unclear what should be achieved.

GSoC 2022

Package problems

  • Package problems have to be settled with the package maintainers. Forks are possible anytime: GPL.

Communications

  • bug #46521 is still lingering with nir_krakauer and lostbard there has been significant progress.
    • Should some energy be directed to closing this? Not related to Octave itself. See note in bug report.

Signal

  • There has been tremendous work submitted by Charles Praplan, JWE, and others.
    • However it appears none of this has been incorporated.
    • After release of version 1.4.1; is this no longer being maintained? Not related to Octave itself. Please reach out for the package maintainer about future plans. If one is interested she might offer to become new package maintainer.

See also