Old modules - gathering stats

[Duncan Gibson]

>> As far as getting stats from user installs as to which modules are
>> being used or installed, I can see a number of issues with that.
>
> [...]
> Another barrier crossed. What else?
> moonbase version? does that come as part of 'lvu installed' ? Yes!
> In fact, the output of 'lvu installed' looks exactly like what is
> needed. Cool! so that means that this 'feature' could be as simple
> as "lvu installed | mail -s 'Installed' something at lunar-linux.org"
> or a new option to "lvu" such as "feedback" or "report".

Bummer. Not quite true. 'lvu installed' gives you:

    module:yyyymmdd:status:version:size

where:
module is the name of the module. OK
yyyymmdd is the date of installtion, not the last update in moonbase.
version is whatever the app-devs want, date, x.y.z, etc.

For stats purposes, it would be better if the date returned was
the last update in moonbase date, and not the installation date.
The version field might be difficult to parse for comparisons.
So we can't easily see whether the module installed yesterday is
an old one or not. But we could join module and version and see
multiple versions in the output.

How about a web page display showing number of user installations
with a given period (colour coded like Striker's Modules page)?

module-version  |  1 Month | 3 Months | 6 Months | 12 Months | Older

Or have a 'Users' column on Striker's Modules page that links to
a page showing all versions for that module, with the format above?

Cheers
Duncan / engelsman