On Thu, Nov 23, 2017 at 11:05:10PM -0500, Neal Gompa wrote: > On Thu, Nov 23, 2017 at 4:33 PM, Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: > > On Thu, Nov 23, 2017 at 08:34:35PM +0000, Will Crawford wrote: > >> On 23 November 2017 at 13:55, Zbigniew Jędrzejewski-Szmek > >> <zbyszek@xxxxxxxxx> wrote: > >> [...] > >> > I think we should consider getting rid of this requirement. Updating > >> > wiki pages is quite a bit of work, and we have better mechanisms to > >> > advertise stuff to users that didn't exist a few years ago. Apart from > >> > the manual effort, the problem with wiki pages is that they tend to > >> > get out of date pretty quickly enough to be out-of-date to often to be > >> > really trustworthy. Instead, I think it'd be better to spend the > >> > effort on making gnome software support fonts even better and to improve > >> > the appdata files for fonts to make them "shine" in gnome-software. > >> > This would be > >> > > >> > a) less effort (a few minutes to create an appdata file when initially > >> > packaging the font, very little ongoing effort, metadata is automatically > >> > updated on package updates), > >> > > >> > b) actually more useful for users (you get a live list, click "install" > >> > on the font you like, instead of going from a wiki page to the command > >> > line). > >> > >> There are still some dinosaurs who don't use GNOME. > >> > >> Maybe some mechanisms that aren't dependent on that would be good? > > > > I'd try to write a page generator that'd turn appdata files into > > html. Might be useful for more than fonts. That doesn't even seem > > like that much work, to write such a script and have it run once a > > week and update the html for all updated packages and push it out to > > a server somewhere. > > > > It'd be nice to integrate this into our package/software search > system[1]. That way the information returned is richer and more > useful... > > Also, I wonder why packages.fedoraproject.org doesn't already point to this...? Yeah, that'd be absolutely great. It seems that this would require two steps: first a service which exports the appdata information on the web somewhere in standarized format, and then code in fedora-packages to display that information. (The reason why fedora-packages cannot do this directly is that appdata information can only be reliably extracted from the final rpm, and that's a slow operation). I cc'd recent fedora-packages contributors, maybe they can provide more info. Zbyszek > [1]: https://apps.fedoraproject.org/packages/ _______________________________________________ fonts mailing list -- fonts@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to fonts-leave@xxxxxxxxxxxxxxxxxxxxxxx
