Dev:GoogleSoC/ApplicationForm - Revision history

Nikitakit: Logs on separate line

2012-03-07T09:43:55Z

Logs on separate line

Nikitakit: Proofread and small edits

2012-03-07T09:41:18Z

Proofread and small edits

Nikitakit: Change answer to question about dealing with disappearing students

2012-03-07T09:19:52Z

Change answer to question about dealing with disappearing students

Zelgadis: Revert some changes as well (agreed with Genete)

2012-03-07T08:34:40Z

Revert some changes as well (agreed with Genete)

Genete: Changes that I think should be applied.

2012-03-07T06:57:38Z

Changes that I think should be applied.

DaveJ: typo envolvement -> involvement

2012-03-07T06:32:25Z

typo envolvement -> involvement

DaveJ: typo insure -> ensure

2012-03-07T06:31:23Z

typo insure -> ensure

Eldruin: Reviewed and edited with an American Politics graduate

2012-03-06T23:07:32Z

Reviewed and edited with an American Politics graduate

Nikitakit: Proofread

2012-03-06T11:33:36Z

Proofread

Nikitakit at 11:29, 6 March 2012

2012-03-06T11:29:21Z

@@ Line 17: / Line 17: @@
 * '''What is the main IRC channel for your organization?'''
-** #synfig on irc.freenode.net Logs: http://dooglus.rincevent.net/synfig/logs
+** #synfig on irc.freenode.net
 * '''What is the main development mailing list for your organization?'''

@@ Line 5: / Line 5: @@
 * '''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.
+** We are a community of developers and animators focused on the 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.
 * '''Organization home page url:'''
@@ Line 35: / Line 35: @@
 * '''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
+** 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.
 * '''What is your plan for dealing with disappearing students?'''
@@ Line 44: / Line 45: @@
 * '''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.
+** 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 to speak 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.
+** 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 who show active involvement and eagerness to participate will be favored for acceptance into the program, and we believe that 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.
+** 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.
+** N.A.
 * '''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.

@@ Line 38: / Line 38: @@
 * '''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?'''

@@ Line 5: / Line 5: @@
 * '''Organization description:'''
-** We are a community of developers and animators centered around 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.
+** 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.
 * '''Organization home page url:'''
@@ Line 23: / Line 23: @@
 * '''Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating?'''
-** Because our developing team is still rather small, we hope to attract new and enthusiastic developers to the project.
+** We hope to attract new and enthusiastic developers to the project.
-An increase of developers would allow us to implement long-awaited features needed by the animation community.
 * '''Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation.'''

@@ Line 39: / Line 39: @@
 * '''What is your plan for dealing with disappearing students?'''
-** We plan to ensure that students know how much we value their participation, and we will reach out to them by offering support and guidance. 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. 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?'''
-** First and foremost, we are certain that our mentor and lead developer is incredibly commited, as he has demonstrated by his many years of service. However, 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.
+** 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?'''

@@ Line 26: / Line 26: @@
 * '''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 have not participated in the past GSoCs.
+** 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)?'''
@@ Line 52: / Line 52: @@
 * '''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.'''
-** No, we're not.
+** N.A.