| 13 | | Branches can be [wiki:gsocguidelines hosted] publically |
| 14 | | |
| 15 | | ---- |
| 16 | | == Suggestions for Student Applications == |
| 17 | | * When thinking about the goals within you project, consider (These do NOT need to be included in your application, but you should acknowledge them in your goals and timeline): |
| 18 | | * Complete Specification Requirements (how can you code it, if you don't know what "it" is) |
| 19 | | * User Stories, wire-frames, flow-charts |
| 20 | | * Testing (If you haven't tested it - it doesn't work) |
| 21 | | * Documentation - for maintenance, for developers (if it is framework functionality which will be re-used) and for users (if the code isn't documented - it's not finsihed) |
| 22 | | * In terms of functionality goals, try to express them in terms of what the user will be able to do. |
| 23 | | * Don't be afraid to ask questions to the mentors for the projects. |
| 24 | | |
| 25 | | == Project Ideas == |
| 26 | | |
| 27 | | Here is a place to start collecting thoughts and ideas for potential projects which could be submitted as part of Google Summer (or Winter - depending on you hemispherial orientation) of Code (GSoC) 2010. |
| 28 | | [[BR]] |
| 29 | | Students are welcome to submit their own project ideas to, although it would be a good idea to share the idea with the community first (via the [http://groups.google.com/group/sahana-eden Mailing List] or IRC: #sahana-eden) to check the viability of it and help to develop it.[[BR]] |
| 30 | | Many of the ideas listed on http://wiki.sahanafoundation.org/doku.php/dev:sahana_gsoc10_ideas could also be implemented in Sahana Eden. [[BR]] |
| 31 | | Finally, just because there are students or mentors listed for a project already doesn't mean that you can't apply. All applications will be judged equally on their merit. |
| 32 | | |
| 33 | | == Synchronization == |
| 34 | | === Description === |
| 35 | | Sharing data between separate instances of Sahana. This might include such functionality as: |
| 36 | | * Automated syncing |
| 37 | | * Syncing via flash drive |
| 38 | | * Creating rule to avoid conflicts |
| 39 | | * Creating user friendly interface to resolve conflict |
| 40 | | * Allowing an instance to either access a local DB or server DB depending on the connection |
| 41 | | * Upgrading a local instance at the time of syncing (could this also be done if syncing by flashdrive?) |
| 42 | | * Cleaning data and removing duplicate entries between versions. |
| 43 | | |
| 44 | | === Appeal === |
| 45 | | * Would allow Sahana to be used in environments without reliable internet. |
| 46 | | |
| 47 | | === Blue Prints === |
| 48 | | [wiki:BluePrintSynchronisation] |
| 49 | | |
| 50 | | === Interested Students === |
| 51 | | Amer Tahir - amertahir (at) gmail (dot) com |
| 52 | | |
| 53 | | === Interested Mentors === |
| 54 | | - Dominic König - dominic (at) nursix (dot) org |
| 55 | | - Michael Howden* - michael (dot) howden (at) gmail (dot) com |
| 56 | | |
| 57 | | == Survey Tool == |
| 58 | | === Description === |
| 59 | | A tool to allow non-technical users to generate custom surveys and: |
| 60 | | * Print the surveys and read the results through Optical Character Recognition (OCR) |
| 61 | | * Allow the survey to be completed via SMS, or on an iPhone, Android, iPad, Abacus |
| 62 | | * Generate pretty graphs & reports |
| 63 | | * Perform analysis on the survey data (How's your Statistics?) |
| 64 | | * Link survey results to maps |
| 65 | | * Data visualization |
| 66 | | * integration with SMS for SMS Surveys |
| 67 | | |
| 68 | | http://groups.google.com/group/GlobalWASHIMTools shows an example of a generic survey tool design for the Global WASH (Water Sanitation and Health) cluster (UNICEF, IR, Oxfam). |
| 69 | | |
| 70 | | === Appeal === |
| 71 | | * In the recovery period after disasters and crisis's, organizations need to collect information about affected people to plan activities better and to assess the impact of those activities. Surveys are also important prior to disasters to assess to vulnerability of populations and help them to better respond to hazards. |
| 72 | | * This could involve playing with a bunch of cool technologies. |
| 73 | | === Blue Prints === |
| 74 | | * [wiki:BluePrintOCR] |
| 75 | | * [wiki:BluePrintReporting] |
| 76 | | * [wiki:BluePrintSurveyTool] |
| 77 | | === Interested Students === |
| 78 | | (there could be more than one project here) [[BR]] |
| 79 | | Robert O'Connor -- [http://robbyoconnor.blogspot.com blog] - robby DOT oconnor AT gmail DOT com - IRC Nicks: robbyoconnor, r0bby[[BR]] |
| 80 | | === Interested Mentors === |
| 81 | | Michael Howden* (Focused on the core functionality)[[BR]] |
| 82 | | Praneeth Bodduluri (Focused on the OCR) |
| 83 | | |
| 84 | | == GIS == |
| 85 | | === Description === |
| 86 | | If you're happy to spend the 5K you get from google on a UAV - the sky's the limit. |
| 87 | | [[BR]] |
| 88 | | Even if not there's still heaps of opportunities: |
| 89 | | * Color coded maps according to Geo-data (threats, needs, etc) |
| 90 | | * Placing variable sized markers on the map in proportion to data (number of people in camp, number of families needing food) |
| 91 | | * Tracking people ( John Smith was registered at Camp A, then collected food at Camp B, then volunteers at Site C), or Items (The shipment of Tarpaulins moved from site C to site D, where it was split, and then half of them have been distributed from site E) |
| 92 | | * Having a playable timeline slider (like [http://haiti.ushahidi.com/main]) |
| 93 | | * Integrating Walking Papers ([http://walking-papers.org/]) functionality into Sahana |
| 94 | | === Appeal === |
| 95 | | * Maps are where it's at |
| 96 | | === Blue Prints === |
| 97 | | [wiki:BluePrintGeographicInformationSystems] |
| 98 | | === Interested Students === |
| 99 | | |
| 100 | | Douglas Soares de Andrade (dsa) - dsandrade at gmail.com |
| 101 | | |
| 102 | | Anil Kumar M - anil(dot)kumar(dot)848(at)gmail(dot)com IRC - mak89k |
| 103 | | |
| 104 | | Zubair Assad - zubairassad89 [at] gmail [dot] com ; IRC: assad |
| 105 | | === Interested Mentors === |
| 106 | | |
| 107 | | Fran Boon (flavour) |
| 108 | | == Importing Tool == |
| 109 | | === Description === |
| 110 | | A generic importing tool, which allowed data to be imported from various sources automatically. The data could be parsed and fitted into our data model, or it may just be added to a news feed aggregator. This project could include: |
| 111 | | * Importing from PDF, XLS, HTML, Ushahidi, new feeds, incoming SMS |
| 112 | | * A User friendly interface to match fields to parse the data |
| 113 | | * Importing from "flat" tables to linked tables |
| 114 | | * Methods of automatically (or with a user friendly interface) cleaning data |
| 115 | | === Appeal === |
| 116 | | * The data is out there, we need it in here. |
| 117 | | * A large amount of Disaster Information Management is still done using Excel. To get people to start using Sahana, we need to give them the option of easily migrating all of that excel data. |
| 118 | | === Blue Prints === |
| 119 | | * [wiki:SpreadsheetImporter] |
| 120 | | * [wiki:BluePrintImporter] |
| 121 | | === Interested Students === |
| 122 | | Nitin Rastogi (IRC nick - codestasher) |
| 123 | | |
| 124 | | Shikhar Kohli - shikharkohli(at)gmail(dot)com IRC-shikhark |
| 125 | | === Interested Mentors === |
| 126 | | Michael Howden* |
| 127 | | |
| 128 | | == Dashboard/Usability == |
| 129 | | === Description === |
| 130 | | Create a dashboards with a slick interface to make : |
| 131 | | * Integrate an electronic whiteboard feature with a Wii remote do display and manipulate information (eg. stock in warehouse, lists of requests, lists of people, vehicles) |
| 132 | | === Appeal === |
| 133 | | * Whiteboards are a highly used tool in disasters for managing information |
| 134 | | === Blue Prints === |
| 135 | | === Interested Students === |
| 136 | | === Interested Mentors === |
| 137 | | Michael Howden* |
| 138 | | |
| 139 | | == Volunteer Management System == |
| 140 | | === Description === |
| 141 | | Volunteer Management and Coordination is the most fundamental component during Disaster Management. It would include, among other essential functions in the current module 'vol', the following: |
| 142 | | * Deployer Interface for customization of requirement from volunteer |
| 143 | | * Volunteer data on Maps with the descriptive placemarks containing Volunteer Information e.g. Resources and the skills |
| 144 | | * Volunteers to be automatically matched to the most appropriate projects based on their proximity to the region and other factors. |
| 145 | | === Appeal === |
| 146 | | * Live data of the location of volunteers would allow immediate dispatch in an organized manner |
| 147 | | * Deployer Interface to elucidate their requirements of volunteer for more customization and effective deployment. |
| 148 | | === Blueprints === |
| 149 | | [wiki:BluePrintVolunteer] |
| 150 | | === Interested Students === |
| 151 | | |
| 152 | | Zubair Assad - zubairassad89 [at] gmail [dot] com ; IRC: assad |
| 153 | | |
| 154 | | Anil Kumar M - anil [dot] kumar [dot] 848 [at] gmail [dot] com ; IRC: mak89k |
| 155 | | |
| 156 | | Shikhar Kohli - shikharkohli [at] gmail [dot] com ; IRC- shikhark |
| 157 | | === Interested Mentors === |
| 158 | | |
| 159 | | |
| 160 | | *Not all 4 - but am flexible. |
| 161 | | |
| 162 | | == Hospital Management System Widget == |
| 163 | | === Description === |
| 164 | | Build a widget (similar to the Google Person Finder widget) for reporting hospital status information directly into the Hospital Management System (HMS). This needs to be EDXL-HAVE and EDXL-DE compliant. Best to dump the data into a table for validation before it is added to the main registry. |
| 165 | | === Appeal === |
| 166 | | This will make Sahana more ready to deploy in future disasters and to become the main registry for capturing hospital availability and capacity data. |
| 167 | | === Interested Mentors === |
| 168 | | Mark Prutsalis |
| 169 | | === Blueprints === |
| 170 | | === Interested Student === |
| 171 | | |
| 172 | | |
| 173 | | [[BR]] |
| 174 | | [[BR]] |
| 175 | | == HTML/JS front-end for S3XRC == |
| 176 | | === Description === |
| 177 | | Create an HTML and JS based frontend for S3XRC REST backend. Provide RAD way of writing reusable UI that can represent data coming from S3XRC (compound results). Provide alternatives to SQLFORM of web2py, which can suitably generate and handle forms based on compound resources. |
| 178 | | === Appeal === |
| 179 | | * This will enable Sahana Eden to show results of complex SQL queries in the front-end. |
| 180 | | * A more responsive jQuery/ExtJS based UI that would change less, and actively load data through AJAX. |
| 181 | | * Will enable developers quickly prototype interfaces. |
| 182 | | === Interested Mentors === |
| 183 | | [[BR]] |
| 184 | | |
| 185 | | === Blueprints === |
| 186 | | * [wiki:S3XRC_v2][[BR]] |
| 187 | | * [wiki:S3XRC] |
| 188 | | === Interested Student === |
| 189 | | Abhishek Mishra ( ideamonk at gmail.com ) [http://blog.ideamonk.in blog] [http://groups.google.com/group/sahanapy/browse_thread/thread/e88638760031ab96?hl=en discussion] |
| | 12 | Branches are [wiki:gsocguidelines hosted] publically |
