[Index] [TitleIndex] [WordIndex

Site Index:

How can I help with Freevo Development?

There are a number of ways you can help. The most obvious one is to work on features that you'd like to see implemented. Read the WishList (user ideas, roadmap) and mailing list archives to see what has been said before about specific features. Please read the section on patches below before you submit anything.

We also need help from people on external programs. Please read HelpNeeded for Freevo 2.0 for details. You can also help by updating the user documentation in this wiki and answering questions from other users on the mailing lists or help with translations (see Translations).

Code Management

Kaa modules (required by Freevo) and Freevo are hosted on GitHub.

Repository Overview

Test Installation of Freevo 1 (moved)

See SourceSVNInstallation


Note: We know our rules place a burden on you, but rest assured that maintaining a big and complex software project is even harder, so please accept our rules. We cannot afford to spend our time fixing buggy, broken or outdated patches.

Having said that, we also appreciate your help of course!

  1. Always make patches against the subversion version. The main website describes how to check out subversion. We do not accept patches for releases or outdated subversion versions.
  2. Make unified diffs (use diff -Naur)

    1. Check out a fresh copy of Kaa and freevo from the repositories (see above)
    2. Outside run svn diff freevo > xmms_playlists.patch

    3. Test your patch! cd freevo ; patch -Np1 -i ../xmms_playlists.patch

  3. Make sure the patch is clean! Common mistakes are patches that include changes to local_conf.py.

  4. Test the functionality of your patch. We'll refuse it if it breaks something, even if it extends other features!
  5. Read your patch. We'll refuse it if it doesn't follow the CodingStandard. Pay particular attention to using spaces, not tabs.

  6. Comment parts that need it (tricky side-effects etc). Include module and function docs using """Comment""" below each function etc.

  7. Include documentation for new/improved features in the Wiki format. After the patch is accepted you are expected to add the docs to the Wiki and keep it updated.
  8. Add your patch to the Freevo Tracker

    1. New features go into Freevo Feature Request Submit New

    2. Bug fixes go into Freevo Bugs Submit New

  9. Describe in a few sentences what you change and why. If you made independent changes, try to send them as separate patches. The Summary line is for a short description on the patch and the Detailed Description box is to describe in a few sentences what you change and why. If you made independent changes, please submit them as separate tracker items.

  10. Submitting patches directly to the freevo-devel mailing is not such a good idea as attachments are sometimes converted to DOS format, and will not apply, and they can be lost in the other messages.
  11. You should receive a response to your patch within a week or so. If not, please post a polite reminder in the tracker item or to the freevo-devel mailing list!

If you are not using subversion version of Freevo and would still like to submit a patch, it is possible to supply a unified diff by diff -Naur path/to/original-file path/to/changed-file > /path/to/my.patch, where path/to/files can also be directories to include a patch for multiple files. It is best executed from the directory containing the freevo directory.

2014-02-15 05:10