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

[André Miranda]

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 - 
http://gezeiten.org/pre-2014/post/2012/11/How-to-start-contributing-to-Xfce-or-any-other-open-source-project

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
>
> https://wiki.xfce.org/releng/4.14/roadmap
> http://docs.xfce.org/xfce/building
> http://docs.xfce.org/contribute/dev/get-a-contributor-account
>
> 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 xfce.org
> https://mail.xfce.org/mailman/listinfo/xfce4-dev