Kdenlive

Sponsor: Mario Fux <fux_AT_kde..org>

Kdenlive is an intuitive and powerful multi-track video editor, including most recent video technologies. It relies on several other open source projects, such as FFmpeg, the MLT video framework and frei0r effects. Our software was designed to answer all needs, from basic video editing to semi-professional work. More information on the Kdenlive website kdenlive.org.

Team

List the people committed to the project and actively working on it:

Vincent Pinon
Simon Eugster
Till Theato
Steve Guilford
Jean-Nicolas Artaud

Manifesto Compliance Plan

List the actions planned to get in compliance with the manifesto. Don't hesitate to even list parts of the manifesto which don't require action and highlight why. This part will really be used as a discussion starting point with the project sponsor.

Values

Open Governance

Already open governance to some extent, anyone with a KDE account can contribute, mailing list and IRC available.

Focus point: mailing list under used?

Free Software

Mainly GPL v2, GPL v3+. Some included 3rd party library use different licenses. There were recent checks and Vincent committed some fixes (=> some old Bezier code, found in other places in KDE, is under unclear license, need feedback from people with better understanding of the topic; maybe could be rewritten if necessary)

Inclusivity

No barrier known toward the contributors.

Innovation

…

Common Ownership

Anyone can contribute directly.

End-User Focus

Functionality is already at a high level, focus is currently dedicated to reliability. Problems reported on forums and tracker are rapidly analyzed, trying to find an immediate workaround, and then fixed in the code. Mature UI still gets polished progressively.

Commitments

Code of Conduct: KDE Community Code of Conduct
Contributor License Agreement: none
Established practices: CMake + Qt like most, reviewboard to send patch (no real code reviews as long as patches are small)
Source materials hosted on KDE git infrastructure
Online services are not on KDE infrastructure: website (some info/documentation and blogs) and bugtracker on own server, mailing list on sf.net, release source tarballs and forum on KDE
KDE Licensing policy: ? (see point "Free Software")
KDE branding guidelines: ?
No patents

Proposed actions:

website: uses drupal, hosting on KDE?
mailing list: should migrate to KDE
bugtracker: from mantis on own server to KDE's bugzilla
continuous integration (build.kde.org)

Sponsor Checklists

Candidate ready

Status	Description	Notes
DONE	Project description	...
DONE	Project team	replies from mailing list correspond to Git activity
IN PROGRESS	Manifesto compliance plan	requires some checks

Incubating

Status	Description	Notes
TO DO	Repository and code available (in playground)	As code is already on git.kde.org as normal project, is it worth moving it twice? Disturbing people pointing to the repo (eg Ubuntu PPA builders). But not blocking, this can be done	<{{{3}}}>
IN PROGRESS	Mailing list available	Looking for SourceForge admin rights, if not possible just abandon old list for a new one?
IN PROGRESS	Website available (if applicable)	Asked for page under KDE domain, need to check about content transfer
IN PROGRESS	Active community	Several users are active on forums, few developers on code (hopefully more in future?!)
IN PROGRESS	Manifesto compliance	Who to ask help on this topic?