On Thu, Nov 23, 2017 at 3:31 AM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > On Tue, Nov 21, 2017 at 03:44:05PM +0530, Akira TAGOH wrote: >> All of fonts is supposed to have an information page for their fonts >> at wiki based on the template[1] according to the package >> lifecycle[2]. however some of them doesn't have. so just tried to pick >> them up and inform you to get one there. > > Are they? From the lifecycle page you link, that seems to be there to > enable the packaging of the font in the first place, not meant to be > long-term documentation. If it _is_ meant to be long-term > documentation, that should be clarified somewhere. Who is the audience > for this documentation? That could be. as some of the wiki pages contains the sample rendering, that should definitely be helpful for the end users too to see how it looks like. unfortunately not available everything. we could improve it. For the audience, I don't know.. maybe Nicolas Mailhot? > If it's supposed to be for end users (and that's a great goal!), I > think the new docs site would be better than the wiki. Sure. yes, I like it. that depends what sort of information we provide though, the wiki pages can be easily outdated if noone maintains. so maybe nice to have the sort of web apps or any infrastructure working at the background to generate information from the packages and so on. well, we could do that with wiki even though. > > If it's for contributors and packagers, wouldn't it be better to have > the documentation in a README.md in dist-git, next to the spec file? > That way, it'd show up at (for example) > https://src.fedoraproject.org/rpms/overpass-fonts > > -- > Matthew Miller > <mattdm@xxxxxxxxxxxxxxxxx> > Fedora Project Leader > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Akira TAGOH _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
