Project ideas for GSOC 2011: Difference between revisions
From LimeSurvey Manual
No edit summary |
No edit summary |
||
| Line 54: | Line 54: | ||
If you fulfill the requirements above the difficulty in this task is to gradually modernize an application with a modern coding approach while resisting the natural urge to rewrite everything at once. Our mantra to modernizing the application is that the framework is just laying the new fundaments while the fance walls can be built later. So we lay the fundament first and make it stable, then we build new walls (See also [[LimeSurvey roadmap|the LimeSurvey roadmp]] ) | If you fulfill the requirements above the difficulty in this task is to gradually modernize an application with a modern coding approach while resisting the natural urge to rewrite everything at once. Our mantra to modernizing the application is that the framework is just laying the new fundaments while the fance walls can be built later. So we lay the fundament first and make it stable, then we build new walls (See also [[LimeSurvey roadmap|the LimeSurvey roadmp]] ) | ||
'''Probable | '''Probable mentors''' | ||
Carsten Schmitz (c_schmitz) | Carsten Schmitz (c_schmitz) | ||
| Line 66: | Line 66: | ||
==Port the LimeSurvey backend (administration) to CodeIgniter== | ==Port the LimeSurvey backend (administration) to CodeIgniter== | ||
LimeSurvey is still written using old procedural code. We want to take the next step into the future and use a MVC-framework name CodeIgniter and port the whole application to this new framework. However | LimeSurvey is still written using old procedural code. We want to take the next step into the future and use a MVC-framework name CodeIgniter and port the whole application to this new framework. However porting the whole application is too much for one student. That is why we will split the task into smaller ones. This particular task deals with porting the backend of LimeSurvey to CodeIgniter - this means all the parts that can be seen by an administration user. | ||
During the rewrite you will be prompted also to encapsulate certain functions to objects where easily doable and it makes sense - we do not want you to rewrite everything. Since you are only working on a certain part of LimeSurvey and | During the rewrite you will be prompted also to encapsulate certain functions to objects where easily doable and it makes sense - we do not want you to rewrite everything. Since you are only working on a certain part of LimeSurvey and another student will port the front-end (=administration) of LimeSurvey you will be required to coordinate your coding with the other student. | ||
'''Skills''' | '''Skills''' | ||
| Line 79: | Line 76: | ||
'''Difficulty''' | '''Difficulty''' | ||
If you fulfill the requirements above the difficulty in this task is to gradually modernize an application with a modern coding approach while resisting the natural urge to rewrite everything at once. Our mantra to modernizing the application is that the framework is just laying the new | If you fulfill the requirements above the difficulty in this task is to gradually modernize an application with a modern coding approach while resisting the natural urge to rewrite everything at once. Our mantra to modernizing the application is that the framework is just laying the new foundation while the fancy walls can be built later. So we lay the foundation first and make it stable (your task in the administration), then we build new walls (See also [[LimeSurvey roadmap|the LimeSurvey roadmp]] ) | ||
'''Probable | '''Probable mentors''' | ||
Carsten Schmitz (c_schmitz) | Carsten Schmitz (c_schmitz) | ||
Revision as of 21:48, 1 March 2011
Welcome
Welcome Google Summer of Code Student aspirants (:razz:)
This page lists project ideas developed by the LimeSurvey Community. These tend to be areas that will get the most support as projects since they have been developed by people who know the project and what it needs the most. However, if you have your own idea for a project discuss your awesome idea with us in our forums, mailing list or at #limesurvey on irc.freenode.net. Then submit your proposal. Good Luck (:biggrin:)
Project ideas
Central participants database (User panel)
Develop a central 'participants' database for LimeSurvey that can be used as a central registry of participants between surveys. The database should allow
- adding/removing of users along with flexible data to store related information for users
- simple copying of user-information to individual survey token tables
- ability to link user entries with survey responses if the linked survey was not unanimous (UUIDs?)
- ability for survey participants to register in the panel
- ability to update the flexible user data from collected results
- a 'do not email' blacklist to allow people to automatically unsubscribe
- data ownership features for multi-user systems - allow different LimeSurvey users to 'own' different participants
Skills
Database and PHP coding
Difficulty
Moderate to high - the coding would be relatively simple, but will entail complex relationships
Probable mentors
Jason Cleeland
Port the LimeSurvey front-end to CodeIgniter
LimeSurvey is still written using old procedural code. We want to take the next step into the future and use a MVC-framework name CodeIgniter and port the whole application to this new framework. However proting the whole application is too much for one students. That is why we will split the task into smaller ones. This particular task deals with porting the front-end of LimeSurvey to CodeIgniter - this means all the parts that can be seen by the average survey participant:
- Survey taking
- Public statistics
- Central landing page
During the rewrite you will be prompted also to encapsulate certain functions to objects where easily doable and it makes sense - we do not want you to rewrite everything. Since you are only working on a certain part of LimeSurvey and other students will port the back-end (=administration) of LimeSurvey you will be required to coordinate your coding with the other students.
Skills
OOP experience in PHP and experience with a PHP framework like CakePHP or CodeIgniter are definately a must. You should get busy with LimeSurvey as early as possible. Students can raise their chance to get accepted by showing off according knowledge about LimeSurvey inner workings.
Difficulty
If you fulfill the requirements above the difficulty in this task is to gradually modernize an application with a modern coding approach while resisting the natural urge to rewrite everything at once. Our mantra to modernizing the application is that the framework is just laying the new fundaments while the fance walls can be built later. So we lay the fundament first and make it stable, then we build new walls (See also the LimeSurvey roadmp )
Probable mentors
Carsten Schmitz (c_schmitz)
Thibault le Meur (tlemeur)
Port the LimeSurvey backend (administration) to CodeIgniter
LimeSurvey is still written using old procedural code. We want to take the next step into the future and use a MVC-framework name CodeIgniter and port the whole application to this new framework. However porting the whole application is too much for one student. That is why we will split the task into smaller ones. This particular task deals with porting the backend of LimeSurvey to CodeIgniter - this means all the parts that can be seen by an administration user.
During the rewrite you will be prompted also to encapsulate certain functions to objects where easily doable and it makes sense - we do not want you to rewrite everything. Since you are only working on a certain part of LimeSurvey and another student will port the front-end (=administration) of LimeSurvey you will be required to coordinate your coding with the other student.
Skills
OOP experience in PHP and experience with a PHP framework like CakePHP or CodeIgniter are definately a must. You should get busy with LimeSurvey as early as possible. Students can raise their chance to get accepted by showing off according knowledge about LimeSurvey inner workings.
Difficulty
If you fulfill the requirements above the difficulty in this task is to gradually modernize an application with a modern coding approach while resisting the natural urge to rewrite everything at once. Our mantra to modernizing the application is that the framework is just laying the new foundation while the fancy walls can be built later. So we lay the foundation first and make it stable (your task in the administration), then we build new walls (See also the LimeSurvey roadmp )
Probable mentors
Carsten Schmitz (c_schmitz)
Thibault le Meur (tlemeur)
Idea template
Describe the idea here in general terms
Skills
Explain what sort of coding skills would be needed for a student to implement this project
Difficulty
Explain the level of difficulty involved
Probable Mentors
Put your name (and tag) here if you are willing to mentor a student for this idea
More information
Getting started
Check out our 'Get started' page for setting up the development environment, coding standards, and all the other important stuff that you need to know before the real fun begins!
Frequently Asked Questions
Check out our GSoC FAQ page.