GSoC selection criteria: Difference between revisions
From LimeSurvey Manual
| Line 37: | Line 37: | ||
What we're not looking for are applications that are short, show little effort, and do not indicate a serious and real desire to contribute to the LimeSurvey Open Source Project. | What we're not looking for are applications that are short, show little effort, and do not indicate a serious and real desire to contribute to the LimeSurvey Open Source Project. | ||
==More Information== | ==More Information== | ||
Revision as of 16:19, 23 February 2015
Google Summer of Code Selection Criteria for LimeSurvey
LimeSurvey will choose applicants that interest us the most, and we will be using the following criteria when coming to a final decision. Given the limited number of places we will have available, it is important to us to choose carefully.
Please note that the final decision of the LimeSurvey Mentoring Organisation is final and not negotiable; these guidelines are to help you when determining and framing your application.
What we are looking for?
- Functionality
Our current focus for LimeSurvey 2 is to achieve a basic level of functionality as an online survey tool. Version 1.8 has a large number of features, and LimeSurvey 2 needs to match version 1 in order to be a logical upgrade path for 1.8 users.
Students who propose ideas that will improve the basic feature set of LimeSurvey 2 will be high on our list of priorities.
- Originality or Clarity
LimeSurvey 2 needs to be as feature rich as LimeSurvey 1, but it's the beginning of a new phase for LimeSurvey. Original ideas will count during the selection process. Where an idea is not original, clarity will be an equivalent alternative. If an application shows a clear and definitive understanding of its purpose and place within LimeSurvey, we'll be interested.
- Achievability
We need to be convinced that you're capable of achieving the idea that you propose.
As part of your application make sure that you think carefully about milestones and deliverables. When we assess your application we'll be looking at these carefully to see if we think they are measurable and achievable. An application with clearly defined milestones that help us understand that path the student intends to take to finish the project will have an advantage over an application with unclear or uncertain milestones.
- Realism
Coding projects take time, and this is a 2 month window. Your project needs to be something that can be completed in 2 months. If we think your idea is not realistically achievable, we're not likely to take it on.
- Ability
To feel confident that you can achieve your proposal, we'll need to feel confident in your abilities. Tell us about your experience and/or skills with PHP, CakePHP, javascript and jQuery. Give us some examples of projects you've completed, or participated in before.
- Communication
We need to feel confident that you'll be a good communicator during the course of your project.
What we are not looking for?
We're pretty open to ideas, but since LimeSurvey 2 is a complete rebuild of a fully functioning version 1, naturally we're going to be more interested in proposals that build core functionality. If you have a great idea that's a little out of left-wing, feel free to propose it, but it'll probably need to be outstandingly brilliant to push aside core feature proposals.
What we're not looking for are applications that are short, show little effort, and do not indicate a serious and real desire to contribute to the LimeSurvey Open Source Project.
More Information
LimeSurvey Google Summer of Code 2015
An introduction to LimeSurvey and our application for this years Google Summer of Code
Project Ideas Page
Getting Started
How to Get Started With LimeSurvey: setting up the development environment, coding standards, and all the other important stuff that you need to know before the real fun begins!