=Description=
As a developer the highlights of my KDE "career" are when I see KDE used in projects that really matter.
Seeing it in screenshots of CERN, news of Munich and Pardus are what make the hours worthwhile.
We're losing our famous Munich deployment (albeit not due to us), we should strive to replace that with 2 more! Or 10 more!
My proposal is to build on all the things that make KDE software deployable in an office / enterprise environment. Plasma's goal is about productivity, that's more important in a work or university environment than in the home.
=What it will take=
This means b* Better LDAP integration in Plasma, p
* Password expiry support, network printer settings.ort
We need documentation that is up to date for sysadmins with all override keys documented. We need hooks throughout the system for custom overrides in all location* Decent network printer settings.
We need LTS focu* Documentation that is up to date for sysadmins with all override keys documented. We need hooks throughout the system for custom overrides in all locations.
We need* Configuration support for mounts on NFS and SMB that doesn't cause stability issuest to allow more admin based control, allowing updates to the system at any time.
..* Support for mounts on NFS and SMB that doesn't cause stability issues.
* Anything else we find from outreach with existing enterprise deployments.
We need LTS focus, and a priority on bug handling.
And possibly most importantly of all we need whitepapers of successful deployments flooding promo.
It's an area that stretches out across all areas from Plasma and Frameworks to UX and outreach.
=How we know we succeeded=
SLED and RHEL ship plasma out the box due to customer demand.
=Relevant links=
=I am willing to put work into this=
* David Edmundson
* Nate Graham (@ngraham)
* Ilya Bizyaev (@IlyaBizyaev)
=I am interested=
* Méven Car (@meven)
* David Strobach (@strobach)