https://wiki.octave.org/wiki/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0Octave - New pages [en]2024-03-28T20:06:56ZFrom OctaveMediaWiki 1.39.2https://wiki.octave.org/Online_Developer_Meeting_(2024-03-26)Online Developer Meeting (2024-03-26)2024-03-02T19:21:04Z<p>Mmuetzel: /* Today's topics */ Update notes</p>
<hr />
<div>* Date: Tuesday, March 26, 2024 @ 18:00 UTC '''[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=03&day=26&hour=18&min=0&sec=0&p1=263&p2=37&p3=26&p4=176&p5=248&p6=108&p7=111&p8=264&p9=2322 Convert timezones here!]'''<br />
* Location: https://meet.jit.si/octave-dev<br />
<br />
== Today's topics ==<br />
* Timing for next bugfix release '''(middle of April, approx. one month after the 9.1.0 release)'''<br />
** bug #65476 (`mkoctfile -p LIBS` includes unnecessary libraries) '''Done'''<br />
** Copyright dates for documentation, and possible MXE-Octave files out of date '''Done'''<br />
** '''In the future, we'll likely aim for a .2.0 release around a month after the .1.0 release; a .3.0 around 3 month after the .1.0 release; and a .4.0 release about 6 months after the .1.0 release. If necessary, additional releases are possible in between or after these approximate dates, or some releases could be skipped.'''<br />
* '''Andreas Bertsatos will open a thread about extracting demos from classdef files''' [https://octave.discourse.group/t/new-feature-to-grab-demo-from-classdefs-that-are-associated-with-methods/5419]<br />
* OctConf 2024<br />
** '''Agreed. Eastern North America likely. Rik will post a poll.'''<br />
* Roadmap and priorities for Octave 10<br />
** Which important features to focus on for Octave 10?<br />
** '''JWE will try to make MExceptions real classdef objects (not overloadable, fully implemented in C++)'''<br />
** '''JWE will try to start a thread on Discourse about potential new features for Octave 10.'''<br />
* Discuss a potential timeline for native string class support<br />
<br />
== Previous topics ==<br />
* Status of 9.1 Release<br />
** Are there remaining blocker bugs? -- None. In case of issues, a version 9.2 could be released early.<br />
** Do we issue a second release candidate (RC2)? -- No RC2. jwe will proceed to create a release tarball for Octave 9.1 and the Windows installers shortly.<br />
* Common id tag for developer of Octave packages in AppStream Metainfo files?<br />
** Should they use a different tag from the identifier of core Octave? See [https://savannah.gnu.org/patch/?10434 core patch] and [https://github.com/gnu-octave/octave-doctest/pull/286 package change/discussion]<br />
** Conclusions: no strong feelings. Each package should generally decide what they want: if they feel that <code>id="octave.org"</code> and <code><name>Octave Community</name></code> describes their community, that's probably fine. If in doubt, just ask.<br />
* How to handle pull requests for the mirror on GitHub?<br />
* New bug reports on Savannah for packages should be tagged by the package name in parenthesis at the start of the report title. E.g., "(statistics) some error" (i.e., no longer prepend with "[octave forge]"). Also, set the report category to "Octave package". Try to CC package developers.<br />
<br />
== See also ==<br />
<br />
* Next meeting: [[Online Developer Meeting (2024-04-23)]]<br />
* Prev meeting: [[Online Developer Meeting (2024-02-27)]]<br />
<br />
[[Category:2024]]<br />
[[Category:Meetings]]</div>ArunGiridharhttps://wiki.octave.org/GSoC_2024_applicationGSoC 2024 application2024-02-02T15:33:32Z<p>Nir: adapted from 2023</p>
<hr />
<div>__NOTOC__<br />
<br />
Octave's application for GSoC 2024.<br />
<br />
=== Organization name ===<br />
<br />
GNU Octave<br />
<br />
=== OSI approved license? ===<br />
<br />
Yes<br />
<br />
=== Has your organization participated in Google Summer of Code before? ===<br />
<br />
Yes<br />
<br />
=== Please select all years in which your organization participated prior to 2023 ===<br />
<br />
2016-2022, 2014<br />
<br />
=== Website URL ===<br />
<br />
https://www.octave.org<br />
<br />
=== Logo (Must be a 24-bit PNG, minimum height 256 pixels.) ===<br />
<br />
https://upload.wikimedia.org/wikipedia/commons/thumb/6/6a/Gnu-octave-logo.svg/283px-Gnu-octave-logo.svg.png (or generate 256x256 PNG from http://hg.savannah.gnu.org/hgweb/octave/raw-file/155d8e90ee1f/doc/icons/octave-logo.svg with <code>inkscape -z -e octave-logo.png -w 256 -h 256 octave-logo.svg</code>)<br />
<br />
=== Tagline (50 characters) ===<br />
<br />
Free Your Numbers<br />
<br />
=== Primary License ===<br />
<br />
GPL 3.0<br />
<br />
=== What year was your project started? ===<br />
<br />
1992<br />
<br />
=== Source code location === <br />
<br />
https://hg.savannah.gnu.org/hgweb/octave<br />
<br />
<br />
=== Organization Category ===<br />
<br />
Programming Languages, Science<br />
<br />
<br />
=== Technology Tags (the primary specific technologies your organization uses) (up to 5) ===<br />
<br />
C++, hg<br />
<br />
=== Topic Tags (general topics that describe your organization) (up to 5) ===<br />
<br />
mathematics, numerical computation, numerical methods, matlab, scientific computing<br />
<br />
<br />
=== Description ===<br />
<br />
GNU Octave is a high-level interpreted language, primarily intended for numerical computations. It provides capabilities for the numerical solution of linear and nonlinear problems and for performing other numerical experiments. It also provides extensive graphics capabilities for data visualization and manipulation. Octave is normally used through its interactive command line interface, but it can also be used to write non-interactive programs. The Octave language is quite similar to Matlab so that most programs are easily portable.<br />
<br />
Octave is continually being upgraded. Student projects may also involve developing or upgrading Octave Forge packages, which can be loaded to provide additional specialized functions that supplement those provided in Core Octave.<br />
<br />
<br />
=== Contributor guidance / Idea List ===<br />
<br />
https://wiki.octave.org/gsoc<br />
<br />
=== Contact methods ===<br />
<br />
Chat: https://octave.discourse.group/<br />
<br />
Mailing list: https://lists.gnu.org/mailman/listinfo/octave-maintainers<br />
<br />
Email: octave-maintainers@gnu.org<br />
<br />
=== Why does your org want to participate in Google Summer of Code? (1000 chars) ===<br />
<br />
We hope to establish collaborations with talented new contributors. We also want to raise awareness of Octave in the free software community.<br />
<br />
Google Summer of Code represents a unique opportunity to bring new perspectives to the Octave community. As a somewhat older project, we benefit from having new and younger contributors among our developers. We have been able to retain several GSoC participants who have become important contributors to the Octave project and we hope to continue this in the future by engaging effectively with students during both the application and mentoring processes, setting clear standards for what is required for acceptance, and maintaining those standards throughout the project.<br />
<br />
=== What would your org consider to be a successful summer? (500 chars) ===<br />
<br />
We would consider a program successful if we selected promising students, provided adequate mentor supervision, developed desired features in Octave, and facilitated a satisfying experience for the students and mentors. We are more interested in the quality of interactions and contributions than in quantity, although, all else being equal, we would be happy to have more talented students join us.<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== Is your organization part of any government? ===<br />
<br />
No<br />
<br />
<br />
<br />
<br />
<br />
=== How will you keep mentors engaged with their students? (1000 chars) ===<br />
<br />
We will select mentors with proven involvement in Octave and free software and align project topics with the priorities of the core developer team. The vast majority of our mentors have been involved in Octave development for several years, and new mentors will be paired with more experienced ones.<br />
<br />
Each project will include at least one core Octave developer as mentor. These are proven, veteran members of the project who are familiar with the code base and with engaging the maintainer and user community. GNU Octave is a project with applications in very diverse domains, so each project should also include a mentor with expertise in the relevant field.<br />
<br />
=== How will you help your students stay on schedule to complete their projects? (1000 chars) ===<br />
<br />
Previous contributions to Octave (which can be small) are a condition for acceptance. In this way, we hope to select students who are familiar with the codebase and able to start their project quickly.<br />
<br />
A tentative project timeline is required as part of the application, and is checked by mentors for realism during the applicant evaluation process. Once a student is selected, the mentors will work with them to come up with a more detailed timeline, including clear expectations for progress by the midterm and final evaluation periods.<br />
<br />
During the summer, mentors will check with students at least weekly to make sure they are staying on schedule and help with any obstacles that might arise. Students are also expected to regularly update their mentors and the Octave maintainers community on their progress via e-mails and blog posts.<br />
<br />
Overall, the vast majority of our over 30 previous SoC students have finished successfully, making substantive contributions to Octave that have been integrated into our codebase.<br />
<br />
=== How will you get your students involved in your community during GSoC? (1000 chars) ===<br />
<br />
Students will be urged to participate in our chat channel and mailing list. We will set clear expectations on the minimum frequency of email progress updates, typically every two to three days. Students will also set up a blog for longer, weekly, updates which will be aggregated at http://planet.octave.org<br />
<br />
Everything should be completely open. Almost all interactions with the student should be public, e.g. contacting the mentor should happen in the public IRC channel or copy the maintainers mailing list.<br />
<br />
Finally, we organize an annual developers' summit, OctConf, and have in previous years provided support for GSoC students to attend and present. We also hold monthly online developer meetings to discuss Octave's direction and future activities, to which GSoC students would be invited. Such meetings strengthen relationships between community members and the new students.<br />
<br />
=== How many Mentors does your Organization have available to participate in this program? === <br />
<br />
5<br />
<br />
=== Number of students/GSoC contributors accepted in 2023 / still active in community ===<br />
<br />
2 / 1<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Summer of Code]]<br />
[[Category:2024]]</div>Nirhttps://wiki.octave.org/Online_Developer_Meeting_(2024-02-27)Online Developer Meeting (2024-02-27)2024-01-23T18:00:12Z<p>Mmuetzel: /* Today's topics */</p>
<hr />
<div>* Date: Tuesday, February 27, 2024 @ 18:00 UTC '''[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=02&day=27&hour=18&min=0&sec=0&p1=263&p2=37&p3=26&p4=176&p5=248&p6=108&p7=111&p8=264 Convert timezones here!]'''<br />
* Location: https://meet.jit.si/octave-dev<br />
<br />
== Today's topics ==<br />
* Status of 9.1 Release<br />
** Are there remaining blocker bugs? -- None. In case of issues, a version 9.2 could be released early.<br />
** Do we issue a second release candidate (RC2)? -- No RC2. jwe will proceed to create a release tarball for Octave 9.1 and the Windows installers shortly.<br />
* Common id tag for developer of Octave packages in AppStream Metainfo files?<br />
** Should they use a different tag from the identifier of core Octave? See [https://savannah.gnu.org/patch/?10434 core patch] and [https://github.com/gnu-octave/octave-doctest/pull/286 package change/discussion]<br />
** Conclusions: no strong feelings. Each package should generally decide what they want: if they feel that <code>id="octave.org"</code> and <code><name>Octave Community</name></code> describes their community, that's probably fine. If in doubt, just ask.<br />
* How to handle pull requests for the mirror on GitHub?<br />
* New bug reports on Savannah for packages should be tagged by the package name in parenthesis at the start of the report title. E.g., "(statistics) some error" (i.e., no longer prepend with "[octave forge]"). Also, set the report category to "Octave package". Try to CC package developers.<br />
<br />
== Previous topics ==<br />
* Enable polymorphic-allocators by default? In Octave 9? In Octave 10? Later? See [https://octave.discourse.group/t/enable-polymorphic-allocator-by-default-if-available/5132 Enable polymorphic allocator by default (if available)?] '''Leave it disabled by default on Octave 9. Enable it by default for Octave 10. Test in the next year, notify in NEWS that it will require a C++17 compiler so that packages can update their flags.'''<br />
* Disable visibility flags by default for Octave 9? '''Yes, disable visibility flags for Octave 9, meaning export all symbols by default. Make necessary refactoring on default branch for Octave 10. Maybe examine whether templates and classes should be refactored as well.'''<br />
* Release candidate for Octave 9? Any pending changes still missing for the RC? '''With no changes to previous two items, this is good to go. Pending activities: update README for Windows, merge MXE with all new package updates, then good to go.'''<br />
** '''Discussion about making edits to Statistics package so it can make it into MXE for Octave 9. Related to recent changes with isargout.'''<br />
** '''Discussion about "nargout <=" vs "nargout ==", making a policy of "nargout <=" and "nargout >=" going forward, no equality.'''<br />
** '''Discussion about iterators and range-based loops and auto types.'''<br />
** '''jwe will post about coding standard updates on the above topics.'''<br />
* Blocking tasks before moving any classdef-based class (e.g., string, table, datetime, ...) into Octave core?<br />
** '''There is already classdef in Octave core, like inputParser. The difference is that typically there is only one object of inputParser, but Octave core doesn't currently have arrays of classdefs, which would be necessary for arrays of strings etc. See [https://savannah.gnu.org/bugs/?65179] for example'''<br />
** '''The second major shortcoming is that classdefs cannot currently be saved in files.'''<br />
* Discuss a road map to port @table class from Tablicious package into Octave core, while making it a dependency for Statistics until @table gets into core (possibly by Octave 10).<br />
<br />
== See also ==<br />
<br />
* Next meeting: [[Online Developer Meeting (2024-03-26)]]<br />
* Last meeting: [[Online Developer Meeting (2024-01-23)]]<br />
<br />
[[Category:2024]]<br />
[[Category:Meetings]]</div>ArunGiridhar