Version 14 (modified by 12 years ago) ( diff ) | ,
---|
Sahana Internship Program - 2012
Table of Contents
Software Development Interns
Objectives
- Supporting deployments of Sahana Eden
- To improve the accuracy of Sahana Eden Documentation and ensure it is up to date
- To increase the reliable of the Sahana Eden software through resolving bugs and automated tests
- Tasks (Preliminary List)
Tasks
Unassigned List:
- Documentation of Project Module
- Implement Schools Module
- Write a Automated Selenium Test Scripts for a Module (or 3-4 Test Scripts), and make an improvement to the automated test framework
- Fix a Difficult Bug from the Trac
- Take on a small Project, like the NCSU ones
- Refactor some of the code (including writing tests to ensure that the refactorization is correct)
- Review the code for “@ToDo” and either do these - or log these as tickets
- Port the Give2LA theme to the current Sahana Eden template framework
- Participate in a Sahanathon
- Review Wiki Projects to ensure that all are current
- Port the Give2LA theme to the current Sahana Eden template framework
- Review the CSS
- Eliminate un-needed CSS
- Better sort it
- Review the Themes to eliminate duplicate CSS between themes (Fran - thoughts?)
- Review the Automated Test Suite
- Ensure that any new tests completed during GCI are included in the test suite.
- Based on this task: http://eden.sahanafoundation.org/wiki/Contribute/QA#CreateAnAutomatedTestsforaTestScriptsfromtheSahanaEdenTestsSpreadsheet and the spreadsheet it links to, make a list of the tests which still need to be automated.
- Document the Project Module - include a description of ALL the different settings
- Write up Deployment Page for Sahana Sunflower (This will be the basis for tasks throughout your internship)
- http://eden.sahanafoundation.org/wiki/Event/2012/Sahanathon
- Create http://eden.sahanafoundation.org/wiki/Deployments/Sunflower
- Using Sahana as a Project Management / Bug Ticketing tool
- “SSF” template - http://eden.sahanafoundation.org/wiki/DeveloperGuidelines/Templates
- Could copy from the “AidIQ” template that AidIQ uses: https://github.com/flavour/aidiq
- Manage Improvements to PM Tool / Sunflower
- Get outstanding tasks from existing Sunflower site
- Review Permissions
- Settings to have new tasks automatically assigned to specific people (based on people for project / activity?)
- Different types of tasks
- Filter lists for different users
- Users can only see
- Make it simpler to log bugs
- http://eden.sahanafoundation.org/ticket/1307
- Less fields
- No login required - but allow user to specify who’s login it in a field
- Add a default link to log a bug in Sunflower - which copies the current URL to the “Source” field
- Log a bug when an error is encountered
- If not already logged for this bug
- Ability to “vote” on tasks
Interns
Somay Jain
Mentor: Michael Howden
- December 2012
- Run the Automated Test Suite (Selenium, Smoke, Roles) - http://eden.sahanafoundation.org/wiki/DeveloperGuidelines/Testing
- Improve documentation on setting up testing environment.
- Fix 2 Bugs from Trac
- Review the Automated Test Suite
- Ensure that any new tests completed during GCI are included in the test suite.
- Based on this task: http://eden.sahanafoundation.org/wiki/Contribute/QA#CreateAnAutomatedTestsforaTestScriptsfromtheSahanaEdenTestsSpreadsheet and the spreadsheet it links to, make a list of the tests which still need to be automated.
- January 2013
- Review the Automated Test Suite
- Fix broken tests
- Document Automated Test Cases
- Document Existing Tests
- Identify & Document Missing Tests - look at bugs which have been reported recently - would these have been captured by the test cases
- Document process for writing manual test cases
- Document the Project Module
- February 2013
- Review Sahana Eden Tests document. It has 2 purposes:
- 1. Record what tests have been automated - and which templates they apply to.
- 2. Be a place people can document manual tests
- Perhaps these 2 purposes should be more separate. Currently the "Test Script" sheet tries to fulfill both of these needs. Maybe we need a different sheet for each purpose.
- Make Sahana Eden Tests document more accessible. Write down instructions for how they can be used. Share these instructions with the community to get feedback.
- Run the Selenium & Smoke tests in the default, DRRPP, SandyRelief templates. Identify any errors. We will probably need a way to define which Selenium tests can be run for which templates.
- Review Sahana Eden Tests document. It has 2 purposes:
- March 2013
- The CI Server is still showing 2 failed Selenium tests and 6 failed smoke tests in the CI email. I would also like the smoke test to accurately report the number of tests run & failed. As well as if it fails.
- Create a config.py file for the SSF template based on the settings in https://github.com/flavour/ssf/blob/master/deployment-templates/models/000_config.py. Compare this to the “AidIQ” template that AidIQ uses: https://github.com/flavour/aidiq/blob/master/private/templates/AidIQ/config.py - they should have the same settings
- Run the smoke tests on the SSF Template - fix or report the bugs
- Use "Projects" to map deployments (Re-name crud strings using the settings.ui.customize_<resource_name> - see: https://github.com/flavour/eden/blob/master/private/templates/DRRPP/config.py#L171)
- Ensure that Deployments (Projects) and Volunteers are displayed on the map
- Re implement project_task_form_inject (https://github.com/flavour/eden/blob/master/modules/s3db/project.py#L5115) using S3SQLForm See: http://eden.sahanafoundation.org/wiki/S3SQLForm and and example here: https://github.com/flavour/eden/blob/master/private/templates/DRRPP/config.py#L421 - this is a big chunk of work. To ensure that you do this right I would like you to write some automated tests (using the create helper function should work) to check that your changes work.
S.P Mohanty
Mentor: Fran Boon
- December 2012
- Continuous Integration Server
- January 2013
- Continuous Integration Server
- February 2013
- Continuous Integration Server
- March 2013
Ashwyn Sharma
Mentor: Fran Boon
- December 2012
- Sandy Tickets
- January 2013
- Requests Tickets
- February 2013
- Requests Tickets
- March 2013
Communication Intern
Objectives
- Increase the awareness of Sahana
- Ensure that external stakeholder understand:
- The Value of Sahana
- How Sahana Can be used
Tasks
Preliminary List:
- Review the Article on Sahana Deployments on the Website, Wiki & Book. Ensure that they are the same and updated
- Mark Prutsalis: the website page has been updated, but it is not a comprehensive list - only highlights.
- Mark Prutsalis: the eden wiki and main ssf wiki have differences that need to be reconciled
[we should probably figure out which pages to deprecate entirely and where to keep a master repository of all Sahana deployments, but this is not a starting intern task]
- Review Wiki - ensure that the navigation flows,index pages have a full list of links and out-of-date pages are updated/removed
- Review Blog
- Update my (Michael) photo on the blog
- Blog on EUROSHA project in Kenya (every two weeks); include photos, etc. (Marine)
- Write up project pages on website (EUROSHA, IFRC, Occupy Sandy, Give2LA, ADPC) (Marine)
- Participate (& Publicize) in a Sahanathon
- Develop a Social Media Strategy
- Setting up a Sahana Software Foundation Mailing list (Not a discussion list - just for announcements eg MailChimp)
- Update Sahana Eden Brochure
- Create a Sahana Software Foundation Brochure
- Design a Sahana Software Foundation Poster to promote our work at conferences/events
- Review, identify static pages that need to be updated, and update them.
- Write Case Studies of Sahana’s use for addition to web site (above - project pages)
- Arrange Community Call - send reminders - invite special guests
- Coordinate Communications from Interns - write up/edit a monthly reports on software development interns for community / blog
- Generate Demo data for demo site
- Blog post on GCI
Interns
Esteve Giraud
Mentor: Leslie Hawthorn
- December 2012
- Blogs about Internship Program (Serie of 8 articles: introduction, 1 x 6 intern, conclusion)
- January 2013
- Post on occupy Sandy, based on:
- Devin’s presentation on during the community call (12/12/12) (See Notes)
- Document Blog Post Process
- Post on occupy Sandy, based on:
- February 2013
- March 2013
Marine Louvigny
Mentor: Mark Prutsalis
- December 2012
- Blog about EUROSHA project
- January 2013
- Blog on IFRC/RMS
- February 2013
- Assist w/ organizing the community call for Feb
- March 2013
Note:
See TracWiki
for help on using the wiki.