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

Line 95: Line 95:
==== New directions ====
==== New directions ====


===== Octave package format =====
===== pkg-index =====


===== pkg-index =====
* https://gnu-octave.github.io/pkg-index/
* https://github.com/gnu-octave/pkg-index/
 
* Super set of Octave Forge (all packages in latest version included)
* Easy to add, update and delete entries (just one file of meta data)
* Advertise pkg-index as (only) major platform for Octave packages?
 
* Future development:
** Automated quality checks (dead URLs, pkg installation problems)


===== pkg tool =====
===== pkg tool =====
* Current pkg very interleaved with / limited by Octave Forge <code>-forge</code>
** Abstracting package registry / index?
* Alternatives exist [https://github.com/apjanke/octave-packajoozle octave-packajoozle (pkj)]
* General design: '''Making pkg an Octave package?'''
** Changes to pkg or the package format can be applied to old Octave versions.
** Multiple pkg tools can be developed.
====== Octave package format ======
* Documented [https://octave.org/doc/v5.2.0/Creating-Packages.html in the Octave manual]
* In general good Octave programming project organization.
* Permitting "DESCRIPTION.md" or "DESCRIPTION.txt" extensions? (Nice highlighting in many modern source code hosting platforms.)
===== General questions =====
* How to teach people that creating an Octave package is as simple as [https://github.com/gnu-octave/pkg-example pkg-example]?
* Packages must become smaller?
** Split large packages into different functionalities?


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