Rather late than never:

Great report - just put a link to this and to Davids report in a news article on limesurvey.org !

Keep up  the great work!

- Carsten

Am 19.01.2011 19:25, schrieb Marcel Minke (Limesurvey):
Hey folks,

finally there is some time to sum up my Google Code in 2010 experience and present the results of some of the tasks I mentored. At the beginning I was a little doubtful if 13-17 year old pupils could really help us much, that was probably because I looked at the whole program from the coding point of you. After all I can say that GCi really brought some great results for Limesurvey because we could "outsource" lots of the smaller "I wish I could do that but I don't have time for it" tasks.

One part of the tasks I mentored was about spreading the word about Limesurvey. A first task was to update and extend the current Limesurvey article at the english Wikipedia (http://en.wikipedia.org/wiki/LimeSurvey). Based on this new articles about Limesurvey in the following languages were created/extended/overworked:
- French: http://fr.wikipedia.org/wiki/LimeSurvey
- Romanian: http://ro.wikipedia.org/wiki/LimeSurvey
- Bulgarian: http://bg.wikipedia.org/wiki/LimeSurvey
- Polish: http://pl.wikipedia.org/wiki/LimeSurvey
- Russian: http://ru.wikipedia.org/w/index.php?title=LimeSurvey
- Belorussian: http://be.wikipedia.org/wiki/LimeSurvey

Wikipedia articles about Limesurvey are no available in 12 languages in total. Feel free to extend and improve them!

Besides the Wikipedia articles there were some blog posts created (e.g. http://kwinn29.blogspot.com/2010/11/wordpressorg-user-feedback-survey.html).
Our manual was also overworked. The pages about templates were merged at http://docs.limesurvey.org/Themes%3A+Templates+and+Styles&structure=English+Instructions+for+LimeSurvey and several question types got their own subpages, listing assigned question attributes and the like. These new pages are linked at http://docs.limesurvey.org/Question+types&structure=English+Instructions+for+LimeSurvey. Furthermore we now have a tutorial about how to edit, translate and add wiki pages (http://docs.limesurvey.org/Creating%2C+editing+and+translating+LimeSurvey+Wiki+pages) and a PDF on how to create a simple survey (see attachments) was written.

Some video tutorials were created e.g. on how to edit a template (http://docs.limesurvey.org/tiki-index.php?page=Themes%3A+Templates+and+Styles&structure=English+Instructions+for+LimeSurvey#Videos_on_Templates) or how to create a survey from scratch.

Testing the 1.91 version and reporting bugs was another part of GCi to improve the upcoming 1.91 version and identify weaknesses. A similar task was to analyse user feedback of previous surveys we published on limesurvey.org (see "Updated User Survey.docx" for details) and monitor how new user use Limesurvey ("list.rtf"). The results were summed up and added as new feature requests to our idea tracker. Currentlythe results of a survey on icons in Limesurvey are analyzed to check which icons might be misleading.

Last but not least some sample surveys for demonstrating certain feature like conditions, quotas, assessments and certain question attributes were created (see attached .lss files).

It was a lot of work to mentor so many tasks but the results are just awesome. So much was done during the last weeks and besides the work I mentioned, also a lot of new features were coded. Maybe Carsten can sum this up because he mentored those tasks!?

What can we learn?
1. Describe your task as detailed as possible, otherwise you'll have to answer lots of questions afterwards!
2. If necessary provide the students with a ready to use Limesurvey installation. Thanks to Limeservice this was no problem.
3. Keep an eye on deadlines. They can always be extended but some work has to be submitted by the student before extending the deadline is possible (workflow problem at Googles software).
4. Always try to get a second mentor on board because deadlines might be pretty tough and you can't have an eye on all tasks all the time so you run into deadlines (and students have to re-claim the task again).
5. Don't hesitate to tell students "That's quite nice but...". If you tell them what has to be improved in detail and how to best do it they take care of it without complaining.
6. The students are eager to work on our tasks and there have been more requests than we could find work for. They only withdraw if tasks were really hard but more often a bad description and  incomplete "how to get started" instructions made them drop a task.
7. Translation tasks can be outsourced very easily. I think we could have had 10 more new Wikipedia articles but I didn't find time to create new tasks.

Let's hope for being accepted for next years GCi, hopefully more people will be bale to help as mentors. It doesn't take that much time and it really pushes the project forward.

if you have any questions about a certain task, just ping me.

Best regards,

------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ limesurvey-developers mailing list limesurvey-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/limesurvey-developers