For a more in-depth look at how to contribute to Xfce, as a developer, it is recommended to read The Ultimate Contributor's Guide to Xfce for more information.

• To request a contributor account, please see the docs for more information.
• Before getting involved with development, it may help to check the current roadmap to get an overview of our current progress.
• A guide to using GIT, in coordination with Xfce, can be found here.
• For more information on making a release, see Making a Release.
• Xfce API documentation can be found on the Xfce development Wiki.

There are various ways to get in touch with Xfce developers:

• For general questions, Xfce's Forum, the Xfce mailing list, and our IRC channel #xfce on Freenode are the places to go.
• For any translation stuff, join the Xfce-i18n mailing list.
• For anything code related, go to the Xfce-dev mailing list, or our IRC channel #xfce-dev on Freenode.

All Xfce developers have a real life and live across multiple time zones. If you don't get an answer straight away, be patient and stay online!

(lists excerpted from The Ultimate Contributor's Guide to Xfce)

• Use whatever text editor/IDE you are comfortable with.
• The terminal is your friend, get used to it, then you will love it.
• Now that almost all components are gtk3-based, GtkInspector is an invaluable tool.
• Offline documentation browser such as Devhelp and Zeal are faster and more convenient than using a web browser.
• Glade is a WYSIWYG interface editor, many Xfce components have their UI created using this editor.
• D-Feet is useful when dealing with D-Bus.
• Tricky bugs will need advanced tools to find their cause, in this case gdb and valgrind are good companions.
• Xorg’s utilities, for instance xev and xprop.

• How to start contributing to Xfce or any other open source project
• The GTK Project pages
• The GLib/GTK+ Development Platform
• Pro Git
• See the Xfce/Git page for additional reference material on using Git

Back To Top