Differences between revisions 1 and 52 (spanning 51 versions)
⇤ ← Revision 1 as of 2013-09-15 15:41:15 →
Size: 1064
Editor: EnricoZini
Comment: Initial todo list
← Revision 52 as of 2014-07-18 16:43:42 → ⇥
Size: 6739
Editor: LauraArjona
Comment: Add Debian voters data source (TODO)
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<TableOfContents>>
Line 3: Line 5:
== TODO list == See http://contributors.debian.org/ for the instance currently deployed. See also http://www.enricozini.org/2013/debian/debian-contributors-right-after-debconf/ for some background. The site is written with [[https://www.djangoproject.com/|Django]].


=== website TODO list ===
Line 6: Line 11:
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 [[http://bugs.debian.org/nm.debian.org|BTS]].
Line 7: Line 13:
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 [[http://bugs.debian.org/nm.debian.org|BTS]] instead.  * [safanaj] Let admins delete all contributions for a data source or single contribution type. See [[http://lists.alioth.debian.org/pipermail/newmaint-site/Week-of-Mon-20140331/000107.html|details on the list]]
 * The layout of the editing forms /sources/update/NAME can still be improved; errors should be laid out so they stand out, spacing is unnecessary.
 * [cmark] Add an interface for people logged in to claim an email addresses, with a url being sent to that email address to confirm the claim. This needs a new model for pending claims, the code to send the mail and a view to accept the confirmations.
 * Also allow to unclaim an identifier (example use case: I want to split my online identity in two: work-Enrico and personal-Enrico, and I want to disassociate an email from personal-Enrico to associate it to work-Enrico)
 * Add a new Source.data_since field to Source, !DateField(null=True), which when present means that there are contributors from before that date, but data is only available since that date. When showing contributions, if c.since<=data_since then show "Since records began" instead of a date.
 * Identifier.get_absolute_url` with a page listing details about an identifier, like all known contributions.
 * Autodetect compression type from uploaded file name, if available. This allows to just use {{{curl -F data=@file.json.gz}}} without needing {{{-F data_compression=gzip}}}. Look into {{{contributors/importer.py}}} {{{ValidatingDict.get_data}}}: f is a Django UploadedFile object with a {{{.name}}} attribute.
Line 9: Line 21:
=== TODO list items === == Data sources ==
Line 11: Line 23:
----
Create an interface to add new data sources
----
Create a POST interface to submit data from a data source		 We want to map all kind of Debian contributions: to do this, we'll need different data sources to mine (repositories, mailing lists, bug tracking system, log of webservices, etc.).
For each contribution, we only need:
 *''$contributor_identifier'': can be a name, a nickname, a mail address
 *''$date'': ideally, a time range is better ($start-date and $end-date for each contributions provided by the same person).

The addition of a new data source is quite easy, and not always requires coding skills.<<BR>>
You have to be a Debian Developer, though: if you are not one but you have a ready-to-cook recipe for a new data source, please contact [[https://lists.alioth.debian.org/mailman/listinfo/newmaint-site|the development mailing list]] and ask for help.<<BR>>
If you are a Debian Developer, check [[DebianContributors|this page]] to find out how to add a new data source.

Is your team/contribution already in the following list? If not, add it and try to work on it (or at least provide a plan on how to gather those data).
=== data sources TODO list ===

{{{#!wiki tabular
|| '''Contribution type / Team''' || '''Status''' || '''by'''|| '''Comment''' ||
|| http://ftp.debian.org || done || Ganneff, ansgar, mhy || - ||
|| http://dsa.debian.org/ || done || zobel || - ||
|| Debian Security Tracker || done || FedericoCeratto || - ||
|| http://bzr.debian.org/ || done || asb || - ||
|| Collab Maint || done || enrico || - ||
|| debconf subtitle team || done || madamezou || needs implementation server side to also show people without a @debian.org address ||
|| nm-site-devel || wip || enrico || scanning git logs, or the mailing list, should do ||
|| spam review || done || formorer, madamezou || ||
|| http://svn.debian.org/ || proof of concept || enrico || can be done scanning SVN repo logs ||
|| http://www.debian.org/ || proof of concept || enrico || can be done scanning CVS repo logs ||
|| debconf || to do || || just ask historical penta logs for all subset of volunteers and process them ('''will need coding skills''') ||
|| Debian Perl team || todo || || could be done adapting [[http://pet.debian.net/pkg-perl/pet.cgi|PET]] ('''will need coding skills''') ||
|| http://wiki.debian.org/ || done || sledge, enrico || ||
|| Debian Publicity team || done || madamezou || uses svndirs via dc-tool ||
|| [[http://bts.debian.org|BTS]] || to be done || || maybe second-hand data via UDD? ('''will need coding skills''') ||
|| Debian Blends || to be done || || there is an activity tracker for the Blends that can be adapted ('''will need coding skills''') ||
|| l10n (po-debconf, website) || wip || enrico, madamezou, laura || the l10n bot can be adapted ('''will need coding skills''', [[http://anonscm.debian.org/gitweb/?p=debian-l10n/dl10n.git;a=summary|here's the repo containing it]])||
|| l10n (manuals, documentation) || to be done || || scanning SVN repo logs for the debian-doc group ([[http://anonscm.debian.org/viewvc/ddp/manuals/trunk/|here the repo]]) ||
|| l10n ([[http://ddtp.debian.net/|ddtp]]) || to be done || || maintainers of the web interface ([[http://ddtp.debian.net/ddtss/index.cgi/xx|ddtss]]) should have logs of submissions, it should be possible to adapt them ('''will need coding skills''') ||
|| l10n (installer) || to be done || || ask debian-boot (may be possible to use the d-i repo, but then we'd have also other contributors to d-i, not only translators. Also, sometime the person translating and the one committing are not the same ||
|| voters || to be done || || Contact points: http://www.debian.org/intro/organization as project secretary. This will be one step in having contributors.debian.org replace the current database used for MIA tracking. ||
}}}
 
Line 19: Line 64:
 * [[http://anonscm.debian.org/gitweb/?p=dc/dc.git;a=blob;f=README.md|Getting started with contributors.debian.org development]] (still to be written, it's basically just syncdb and migrate now, there is no test data atm)  * [[http://anonscm.debian.org/gitweb/?p=nm/dc.git;a=blob;f=README.md|Getting started with contributors.debian.org development]]
Line 21: Line 66:
 * [[http://lists.alioth.debian.org/pipermail/newmaint-site/Week-of-Mon-20131028/000032.html|contributors.debian.org milestones]]
 * Data model: [[attachment:nm-dc.png]] (graphed with {{{sqlt-graph}}} from {{{manage.py sqlall contributors}}}
 * How to create a new data source: DebianContributors

Contents

  1. contributors.debian.org website development
    1. website TODO list
  2. Data sources
    1. data sources TODO list
  3. Resources

contributors.debian.org website development

See http://contributors.debian.org/ for the instance currently deployed. See also http://www.enricozini.org/2013/debian/debian-contributors-right-after-debconf/ for some background. The site is written with Django.

website TODO list

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.

  • [safanaj] Let admins delete all contributions for a data source or single contribution type. See details on the list

  • The layout of the editing forms /sources/update/NAME can still be improved; errors should be laid out so they stand out, spacing is unnecessary.
  • [cmark] Add an interface for people logged in to claim an email addresses, with a url being sent to that email address to confirm the claim. This needs a new model for pending claims, the code to send the mail and a view to accept the confirmations.
  • Also allow to unclaim an identifier (example use case: I want to split my online identity in two: work-Enrico and personal-Enrico, and I want to disassociate an email from personal-Enrico to associate it to work-Enrico)

  • Add a new Source.data_since field to Source, DateField(null=True), which when present means that there are contributors from before that date, but data is only available since that date. When showing contributions, if c.since<=data_since then show "Since records began" instead of a date.

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

  • Autodetect compression type from uploaded file name, if available. This allows to just use curl -F data=@file.json.gz without needing -F data_compression=gzip. Look into contributors/importer.py ValidatingDict.get_data: f is a Django ?UploadedFile object with a .name attribute.

Data sources

We want to map all kind of Debian contributions: to do this, we'll need different data sources to mine (repositories, mailing lists, bug tracking system, log of webservices, etc.). For each contribution, we only need:

  • $contributor_identifier: can be a name, a nickname, a mail address

  • $date: ideally, a time range is better ($start-date and $end-date for each contributions provided by the same person).

The addition of a new data source is quite easy, and not always requires coding skills.
You have to be a Debian Developer, though: if you are not one but you have a ready-to-cook recipe for a new data source, please contact the development mailing list and ask for help.
If you are a Debian Developer, check this page to find out how to add a new data source.

Is your team/contribution already in the following list? If not, add it and try to work on it (or at least provide a plan on how to gather those data).

data sources TODO list

Contribution type / Team

Status

by

Comment

http://ftp.debian.org

done

Ganneff, ansgar, mhy

-

http://dsa.debian.org/

done

zobel

-

Debian Security Tracker

done

FedericoCeratto

-

http://bzr.debian.org/

done

asb

-

Collab Maint

done

enrico

-

debconf subtitle team

done

madamezou

needs implementation server side to also show people without a @debian.org address

nm-site-devel

wip

enrico

scanning git logs, or the mailing list, should do

spam review

done

formorer, madamezou

http://svn.debian.org/

proof of concept

enrico

can be done scanning SVN repo logs

http://www.debian.org/

proof of concept

enrico

can be done scanning CVS repo logs

debconf

to do

just ask historical penta logs for all subset of volunteers and process them (will need coding skills)

Debian Perl team

todo

could be done adapting PET (will need coding skills)

http://wiki.debian.org/

done

sledge, enrico

Debian Publicity team

done

madamezou

uses svndirs via dc-tool

BTS

to be done

maybe second-hand data via UDD? (will need coding skills)

Debian Blends

to be done

there is an activity tracker for the Blends that can be adapted (will need coding skills)

l10n (po-debconf, website)

wip

enrico, madamezou, laura

the l10n bot can be adapted (will need coding skills, here's the repo containing it)

l10n (manuals, documentation)

to be done

scanning SVN repo logs for the debian-doc group (here the repo)

l10n (ddtp)

to be done

maintainers of the web interface (ddtss) should have logs of submissions, it should be possible to adapt them (will need coding skills)

l10n (installer)

to be done

ask debian-boot (may be possible to use the d-i repo, but then we'd have also other contributors to d-i, not only translators. Also, sometime the person translating and the one committing are not the same

voters

to be done

Contact points: http://www.debian.org/intro/organization as project secretary. This will be one step in having contributors.debian.org replace the current database used for MIA tracking.

Resources