Differences between revisions 2 and 36 (spanning 34 versions)
Revision 2 as of 2013-09-15 15:44:18
Size: 1332
Editor: EnricoZini
Comment: More verbose
Revision 36 as of 2014-03-20 13:47:29
Size: 4553
Comment: wiki is working again
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== contributors.debian.org website development == = 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.

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 [[http://bugs.debian.org/nm.debian.org|BTS]].
Line 5: Line 13:
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. Add a nullable display_name field to the User model, and allow users to edit it.
Change User.get_full_name to return display_name as a first choice, falling back to email if it is None.
----
During maintenance, scan names from GECOS / LDAP and add them to missing first/last names in User.
----
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.
----
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.
----
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 7: Line 29:
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. == Desired data sources ==
Line 9: Line 31:
=== TODO list items === {{{#!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 ||
|| http://nm.debian.org/ || done || enrico || - ||
|| spam review || done || formorer, madamezou || ||
|| http://svn.debian.org/ || proof of concept || enrico || ||
|| 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 || to be done || || can be done scanning SVN repo logs ||
|| [[http://bts.debian.org|BTS]] || to be done || || maybe second-hand data via UDD? (will need coding skills) ||
Line 11: Line 49:
----
Create an interface to add new data sources and edit existing ones.
For each source, we also need to edit the various contribution types.
----
Create a POST interface to submit data from a data source. See contributors/importer for the code used to import the data that gets submitted.
The POSTed data needs to contain the auth_token defined in the matching Source record.
}}}
Line 18: Line 51:
''' stuff to add in the table '''
 * nm-site-devel (scanning git log, or the mailing list, should do)
 * L10N:
    * po-debconf, website: via l10n bot (bubulle already replied sending link to the bot's source, need coding people to look at it)
    * manuals, doc: scanning svn repo commits
    * installer: ?
    * wiki: ?
    * ddtss: ask maintainers of the service (waiting for reply)
 * Debian Blends: they have an activity tracker, it can be adapted (ask them)
 
Line 21: 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 23: 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

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.

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.

TODO list

Add a nullable display_name field to the User model, and allow users to edit it. Change User.get_full_name to return display_name as a first choice, falling back to email if it is None.


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


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.


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.


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.

Desired data sources

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

http://nm.debian.org/

done

enrico

-

spam review

done

formorer, madamezou

http://svn.debian.org/

proof of concept

enrico

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

to be done

can be done scanning SVN repo logs

BTS

to be done

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

stuff to add in the table

  • nm-site-devel (scanning git log, or the mailing list, should do)
  • L10N:
    • po-debconf, website: via l10n bot (bubulle already replied sending link to the bot's source, need coding people to look at it)
    • manuals, doc: scanning svn repo commits
    • installer: ?
    • wiki: ?
    • ddtss: ask maintainers of the service (waiting for reply)
  • Debian Blends: they have an activity tracker, it can be adapted (ask them)

Resources