Making Pitivi rock

Whether you are an artist, a software developer, a translator or an avid tester, you can help improve Pitivi. This page will help you get started. Do not hesitate to come have a chat with us online — or meet us at one of the various conferences/hackfests we attend!

Why contribute to Pitivi instead of another project?

In summary: when you contribute to Pitivi, your time is not lost.

Writing code

There are three main areas where you can contribute code:

Getting started

  1. Build the current development versions of Pitivi and GES (see the download page).
  2. Take a look at the "stuff to be done" and "developer documentation" sections below.
  3. Start your own git branch and dive into the code!

Come chat with us. We will gladly help you help started.

Stuff to be done in Pitivi

To have a rough idea of the work ahead, take a look at the Pitivi love page, the roadmap and the list of bug reports.

Developer documentation

The wiki is our main documentation. It has been completely reorganized in 2011 to make it easier for you to find what you're looking for right from the main page, be it our PyGST tutorial, the design specifications of core components or user interface components, how to interact with the project, etc. Go ahead, take a look at the developer documentation, and if you find incomplete or outdated information, please notify us (or edit the pages directly!).

Other ways to help

Translating

To be able to commit translations to Pitivi, you must be part of the GNOME translation team for your native language. If you simply want to report an error in a translation or suggest minor changes, simply file a bug about it, and add the "I18N" and "L10N" keywords after filing the bug.

Improving the user manual

We use Mallard to provide a high-quality, topic-oriented user manual. Help us by writing new topics, refining existing ones, or simply by reviewing and keeping the user manual up-to-date and ready for the next release.

Maintaining the wiki

Our wiki has many documentation pages that need to be updated, cleaned or made obsolete. Having an up-to-date and consistent wiki for contributors is important. Of course, we will provide guidance and help you towards this glorious goal.

Making suggestions and reporting bugs

We use the GNOME Bugzilla infrastructure to track enhancement requests and bug reports. Take a look at our bug reporting page for details and useful links.

Beer funds

If you really like the work we do, please consider donating for our 2014 fundraising campaign!