dLeyna updates and general project things

I have too many projects. That’s why I also picked up dLeyna which was laying around looking a bit unloved, smacked fixes, GUPnP 1.2 and meson support on top and made new releases. They are available at

  • https://github.com/phako/dleyna-core/archive/refs/tags/v0.7.0.tar.gz
  • https://github.com/phako/dleyna-connector-dbus/archive/refs/tags/v0.4.0.tar.gz
  • https://github.com/phako/dleyna-server/archive/refs/tags/v0.7.0.tar.gz
  • https://github.com/phako/dleyna-renderer/archive/refs/tags/v0.7.0.tar.gz

Furthermore I have filed an issue on upstream’s dLeyna-core component asking for the project to be transferred to GNOME infrastructure officially (https://github.com/intel/dleyna-core/issues/55).

As for all the other things I do. I was trying to write many versions of this blog post and each one sounded like an apology, which sounded wrong. Ever since I changed jobs in 2018 I’m much more involved in coding during my work-time again and that seems to suck my “mental code reservoir” dry, meaning I have very little motivation to spend much time on designing and adding features, limiting most of the work on Rygel, GUPnP and Shotwell to the bare minimum. And I don’t know how and when this might change.

1 thought on “dLeyna updates and general project things

  1. The long term maintainance of projects running on volunteer-time only, is a very general problem in open source and I can’t really suggest how/what you can do here. Also it’s very understandable if you find it hard to continue to be motivated for the work.

    However, I can tell you one thing: You must not feel guilty about not being able to give enough maintenance time for things you’re not getting paid to do. You’ve done an awesome job with maintaining and developing GUPnP and Rygel after I left. Take pride in that!

Leave a Reply to Zeeshan Ali Cancel reply

Your email address will not be published. Required fields are marked *