Using an LDAP directory server to host the user database could be a good idea.
But transfering that database to LDAP just for the sake of using LDAP is a bit light...
If you're going to go the LDAP way, you might consider trying to give some "value-added" stuff. LDAP use is often justified by the need to come closer to the "single-logon" utopia. User profile is stored in a central place and used to control access to hosts, e-mail, etc.
I could see a use for LDAP authentication in the following scenario: an organization is hosting multiple scoop sites, each dedicated to a particular subject (or targeted at a particular audience), but wants it's users to have only one user/password for convenience, since a user might be interested in more than one scoop site.
I've downloaded scoop recently to "test-drive" it in the company I work for. We're just starting playing with the tool, but I can already see a need for that type of functionnality.
Another feature that could be interesting -- but I'm not sure it a job for scoop -- is to provide a "portal" view of multiple scoop sites, something like a MyNetscape but for scoop sites. Since scoop supports RSS (right?), this might already exists.
