elisa-developers team mailing list archive

[Florian Boucault <florian@xxxxxxxxxxxx>]

Hello team,

David's email was quite interesting and I believe he nailed the major
key features that are either necessary (local content scanning) or could
make users tick (user driven content and media exploration).

Unrelated to these but something that was dearly missing in the past:
I set myself to finding an efficient solution for continuous
integration, that is a set of tools that would give us constant feedback
on how the quality of the software is. A summary of my findings is
available in the wiki:
http://wiki.elisa-media-center.org/ContinuousIntegration

The attachment in the e-mail is a screenshot of an Elisa project setup
in a Hudson instance that does reporting of:
- unit tests
- code coverage
- static code analysis with pylint

It uses the media scanner branch [1] that is in deep need of love.

Next steps are:
1) to transfer my Hudson instance to our public server (Saviq ;);))
2) produce a summary of the media scanner branch (concepts,
architecture, pending work etc.) so that other people can work on it. I
do believe that it's where we should start.

Florian

[1] https://code.launchpad.net/~elisa-developers/+junk/mediascanner