Incubator/Projects/Kdenlive: Difference between revisions

From KDE Community Wiki
No edit summary
Line 52: Line 52:
* mailing list: should migrate to KDE
* mailing list: should migrate to KDE
* bugtracker: from mantis on own server to KDE's bugzilla
* bugtracker: from mantis on own server to KDE's bugzilla
* continuous integration (build.kde.org)


== Sponsor Checklists ==
== Sponsor Checklists ==

Revision as of 19:39, 25 August 2014

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

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.

Inclusivity

No barrier known toward the contributors.

Innovation

Common Ownership

Anyone can contribute directly.

End-User Focus

Commitments

  • Code of Conduct: ?
  • Contributor License Agreement: none
  • Established practices: CMake + Qt like most, code reviews except for most active core contributors ?
  • 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)

Candidate ready

Status Description Notes
DONE Project description ...
IN PROGRESS Project team awaiting answers from mailing list
IN PROGRESS Manifesto compliance plan requires some checks

Incubating

Status Description Notes
TO DO Repository and code available (in playground) ... <{{{3}}}>
TO DO Mailing list available ... <{{{3}}}>
TO DO Website available (if applicable) ... <{{{3}}}>
TO DO Active community ... <{{{3}}}>
TO DO Manifesto compliance ... <{{{3}}}>