Changes between Version 120 and Version 121 of ProjectInformation
- Timestamp:
- 11/17/10 11:56:22 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectInformation
v120 v121 22 22 ''Projects that do not involve programming.'' 23 23 24 === Usability === #Usability24 === Ideas: Usability === 25 25 26 26 * Role-play being a user: … … 32 32 * What features would you want? 33 33 * What do you think the workflow should be? 34 * Improve usability:35 * Find bugs:36 * Try to break it.37 * [BugReportingGuidelines Report bugs].38 34 * Document it: 39 35 * Explore it and document the existing workflow. 40 36 * Develop a how-to guide for users. 41 * Write tooltips (help info) for fields on forms.42 * What's missing?43 * What did you want to do that wasn't available?44 * Where is the workflow inconvenient?45 * [BugReportingGuidelines Request features and suggest improvements].46 37 * Modules that could use some usability improvement: 47 * All of them. Well, ok, try these:38 * All of them. In particular: 48 39 * [http://demo.eden.sahanafoundation.org/eden/gis Mapping] 49 40 * [http://demo.eden.sahanafoundation.org/eden/cr Shelter registry] … … 56 47 * [http://demo.eden.sahanafoundation.org/eden/rat Rapid assessment tool] 57 48 58 === Bug Verification === 59 ''GCI'' 60 Some bugs have been left open even though they've been fixed. Others don't have much information. 61 * Go through the list of [/report/1 open bugs] and try to reproduce the bug: 62 * If the bug is gone, add a reply to the ticket with what you did and "resolve" the bug as "invalid". (The submitter can still reply and reopen the bug if they want.) 63 * If you can reproduce the bug but the description isn't clear, add better "how to reproduce" instructions. 64 * If you can't figure out what the ticket means, add a reply that tells the bug reporter what info would be helpful. 65 66 === Project: Improve installation procedures === 67 ''GCI'' 68 * Step-by-step documentation -- we have been concentrating on Windows & Debian/Ubuntu so other distros are poorly-documented. 49 === Project: Ticket Reporting === 50 ''GCI'' 51 [wiki:BugReportingGuidelines Guidelines] 52 * Bugs - Try to break it! 53 * Usability Enhancements 54 * Additional/clearer help text required. Suggest tooltips (help info) for fields on forms. 55 * Unclear/Inconvenient workflow 56 * What did you want to do that wasn't available? 57 * Suggest Improvements 58 59 === Project: Ticket Verification === 60 ''GCI'' 61 Some tickets have been left open even though they've been fixed. Others don't have much information. 62 * Go through the list of [/report/1 open bugs] and try to reproduce the ticket issue: 63 * If the issue is gone, add a reply to the ticket with what you did and "resolve" the ticket as "invalid". (The submitter can still reply and reopen the bug if they want.) 64 * If you can reproduce the issue but the description isn't clear, add better "how to reproduce" instructions. 65 * If you can't figure out what the ticket means, add a reply that tells the ticket reporter what info would be helpful. 66 67 == Infrastructure Projects == 68 ''Projects that may involved varying degrees of technical skills, but not programming.'' 69 70 === Project: Improve Installation Documentation === 71 ''GCI'' 72 We have been concentrating on Windows & Debian/Ubuntu, but better documentation could be provide for other distributions: 73 * ??? 69 74 70 75 == Basic Coding Projects == 71 76 ''Projects for beginning coders, or if new to Python or web services'' 72 77 73 === = ''Bug fixing'' ====78 === Tickets === 74 79 ''GCI'' 75 80 * Pick from these [/report/18 easy bugs for new Eden developers]. 76 81 77 === = ''Feature Enhancements'' ====82 === Feature Enhancements === 78 83 ''GCI'' 79 84 * Fix UI issues, add features, provide user-requested enhancements. … … 86 91 * Is there a common sort of menu that would be useful? 87 92 88 === = ''Building Assessments'' ====93 === Building Assessments === 89 94 We had a basic Building Assessments tool added to Sahana recently (which is based on the ATC forms), although it was done in a Web2Py style & so didn't get completed & isn't yet merged to Trunk. 90 95 … … 96 101 * https://code.launchpad.net/~flavour/sahana-eden/buildingAssessments 97 102 98 === = ''Geocoding'' ====103 === Geocoding === 99 104 ''GCI'' 100 105 A favorite missing feature is geocoding addresses. There is already a geocoding service supported in Eden, but it's not used when a user adds a location. Your job: … … 102 107 * When the user adds a location and enters an address, use the geocoding function to get latitude and longitude. 103 108 104 === = Misc. GIS/Mapping ==== #MiscGISMapping109 === Ideas: GIS/Mapping === 105 110 These are a number of various GIS/Mapping Tasks: 106 111 * Use the !GeoCoder ({{{geolocate}}} function in {{{controllers/gis.py}}}) to lookup location Lat/Lons … … 124 129 * Map Preview when Lat/Lon set in pr/person/presence (auto or not) 125 130 126 === = ''Suggestion Box'' ====131 === Suggestion Box === 127 132 ''GCI'' 128 133 Here are some potential features for a "suggestion box", roughly in order of priority: … … 135 140 * Original suggestion from: http://groups.google.com/group/sahana-eden/browse_thread/thread/bbda1e98b73e1437 136 141 137 === = ''!SysAdmin'' ====142 === !SysAdmin === 138 143 139 144 * DeveloperGuidelinesReleaseProcess#ExportApplication … … 149 154 150 155 Fuller list of Projects being scoped: BluePrints 151 ==== Misc. GIS/Mapping ==== 156 157 === Ideas: GIS/Mapping === 152 158 These are a number of GIS/Mapping Tasks to be done: 153 159 * Allow Sahana to import Wikipedia locations easily … … 157 163 * Port from Ext-2.2.1 to Ext-3.2.1 158 164 159 === = Framework ====165 === Framework === 160 166 * Provide localisation of jquery.ui.datepicker 161 167 * Means that user profile will need extending to support locales … … 168 174 * e.g. Messaging Users/Groups 169 175 170 ==== ''Test automation'' ==== 171 176 === Test Automation === 172 177 * Figure out how to do unit tests against a web application. 173 178 * Write unit and functional tests. 174 179 * DeveloperGuidelinesTesting#FunctionalTests 175 180 176 ==== ''Tweet or SMS parsing -- allow users to provide info via tweets or SMS messages'' ==== #Tweet 181 === Tweet / SMS Parsing === 182 Allow users to provide info via tweets or SMS messages 177 183 * Parse formatted SMS messages or tweets (e.g. key value pairs). 178 184 * Detect when message interpretation isn't certain and dispatch to a human reader (use existing "task" database, or Job Jar, below!). … … 182 188 * BluePrintMessagingModule#Micro-Syntax 183 189 184 === = Sending Tweets ====190 === Sending Tweets === 185 191 * BluePrintMessagingModule#Twitter 186 192 * [wiki:NCSU#Projectsbeingworkedon NCSU Students] working on this 187 193 188 === = ''Job Jar -- manage tasks performed on the site, e.g. data entry'' ==== #JobJar189 194 === Job Jar === 195 Manage tasks performed on the site, e.g. data entry 190 196 * Assign tasks to users or let users select tasks. 191 197 * Track who does what, mark completed.