Online Developer Meeting (2020-11-10): Difference between revisions

→‎The future of Octave Packages: The package legacy in Savannah
(Update date and location)
(→‎The future of Octave Packages: The package legacy in Savannah)
Line 8: Line 8:
=== The future of Octave Packages ===
=== The future of Octave Packages ===
: ''See also [https://octave.discourse.group/t/online-developer-meeting-2020-11-10-the-future-of-octave-packages/349 Discourse].''
: ''See also [https://octave.discourse.group/t/online-developer-meeting-2020-11-10-the-future-of-octave-packages/349 Discourse].''
=== The package legacy in Savannah ===
When reporting an Octave (core) bug on https://savannah.gnu.org/bugs/?group=octave you are "greeted" with '''1523 open bug reports''' of which [https://savannah.gnu.org/bugs/?group=octave&func=browse&set=custom&msort=0&status_id=1&resolution_id=0&submitted_by=0&assigned_to=0&category_id=108&bug_group_id=0&severity=0&priority=0&summary=&details=&advsrch=0&msort=0&chunksz=100&spamscore=5&report_id=101&sumORdet=0&morder=bug_id%3C&sumOrdet=0&offset=0#results '''330 reports (22%)'''] belong to Octave Forge packages and '''240 (15%) are older than a year'''.
* They are not likely to be closed or worked on and leave a maintenance burden and bad impression (user requests for unmaintained packages are ignored there) back to Octave (core).
Ideas:
* Ignore and collect requests to infinity?
* Close bugs of inactive packages older than X years?  (Drop the illusion, that someone ever will fix it.)
* Octave Forge suggests to [https://octave.sourceforge.io/support-help.php use the Savannah Bug tracker] for bug reports.  Drop this announcement?
* Reopen the [https://sourceforge.net/p/octave/bugs/ old Octave Forge bug tracker]?


== Ideas for next meeting ==
== Ideas for next meeting ==