LimeSurvey project ideas for Google Code-in 2011
From LimeSurvey Manual
Welcome
Welcome Google Code-in Student aspirants (:razz:)!! Please check if you are an eligible candidate for the GCI program.
This page lists task ideas developed by the LimeSurvey Community. These tend to be areas that will get the most support as tasks since they have been developed by people who know the project and what it needs the most. Good Luck (:biggrin:)
All tasks aim at the 2.1 development version.
How to claim a task
All tasks below will be entered in the Google Code-in task tracker (which is not yet available). You have to be a registered and accepted Google Code-In participant to claim a task.
Task ideas
Idea Template
This is just a template you can use to add your ideas:
Code/Documentation/Outreach/Quality assurance/Training/Research/User interface: Some descriptive task description
Idea posted by: <myname>
Here comes some text describing the current situation and how LimeSurvey will benefit from this task. The description should make clear what this task is about.
Task steps:
- Some steps like...
- Install LimeSurvey or use the online system we provide
- Analyse the problem
- Discuss the issue and your proposed solution with your mentor
- Code/document/translate/... and submit your work
- Discuss the work with your mentor
- Check-in your changes into the limesurvey svn trunk/add it to the wiki/...
Time frame | Skills | Difficulty | Mentor |
X days | some skills the applicants should have | easy/moderate/difficult | mentorname |
Second wave
...add your ideas here...
Create a LimeSurvey glossary
Idea posted by: Mazi
Sometimes you stumble upon a LimeSurvey feature and don't know about any details. Since LimeSurvey offers have quite a wide range of features, having an alphabetical list of keywords like assessments, conditions, label sets, quotas, ... with 2-3 sentences to describe each feature will help a lot. If possible these keywords should be linked to the according manual page.
You won't have to work on this alone. This can be collaborative work meaning you can ask at our forums, on Facebook, out on the streets for help. Create a list and ask others to add missing features.
Task steps:
- Have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey
- Ask your mentor to create a new wiki page
- Create a user accout at www.limesurvey.org. Once done, click on the "documentation" link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.
- Create an alphabetical list of features. Add a feature description of 2-3 sentences and if possible link to the according english manual pages.
- Ask other at our forum (or other places) to add missing features.
- We expect the list to contain at least 25 features. The more the better.
- Discuss the created glossary with your mentor
Time frame | Skills | Difficulty | Mentor |
5 days | wiki editing, writing documentation | moderate | Mazi |
Code: Port the "lost password" feature to Yii
Idea posted by: Mazi
LimeSurvey offers a "forgot password" feature so you can access your Limesurey installation even if you forgot your password. This feature has to be ported to the Yii framework.
Task steps:
- ...
Time frame | Skills | Difficulty | Mentor |
3 days | PHP, MVC, Yii framework | easy | c_schmitz |
Documentation/Translation: (GERMAN) Merge article "Vorlagen / Vorlagen Editor" and "Templates Styles" and add new/missing parts of english article "The template editor"
Idea posted by: vierundzwanzig
The english article "The template editor" has both the description for the template editor as well as the description for template styles. In the german part of the documentation this article is seperated into two articles "Vorlagen / Vorlagen Editor" and "Templates Styles". For the reason of simplicity and unity both articles should be merged together. If the english article "The template editor" has new/missing parts this parts should be translated and added to the new merged article.
Task steps:
- Have a look at the english page at http://docs.limesurvey.org/The+template+editor
- Then have a look at the german page at http://docs.limesurvey.org/Der+Vorlagen+Editor and http://docs.limesurvey.org/Templates+++Styles
- Merge the information from http://docs.limesurvey.org/Templates+++Styles into http://docs.limesurvey.org/Der+Vorlagen+Editor
- Copy the missing parts to a fitting place of http://docs.limesurvey.org/Der+Vorlagen+Editor
- Rewrite the article http://docs.limesurvey.org/Der+Vorlagen+Editor that it sounds acceptable.
- Compare http://docs.limesurvey.org/Der+Vorlagen+Editor with http://docs.limesurvey.org/The+template+editor
- Translate new/missing parts of http://docs.limesurvey.org/The+template+editor into german and add them to http://docs.limesurvey.org/Der+Vorlagen+Editor
- Discuss the article http://docs.limesurvey.org/Der+Vorlagen+Editor with your mentor
Time frame | Skills | Difficulty | Mentor |
3 days | German and English language | easy | Mazi, vierundzwanzig |
Documentation: Update the LimeSurvey 2.0 database layout
Idea posted by: Mazi
The documentation of the LimeSurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.
Task steps:
- Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&structure;=LimeSurvey+development
- Install a subversion client and download LimeSurvey 2.0a (that's the version still based on CodeIgniter) using subversion and install it by running http://<yourserver>/limesurvey/index.php/admin
- Install phpmyadmin: http://www.phpmyadmin.net/home_page/index.php
- Have a look at the current database layout and compare it t the outdated docs.
- Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.
- If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)
- Discuss the work with your mentor
- Add your file at our wiki (Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the "documentation" link on the LimeSurvey main page and navigate to the page you want to update).
Time frame | Skills | Difficulty | Mentor |
2 days | documentation, Excel, Database design | easy/ | Mazi, c_schmitz |
Code: Enable filling out additional token attributes when registering for a survey
Idea posted by: Mazi
When using tokens and enabling public registration, the additionally added token attributes (see Have a look at additional token attributes: http://docs.limesurvey.org/Tokens&structure;=English+Instructions+for+LimeSurvey#User-defined_attribute_fields) can't be filled out at registration. This feature has to be added to the registration screen.
Task steps:
- Install LimeSurvey or use the online system we provide
- Analyse the problem
- Discuss the issue and your proposed solution with your mentor
- Code/document/translate/... and submit your work
- Discuss the work with your mentor
- Check-in your changes into the limesurvey svn trunk/add it to the wiki/...
Time frame | Skills | Difficulty | Mentor |
X days | some skills the applicants should have | easy/moderate/difficult | c_schmitz |
Translation: Update the German version of the english "optional settings" wiki page
Idea posted by: Mazi
The "optional settings" wiki page (http://docs.limesurvey.org/Optional+settings) holds information about LimeSurvey settings for certain parts of the programm that are to be set at the config.php file and are not included at the global settings.
The German version of this page (http://docs.limesurvey.org/tiki-index.php?page=Optionale+Einstellungen) is outdated and needs to be updated based on the english page.
Task steps:
- Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the "documentation" link on the LimeSurvey main page.
- Have a look at the english base page: http://docs.limesurvey.org/tiki-index.php?page=Optional+settings
- Port the document structure (page sections) to the German page (http://docs.limesurvey.org/tiki-index.php?page=Optionale+Einstellungen)
- Check which settings are missing -> add those
- Check which settings are incomplete -> extend those
- Check which settings are not listd at the english version -> delete those
- When you are done, check carefuly if no settings is missing
- If you have any questions about a certain setting, ask it here, your mentor will be notified.
- When you are done, submit your work here (just give the link to the translated page).
Time frame | Skills | Difficulty | Mentor |
3 days | German language, wiki editing | moderate | Mazi, mot |
Translation: Translate the english "optional settings" wiki page to Spanish
Idea posted by: Mazi
The "optional settings" wiki page (http://docs.limesurvey.org/Optional+settings) holds information about LimeSurvey settings for certain parts of the programm that are to be set at the config.php file and are not included at the global settings.
A Spanish version of this page doesn't exist and needs to be created based on the english page.
Task steps:
- Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the "documentation" link on the LimeSurvey main page.
- Have a look at the english base page: http://docs.limesurvey.org/tiki-index.php?page=Optional+settings
- On top right, choose the option to translate the current english version and assign the new page a matching name and the Spanish language
- Translate the english page to Spanish
- When you are done, check carefuly if no settings is missing
- If you have any questions about a certain setting, ask it here, your mentor will be notified.
- When you are done, submit your work here (just give the link to the translated page).
Time frame | Skills | Difficulty | Mentor |
5 days | Spanish language, wiki editing | difficult | Mazi, holch |
Translation: Update the German version of the english "Exporting results" wiki page
Idea posted by: Mazi
The "Exporting results" wiki page (http://docs.limesurvey.org/Exporting+results&structure;=English+Instructions+for+LimeSurvey) holds information about exporting survey data for different applications.
The German version of this page (http://docs.limesurvey.org/tiki-index.php?page=Ergebnisse+exportieren) is outdated and needs to be updated based on the english page.
Task steps:
- Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the "documentation" link on the LimeSurvey main page.
- Have a look at the english base page: http://docs.limesurvey.org/Exporting+results
- Port the document structure (page sections) to the German page (http://docs.limesurvey.org/tiki-index.php?page=Ergebnisse+exportieren)
- Check which parts missing -> add those
- Check which parts are incomplete -> extend those
- When you are done, check carefuly if no settings is missing
- If you have any questions about a certain part of the english page, ask here, your mentor will be notified.
- When you are done, submit your work here (just give the link to the translated page).
Time frame | Skills | Difficulty | Mentor |
3 days | German language, wiki editing | moderate | Mazi, mot |
Translation: Update the French version of the english "Exporting results" wiki page
Idea posted by: Mazi
The "Exporting results" wiki page (http://docs.limesurvey.org/Exporting+results&structure;=English+Instructions+for+LimeSurvey) holds information about exporting survey data for different applications.
The French version of this page (http://docs.limesurvey.org/Exportation+des+r%C3%A9sultats) is outdated and needs to be updated based on the english page.
Task steps:
- Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the "documentation" link on the LimeSurvey main page.
- Have a look at the english base page: http://docs.limesurvey.org/Exporting+results
- Port the document structure (page sections) to the French page (http://docs.limesurvey.org/Exportation+des+r%C3%A9sultats)
- Check which settings parts missing -> add those
- Check which parts are incomplete -> extend those
- When you are done, check carefuly if no settings is missing
- If you have any questions about a certain part of the english page, ask here, your mentor will be notified.
- When you are done, submit your work here (just give the link to the translated page).
Time frame | Skills | Difficulty | Mentor |
5 days | French language, wiki editing | moderate | Mazi, Shnoulle |
Translation: Translate the english "Exporting results" wiki page to Spanish
Idea posted by: Mazi
The "Exporting results" wiki page (http://docs.limesurvey.org/Exporting+results&structure;=English+Instructions+for+LimeSurvey) holds information about exporting survey data for different applications.
A Spanish version of this page doesn't exist and needs to be created based on the english page.
Task steps:
- Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the "documentation" link on the LimeSurvey main page.
- Have a look at the english base page: http://docs.limesurvey.org/Exporting+results&structure;=English+Instructions+for+LimeSurvey
- On top right, choose the option to translate the current english version and assign the new page a matching name and the Spanish language
- Translate the english page to Spanish
- When you are done, check carefuly if no section is missing
- If you have any questions about a certain part of the english page, ask here, your mentor will be notified.
- When you are done, submit your work here (just give the link to the translated page).
Time frame | Skills | Difficulty | Mentor |
5 days | Spanish language, wiki editing | difficult | Mazi, holch |
Documentation: Include description from question type articles into question types overview page
Idea posted by: vierundzwanzig
The english article "Question Types", http://docs.limesurvey.org/Question+types has its own description and images. It would be better to include the description from the question type articles. This can make maintenance easier.
Task steps:
- Use http://docs.limesurvey.org/English+Instructions+for+LimeSurvey to get to the articles for the question types. For example, the first is "Question type - Array" at http://docs.limesurvey.org/Question+type+-+Array .
- If the article doesn't have a header called "short description" (Wiki: !Short description) add the short description header.
- The short description should be short and tell the user in one to three sentences what this question type is used for. You can use the existing description in the article if it fits well or copy and customise it. After your work is done it should look like
=Short description= An array allows you to create subquestions as your left hand headings, and let your participants respond to a series of possible answers options using those subquestions. [[File:F_AFL.jpg]] ---- =General description= ...
- Have a look at the english page http://docs.limesurvey.org/Question+types
- Edit http://docs.limesurvey.org/Question+types : Remove the old text/images and include the short description of the question type article.
- Before:
=== Array=== [[File:F_AFL.jpg]] [[Media:F_-_Array_Flexible_Labels.csv|Download this question type to import it at your survey]] To show scale details left/right of the answer scale you can use "|" as a separator when adding the answer text e. g. "sweet|bitter" or "not at all satisfied|extremely satisfied" [[File:H_SD.jpg]] [[Media:H_-_Array_Flexible_Labels_-_Semantic_Differential.csv|Download this question type to import it at your survey]] Find out [[Question type - Array|more about the Array question type...]]
- After:
=== Array=== {INCLUDE(page="Question type - Array",start="!Short description}} Find out [[Question type - Array|more about the Array question type...]]
- Repeat this for all question types
- Discuss your changes with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | English language, understand wiki syntax | easy | Mazi |
First wave (already ported to GCi system)
Localization
Localization: Translate LimeSurvey to your mother language
The LimeSurvey software is available in more than 50 languages - not all of them are completely translated. Check if your language is supported at: http://www.limesurvey.org/translationstatus_v2/
Task Steps:
- Check out if your language is already there and if the translation status is below 70% OR if your language does not exist at all.
- Read the documentation on Translating LimeSurvey
- Translate as crazy - check your translation using a local copy of LimeSurvey.
- Submit your updated/new translation to us.
Updating a translation from <70% to 100%:
Time frame | Skills | Difficulty | Mentor |
2 Days | Translation | Easy | c_schmitz |
New translation (at least 50%):
Time frame | Skills | Difficulty | Mentor |
3 Days | Translation | Moderate | c_schmitz |
Translation: (GERMAN) Translate the english "ExpressionScript" docs page to German
Idea posted by: Mazi
The upcoming LimeSurvey 2.0 version will contain a powerful "ExpressionScript" which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to translate the current wiki page to German.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Expression+Manager
- Create a new German translation of this page directly at our wiki and translate the page carefully
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | German and English language | easy | mot2 |
Translation: (GERMAN) Translate the english "Central Participants Database" docs page to German
Idea posted by: Mazi
The upcoming LimeSurvey 2.0 version will have a new feature called "Central Participants Database" (CPDB). The documentation of this new feature is only available in English yet. Your task is to translate the current wiki page to German.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29
- Create a new German translation of this page directly at our wiki and translate the page carefully
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | German and English language | easy | mot2 |
Translation: (GERMAN) Translate the english "Creating a new survey" docs page to German
Idea posted by: Mazi
The "Creating a new survey" page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the German documentation of this page is really outdated. Your task is to update the German translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&structure;=English+Instructions+for+LimeSurvey
- Check if it's worth keeping parts of the current German version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the German translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | German and English language | easy | mot2 |
Translation: (GERMAN) Translate the english "Advanced question settings" docs page to German
Idea posted by: Mazi
The "Advanced qustion attributes" page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the German documentation of this page is really outdated. Your task is to update the German translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings
- Check if it's worth keeping parts of the current German version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the German translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | German and English language | easy | mot2 |
Translation: (GERMAN) Translate the english "Tokens" docs page to German
Idea posted by: Mazi
The "Tokens" page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the German documentation of this page is really outdated. Your task is to update the German translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Tokens&structure;=English+Instructions+for+LimeSurvey
- Check if it's worth keeping parts of the current German version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the German translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | German and English language | easy | mot2 |
Translation: (GERMAN) Translate the english "Installer" docs page to German
Idea posted by: Mazi
The new installer is one of the most important featres of the new LimeSurvey 2.0 version. Once the English instructions page (see this idea) was set up, the German translation of that page has to be created.
Task Steps:
- Have a look at the english installer page once it was set up.
- Create the German translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | German and English language | easy | mot2 |
------------------
Translation: (FRENCH) Translate the english "ExpressionScript" docs page to French
Idea posted by: Mazi
The upcoming LimeSurvey 2.0 version will contain a powerful "ExpressionScript" which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to translate the current wiki page to French.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Expression+Manager
- Create a new French translation of this page directly at our wiki and translate the page carefully
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | French and English language | easy | Shnoulle |
Translation: (FRENCH) Translate the english "Central Participants Database" docs page to French
Idea posted by: Mazi
The upcoming LimeSurvey 2.0 version will have a new feature called "Central Participants Database" (CPDB). The documentation of this new feature is only available in English yet. Your task is to translate the current wiki page to French.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29
- Create a new French translation of this page directly at our wiki and translate the page carefully
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | French and English language | easy | Shnoulle |
Translation: (FRENCH) Translate the english "Creating a new survey" docs page to French
Idea posted by: Mazi
The "Creating a new survey" page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the French documentation of this page is really outdated. Your task is to update the French translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&structure;=English+Instructions+for+LimeSurvey
- Check if it's worth keeping parts of the current French version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the French translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
1 day | French and English language | easy | Shnoulle |
Translation: (FRENCH) Translate the english "Advanced question settings" docs page to French
Idea posted by: Mazi
The "Advanced question attributes" page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the French documentation of this page is really outdated. Your task is to update the French translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings
- Check if it's worth keeping parts of the current French version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the French translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | French and English language | easy | Shnoulle |
Translation: (FRENCH) Translate the english "Tokens" docs page to French
Idea posted by: Mazi
The "Tokens" page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the French documentation of this page is really outdated. Your task is to update the French translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Tokens&structure;=English+Instructions+for+LimeSurvey
- Check if it's worth keeping parts of the current French version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the French translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | French and English language | easy | Shnoulle |
Translation: (FRENCH) Translate the english "Installer" docs page to French
Idea posted by: Mazi
The new installer is one of the most important featres of the new LimeSurvey 2.0 version. Once the English instructions page (see this idea) was set up, the French translation of that page has to be created.
Task Steps:
- Have a look at the english installer page once it was set up.
- Create the French translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | French and English language | easy | Shnoulle |
---------------
Translation: (SPANISH) Translate the english "ExpressionScript" docs page to Spanish
Idea posted by: Mazi
The upcoming LimeSurvey 2.0 version will contain a powerful "ExpressionScript" which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to translate the current wiki page to Spanish.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Expression+Manager
- Create a new Spanish translation of this page directly at our wiki and translate the page carefully
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | Spanish and English language | easy | holch |
Translation: (SPANISH) Translate the english "Central Participants Database" docs page to Spanish
Idea posted by: Mazi
The upcoming LimeSurvey 2.0 version will have a new feature called "Central Participants Database" (CPDB). The documentation of this new feature is only available in English yet. Your task is to translate the current wiki page to Spanish.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29
- Create a new Spanish translation of this page directly at our wiki and translate the page carefully
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | Spanish and English language | easy | holch |
Translation: (SPANISH) Translate the english "Creating a new survey" docs page to Spanish
Idea posted by: Mazi
The "Creating a new survey" page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the Spanish documentation of this page is really outdated. Your task is to update the Spanish translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&structure;=English+Instructions+for+LimeSurvey
- Check if it's worth keeping parts of the current Spanish version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the Spanish translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
1 day | Spanish and English language | easy | holch |
Translation: (SPANISH) Translate the english "Question types" docs page to Spanish
Idea posted by: Mazi
The "Question types" page is one of the most important pages at our documentation because it lists all available question types. Unfortunately the Spanish documentation of this page is really outdated. Your task is to update the Spanish translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Question+types&structure;=English+Instructions+for+LimeSurvey
- Check if it's worth keeping parts of the current Spanish version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the Spanish translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | Spanish and English language | moderate | holch |
Translation: (SPANISH) Translate the english "Advanced question settings" docs page to Spanish
Idea posted by: Mazi
The "Advanced question attributes" page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the Spanish documentation of this page is really outdated. Your task is to update the Spanish translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings
- Check if it's worth keeping parts of the current Spanish version. If so, update the existing page, if not, clear the page and translate the english base version.
- Create the Spanish translation of this page directly at our wiki.
- Check if your new/updated translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | Spanish and English language | easy | holch |
Translation: (SPANISH) Translate the english "Tokens" docs page to Spanish
Idea posted by: Mazi
The "Tokens" page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the Spanish documentation of this page doesn't exist yet. Your task is to create the Spanish translation of that wiki page based on the current english wiki page.
Task Steps:
- Have a look at the english page at http://docs.limesurvey.org/Tokens&structure;=English+Instructions+for+LimeSurvey
- Translate the page based on the english base version.
- Check if your new translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
3 days | Spanish and English language | difficult | holch |
Translation: (SPANISH) Translate the english "Installer" docs page to Spanish
Idea posted by: Mazi
The new installer is one of the most important featres of the new LimeSurvey 2.0 version. Once the English instructions page (see this idea) was set up, the Spanish translation of that page has to be created.
Task Steps:
- Have a look at the english installer page once it was set up.
- Create the Spanish translation of this page directly at our wiki.
- Check if your new translation contains all information of the english base version.
- Discuss the translation with your mentor
Time frame | Skills | Difficulty | Mentor |
2 days | French and English language | moderate | holch |
Code
Code: Usability changes for LimeSurvey
The LimeSurvey user interface (like most interfaces) has its kinks - often it is very easy to enhance the usability by just making small changes to the interface.
Task Steps:
- Install LimeSurvey - create a small survey, play around with the interface.
- Pick a couple things you would like to change to have better usability
- Discuss the found issues with your mentor
- Together we will either pick one of your found issues or the mentor will make an suggestion for another change.
- Code the usability change and create a patch
- Discuss the patch with your mentor and the mentor
- If necessary make re-submit patch with discusse changes
Time frame | Skills | Difficulty | Mentor |
2 days | PHP, HTML, CSS, maybe SQL | Moderate | c_schmitz |
Code: Implement "Embedd all text answers" setting at admin statistics
Idea posted by: Mazi
Currently the admin statistics only sum up data. If you want to have a look at text responses in detail, you have to click another button within the summary which opens a new windows.
This is a bad solution if you want to exports results and include the texts because you have to copy them manually. Therefore a new "Embedd all text answers" setting should be introduced so that all text answers will be listed for all corresponding questions. This way this data would also be avialable when exporting the statistics.
Task Steps:
- Install LimeSurvey - create a small survey with text questions and add some dummy data.
- Have a look at the data summary and the available export options.
- Add a "Embedd all text answers" setting.
- Implement the code to embedd that data and create a patch
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the limesurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2 days | PHP, some very basic HTML, SQL | Moderate | c_schmitz |
Code: Implement Google map at admin statistics
Idea posted by: Mazi
LimeSurvey offers a "Map" question type which can be used to let the user mark a certain location. The results are stored as lat./long. coordinates at a simply text question. Currently the admin statistics only show the raw coordinates. To improve this, a Google Map should be included at the admin statistics, showing the users' answers at that overview.
Task Steps:
- Install LimeSurvey - create a small survey with a map question and add some dummy data.
- Have a look at the admin statistics of that question.
- Implement the code to embedd a Map and mark the users' answers in there and create a patch
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the limesurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
3 days | PHP, some very basic HTML, (knowledge about Google Maps API or: learning by doing) | Moderate | c_schmitz |
Code: Implement jqgrid at token overview table
Idea posted by: Mazi
The LimeSurvey admin backend includes several tabular overviews, e.g. when listing all the existing users at the token overview. Usability will benefit a lot if those overviews would be sortable, searchable and filterable. For this we can use jqgrid.
Task Steps:
- Install LimeSurvey - create a small survey with a token table and add a few dummy people there.
- Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php
- Implement jqgrid for the token overview and create a patch
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the limesurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2 days | Javascript, PHP, HTML, maybe a little CSS | Difficult | c_schmitz |
Code: Implement jqgrid at browse response table
Idea posted by: Mazi
The LimeSurvey admin backend includes several tabular overviews, e.g. when listing survey results at the browse responses screen. Usability will benefit a lot if this overview would be sortable, searchable and filterable. For this we can use jqgrid.
Task Steps:
- Install LimeSurvey - import a test survey with all question types (we'll hand that to you) and add some test answer data.
- Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php
- Implement jqgrid for the browse response table and create a patch
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the limesurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2 days | Javascript, PHP, HTML, maybe a little CSS | Moderate | aniessh |
Code: Improve drag and drop functionality at attribute mapping
Idea posted by: Aniessh
Central Participant's Database feature has a special drag and drop functionality for mapping/creating attributes in the token table to the central table and vice versa. The feature is working but needs improvement in the user interface.
Task Steps:
- Install LimeSurvey - create a small survey with a token table and add a few dummy people there.
- Create some attributes at the token level.
- Create some attributes at the Central Participant Database panel.
- Copy the previously added dummy people from token table to the central table.
- You will be presented with a drag and drop screen that will allow you to match the attributes from the central and the token table.
- Suggest how to improve the user interface.
- Improve the user interface and create a patch.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the limesurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2 days | Javascript, PHP, HTML, CSS | Moderate | aniessh |
Code: Add drag and drop feature to ranking question
Idea posted by: Mazi
LimeSurvey contains a "ranking" question type (see http://docs.limesurvey.org/Question+type+-+Ranking&structure;=English+Instructions+for+LimeSurvey) which isn't very user friendly when it comes to sorting and it also causes problems when being used by screen readers. Nowadays there are better interfaces for such question types so switching to a drag and drop version is the goal of this coding task.
There is already a workaround and a demo version available so what has to be done is porting the code to create a more generic solution and embedding the CSS for the available shipped templates.
Task Steps:
- Install LimeSurvey - create a test survey with ranking question types and different question attributes
- Have a look at the question type within the survey to see what could be improved.
- Check the workaround linked above and the demo survey to see where we would like to go to.
- Implement a generic solution to make the ranking question type a little nicer (no DB changes required).
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the limesurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
3 days | Javascript, PHP, CSS | difficult | c_schmitz |
Code: Add option to switch between bar chart and pie chart at statistics
Idea posted by: Mazi
LimeSurvey uses bar charts for multiple choice questions and pie charts for single choice questions. Often users want to switch to a different chart type so this fixed assignment of certain types should be replaced by a more dynamic system which allows the user to set chart types himself.
Task Steps:
- Install LimeSurvey - import a test survey with all question types (we can provide one) and add some test data.
- Have a look at the admin statistics and the charts that are created. Check how we could best offer a choice for the user to set chart types.
- Discuss your suggestions with your mentor and together create a concept how to deal with the problem.
- Implement a generic solution.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the limesurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
4 days | PHP, MySQL, a little HTML | difficult | c_schmitz |
Code: Refactor the CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. The code however is far from ideal. In order to improve code quality, there are plenty of refactorings required like splitting up long methods, extracting view-related and database-related code from controllers, adding new helper functions, ...
Task Steps:
- Download the LimeSurvey CI-branch
- Find a class or method with smelly (bad) code
- Discuss the code smell with the mentor and make a proposal on how to improve the code
- Work out the improvement and create a patch
- Discuss your patch with the mentor
- Check-in your changes into the limesurvey svn trunk
Time frame | Skills | Difficulty | Mentor |
2-4 days (depending on chosen smell) | PHP, CodeIgniter (depending on chosen smell) | Moderate | mrp001 |
Code: Make unit tests for the CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. Now we are using the framework, it is possible to write unit tests for the different classes (domain classes, controllers, helpers, libraries, ...) The goal of this task is to write a unit test for an untested class or method.
Task Steps:
- Download the LimeSurvey CI-branch
- Find an untested class which could use some testing
- Discuss the badly tested class/method with the mentor and make a proposal on how to test the code
- Write tests for class/method and create a patch
- Discuss your patch with the mentor
- Check-in your changes into the limesurvey svn trunk.
Time frame | Skills | Difficulty | Mentor |
2-4 days (depending on chosen class/method) | PHP, CodeIgniter (depending on chosen class/method) | Moderate | mrp001 |
Code: Re-factoring HTML into views : CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, there are still some controllers which have lots of HTML content in them. This task aim for separating this HTML(wherever possible) from controllers and move it to View files. This task will be on controller by controller basis.
Code: Re-factoring database calls into models (Browse Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Browse Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Browse Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Check Integrity Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Check Integrity Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Check Integrity Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Conditions Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Conditions Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Conditions Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Database Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Database Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Database Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Data Entry Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Data Entry Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Data Entry Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Email Templates Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Email Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Email Templates Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Export Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Export Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Export Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Labels Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Labels Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Labels Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Printable Survey Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Printable Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Printable Survey Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Question Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Question Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Question Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Question Group Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Question Group Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Question Group Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Quotas Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Quotas Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Quotas Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Saved Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Saved Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Saved Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Statistics Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Statistics Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Statistics Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Survey Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Survey Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Survey Permission Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Survey Permission Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Survey Permission Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Templates Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Templates Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Tokens Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Tokens Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Tokens Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (Translate Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
Translate Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in Translate Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (User Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
User Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in User Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Code: Re-factoring database calls into models (User Groups Controller): CodeIgniter branch
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and "Active Records" should be used everywhere. This task aim for searching through the
User Groups Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).
Task Steps:
- Download LimeSurvey's CodeIgniter branch
- Read the Documentation
- Find outdated database calls in User Groups Controller (db_execute_assoc()).
- Identify which calls have equivalent methods in models.
- Port these calls using the existing models.
- Create or extend the models for the remaining calls.
- Port the remaining calls using the new models.
- Discuss the patch with your mentor and ask for feedback.
- Check-in your changes into the LimeSurvey svn trunk.
- Done!
Time frame | Skills | Difficulty | Mentor |
2-4 days | PHP, CodeIgniter, MySQL | Moderate | dionet/magiclko |
Documentation
Documentation: Rewrite template editor wiki page
LimeSurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Currently the documentation for the template editor is out of date needs to be brought up to date with the latest version of limesurvey. Cropped screenshots should also be inserted to visually reference the documentation and the software.
Task Steps:
- Read the existing outdated documentation.
- Explore limesurvey's template editor and compare it to the existing documentation.
- Design a new structure for the documentation which is easy to follow and well structured.
- Discuss your planned documentation structure with your mentor.
- Rewrite the template editor documentation.
- Insert cropped screenshots where needed.
- Submit your documentation for review by your mentor.
Time frame | Skills | Difficulty | Mentor | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 Days | Wiki editing,LimeSurvey | Moderate Mazi
} Documentation: Rewrite the survey settings pageTask Steps:
|