Results of the App Installer Meeting

[Samuel Verschelde]

Le jeudi 27 janvier 2011 17:28:55, seth vidal a écrit :
> On Thu, 2011-01-27 at 17:24 +0100, Samuel Verschelde wrote:
> > Le jeudi 27 janvier 2011 17:14:17, seth vidal a écrit :
> > > On Thu, 2011-01-27 at 17:05 +0100, Samuel Verschelde wrote:
> > > > I would prefer to have this in some metadata file and query the OCS
> > > > server for more up to date description or new translations, for the
> > > > following reasons : - full text searching in descriptions (like
> > > > apt-xapian-index does currently for packages).
> > >
> > > We do full text searching in descriptions in yum now - but we're just
> > > using the sqlite searches.
> > >
> > > > - having only the name and a one-liner when offline is not great :)
> > >
> > > right but name+summary+eng-description+LANG-description when offline
> > > seems like good coverage for searches.
> >
> > That's what I'm saying. If we deport eng-description and LANG-description
> > to an OCS server without anything in metadata downloaded from mirrors,
> > then we wont have this :)
> 
> Right - this is why I'm saying keep the set of things restricted.
> 
> A big paragraph/page is not unreasonable provided you know how many you
> plan to scale to, but don't add too much data there and let people link
> out to OCS for 'more info'.
> 
> 
> So - a name + summary + descrip + lang-descrip + icon?
> 
> then link out for 'extended info' which could include screenshots, etc.
> 
> Also by not including any type of markup you can conserve space in the
> metadata that's not strictly content.
> 
> -sv
> 

This is what I would go for, provided we define the whole chain (who writes 
descriptions and their translations, how, where, and how do they end up in 
metadata files on the mirrors).

Samuel