Differences between revisions 1 and 14 (spanning 13 versions)
Revision 1 as of 2013-09-15 15:41:15
Size: 1064
Editor: EnricoZini
Comment: Initial todo list
Revision 14 as of 2013-10-28 19:57:11
Size: 2065
Editor: EnricoZini
Comment: Removed controversial item
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

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.
Line 7: 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]] instead. 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 12: Line 16:
Create an interface to add new data sources Details for a person, listing the contribution periods for each data source and contribution type, and all the associated identifiers.
Line 14: Line 18:
Create a POST interface to submit data from a data source `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 `git.debian.org:~enrico/get-webteam-contributors`
----
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)
Line 19: Line 34:
 * [[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]]

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.

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.

TODO list items


Details for a person, listing the contribution periods for each data source and contribution type, and all the associated identifiers.


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 git.debian.org:~enrico/get-webteam-contributors


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)

Resources