On Sun, Feb 9, 2014 at 3:18 PM, Janne Liljeblad <janne.liljeb...@gmail.com> wrote: > Hi Dan, > > After last release of Flowblade I realized that I need some new > filters for my application. Earlier I contributed Frei0r, but now I > have decided to switch my contributions from Frei0r to MLT mainly > because: > > - Frei0r is essentially dead. Maintainer isn't interested in doing new > releases, and I was the last active contributor anyway. > > - There is no way to know how quickly new plugins for Frei0r will land > on distributions. I think most of the ones I wrote a year ago are > still not available in e.g. Ubuntu.
Freshness of software in Linux distributions is a general problem. > - Contributing to MLT builds my expertise on the library and this is > useful for me in the long term as a MLT dependent application > developer. > > - I think MLT and GStreamer are the only reasonable alternatives for > developing FLOSS editing applications, so the "shared plugins between > projects" rationale for Frei0r no longer exists, even more so because > GStreamer/PiTiVi people never contribute to Frei0r. > > I have some questions on contributing to MLT: > > - There are two repositories, one on sourceforge and another one one > github. I'm assuming that the github one is the main one and > sourceforge exists for some additional reasons, right? github. There is no source repository on SourceForge for MLT, but we still use it for project files and bug tracker. > - Do you prefer github pull requests or git patches? yes > - Should I be contributing to "plus" module? Yes, if it does not have any external dependencies and is LGPL. > - If I'm porting code from Gimp that has "GPL2 or later" license I > think I can't add them to "plus" because all code there has LGPL 2.1 > license, right? Should there be a "plusgpl" module or something? I'm > not really sure how this works. That is a good idea. I already see a few modules that can be merged into a plusgpl such as effectv, dgraft, and rotoscoping. > - If I understood correctly you required copyright assignment for some > parts of the library but not others? yes, the framework and the core and avformat modules. > Some future directions that I'm interested in working: > - port useful code with compatible licenses. > - create a "cairo" module and reimplement the cairo mix transitions so > that I can drop the silly 0- 1 ranges. I also have some ideas for > other cairo based filters > - later help with bug fixes and other "core" features > > If there is something you think would benefit from my contributions, > let me know. Look for ways to improve the python binding for your own sake. Nothing really specific, but maybe you need a way to handle mlt_events. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
