[Lsb-infrastructure] making Navigator app stats easier ?

[Wichmann, Mats D]

> To make analysis of the application statistics easier I would suggest:
> 
> 1. Add an additional type of attribute to the
> InterfaceAttribute table named, for example, 'Ban'. If we
> believe that we definitely are not going to include an
> interface into the LSB we will mark such interfaces with the
> 'Ban' attribute and put a reasoning to 'Recommendation'. This
> will help us to filter out (optionally) unnecessary interfaces
> from application analysis. ATK Manager will be able to use
> this information for advanced reports too.

Maybe Ban is too strong a term but I like the concept of
being able to capture our stance about a library and
report on it easily. We have a variety of issues, for example
we know certain libraries are full GPL and would cause
problems for using in applications which are not willing
to accept such a license.

> 2. Add LibraryAttribute table similar to the
> InterfaceAttribute one. 'Recommendation' and 'Ban' will be
> useful here too.
> 
> 3. May be it makes sense to mark also libraries, which are
> known to be easily statically linked or delivered with an
> application. If we would like to use this information in
> reports of ATK Manager only, the 'Recommendation' in
> LibraryAttribute is enough. If we would like to implement more
> sophisticated scenarios (for example, filtering in application
> statistics), a separate attribute is better.

These all sound pretty good to me.  

> If we implement filter facilities on base of these attributes
> in application statistics we will be able to concentrate our
> efforts on analysis of really important interfaces to be
> included into LSB.

Yes, this was the intent of my email.  I was looking at
these things and realized that I know to ignore certain
things based on memory of years of discussion, but it
would be much less clear to a newcomer.