On 28.05.2012 16:09, Michael Gapczynski wrote:
On Monday, May 28, 2012 06:37:57 PM Peter Chubb wrote:
there are use cases where it's important for the admin to br able to control
sharing, to prevent, say, corporate info lealing to unauthorised places.
Robin and I discussed the project yesterday and came to some conclusions.
The use case of sharing between two companies is extremely limited. The chance
of two companies that need to share files and both use ownCloud is very small.
I agree very much that its an rare case which, on the other hand, could
open doors at some customers. It thus should be an option in the
enterprise version imo.
The focus should be on sharing with individuals, in some syntax as Frank
discussed. Requiring admins to link ownClouds to allow inter sharing breaks
the workflow. Rather, as Peter points out, admins should be able to control
the instances that users can share to, if the admin decides that it needs to
be restricted. This can be implemented as a whitelist of ownCloud instances.
Yes, agreed.
I still believe this project could be used to design an api for the desktop
and mobile clients to use. The end goal should still be to allow for inter
owncCloud sharing. This means that the authentication, action listening, and
sharing logic needs to be separated.
Yes. Maybe you later on can share a more detailed plan.
Klaas
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
