Hall of Fame plans for the O cycle
What needs to be done with the Django rewrite of hall-of-
Blueprint information
- Status:
- Started
- Approver:
- Kate Stewart
- Priority:
- Undefined
- Drafter:
- Hall of Fame Developers
- Direction:
- Approved
- Assignee:
- Hall of Fame Developers
- Definition:
- Approved
- Series goal:
- Accepted for oneiric
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- Chris Johnston
- Completed by
Whiteboard
The blueprint for work done on the Hall of Fame in the Natty cycle:
https:/
Some features have already been implemented in the linked branch. The current state of the data models is:
http://
According to Bilal, the code base should be written like this (needs discussion at UDS session for any changes/
* The hall_of_fame django app will be responsible for the front-end as well as gathering and displaying all information from other apps in the same project.
* Each Data Source will be implemented as a separate Django app, having its own models, etc. There will be a function in the hall_of_fame app which will be run regularly by cron and will call the update() function in every data source app. The update() function would then collect/prepare its data and dump in its DB table, to be picked up by hall_of_fame later.
* To ease transition from the old hall-of-fame, we'll also implement a legacy data source app. This app would have a list of python scripts which would fetch and return data in the form of a CSV file. The 'legacy data store' app would then put it in a DB to be later fetched by hall_of_fame.
Work items:
[hall-of-fame-devs] Test new code: POSTPONED
[chrisjohnston] Create deployment process and document instructions: POSTPONED
[chrisjohnston] Deploy HoF: POSTPONED
[bilalakhtar] everything else (Code code code!): INPROGRESS
[daker] Help with CSS: TODO
Work Items
Dependency tree
* Blueprints in grey have been implemented.
