Difference between revisions of "Dev:GoogleSoC/ApplicationForm"

From Synfig Studio :: Documentation
Jump to: navigation, search
m
m (Logs on separate line)
 
(54 intermediate revisions by 8 users not shown)
Line 1: Line 1:
−
We missed the 2007 SoC, so let's be ready at some point!
+
Questions from http://www.google-melange.com/gsoc/org/application/google/gsoc2012 (needs registration)
  
−
== TODO ==
+
* '''Organization name:'''
−
We need:
+
** Synfig
−
* more mentors!
+
−
* real names and google accounts for mentors and administrators
+
−
* project ideas before we submit proposal application (look through wiki an bugtracker)
+
  
−
== Administrators and Mentors ==
+
* '''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.
  
−
Please read the [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/ Summer of Code Mentoring HOWTO].
+
* '''Organization home page url:'''
−
 
+
−
* [[User:PaulWise|Paul Wise aka pabs3]] (project administrator)
+
−
* [[User:Zelgadis|Zelgadis]] (backup administrator)
+
−
* [[User:dooglus|dooglus]] (chief project mentor)
+
−
* [[User:Yoyobuae|Yoyobuae]] (project mentor)
+
−
 
+
−
== Draft application ==
+
−
 
+
−
Questions from http://code.google.com/soc/org_signup.html
+
−
 
+
−
=== About Your Organization ===
+
−
 
+
−
* What is your Organization's Name?
+
−
** Synfig Studio project team
+
−
 
+
−
* What is your Organization's Homepage?
+
 
** http://synfig.org/
 
** http://synfig.org/
  
−
* Describe your organization.
+
* '''Main organization License:'''
−
** Our team 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.
+
−
 
+
−
* Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?
+
−
** There are lot of features what needs to be developed to make our software more powerful, stable and user-friendly. We also hope to involve more people into project development.
+
−
 
+
−
* Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.'''
+
−
** Unfortunately, no.
+
−
 
+
−
* If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)
+
−
** No, however we have had lots of people suggest that we participate.
+
−
 
+
−
* What license does your project use?
+
 
** GNU GPL v2 or later.
 
** GNU GPL v2 or later.
  
−
* URL for your ideas page
+
* '''What is the URL for your Ideas page?'''
−
** http://synfig.org/GoogleSoC#Ideas
+
** http://wiki.synfig.org/wiki/Dev:GoogleSoC/Ideas
  
−
* What is the main development mailing list for your organization?
+
* '''What is the main IRC channel for your organization?'''
−
** http://lists.sourceforge.net/lists/listinfo/synfig-devl
+
−
 
+
−
* Where is the main IRC channel for your organization?
+
 
** #synfig on irc.freenode.net
 
** #synfig on irc.freenode.net
 +
** Logs are available at: http://dooglus.rincevent.net/synfig/logs
  
−
* Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)
+
* '''What is the main development mailing list for your organization?'''
−
** No
+
** http://lists.sourceforge.net/lists/listinfo/synfig-devl
−
 
+
−
* Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)
+
−
** Konstantin Dmitriev aka Zelgadis - ksee.zelgadis AT gmail.com
+
−
 
+
−
=== About Your Mentors ===
+
−
 
+
−
* What criteria did you use to select these individuals as mentors? Please be as specific as possible.
+
−
** Individual selected as mentor in project must have a knowledge of C/C++ and Synfig Studio program code (or its specific area). It could be easily determined from the SVN commit history (http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=log). He also must be a regular on IRC and wiki (see http://dooglus.rincevent.net/synfig/logs/ and http://synfig.org/Special:Recentchanges). Synfig Studio is an animation program, so the selected mentor should know its common animation concepts: keyframes, waypoints, layers, blend methods. Selected individuals are highly-motivated, long-standing contributors of the project.
+
−
* Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)
+
−
** dooglus (?)
+
−
** pabs3 (?)
+
−
** Yoyobuae
+
−
** factor (?)
+
−
 
+
−
=== About The Program ===
+
−
 
+
−
* What is your plan for dealing with disappearing students?
+
−
** First of all our mentors will try to clearly define the final target of the project and motivate the student to make the project valuable for him as much as possible. At the beginning of work we must get from student as much alternative contact information as possible (i.e. e-mail, ICQ, Jabber, home and mobile phone, home address, website, etc.). This must minimize the likelyhood of disappearing students. If student disappears from regular contact we'll try to establish contact with him via phone or IM to find out the reason of his absence and also notify Google about disappeared student. If a student actually decides to leave, the project will likely be taken on by somebody from the community in the future (depending on the priority) or be saved for the next season.
+
−
 
+
−
* What is your plan for dealing with disappearing mentors?
+
−
** During the SoC we are planning to have one backup mentor. If existing mentors become unavailable or unresponsive during the project period backup mentor takes place of absence mentor. Most communications are take place on IRC which logs stored on http://dooglus.rincevent.net/synfig/logs/, so the backup mentor always could receive all information about status of student's work.
+
−
 
+
−
* What steps will you take to encourage students to interact with your project's community before, during and after the program?
+
−
** We are require participation on public IRC channels where community discussing the directions of future development, shares their works and examples, motivates each other. There are not only developers there, but also translators and artists who uses Synfig Studio so the bar is low enough for newbie. Our community always open for any contributions, not only matter whether they're funded by SoC or not. For particular guidance, students are welcome to contact any of the IRC members, no matter whether they're funded or not.
+
−
** To involve students to process at early stages the general steps are:
+
−
*** preparing a brief plan of project implementation
+
−
*** defining milestones
+
−
*** defining "need to study" things for each milestone
+
−
** The steps taken during the program depend on the individual projects
+
−
** At the end of program project results must be summarized to provide complete view of done work and encourage students to participate in further development.
+
  
−
* What will you do to ensure that your accepted students stick with the project after GSoC concludes?
+
* '''Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating?'''
−
** The community is inspired by the art produced by Synfig Studio artists. We hope what during the SoC much more animations will be produced and students will be able to see results of their work not only as a piece of code or software package, but also as funny cartoons done with all great new features implemented during the study process. Our developers are always in touch with the people who uses Synfig Studio, paying much attention to their needs and feedback.
+
** We hope to attract new and enthusiastic developers to the project.
  
−
== Ideas ==
+
* '''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.
  
−
=== General ===
+
* '''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.
  
−
* UI revamp - see [[Wish_List#Single_window]], [http://sourceforge.net/tracker/index.php?func=detail&aid=1687557&group_id=144022&atid=757419 #1687557], [http://sourceforge.net/tracker/index.php?func=detail&aid=1687726&group_id=144022&atid=757416 #1687726]
+
* '''Does your organization have an application template you would like to see students use? If so, please provide it now.'''
−
* [[Wish_List#Collect_for_Publication]]
+
** http://wiki.synfig.org/wiki/Dev:GoogleSoC/StudentApplicationTemplate
−
* [[Sound_Layer]]
+
−
* Completely fix all issues found by valgrind
+
−
* SWF, SVG, etc import and or export
+
−
* Implement the Palette Browser, which is a stub in the current code
+
−
* Implement icon theming, usage of the Tango and ArtLibreSet naming schemes and draw icons for all the missing actions
+
−
* Implement a parameter system for output targets and the command-line and GUI interfaces for them.
+
  
−
=== Construction ===
+
* '''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
  
−
* Easy way to link ducks to blines with mouse - see [[Linking_to_Blines]] and [[Wish_List#Riding_ducks]]
+
* '''What is your plan for dealing with disappearing students?'''
−
* [[Wish_List#Layer_Convert]]
+
** 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.
−
* Redraw tool suggested by snapsilverlight
+
  
−
=== Animation ===
+
* '''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.
  
−
* Keyframe manipulation tool - see [http://sourceforge.net/tracker/index.php?func=detail&aid=1904463&group_id=144022&atid=757419 #1904463]
+
* '''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.
  
−
=== Misc ===
+
* '''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.
  
−
* Most any common bug in bugzilla (if its a large implementation, or several smaller bugs)
+
* '''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://www.wiki.synfig.org/index.php?title=Dev:GoogleSoC/ApplicationForm&oldid=15348"