Hi all,

I'm following up on my RFS for lamco-rdp-server (Bug #1127979). The package has 
been on mentors since mid-February and has gone through several rounds of 
review. I'm still looking for a DD sponsor.

Quick status:

* v1.4.1-1 is on mentors.debian.net, targeting non-free/net
* Salsa CI is green: https://salsa.debian.org/glamberson/lamco-rdp-server
* All reviewer feedback has been addressed (Tobias Frost x4, Fabio Fantoni x6)
* Full DEP-5 copyright covering 857 vendored crate dependencies
* Proper lintian-overrides (not CI suppressions)
* Desktop file, AppStream metainfo, and icons installed
* gbp workflow on Salsa (upstream/latest, debian/latest, pristine-tar)

The package is a native Wayland RDP server written in Rust, built on IronRDP. 
It works across compositors (GNOME, KDE, Sway, Hyprland) with automatic backend 
detection, supports H.264 encoding, VA-API hardware acceleration, clipboard 
sync, and has a configuration GUI.

The challenge I've run into is finding a sponsor who works in both Rust and the 
remote desktop domain. Tobias Frost gave a thorough initial review but declined 
to sponsor because he doesn't work in Rust. Fabio Fantoni has been giving 
helpful packaging feedback but hasn't offered sponsorship. I also emailed 
debian-rust about the vendoring approach on Feb 16 and didn't get a response.

The vendoring is necessary because several upstream IronRDP crates I depend on 
aren't published to crates.io yet, and others carry my upstream patches that 
haven't been released. The vendor tarball includes all sources with full 
license enumeration in d/copyright.

If anyone here is willing to sponsor a non-free Rust package, or can point me 
toward someone who might be, I'd really appreciate it.

RFS: https://bugs.debian.org/1127979
Mentors: https://mentors.debian.net/package/lamco-rdp-server/
Salsa: https://salsa.debian.org/glamberson/lamco-rdp-server
Upstream: https://github.com/lamco-admin/lamco-rdp-server
Product Website: https://lamco.ai/products/lamco-rdp-server/

Thanks,
Greg Lamberson
[email protected]

Reply via email to