Difference between revisions of "Dev:GoogleSoC/ApplicationForm"

From Synfig Studio :: Documentation
Jump to: navigation, search
m (Logs on separate line)
 
(20 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
We have missed the SoC so far. Before 2007 we didn't have an application ready in time. We signed up for the 2008 Google SoC, but didn't get accepted. We haven't signed up since then.
+
Questions from http://www.google-melange.com/gsoc/org/application/google/gsoc2012 (needs registration)
  
−
== Administrators and Mentors ==
+
* '''Organization name:'''
 +
** Synfig
  
−
Please read the [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/ Summer of Code Mentoring HOWTO].
+
* '''Organization description:'''
 +
** 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.
  
−
* Administrator: {{l|User:Zelgadis|Konstantin Dmitriev aka Zelgadis}}, LinkID: zelgadis
+
* '''Organization home page url:'''
−
* Mentor: {{l|User:Genete|Carlos López González aka Genete}}, LinkID: genete
+
−
* Student: {{l|User:Eldruin|Diego Barrios Romero aka Eldruin}}, LinkID: '''???'''
+
−
* Backup Mentor: {{l|User:Pxegeek|Chris Norman aka pixelgeek}},  LinkID: '''pixelgeek'''
+
−
* Backup Administrator: {{l|User:Yaco|Franco Iacomella aka Yaco}}, LinkID: yaco
+
−
 
+
−
 
+
−
== Draft application ==
+
−
 
+
−
Questions from http://socghop.appspot.com/gsoc/org_app/take/gsoc_program/google/gsoc2010/orgapp (needs registration)
+
−
 
+
−
* '''Organization's Name:'''
+
−
** Synfig Project Development Team
+
−
:: We have used that name here: http://synfig.org/wiki/Synfig:Copyrights --[[User:Zelgadis|Zelgadis]] 06:51, 10 March 2010 (UTC)
+
−
 
+
−
* '''Description:'''
+
−
** Our team is developing a powerful, industrial-strength vector-based 2D animation software package, called Synfig Studio. It designed from the ground-up for producing feature-film quality animation with fewer people and resources. While there are many other programs currently on the market to aid with the efficient production of 2D animation, we are currently unaware of any other software that can do what our software can.
+
−
 
+
−
* '''Homepage:'''
+
 
** http://synfig.org/
 
** http://synfig.org/
  
Line 29: Line 13:
 
** GNU GPL v2 or later.
 
** GNU GPL v2 or later.
  
−
* '''Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?'''
+
* '''What is the URL for your Ideas page?'''
−
** We have student willing to contribute to the project for the next two years. By participating in GSoC we want to get funding for him to increase his motivation and to help complete a particular feature during this summer.
+
** http://wiki.synfig.org/wiki/Dev:GoogleSoC/Ideas
  
−
* '''Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.'''
+
* '''What is the main IRC channel for your organization?'''
−
** Unfortunately, no.
+
** #synfig on irc.freenode.net
 +
** Logs are available at: http://dooglus.rincevent.net/synfig/logs
  
−
* '''If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.'''
+
* '''What is the main development mailing list for your organization?'''
−
** Not applicable
+
** http://lists.sourceforge.net/lists/listinfo/synfig-devl
  
−
* '''If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?'''  
+
* '''Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating?'''
−
** Yes, in 2008.
+
** We hope to attract new and enthusiastic developers to the project.
  
−
* '''What is the URL for your ideas page?'''
+
* '''Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation.'''
−
** http://synfig.org/wiki/Dev:GoogleSoC#Ideas
+
** Our organization has not participated in any past GSoCs.
  
−
* '''What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for GSoC 2010. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.'''
+
* '''If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)?'''
−
** http://lists.sourceforge.net/lists/listinfo/synfig-devl This one is for development related items.
+
** We applied to GSoC in 2008 and 2010.
−
** http://lists.sourceforge.net/lists/listinfo/synfig-user This one is for user related items
+
  
−
* '''Where is the main IRC channel for your organization?'''
+
* '''Does your organization have an application template you would like to see students use? If so, please provide it now.'''
−
** #synfig on irc.freenode.net
+
** http://wiki.synfig.org/wiki/Dev:GoogleSoC/StudentApplicationTemplate
−
** Comment: We keep logs at: http://dooglus.rincevent.net/synfig/logs. Also we use forums for community interaction at: http://synfig.org/forums/
+
  
−
* '''Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2010 site.'''
+
* '''What criteria did you use to select your mentors for this year's program? Please be as specific as possible.'''
−
** No, we do not.
+
** 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 criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible:'''
+
−
** The individual selected as the mentor in the project must have a knowledge of C/C++ and Synfig Studio program code (or it's specific area). It could be easily determined from the svn/git commit history (http://synfig.git.sourceforge.net/git/gitweb.cgi?p=synfig/synfig;a=summary). He also must be a regular on IRC and wiki or forums (see previous http://dooglus.rincevent.net/synfig/logs/,  http://synfig.org/Special:Recentchanges and http://synfig.org/forums/). Synfig Studio is an animation program, so the selected mentor should know its common animation concepts: keyframes, waypoints, layers, blend methods, and so forth. Selected individuals are highly-motivated, long-standing contributors of the project. Carlos López González (aka Genete) is willing to be a mentor for this student, because he is complying with all these requirements: he is experienced enough with Synfig code (http://cia.vc/stats/author/Carlos%20Lopez), he is experienced in animation (http://www.youtube.com/user/Genete) and more than that - he lives in the same town as the student and they already have direct meetings working on Synfig code.
+
  
 
* '''What is your plan for dealing with disappearing students?'''
 
* '''What is your plan for dealing with disappearing students?'''
−
** We already have student willing to work on the particular project idea during SoC. That student already proved his capabilities by contributing the patches to the source code (http://cia.vc/stats/author/Diego%20Barrios%20Romero). As he lives in the same town as his mentor, the mentor will have the opportunity to visit him personally in case of his disappearance.
+
** 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?'''
−
** During the SoC we have one backup mentor. If existing mentors become unavailable or unresponsive during the project period a backup mentor will take the place of absent mentor. But the probability of our mentor disappearing is very low because he has been an active member of the Synfig community since 2006 and has declared himself as a very responsible person.
+
** 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?'''
+
−
** Student and mentor have already met directly (offline) and have discussed their plans for development. The student is contributing to the wiki, participating in forum discussions and hangs out on the IRC channel.
+
−
 
+
−
* '''What will you do to ensure that your accepted students stick with the project after GSoC concludes?'''
+
−
** The participating student has made his decision to choose Synfig as his "final career project". That means that he will stick with the project for at least 2 years.
+
−
 
+
−
* '''Is there anything else you would like to tell the Google Summer of Code program administration team?:'''
+
−
** We strongly believe that Synfig Studio is a software that has no equivalent in the world of Free Open Source Software. This is our highest motivation and because of it we are putting all of our efforts towards keeping the Synfig Studio project alive. It would be of great help to the project's maturity and to it's regular development to be chosen as a Mentor Organization.
+
−
 
+
−
== Ideas ==
+
−
 
+
−
As we already have a mentor and a student defined, they chose a particular idea to work on:
+
−
 
+
−
'''Implement OpenGL render engine'''
+
−
 
+
−
You may notice that Synfig Studio is SLOW, making it practically unusable on hardware that is over 6 years old. The biggest reason for this is that all of the color calculations are done in floating point -- because Synfig Studio was built from the ground up with High-Dynamic-Range Imaging in mind. HOWEVER, this will not be the case forever.
+
−
 
+
−
Today's graphics processors are powerful and we want to speed up Synfig Studio by implementing the rendering via OpenGL.
+
  
−
First attempts for such implementation were made earlier ([http://synfig.git.sourceforge.net/git/gitweb.cgi?p=synfig/synfig;a=shortlog;h=refs/heads/uiomae_opengl 1]), ([http://synfig.org/forums/viewtopic.php?f=22&t=362 2]) and the first tests showed speed increase up to 14 times.
+
* '''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 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 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.
  
−
Unfortunately the person who initiated the development of the OpenGL branch was unable to continue development because of personal issues, and the branch were abandoned.
+
* '''Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.'''
 +
** N.A.
  
−
We want to pursue implementing full OpenGL-powered rendering for Synfig Studio. That will result in faster redraw for the workarea during the animation construction and thus make a much better user experience. A good performance of the application during playback and screen redraw is vital for implementing other resource-consuming features like bones and sound support (we need close to real-time response for that.)
+
* '''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.

Latest revision as of 11:43, 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 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.
  • 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 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 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.
  • Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.
    • 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.
Retrieved from "https://wiki.synfig.org/index.php?title=Dev:GoogleSoC/ApplicationForm&oldid=15348"