[dash-dev] Dashboard architecture

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[dash-dev] Dashboard architecture

From: Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Date: Mon, 22 May 2006 10:00:02 -0700
Delivered-to: dash-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/dash-dev>
List-help: <mailto:dash-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/dash-dev>, <mailto:dash-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/dash-dev>, <mailto:dash-dev-request@eclipse.org?subject=unsubscribe>
Organization: Eclipse Foundation Inc.
User-agent: Thunderbird 1.5.0.2 (Windows/20060308)

Ward and I have been working on the Commits Explorer (http://dash.eclipse.org/dash/commits/). The basic architecture of this dashboard is in three parts:

A database summarizing all commits to all the Eclipse CVS repositories
A web API to run specific queries against this database (e.g. http://dash.eclipse.org//dash/commits/commit-summary.php?top=y&year=x)
A web front end to take the API results and massage/format/navigate them in interesting ways (e.g. http://dash.eclipse.org/dash/commits/summary.cgi)

We plan to build the same sort of structure for the old dashboard data: newsgroups, mailing lists, bugzilla, etc. The combination of the web API and the web front end allows other front ends to use the same raw data. And the other front ends can run on other non-Eclipse machines.

What do you all think? Is this a reasonable approach?

- Bjorn

Follow-Ups:
- [dash-dev] Groovy Monkey
  - From: James E. Ervin
- Re: [dash-dev] Dashboard architecture
  - From: Ian Bull

Prev by Date: Re: [dash-dev] Groovy Monkey Plugin
Next by Date: [dash-dev] Re: dash
Previous by thread: [dash-dev] Re: [dsdp-pmc] The Eclipse Project Dashboard
Next by thread: Re: [dash-dev] Dashboard architecture
Index(es):
- Date
- Thread

Breadcrumbs