Hi Jimmy, First of all thank you Jimmy for providing this feedback, any help you and others can provide to help us build the requirements list for the various usecases is great. I will make sure to take your points with me as part of the continued working group effort and tasklist. Christian On Wed, 2013-11-06 at 15:32 -0500, Jimmy Dorff wrote: > > “Case 4” in the Product Description is the most important for me. The is > where I work in a university, but I know some commercial orgs that work > similarly. My developers are writing code and analyzing data. They are not > building or contributing to Fedora. Key tools are C, C++, python, R, > Matlab, Octave, plus git and svn. > > We use enterprise logins (ldap + MIT krb5). Desktops are NFS clients, data > is stored on file servers. Desktops often have multiple displays. > > Desktops are professionally managed. The level of developer admin is going > to vary based on the organization. Generally the developer isn’t > installing the workstation. Home directories are centrally stored and > preserved across updates. > > In summary: > * enterprise logins (large numbers of users and groups) > * network filesystems (NFS, SMB, etc..) > * centralized network and desktop management (lots of great tools exist) > > Cheers, > Jimmy -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
