Launchpad itself

offer per-project statistics

Bug #431011 reported by kimus on 2009-09-16

This bug affects 13 people

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	Triaged	Low	Unassigned

Bug Description

I think LP should have a way to get statistics of the projects. The most important statistics for me are: visits, repository usage and downloads. Tough visits could be for the team only.

Source Forge has some kind of statistics and even Google Code has a way to get statistics configuring the Google analytics key in the project administration.

I think this is a very important feature/tool for teams that have projects hosted in LP.

Mailing List discussion Thread: https://lists.launchpad.net/launchpad-users/msg05474.html

Using Google Analytics would be great because it's trivial to integrate (just add a javascript on every page) and project owners can add the key in the administration.

Tags:

Karl Fogel (kfogel) on 2009-09-16

summary:

- Launchpad statistics
+ offer per-project statistics

Revision history for this message

Fernando Miguel (fernandomiguel) wrote on 2009-09-22:

I run a few projects and also would like to see this improved

Ursula Junque (ursinha) on 2009-09-22

affects:

launchpad → launchpad-registry

Revision history for this message

Curtis Hovey (sinzui) wrote on 2009-09-24:

I cannot find a bug about this, but this is a well understood story that has been discussed often. This information comes from the web server, not the project or launchpad itself. In 2.0 we created a means to parse the logs to get this information. We now need a way to identify the kinds of information we are gathering. The proxy and HTTPS issues continue to make this harder than it seems.

affects:

launchpad-registry → launchpad-foundations

Revision history for this message

kimus (kimus) wrote on 2009-09-24:

Adding a preference for using Google Analytics, like other project management tools have. will be a trivial add-on to the HTML template. Using you own logs parsing (or should I say analytics module / project) would be harder and depends on how LP is setup (Proxy, HTTP, etc). The first is more personal to the project team but also trivial to implement. The second could offer a more elaborated and public statistics but it's also less simple to implement.

So I think it should be two different ways of offering pre-project statistics that also can work together. I would choose the trivial way first, because can be offered now, the stats are not present in the project page because they are in Google. LP will not display nothing different but the teams gain a lot! After you have time to implement a LP statistics project.

Curtis Hovey (sinzui) on 2010-01-25