Request: A beginner's guide to dive into xfce development

Romain B skunnyk at
Thu Nov 2 22:40:45 CET 2017


Oh, and don't forget to open a bug on with 
your patches assigned to the correct component :)

We need to improve our "beginner's guide": / , and maybe only keep only one 
version, there is lot of duplicate content between the "open" wiki.x.o 
and docs.x.o , help needed ! ;)

On 11/02/2017 09:24 PM, Alex wrote:
> Hi Hanno,
> always happy to see that somebody wants to contibute !
> Andre already told most of the stuff I wanted to tell ;) ... just a few
> more notes regarding the workflow for gtk3 porting:
> - Clone the related repo and do your changes ( in the branch of your
> choice )
> - When everything works fine with gtk3 and you think you fixed all
> regressions, ask some other devs to test your changes. Either post a
> link to your patch on #xfce-dev, or provide a fork of your repo e.g. via
> some public git webhoster.
> ( Infrastructure-people are currently evaluating to move the xfce repos
> to gitea ... so hopefully we will have support for pull-requests soon )
> - After others tested and approved your patch, either it will be applied
> on master, or you will get permissions to do so yourself.
> Probably you will have more questions ... feel free to ask! But remember
> to be patient, these people all have a real-life. Unfortunately most of
> them need to go to work and such things :X
> So best get some irc-bouncer ( I use a free one from
> and idle in #xfce-dev on freenode to keep track on ongoing changes.
> Cheers,
> Alex ( alexxcons)
> On 02.11.2017 03:26, André Miranda wrote:
>> Hi Hanno,
>> As Igor suggested, join #xfce-dev and let us know what parts of Xfce
>> you're more interest to work on, what's missing and etc.
>> New features and enhancements are not the currently our focus, but are
>> welcome and might be released in 4.14.
>> Things are slow due the port, it's far from exciting, but most of the
>> job is done, only few apps and some plugins need work, obviously the
>> ones that are not so popular. If by any chance you use one of them, I
>> suggested that you try to port it to gtk3.
>> Another way to help with the migration is to test development releases
>> and report regressions (patches are a plus), some components (e.g.
>> panel and thunar) still have pending regressions to be solved. If
>> you're interested ask for directions on #xfce-dev (please be patient,
>> we're all volunteers in multiple timezones).
>> All in all, independent of the OSS project, you can always start
>> "scratching your own itch"[1], that's how I started a few years ago,
>> fixing bugs that annoyed me and making small improvements (e.g.
>> closing windows with middle-click on panel).
>> 1 -
>> Cheers,
>> Andre Miranda
>> On 11/01/2017 11:28 AM, Hanno Zulla wrote:
>>> Hi there,
>>> it would be helpful to have a Wiki document that will guide a
>>> semi-interested beginning developer to dive into contributing.
>>> I did read these
>>> But right now, I'm at a loss at where to start. XFCE is a big code base
>>> and it's unclear which parts need work.
>>> There's status information on the roadmap, but some entries there have a
>>> percentage > 0 yet haven't been worked on in a while, so apparently work
>>> on them has stalled.
>>> The roadmap states that the current focus is on the GTK transition, yet
>>> the Wiki suggests that a beginning developer should try to fix easy bugs
>>> instead.
>>> So it's difficult to find a good entry to contributing. It's unclear
>>> which branch to work on, where to fix bugs, the proper way to contribute
>>> patches or how to choose a subproject that needs work and e.g. what are
>>> the common steps of GTK transition work.
>>> Kind regards,
>>> Hanno
>>> _______________________________________________
>>> Xfce4-dev mailing list
>>> Xfce4-dev at
>> _______________________________________________
>> Xfce4-dev mailing list
>> Xfce4-dev at
> _______________________________________________
> Xfce4-dev mailing list
> Xfce4-dev at

More information about the Xfce4-dev mailing list