website development

See for the instance currently deployed.

See also for some background.

This website TODO list contains only those items that can clearly be worked on right now, and is used as coordination between the people working on the site.

Generic wishlists, things that require large changes in the site, or things that need a lot of discussion before being implemented, are tracked on the BTS.

Milestone 1: proof of concept

We show only data from and accounts, which we can safely assume it can be made public without asking first.

We document how to build data mining scripts.

We call for teams to start experimenting with sending data to the site.

TODO list items

Associate to each Source a list of one or more Users who can edit it. This will also act as a documentation for who to contact if it stops posting data. The ?ManyToManyField has been added, but the interface to add it on source creation and add/remove names is still missing.

To break it down:

  1. When a new source is created, associate the current User as its only 'admins' memer
  2. Add an interface to list the current admins to anyone logged in.
  3. Add an interface for admins to add or remove admins OR add an interface for a person logged in to add or remove themselves as admins for one source (this is probably easier)

Identifier.get_absolute_url with a page listing details about an identifier, like all known contributions.

Document how to create a data source (an example script to do it is in

Milestone 2: more data sources

TODO list items

We can help team set these up, but they should ultimately be the responsibility of the teams themselves.

Team submission health report, a page with each data source, the time data was last posted to it, and the time of the last known contribution.

bts-based source

commit log based source

spam review data source data source data source

DSA data source

translators data source

wiki data source

events team data source

Add more ideas for data sources here

Milestone 3: more identifiers

Get more kinds of identifiers into the mix: emails, gpg fingerprints, wiki names.

This needs figuring out both privacy requirements and integrity requirements: we need to avoid to open trolling avenues, like sending one silly bugreport a week as debiansux@ownyouftw.troll to get into the list. Identifiers should be somehow tied to reputation that is built up with constructive work: if one wants to have debiansux@ownyouftw.troll end up in the list, they need to earn it honestly :)

Identity management needs to be implemented, and this probably means waiting until after the single signon sprint meeting that should happen in January. Too much information is missing now to make good tradeoffs.

TODO list items

During maintenance, scan names from GECOS / LDAP and add them to missing first/last names in User.