Changes between Version 90 and Version 91 of ProjectInformation
- Timestamp:
- 09/30/10 05:41:11 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectInformation
v90 v91 9 9 10 10 == Projects that do not involve programming == 11 11 12 ==== ''Usability'' ==== #Usability 13 12 14 * Role-play being a user: 13 15 * Try it out -- you can use: … … 43 45 44 46 ==== ''Bug verification'' ==== 47 45 48 Some bugs have been left open even though they've been fixed. Others don't have much information. 46 49 * Go through the list of [/report/1 open bugs] and try to reproduce the bug: … … 48 51 * If you can reproduce the bug but the description isn't clear, add better "how to reproduce" instructions. 49 52 * If you can't figure out what the ticket means, add a reply that tells the bug submitter what info would be helpful. 50 ==== ''Current relief efforts (Help out with a current relief effort)'' ====#ReliefEfforts 53 54 ==== ''Current relief efforts (Help out with a current relief effort)'' ==== #ReliefEfforts 55 51 56 Pakistan floods -- see [/Pakistan background information]. 52 57 * Research missing map and location data for PakistanUnionCouncils, part of the [/PakistanUserGuide#LocationsHierarchy GIS location hierarchy]. 53 58 * Do you speak Urdu? Help with [PakistanTranslation translation]. 54 ==== ''Improve installation procedures'' ====#ImproveInstall 59 60 ==== ''Improve installation procedures'' ==== #ImproveInstall 61 55 62 * Step-by-step documentation -- we have been concentrating on Windows & Debian/Ubuntu so other distros are poorly-documented. 56 63 57 64 == Projects for beginning coders, or if new to Python or web services == 65 58 66 ==== ''Bug fixing'' ==== 67 59 68 * Pick from these [/report/18 easy bugs for new Eden developers]. 69 60 70 ==== ''Feature Enhancements'' ==== 71 61 72 * Fix UI issues, add features, provide user-requested enhancements. 62 * You can pick from these [/report/21 feature requests]. 63 * Or talk to the folks at the Codeathon who are [#Usability cataloging issues]. 73 * You can pick from these [/report/21 feature requests]. 74 * Or talk to the folks at the Codeathon who are [#Usability cataloging issues]. 75 64 76 * The landing page for each module is different -- some have descriptive text, others have statistics (a "dashboard"). Each has a different layout of menus. 65 * Are any of these landing pages useful? What would be better? Maybe go straight to a list page? Make appropriate changes. 66 * Is there a common sort of menu that would be useful? 77 * Are any of these landing pages useful? What would be better for a typical workflow? 78 * Make appropriate changes. 79 * Is there a common sort of menu that would be useful? 80 67 81 ==== ''Geocoding'' ==== 68 A favorite missing feature: Geocoding addresses. There is already a geocoding service supported in Eden, but it's not used when a user adds a location. Your job: 82 83 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: 69 84 * Find the geocoding function. 70 85 * When the user adds a location and enters an address, use the geocoding function to get latitude and longitude. 71 ==== ''Suggestion Box Module'' ==== 72 * http://groups.google.com/group/sahana-eden/browse_thread/thread/bbda1e98b73e1437 86 87 ==== ''Suggestion Box'' ==== 88 89 Here are some potential features for a "suggestion box", roughly in order of priority: 90 * Text data entry form -- just use standard Eden database fields like "timestamp", "authorstamp", and "comments", maybe with a subject field. 91 * Allow defining topics or keywords. Let user choose a topic for their suggestion. Add all module names as an initial list of topics. 92 * Simple search in the body of posts -- match words. 93 * Regexp search. 94 * Allow commenting on (replying to) suggestions -- show comment thread with original post. 95 * Some form of importance rating (e.g. voting up or down). 96 * Original suggestion from: http://groups.google.com/group/sahana-eden/browse_thread/thread/bbda1e98b73e1437 97 73 98 ==== ''!SysAdmin'' ==== 99 74 100 * DeveloperGuidelinesReleaseProcess#ExportApplication 75 101 * PakistanDeploymentCycle#SysadminToDo … … 77 103 78 104 == Projects for more experienced coders == 105 79 106 Some things to keep in mind when planning new modules or major features: 80 107 * Consider what other FOSS tools exist, that could be installed alongside Eden. … … 82 109 83 110 ==== ''Test automation'' ==== 111 84 112 * Figure out how to do unit tests against a web application. 85 113 * Write unit and functional tests. 86 114 * DeveloperGuidelinesTesting#FunctionalTests 87 ==== ''Tweet or SMS parsing -- allow users to provide info via tweets or SMS messages'' ====#Tweet 115 116 ==== ''Tweet or SMS parsing -- allow users to provide info via tweets or SMS messages'' ==== #Tweet 117 88 118 * Parse formatted SMS messages or tweets (e.g. key value pairs). 89 119 * Detect when message interpretation isn't certain and dispatch to a human reader (use existing "task" database, or Job Jar, below!). 90 120 * Create database records from parsed messages. 91 121 * BluePrintMessagingModule#Twitter 92 * BluePrintMessagingModule#Micro-Syntax 93 ==== ''Job Jar -- manage tasks performed on the site, e.g. data entry'' ====#JobJar 122 * BluePrintMessagingModule#Micro-Syntax 123 124 ==== ''Job Jar -- manage tasks performed on the site, e.g. data entry'' ==== #JobJar 125 94 126 * Assign tasks to users or let users select tasks. 95 127 * Track who does what, mark completed. … … 97 129 * Cross-check / verify task, or compare result of two users on same task. 98 130 * Administer tests and training for new workers. 99 ==== ''Mobile photo or video upload'' ====#MobilePhoto 131 132 ==== ''Mobile photo or video upload'' ==== #MobilePhoto 133 100 134 * Design a widget (to be included in an Eden form) that can be used to select images or video, with any needed detection of the type of phone. 101 ==== ''Run Eden on a smart phone'' ====#Mobile 135 136 ==== ''Run Eden on a smart phone'' ==== #Mobile 137 102 138 * See BluePrintMobileClient. 103 139 * Alternate Layout for web view: [wiki:BluePrintCSS#MobileView] 104 140 * Android Application: MobileAndroid 105 141 * Note this [http://gracehopper.org/2010/conference/open-source-track/#session3 GHC session on Android development]! 142 106 143 ==== ''Chat with other logged in users'' ==== #Chat 107 * Provide a chat board through which users can help each other. 144 145 * Provide a chat board through which users can help each other or get help from the system administrator. 108 146 * Perhaps have one chat for each organization or project. 109 147 * Is there existing IRC or other chat software that could be incorporated? 110 ==== ''Refactor and complete the Survey module'' ====#Survey 148 149 ==== ''Refactor and complete the Survey module'' ==== #Survey 150 111 151 The survey module was started during GSoC this summer. The author will be online on freenode #sahana-ghc under the nicknames '''''robbyoconnor''''' or '''''r0bby|android''''' during the Codeathon. 112 152 * Change it so that it uses "components" to relate survey sections to the survey, and questions to the survey sections. 113 * Ideally, the look and feel of the surveys should be modeled after the Rapid Assessment Tool (rat) module (see '''''models/rat.py''''' and '''''controllers/rat.py''''' to get an idea of what needs to happen)153 * Ideally, the look and feel of the surveys should be modeled after the Rapid Assessment Tool (rat) module. (See '''''models/rat.py''''' and '''''controllers/rat.py''''' to get an idea of what needs to happen.) 114 154 * '''Note:''' You will be required to write some supporting code! No way around that, but this is possible! 115 155 * We are aiming to allow non-technical savvy users to create surveys similar to what was done in the rat module.
