 | This page is currently inactive and is retained for historical reference. Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the village pump. It was last substantively updated in April 2011. |
Some notes about redesigning the database reports project.
Goals edit
- allow on-wiki localization of report description text and table headers
- need to be sure that localization doesn't break "data as of" magic (or that magic needs to be re-implemented)
- this means better abstraction in the code and some template magic, presumably
- allow on-wiki customization of link formatting and output (appending edit/hist/etc. links); this is already somewhat done with {{dbr link}}
- shared functions in a dbr module
- calculate_replag()
- post_results() — for single pages
- post_paginated_results() — for paginated results
- switch to use cronsub — svick has already started on this
- licensing
- strongly in favor of making all of this PD; not enough creativity in any of this anyway
- single AUTHORS file
- clean up shebang in the files to use generic Python instead of 2.5?
- switch to a multi-maintainer project/tool on the Toolserver
- people who should have access:
- svick
- mzmcbride
- dispenser
- bjweeks
- tim1357
- need to pick a name, "reports" is already taken
- people who should have access: