Differences between revisions 1 and 9 (spanning 8 versions)
Revision 1 as of 2013-09-15 15:41:15
Size: 1064
Editor: EnricoZini
Comment: Initial todo list
Revision 9 as of 2013-09-30 12:18:10
Size: 2298
Comment:
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 Also show when one started contributing
Line 14: Line 18:
Create a POST interface to submit data from a data source Group contributors by 'until' year, in the contributors list.
Contributors who stopped contributing before this year, go into a 'Contributors until year YYYY' section.
----
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.
----
Data source page (accessible via `Source.get_absolute_url`) which lists source information and a list of contributors.
----
ContributorType page (accessible via `ContributorType.get_absolute_url`) which lists source and contributor type information, and a list of contributors.
----
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.
----
Add to Source a comment field where one can annotate implementation details, such as "the source is implemented on foo.debian.org as script bar run as user baz, scheduled to run via cron every night"
Line 19: Line 38:
 * [[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


Also show when one started contributing


Group contributors by 'until' year, in the contributors list. Contributors who stopped contributing before this year, go into a 'Contributors until year YYYY' section.


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.


Data source page (accessible via Source.get_absolute_url) which lists source information and a list of contributors.


?ContributorType page (accessible via ContributorType.get_absolute_url) which lists source and contributor type information, and a list of contributors.


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.


Add to Source a comment field where one can annotate implementation details, such as "the source is implemented on foo.debian.org as script bar run as user baz, scheduled to run via cron every night"

Resources