News and Meetings‎ > ‎(GSoC 2013)‎ > ‎

Our application



-Organisation description

TuttleOFX is an open source image sequences processing framework made up of :

- a set of plugins to read and write professional VFX image formats and to perform various image processings (color corrections, filters, video compression, ...)

- a set of command line tools called Sam to browse, copy, move, delete and batch process the aforementioned plugins.


The aim of TuttleOFX is to help post-production facilities to deal with large-scale everyday image processing tasks. Compared with other programming libraries and image processing tools, TuttleOFX is based on some extended OpenFX plugins architecture, combined with optimised selection bit-depth processing.


In addition of standard process features, TuttleOFX also addresses requested VFX processes like lens-distort corrections or movie compression and even some more specific color treatments like Color Transform Language and OpenColorIO nodes.


Thanks to their OpenFX nature, TuttleOFX plugins can be used either in the Sam command line tool or by other applications such as Nuke® (The Foundry), Scratch® (Assimilate), Baselight® (FilmLight), Mistika® (SGO). Similarly, commercial OpenFX plugins (Sapphire, Furnace, Keylight, ...) can be used within Sam command line.


-Our participating members

Fabien Castan, fabcastan, https://github.com/fabiencastan (GSoC username : fabcastan)
Marc-Antoine Arnaud, arnaud.marcantoine, https://github.com/MarcAntoine-Arnaud (GSoC username : marcantoine)
Marie Fétiveau, marie.fetiveau, https://github.com/mfe (GSoC username : mfe)

-List of our administrators

Primary administrator :

Marie (mfe)


Backup administrator :

Fabien (fabcastan)


-List of our mentors

Fabien (fabcastan)

Marc-Antoine (marcantoine)

Marie (mfe)


-List of our reviewers

Fabien (fabcastan)

Marc-Antoine (marcantoine)

Marie (mfe)


-Why is your organization applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?

GSoC is a great opportunity for us to bring enthusiastic new members to our community. We also hope that we’ll enrich TuttleOFX with some new cool features.

And of course, being more visible in Open source community will be priceless for us to gain more and more interactions with potential users and developers.


-Has your organization participated in past Google Summer of Codes?

No.


-If your organization has not previously participated in Google Summer of Code, have you applied in the past?

No, first time application.


-What Open Source Initiative approved license(s) does your project use?

TuttleOFX project is published under multi-licensing, so users can choose between:

  • TuttleOFX Public License, version 1 (**less restrictive version of LGPL**), see LICENSE.TuttleOFX file.

  • GNU Lesser General Public License, version 3 (**LGPL**), see LICENSE.LGPL file.

  • GNU General Public License, version 3 (**GPL**), see LICENSE.GPL file.

This multi-licensing scheme applies to the whole project: applications, libraries and plug-ins.


-What is the URL for your Ideas list?

https://sites.google.com/site/tuttleofx/gsoc-2013/ideas-list


-What is the main development mailing list for your organization?

tuttleofx-dev@googlegroups.com


-What is the main IRC channel for your organization?

#tuttleofx on freenode.


-Who will be your backup organization administrator?

Fabien Castan, username : fabcastan.


-What criteria did you use to select the mentors? Please be as specific as possible.

All of them are main contributors of TuttleOFX. They have a great knowledge of the code and a willingness to move forward and make TuttleOFX a great project.

Beside, they already successfully mentored several non GSoC student projects. Some of these projects lead to useful plugins and features like debug of Text and viewer plugins, Histogram and Color Keyer plugin, Denoise plugin... One of our last student projects is ButtleOFX, a pretty nice nodal GUI for TuttleOFX.


-What is your plan for dealing with disappearing students? Please be as specific as possible.

First, we’ll ask the student to be connected on our IRC channel during his day work.

We’ll also encourage him to push at least once a day. If he can’t push, he’ll have to send an email reporting his daily task or at least have a talk (chat or IRC) with his mentor about it (this will also ensure that he won’t stay blocked by something too long).


Mentor and student will have to hang out (or chat ) once a week. After the meeting, a quick report (summary of achieved tasks and next tasks to be done) will have to be sent by the student to every people involved (his mentor, his back-up mentor(s) and administrators).


If a student forget to push or send an email, he’ll be warned. If he didn’t answer for several days, in accordance with his mentors, he’ll be disqualified and it’ll be pity for everyone. We’ll try as much as possible to never reach that dramatic point.


Students will be warned about these rules.


-What is your plan for dealing with disappearing mentors? Please be as specific as possible.

Our mentors are main and active contributors (commits every weeks since 3 years). They also are friends now, we meet regularly in real life. It’s quite unlikely for them to disappear.

With GitHub, it will be pretty easy to see if the interactions between students and mentors are fulfilled. We’ll also encourage mentors to code review with comments.


That being said, if a mentor really disappears, we’ll ask the back-up mentor to take charge.


-What steps will you take to encourage students to interact with your project's community before, during and after the program?

First, we’ll encourage them to follow the TuttleOFX google+ page to remain informed on main TuttleOFX events.

As said before, they’ll have to be present on our IRC during the summer of code. We hope that this will become an habit. We’ll also advice them to ask main questions on the dev google group such as answers will benefit the whole community.


-What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?

We hope that by participating, students will gain interests and want to stay in touch with their work until the corresponding final release and then become an active member of the community. We also are counting on to pass on them our enthusiasm for TuttleOFX.


-Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.

Mashiat Sarker Shakkhar can vouch for us. He participated as a student in 2011 (for FFmpeg) and as a mentor in 2012 (for Libav). 
He also mentored for Videolan during Google Code-in 2011 and regularly contributes to TuttleOFX.

Comments