Merge in Loco Reports into loco.ubuntu.com

Bug #605651 reported by Jono Bacon on 2010-07-14
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Low
Paul Tagliamonte

Bug Description

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) wrote :

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

Changed in loco-directory:
assignee: nobody → Daniel Holbach (dholbach)
importance: Undecided → High
status: New → Triaged
tags: added: stats teams ui
Daniel Holbach (dholbach) wrote :

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) wrote :

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

tags: added: research schema-change
Daniel Holbach (dholbach) wrote :
tags: added: needs-decision
removed: research
Daniel Holbach (dholbach) wrote :

What kind of data is interesting?

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

Paul Tagliamonte (paultag) wrote :

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) wrote :

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

Changed in loco-directory:
assignee: Daniel Holbach (dholbach) → nobody
Changed in loco-directory:
assignee: nobody → Paul Tagliamonte (paultag)
Paul Tagliamonte (paultag) wrote :

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) wrote :

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

Adnane Belmadiaf (daker) on 2013-03-30
Changed in loco-team-portal:
importance: High → Low
Benjamin Kerensa (bkerensa) wrote :

^ 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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers