Hermes Tasks
From openSUSE
(Difference between revisions)
| Revision as of 09:37, 27 May 2009 Matejcik (Talk | contribs) Unit tests � Previous diff |
Revision as of 09:38, 27 May 2009 Jkupec (Talk | contribs) User management Next diff → |
||
| Line 2: | Line 2: | ||
| == User management == | == User management == | ||
| - | + | (locilka, jkupec) | |
| * Implement user UI to edit user data | * Implement user UI to edit user data | ||
| * Implement admin UI to set the admin bit | * Implement admin UI to set the admin bit | ||
Revision as of 09:38, 27 May 2009
This is a list of tasks for implementation in the Hermes web app (Starship).
Contents |
User management
(locilka, jkupec)
- Implement user UI to edit user data
- Implement admin UI to set the admin bit
- Admin UI to see other user's subscriptions
Port herminator to Rails
- Implement HTTP API to receive notifications and write them to the notifications table
- Implement admin UI to edit notification descriptions
- Implement authentication for the HTTP API and the admin UI
- Implement access control to define which user is able to create new notification types
- Show statistics about business of system
Notification Online reader
- Make /messages cool
- Only show unread messages by default
- Implement paging
- Implement searching in messages
- Don't show messages which are obsoleted by other messages
Unit tests
- Write unit tests for the models
- Write functional tests for the controllers
- Check test coverage with rcov
(jmatejek, mkudlvasr)
Admin UI
- Implement a view to see notifications which aren't processed yet
- Implement an editor for templates

