111
edits
No edit summary |
No edit summary |
||
Line 9: | Line 9: | ||
* Common id tag for developer of Octave packages in AppStream Metainfo files? | * Common id tag for developer of Octave packages in AppStream Metainfo files? | ||
** 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] | ** 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] | ||
** Conclusions: no strong feelings. Each package should generally decide what they want: if they feel that `id="org.octave"` and `<name>Octave Community</name>` describes their community, that's probably fine. If in doubt, just ask. | |||
== Previous topics == | == Previous topics == |
edits