We take care of the common bits used between the multiple available desktop environments.

For example:

• devel/dbus
• graphics/poppler
• net/libproxy
• devel/xdg-utils
• misc/shared-mime-info

All members of gnome@, kde@, xfce@ and so on are free to join.

• KoopMast (kwm@)
• CharlieLi (vishwin@)

• AdriaanDeGroot (adridg@)
• GlebPopov (arrowd@)
• JasonHale (jhale@)
• LoicBartoletti (lbartoletti@)
• TobiasBerner (tcberner@)

• GuidoFalsi (madpilot@)

• NiclasZeising (zeising@)

• freebsd-desktop mailing list
• Currently: #freebsd-desktop on Libera IRC

• Gnome
• KDE
• Xfce
• Phabricator #desktop group
• desktop@ open issues
• DesktopIntegration

To be able to provide a more pleasant desktop experience the following tasks should be done:

NetworkManager itself cannot be ported due to a monolithic architecture and extensive Linux syscall use (for activating network interfaces, et al). The libnm interface can be implemented as a shim to an existing FreeBSD interface, if one exists.

It is currently recommended to remove anything that calls NetworkManager in any form in existing software.

consumers:

• qt5
• plasma desktop
• gnome

See: https://developer.gnome.org/NetworkManager/stable/spec.html

consumers:

• plasma5-discover
• gnome-software

See: https://www.freedesktop.org/software/PackageKit/pk-faq.html

• No sound on speakers out of the box on Realtek (0x0230) HDA CODEC, Lenovo laptop, bug#233398

List other services with lower priority here.

ConsoleKit2 is actively maintained again, and between it and logind, the interfaces are different. elogind cannot be directly ported to FreeBSD without a lot of work to remove or mitigate extensive Linux-isms, as it is effectively extracted from systemd.

consumers:

• gdm
• gvfs
• sddm
• desktop sessions
• lock screens and session managers in general

See: http://www.freedesktop.org/wiki/Software/systemd/logind