| 10 | | * Provide feedback on an existing Eden module. |
| 11 | | * Role-play being a user: |
| 12 | | * Try it out. |
| 13 | | * What do you expect it to do? |
| 14 | | * What features would you want? |
| 15 | | * What do you think the workflow should be? |
| 16 | | * Improve it: |
| 17 | | * Try to break it. Report bugs. |
| 18 | | * Document the existing workflow. |
| 19 | | * Develop a how-to guide for users. |
| 20 | | * Write tooltips (help info) for fields on forms. |
| 21 | | * Request features. |
| 22 | | * Suggest improvements. |
| 23 | | * How to report bugs, make suggestions, etc.: |
| 24 | | * Request a Trac account. |
| 25 | | * File a ticket [http://eden.sahanafoundation.org/newticket here]. |
| 26 | | * [BugReportingGuidelines Bug reporting guidelines] (aimed at acceptance testing but describes how to classify bugs) |
| 27 | | * Modules that could use some usability improvement: |
| 28 | | * All of them. Well, ok, try these: |
| 29 | | * Mapping |
| 30 | | * Shelter registry |
| 31 | | * Hospital registry |
| 32 | | * Person registry |
| 33 | | * New or unfinished modules that would benefit from feature and workflow suggestions: |
| 34 | | * Logistics |
| 35 | | * Volunteer management |
| 36 | | * Messaging |
| 37 | | * Rapid assessment tool |
| | 9 | ==== Provide feedback on an existing Eden module ==== |
| | 10 | * Role-play being a user: |
| | 11 | * Try it out. |
| | 12 | * What do you expect it to do? |
| | 13 | * What features would you want? |
| | 14 | * What do you think the workflow should be? |
| | 15 | * Improve it: |
| | 16 | * Try to break it. Report bugs. |
| | 17 | * Document the existing workflow. |
| | 18 | * Develop a how-to guide for users. |
| | 19 | * Write tooltips (help info) for fields on forms. |
| | 20 | * Request features. |
| | 21 | * Suggest improvements. |
| | 22 | * How to report bugs, make suggestions, etc.: |
| | 23 | * Request a Trac account. |
| | 24 | * File a ticket [http://eden.sahanafoundation.org/newticket here]. |
| | 25 | * [BugReportingGuidelines Bug reporting guidelines] (aimed at acceptance testing but describes how to classify bugs) |
| | 26 | * Modules that could use some usability improvement: |
| | 27 | * All of them. Well, ok, try these: |
| | 28 | * Mapping |
| | 29 | * Shelter registry |
| | 30 | * Hospital registry |
| | 31 | * Person registry |
| | 32 | * New or unfinished modules that would benefit from feature and workflow suggestions: |
| | 33 | * Logistics |
| | 34 | * Volunteer management |
| | 35 | * Messaging |
| | 36 | * Rapid assessment tool |
| 52 | | == More complex projects for Python (or Web Services) coders == |
| 53 | | * Tweak the Tweet (or SMS) parsing |
| 54 | | * Parse formatted SMS messages or tweets (e.g. key value pairs) |
| 55 | | * Detect when message interpretation isn't certain and dispatch to a human reader (use Job Jar) |
| 56 | | * Create database records from parsed messages |
| | 51 | == Projects for more experienced coders == |
| | 52 | |
| | 53 | * Tweet or SMS parsing -- allow users to provide info via tweets or SMS messages |
| | 54 | * Parse formatted SMS messages or tweets (e.g. key value pairs). |
| | 55 | * Detect when message interpretation isn't certain and dispatch to a human reader (use existing "task" database, or Job Jar, below!). |
| | 56 | * Create database records from parsed messages. |
| 60 | | * Job Jar |
| 61 | | * UI for assigning data entry or similar tasks to users |
| 62 | | * Track who does what, mark completed |
| 63 | | * Admin UI for defining tasks |
| 64 | | * Cross-check / verify task, or compare result of 2 users on same task |
| | 60 | * Job Jar -- manage tasks performed on the site, e.g. data entry |
| | 61 | * Assign tasks to users or let users select tasks. |
| | 62 | * Track who does what, mark completed. |
| | 63 | * Provide administrator UI for defining tasks. |
| | 64 | * Cross-check / verify task, or compare result of two users on same task. |
| | 65 | * Administer tests and training for new workers. |
