[FFmpeg-devel] [RFC] Google Summer of Code 2013
stefasab at gmail.com
Sun Mar 17 18:43:24 CET 2013
On date Thursday 2013-03-07 00:16:37 +0100, Stefano Sabatini encoded:
> On date Thursday 2013-02-21 21:48:23 -0900, Lou Logan encoded:
> > Hello*,
> > It's GSoC time again, so I'll get the ball rolling:
> > http://www.google-melange.com/gsoc/homepage/google/gsoc2013
> > I started a new ideas list:
> > http://wiki.multimedia.cx/index.php?title=FFmpeg_Summer_of_Code_2013
> > Our previous list from 2012:
> > http://wiki.multimedia.cx/index.php?title=FFmpeg_Summer_of_Code_2012
> > IRC log describing why we didn't get accepted last year:
> > http://blackhole.ubitux.fr/gsoc.log
> > Last years GSoC RFC:
> > http://ffmpeg.org/pipermail/ffmpeg-devel/2012-March/121557.html
> > To reduce bloat I did not simply copy last years idea list because I'm
> > not sure what is outdated or relevant. I left "Libavfilter extension"
> > as an example, but please begin adding new ideas or copying over
> > whatever you feel is acceptable (or you can tell me what you would like
> > copied and I can do it). You may have to contact Mike Melanson for wiki
> > account approval: mike at multimedia.cx.
> > I would like to keep all ideas in a consistent format. Application
> > reviewers seem fairly sensitive to the visual presentation in my
> > opinion.
> > We can submit our mentoring organization application beginning March 18
> > and the deadline is March 29 at 19:00 UTC.
> We need an admin and a co-admin for the program. I volunteer to act as
> admin, Lou already proposed to act as co-admin, any other volunteers?
Tomorrow since 19:00 UTC GSoC applications are being accepted.
Since no other volunteer showed up, I'm assuming the role of
administrator, with Lou acting as backup administrator.
Interested parties are welcome to read and review the application text
draft in attachment, based on the text used for the GSoC 2012
application with a few edits.
> Same for the mentored tasks, we need a backup-admin for each task.
> Please add the tasks that you want to mentor as soon as possible. If
> you're not sure about what/if/how you should mentor, feel free to
> discuss on this list (or on IRC).
Ping on this.
FFmpeg = Fostering and Fanciful MultiPurpose Ecumenical Game
-------------- next part --------------
* Organization id
* Organization name
* Organization description
FFmpeg is a complete, cross-platform solution to record, convert,
filter and stream audio and video. It includes libavcodec - the
leading audio/video codec library.
FFmpeg is possibly the most ubiquitous multimedia framework in the
world, is used as the multimedia engine by a significant part of FLOSS
multimedia applications, and provides the back-end of most transcoding
FFmpeg strives at being the *universal* multimedia tool, implementing
all possible multimedia formats (even the most obscure fringe formats),
and at being *complete*, providing full fledged support for all
multimedia operations, relying on external projects when it makes
* Organization home page URL
* Main organization license
GNU LGPL v2
* Backup admin
* What is the URL for your Ideas page?
* What is the main IRC channel for your organization?
#ffmpeg-devel on irc.freenode.net
* What is the main development mailing list for your organization?
The main development list is:
ffmpeg-devel at ffmpeg.org
You can find contact information for this and other mailing lists at
* Why is your organization applying to participate in Google Summer of
Code 2013? What do you hope to gain by participating?
We hope to involve more contributors in the community, gain
visibility, improve and extend our codebase, have an opportunity to
meet and discuss with other project developers thanks to the events
and the channels related to the program.
* Did your organization participate in past Google Summer of Codes? If
so, please summarize your involvement and the successes and challenges
of your participation.
FFmpeg participated to the Google Summer of Code editions of 2007,
2008, 2009, 2010, 2011.
You can find a comprehensive list of all the past applications and
* If your organization has not previously participated in Google Summer
of Code, have you applied in the past? If so, for what year(s)?
* Does your organization have an application template you would like to
see students use? If so, please provide it now.
* What criteria did you use to select your mentors for this year's
program? Please be as specific as possible.
Availability and qualification.
Mentors propose themselves based on their expertise in the domain area
for the mentored tasks, and on their skill and will to deal with
Mentors are usually veteran developers who delivered significant
contributions to the project and who deeply know the codebase, the
community and the resources around the project.
* What is your plan for dealing with disappearing students?
We will try to keep scheduled contacts with students during
qualification tasks to make sure they are reliable before they are
accepted. We'll also urge the student to provide periodical reports
in order to track their progress.
In case of a disappearing student, we'll try to get in touch with
him/her using all the possible channels at our disposal, and in case
the student can't be reached within a reasonable amount of time, we'll
declare his/her task failed.
* What is your plan for dealing with disappearing mentors?
We assign a backup mentor to each task. The GSoC admin will take the
responsibility to act as backup mentor in case the appointed mentors
will disappear during the project.
Also, we rely on the developers community to help the student to
accomplish the given task, in addition to the help provided by the
Since students will be urged to join IRC, they will likely get help
from other developers, even if the mentor is not available.
* What steps will you take to encourage students to interact with your
project's community before, during and after the program?
We'll recommend students to idle on IRC and we'll request them to read
and possibly participate in discussions on the main development
We will also try to create a friendly environment where the students
can freely participate and where they can find support from the
community. We rely on personal communication between student and
mentor in order to make the student acquainted with the community
We expect the accepted students to be future contributors, thus will
try to create an environment where the student is encouraged to assume
responsibility on the code that s/he will write during the task.
We hope the students will stay around after the task termination on
the ground that they will feel comfortable with the project community
and will have genuine interest in continuing their effort with it.
* Are you a new organization who has a Googler or other organization to
vouch for you? If so, please list their name(s) here.
* Are you an established or larger organization who would like to vouch
for a new organization applying this year? If so, please list their
More information about the ffmpeg-devel