GSoC 2009/Proposal

(Does your organization have an application template you would like to see students use? If so, please provide it now.)
(What is your plan for dealing with disappearing students?)
Line 68: Line 68:
==<b>What is your plan for dealing with disappearing students?</b>==
==<b>What is your plan for dealing with disappearing students?</b>==
 +
 +
At the students selection process we will be careful with students with other commitments during the Google Summer of Code coding period, in order to avoid situations where the student have a big overload of work, that can lead to not fulfill our expectations.
 +
We will require students weekly reports to their mentors and assigned backup mentors in order to keep track of the students progresses, we will also require bi-weekly reports of the projects for our community mailing list, with this we will have the student status at any time, avoiding problems that can be arise during the coding period.
 +
At the beginning of the coding period the students and their mentors will review and adapt the project schedule, in order to keep the student in the schedule.
 +
Besides the preventive measures described above, we will try to keep our students motivated at any time.
==<b>What is your plan for dealing with disappearing mentors?</b>==
==<b>What is your plan for dealing with disappearing mentors?</b>==

Revision as of 19:07, 7 March 2009

Contents

Describe your organization.

Maemo Community is an open source community developing software around the Maemo platform. The Maemo community has over 16.000 registered members that contribute to more than 800 development projects. We work with open source tools and processes. We develop new software for both the platform itself and on top of the platform. Applications developed with the Maemo SDK are used today by thousands of persons around the world. <some something about the maemo council>

Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating?

Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.

If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?

N/A

What license(s) does your project use?

The majority of the projects are licensed under this licenses:

  • GPL v2 or later;
  • LGPL v2 or later;
  • MIT license.

What is the URL for your ideas page?

http://wiki.maemo.org/GSoC_2009

What is the main development mailing list or forum for your organization?

Main development mailing list is: maemo-developers@maemo.org

All Maemo community mailing lists can be found at: http://maemo.org/community/mailing-lists/

The main forum for discussing Maemo related topics is Internet Tablet Talk: http://www.internettablettalk.com/

What is the main IRC channel for your organization?

The main IRC channel for Maemo is #maemo @ freenode

Does your organization have an application template you would like to see students use? If so, please provide it now.

Yes.

Student Template:

  • Project title
  • Project Abstract (short description, can be the same used above)
  • Project full description
  • Project tasks and deliverables
  • Project schedule
  • Do you have other commitments during the summer of code coding period ? If yes, what kind of commitments ?
  • Why are you the right person for this project ?
  • What are the benefits of your project for the Maemo Community ?
  • Bio (academic work, open source background and other activities that you like to do)

Who will be your backup organization administrator? Please include Google Account information.

  • Luis Felipe Moraes

Who will your mentors be? Please include Google Account information.

  • Csaba Kertész
  • Florian Boor
  • Leandro Sales
  • Luis Felipe Moraes
  • Mike Jipping
  • Mohammad Anwari
  • Valério Valério
  • Zeeshan Ali

What criteria did you use to select these individuals as mentors? Please be as specific as possible.

What is your plan for dealing with disappearing students?

At the students selection process we will be careful with students with other commitments during the Google Summer of Code coding period, in order to avoid situations where the student have a big overload of work, that can lead to not fulfill our expectations. We will require students weekly reports to their mentors and assigned backup mentors in order to keep track of the students progresses, we will also require bi-weekly reports of the projects for our community mailing list, with this we will have the student status at any time, avoiding problems that can be arise during the coding period. At the beginning of the coding period the students and their mentors will review and adapt the project schedule, in order to keep the student in the schedule. Besides the preventive measures described above, we will try to keep our students motivated at any time.

What is your plan for dealing with disappearing mentors?

We plan for each project to have one "backup" mentor, that will be involved in the project development, in case of problems with the regular mentor, the backup mentor shall assist the student in order to accomplish the final goals of the project.

What steps will you take to encourage students to interact with your project's community before, during and after the program?

What will you do to ensure that your accepted students stick with the project after GSoC concludes?