| #summary Project Documentation for Social Features for Melange(GSoC2010) | |
| #labels Phase-Design,Contents-Draft,Importance-Details | |
| <wiki:toc max_depth="3" /> | |
| = Introduction = | |
| This document will be used to documents the progress and details of the Social Features (GSoC 2010) project for Melange. | |
| = Meetings and Agendas = | |
| == Friday April 30, 2010 13:30:00 in UTC == | |
| ===Meeting Logs=== | |
| Meeting start: http://www.thousandparsec.net/~irc/logm/%23melange.2010-04-30.log.html#t2010-04-30T13:30:05 | |
| Meeting End: http://www.thousandparsec.net/~irc/logm/%23melange.2010-04-30.log.html#t2010-04-30T14:19:13 | |
| ===Meeting Notes=== | |
| Location: #melange on freenode | |
| Time: 13:30:00 Friday April 30, 2010 in UTC | |
| Chaired by: Madhusudan C.S | |
| Notes taken by: Savitha R | |
| * A general overview of the project design was discussed. | |
| * Users should be able to view fellow GSoC students/mentors/admin by (i) geographic location (perhaps like a global map) (ii) by organization attached to (iii) by type of work/projects they are doing (iv) a complete list of all users in the program. | |
| * Users should be able to find other users using the above categories and then further have the option of finding out more information by clicking to view their personal GSoC user pages. | |
| * Privacy & Visibility issues: Users might need to have the option to keep their location and personal information private. In their personal user pages they may or may not choose to share their personal profile. However, they can share information about their projects such as progress, issues and other information related to the project. Further discussion on the specific details is required. | |
| * In addition to finding fellow users by location, users can also choose to view events/calendars by selecting to view the happenings in certain locations only. In this case, the location will dictate the calendar to be displayed. | |
| * Tips on getting familiar with the code and documentation. | |
| * Select or get assigned to a simple patch/issue. Fix and submit the patch. | |
| * Homework assignments during community bonding period to get familiar with Melange code base. | |
| ===Next Meeting=== | |
| Location: #melange on freenode | |
| Time: 13:30:00 Wednesday May 5, 2010 in UTC | |
| Attendees: C.S.Madhusudan, Savitha | |
| Agenda: | |
| * Detailed Project requirements | |
| * Design and Implementation details of project | |
| * Discuss and assigning of patch/bug-fixing home works to be taken up. | |
| == Wednesday May 5, 2010 13:30:00 in UTC == | |
| ===Meeting Logs=== | |
| Meeting start: http://www.thousandparsec.net/~irc/logm/%23melange.2010-05-05.log.html#t2010-05-05T13:30:33 | |
| Meeting End: http://www.thousandparsec.net/~irc/logm/%23melange.2010-05-05.log.html#t2010-05-05T15:19:58 | |
| ===Meeting Notes=== | |
| Location: #melange on freenode | |
| Time: 13:30:00 Wednesday May 5, 2010 in UTC | |
| Chaired by: Madhusudan C.S | |
| Notes taken by: Savitha R | |
| * General discussion on version control. | |
| * Cloning project. - Done | |
| * Learn and understand mercurial version control system as well as commands etc. How to make changes, submit patches, push changes etc. | |
| * Fix and submit a patch a.s.a.p. for the issue no. 890 bug | |
| * APIs to be used – Google Calendar API, Maps API, CalVi UI library, GeoModel for filtering in maps, Google AJAX APIs, default GMAPs UI. | |
| * Project features in detail - Maps | |
| * Global map indicating GSoC students/mentors/etc. and events occurring at specific locations. | |
| * Filtering data displayed on global map using different categories such as | |
| (i)show all GSoC students from specific location | |
| (ii)show all students from specific organization | |
| (iii) show all events organized by program | |
| (iv) show all events for a specific organization | |
| (v) show all events between given date range | |
| (vi) show all students based on the work they are doing (e.g all students working with C/C++ project tags) | |
| issue: have to check app engine quota restrictions | |
| * Maps can be used to display student items or event items with any combination of the above filters. | |
| * UI – An AJAX-based UI which shows the map and a section for users to type in their filtering options, as they type input, map display gets updated dynamically. When users mouse over and click indicated points on the map, there will be a pop-out widget providing more information. If a user scrolls over and clicks on a GSoC meet up event at Singapore then a small widget will pop out showing the details such as time, venue and info about the event. | |
| * Project features in detail – Calendars | |
| * Other than maps view, there will be calendar-only display, to just view events. | |
| * Program calendar and their own organization calendar will be shown in this view. | |
| * If organization admins choose to make their org calendar “public”, this can also be viewed in the calendar display. | |
| * Events can be added by calendar owners only, such as org admins and program admins. Other wishing to share events, can submit a simple form with event details, which calendar owners can approve and publish on their calendar. | |
| * Display-only UI as users will not be allowed to edit calendar events without authorization. | |
| * Pop-out widget like In the maps, with event information and optional Google map view and optional YouTube video embed related to the event. | |
| * Project Features in detail – User pages | |
| * User pages will contain (i)personal profile (ii) picture (iii)project updates (iv) rss widget (iv) (if time permits) twitter widget also! | |
| * UI to be like face book profile pages, with tabs. (i) Profile tab for users to share personal, educational and professional information. (ii) Project tab for users to share info about their project progress, updates and issue. (iii) Other stuff tab where users can add other social widgets such as rss widget for their blog feed. | |
| * Simple forms to be used to get users to fill in profile information etc. Under “Project” tab users can post using a text field which takes in “html”. | |
| * Discussion on resolving issue 890 and submitting patch this weekend. Posting weekly updates to dev blog and submit patches by Friday night (compulsory!). | |
| * Todo List for Savitha | |
| * Keep updating wiki with project design, workflows and formalized implementation details over the week. | |
| * Post on Dev Blog this weeks’ update. | |
| * Fix issue 890 and submit patch. | |
| = Specification & Requirements = | |
| The detailed project specification will be added and updated here. | |
| = Timeline = | |
| The tentative project timeline will be added here. | |
| = Project Design and Implementation = | |
| The software design and implementation details will be added here. |