Contributing

Getting the Latest Source Code

MLT now uses the Git distributed version control system instead of the Subversion service provided by SourceForge.

You can get the latest version of the MLT framework source code (including mlt++ and other language bindings) using:

git clone git://mltframework.org/mlt.git or git clone http://mltframework.org/mlt.git

You can browse the repository through the web interface: http://mltframework.org/gitweb/mlt.git

You can fetch the latest version of the Melted Video Server source code (including libmvcp) using:

git clone git://mltframework.org/melted.git or git clone http://mltframework.org/melted.git

You can browse the repository through the web interface: http://mltframework.org/gitweb/melted.git

Contributing Code

The preferred way to receive code changes is by publishing your git repo and telling DanDennedy or the mailing list whenever you have something new or have updated something worthy of notice.

Otherwise, send patches to the mailing list. All patches must be in the unified diff format. Short patches can be in the body of the message. Long patches should be attached. Use your best judgment.

Any contributions to the framework and the core module must assign copyright to Ushodaya Enterprises Limited. Otherwise, you can copyright it in a name of your choosing unless, of course, you have integrated a fair amount of code that someone else wrote and copyrighted.

All contributions to the framework, mlt++, libmvcp, and the core module must be provided under the LGPL v2.1 license. All contributions to melt and melted must be provided under the GPL v2 or v3 license. Modules (plugins) can be offered under different licenses. If you are contributing to an existing module, then you must use the same license as the rest of the code in that module. If you are contributing to your own, new module, you can license however you choose. However, at this time, it must be a license compatible with Free Software to be included in the repository at mltframework.org.