Merge in Loco Reports into loco.ubuntu.com

[Jono Bacon]

paultag has been doing some awesome work generating LoCo stats (see http://me.paultags.com/reviews/dataset-ubuntu-ie-report.html for an example).

This is perfect content to be merged into the teams page in the LoCo Directory. I would like to recommend that Paul does the development work on report generation code and Daniel works to merge this into the LoCo Directory.

[Paul Tagliamonte (paultag)]

The existing code is in PHP and not done up to the standard expected in a live and stable application. Existing code is in [1] ( git ).

I do know of a lib that has similar graphic output for Python, and would not have to work too hard to port that over.

[1]: http://github.com/paultag/locotools

[Daniel Holbach (dholbach)]

I think I'll write another management command that gets the data about teams and use parts of the code that you wrote. We need to change the database schema for this.

[Daniel Holbach (dholbach)]

For graphing I'd recommend some javascript library, so we don't need to get additional dependencies for the LoCo Directory installed. Recommendations?

[Daniel Holbach (dholbach)]

http://g.raphaeljs.com/piechart2.html and http://raphaeljs.com/pie.html could be a good start.

[Daniel Holbach (dholbach)]

What kind of data is interesting?

Is it really
 - percentage-of-members-per-year and
 - highest and lowest karma?

[Paul Tagliamonte (paultag)]

Hey Danial, I've been poking around -- I know lplib and I have some basic stuff in lpupdate --

Mind if I give this a shot, and have you review it for issues?

[Daniel Holbach (dholbach)]

Sure, I'm happy to help if I can. Just push your branch to LP and propose a merge of it.

[Paul Tagliamonte (paultag)]

Currently, when a team is being updated via lpupdate ( called by update off the ./manage script ) membership.

The current data being pulled is very little, but it will be enough to prove the concept.

The data pulled is an array of POSIX dates that mark the date / time of the join to the team. I set it up as follows ( to try and make it easy to expand, when we need to )

array( { "join" : nnnn }, { "join" : nnnn }, { "join" : nnnn } );

Extra data will be pulled after the iteration is finished ( pull down lp member object and store real name for oldest member etc )

How should this be changed to fit with the database? My guess is that we should allow for general statistics, if we would hypothetically pull from other sources as well.

[Grant Bowman (grantbow)]

Sounds like more resources are required and here is how to ramp up with a development environment, right? http://princessleia.com/journal/?p=6662

[Benjamin Kerensa (bkerensa)]

We should fork this repo https://github.com/mozilla/remo/blob/master/remo/reports/

[Benjamin Kerensa (bkerensa)]

^ Django application for reporting of open source contributor events/activity.... Could easily be forked and modified and hooked into LoCo Portal for Team Reports.... Had a wiki export hook not sure if its still there but it use to work with moinmoin.