Online Developer Meeting (2022-12-20): Difference between revisions

From Octave
Jump to navigation Jump to search
(new page)
 
(+followup)
Line 10: Line 10:
** '''Consensus: mmuetzel preferred not being listed. Rik was OK either way. Other signatories (jwe, siko1056, nrjank, arungiridhar) converged.'''
** '''Consensus: mmuetzel preferred not being listed. Rik was OK either way. Other signatories (jwe, siko1056, nrjank, arungiridhar) converged.'''
** '''mmuetzel and colin wanted to know other GNU projects that have joined NumFOCUS and how they managed their transition. Arun has reached out to GNU Radio.'''
** '''mmuetzel and colin wanted to know other GNU projects that have joined NumFOCUS and how they managed their transition. Arun has reached out to GNU Radio.'''
** '''(Follow-up, 2022-12-06: GNU Radio's response strongly encouraged getting classified as a fiscally supported member of NumFOCUS ASAP and redirecting any current funding flows to the new NumFOCUS account. Any funds in the FSF fund gathered for Octave can be requested to be transferred afterwards. We should also let FSF know our intention to become a NumFOCUS project. We should also find out from FSF how much money we have in the Octave account, but that is not a prerequisite for joining NumFOCUS.)'''


* Octave infrastructure - FOSSHost abandonment
* Octave infrastructure - FOSSHost abandonment

Revision as of 23:06, 6 December 2022

Today's topics

Previous topics

  • Outcomes from NumFOCUS meeting (2022-11-07).
    • Converge on who's willing / unwilling to be a signatory.
    • Consensus: mmuetzel preferred not being listed. Rik was OK either way. Other signatories (jwe, siko1056, nrjank, arungiridhar) converged.
    • mmuetzel and colin wanted to know other GNU projects that have joined NumFOCUS and how they managed their transition. Arun has reached out to GNU Radio.
    • (Follow-up, 2022-12-06: GNU Radio's response strongly encouraged getting classified as a fiscally supported member of NumFOCUS ASAP and redirecting any current funding flows to the new NumFOCUS account. Any funds in the FSF fund gathered for Octave can be requested to be transferred afterwards. We should also let FSF know our intention to become a NumFOCUS project. We should also find out from FSF how much money we have in the Octave account, but that is not a prerequisite for joining NumFOCUS.)
  • Octave infrastructure - FOSSHost abandonment
    • (That host never came back up at all. Arun has been checking its status daily.)
    • Not much discussion on this topic, except jwe reiterated that it was good practice for emergency recovery, and mentioned he and siko1056 are continuing to strengthen the server backup systems.
  • Progress toward Octave 8.1 release
    • bugs that must be resolved first ("blockers"):
    • bugs requiring some effort that would be nice to resolve first:
    • "easy" close bugs that should be able to be resolved first:
      • This discussion turned into organizing the release checklists better for Octave 8, and as a result, the wiki page 8.1 Release Checklist was created by nrjank based on 7.1 Release Checklist and is being updated.
  • Pick some "big feature(s)" to work on for Octave 9:
    • VM?
    • String class?
    • Dictionary / hashmap?
    • Context-sensitive tab completion? (GSoC maybe)
    • (your ideas here)
    • The string class was agreed upon as the highest priority among the above. It is necessary for other features like the dictionary.
    • There was discussion about whether to deprecate existing string behavior for two releases or make a change when it's ready. That was not converged upon, but it was agreed that putting an early notice of potential future breakage in the NEWS file would be good.

See also

Retrieved from "https://wiki.octave.org/wiki/index.php?title=Online_Developer_Meeting_(2022-12-20)&oldid=14548"