Difference between revisions of "Dev:GoogleSoC/ApplicationForm"

From Synfig Studio :: Documentation
Jump to: navigation, search
(Revert some changes as well (agreed with Genete))
(Change answer to question about dealing with disappearing students)
Line 38: Line 38:
  
 
* '''What is your plan for dealing with disappearing students?'''
 
* '''What is your plan for dealing with disappearing students?'''
** We ask students to provide their email and phone number to the project administrator. If a student disappears without notice, the mentor will contact him/her via email to clarify the situation. If there is no reply within 3 days, the administrator will phone him/her personally. If the student cannot be reached, the administrator will contact Google and report the situation.
+
** We ask students to provide their email and phone number to the project administrator. Our mentors will maintain regular contact with students throughout the summer and let them know that we are always available to answer questions and provide guidance. If a student disappears without notice, the mentor will contact him/her via email to clarify the situation. If there is no reply within 3 days, the administrator will phone him/her personally. If the student cannot be reached, the administrator will contact Google and report the situation.
  
 
* '''What is your plan for dealing with disappearing mentors?'''
 
* '''What is your plan for dealing with disappearing mentors?'''

Revision as of 11:19, 7 March 2012

Questions from http://www.google-melange.com/gsoc/org/application/google/gsoc2012 (needs registration)

  • Organization name:
    • Synfig
  • Organization description:
    • We are a community of developers and animators focused on development of Synfig Studio, a 2D vector animation program aiming to improve artistic workflow by focusing on tweening and interpolation. We work together to refine and add new features to the Synfig software, create tutorials, and run challenges to help and inspire our artists.
  • Main organization License:
    • GNU GPL v2 or later.
  • Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating?
    • We hope to attract new and enthusiastic developers to the project.
  • Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation.
    • Our organization has not participated in any past GSoCs.
  • If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)?
    • We applied to GSoC in 2008 and 2010.
  • What criteria did you use to select your mentors for this year's program? Please be as specific as possible.
    • For our mentors, we have selected the most motivated and consistent contributors to the project who have extensive knowledge of specific areas of the Synfig Studio source code. Mentor: Carlos López González, Lead Developer
  • What is your plan for dealing with disappearing students?
    • We ask students to provide their email and phone number to the project administrator. Our mentors will maintain regular contact with students throughout the summer and let them know that we are always available to answer questions and provide guidance. If a student disappears without notice, the mentor will contact him/her via email to clarify the situation. If there is no reply within 3 days, the administrator will phone him/her personally. If the student cannot be reached, the administrator will contact Google and report the situation.
  • What is your plan for dealing with disappearing mentors?
    • Our backup mentor will be available throughout the summer to provide additional support for students, and will be able to fill in for the primary mentor if he is unavailable. In the case of an emergency, or if the mentor disappears and the project administrator fails contact him by phone, the backup mentor will fully take over his responsibilities.
  • What steps will you take to encourage students to interact with your project's community before, during and after the program?
    • We want to have students who are active with the project before the application process begins. We ask potential students to introduce themselves on the project mailing list and forums and they would get to talk with some of our developers and animators. We will treat them as any new member of our community and help them learn how the project works, and we will answer any questions they may have.

As part of our application process, we require that students are able to compile and run Synfig, and we ask them to submit several patches or pull requests and any artwork made in Synfig that they want to share. Those that have shown active involvement and eagerness to participate will be favored for acceptance into the program, and we believe that the enthusiastic students will choose to stay after the summer is over. Once a student's code is reviewed and critiqued, we will strive to integrate it into a new release of Synfig. If students see the tangible impact of their work over the summer, they will be more motivated to remain a part of our community after GSoC is over.

  • Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.
    • No, we're not.
  • Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here.
    • N.A.