Xfce Wiki

Sub domains
 

This is an old revision of the document!


Contributing to Xfce

Purpose of this document

At the time of writing (FOSDEM 2013), the entry barrier for contributing to Xfce is substantially higher than it could be. There are several hurdles that people have to figure out themselves. There is no easily accessible list of low-hanging fruit or tasks to get started with. Also, there is no defined, transparent contribution process. Our aim should be to make obvious to interested developers how they can contribute and what they can contribute.

The purpose of this document is to come up with a concept for providing low-hanging fruit to the developer community and a contribution process that removes uncertainty about what the right way/format of contributing code is. This document is only about contributing code since other areas, like translations, are already well documented.

Present State

Documentation on Contributing

The Get Involved page on the Xfce website has no information about contributing code at all. There is no documentation describing the contribution process. Possible tasks to work on are scattered across various areas of the Xfce wiki. Unless you know the wiki inside-out, you'll have a hard time finding these pages:

The Design SIG is an initiative that Xfce developers and designers use to collaborate on improving the user experience of Xfce in general. It's been quite successful in the last 1-2 years. However, the majority of Design SIG topics are complex and thus not necessarily useful for people looking to start contributing to Xfce.

The two wish lists are, unfortunately, rarely used by developers, if at all, so their usefulness is questionable.

Current Contribution Process

The current recommended (but undocumented) way to get started essentially is: subscribe to xfce4-dev@xfce.org, join us in #xfce-dev on IRC and start by fixing bugs filed on http://bugzilla.xfce.org. Code can be attached to bugs in the form of patches but that is up to contributors to figure out themselves and the desired patch format (ideally patches generated by git, with commit messages included) is not documented anywhere.

Proposals

Presenting Low-Hanging Fruit

Contribution Process