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.
--
Merge in Loco Reports into loco.ubuntu.com
https://bugs.launchpad.net/bugs/605651
You received this bug notification because you are a member of loco-
directory-dev, which is the registrant for loco-directory.
Status in LoCo Directory: Triaged
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.
_______________________________________________
Mailing list: https://launchpad.net/~loco-directory-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~loco-directory-dev
More help : https://help.launchpad.net/ListHelp
