[Owncloud] Group backend question

[Michael Gapczynski]

I chose to store group shares in that fashion because it would allow users
to rename the file only on their end or unshare it from their selves. Of
course this means that a new entry needs to be created if a new group
member is added. I was going to have all of those entries show up as just
the group name in the drop down, but I haven't gotten around to this. The
main reason I haven't fixed these problems is because I believe groups
needs to be expanded and possibly a separate grouping mechanism for
sharing.

The current implementation of groups in ownCloud is only used for checking
admin status and only admins can create/modify groups. In terms of sharing
this is alright for enterprise, but it isn't ideal for a normal user who
may want to group people together for quick sharing on a reoccuring basis.
In my mind this is a different definition of groups and so it may break off
from the group backend. For the future of sharing in ownCloud I envision
sharing becoming more focused on a user's contacts rather than users of the
same ownCloud instance. I'm still formulating these changes in my head.

Michael

On Wed, Feb 1, 2012 at 11:58 AM, Dirk Kastens <
dirk.kastens at uni-osnabrueck.de> wrote:

> Hi,
>
>
>  You're right, the group system isn't build for multiply backends yet.
>>
>> Changing it to behave simular to the users system has been a plan for a
>> while
>> but I never got to it.
>>
>
> I've nearly finished writing an ldap backend for groups. It depends on the
> user_ldap app and adds a search path and some attributes for posixgroups. I
> had to change the lib/group.php, lib/group/database.php, and
> lib/group/backend.php.
>
> In the admin user menu I see my ldap users and the local group and
> posixgroup memberships of each user, and I can share my files with members
> of a posixgroup.
>
> The only drawback is the implementation of group file sharing (that's
> independent from my ldap groups). If I share a file with a group, owncloud
> makes an entry of the form user at group for each group member in the
> oc_sharing table of the database. So it doesn't support dynamic group
> memberships. If there are new members in a group, they are not allowed to
> access the shared files. And if a user has been deleted from a group he can
> still access the shared files. Another drawback is, that if you have a big
> group with, let's say, 100 members, there are 100 entries made in the
> database table. And if you want to disallow the sharing, you have to delete
> the 100 members individually from the sharing menu. That's very
> uncomfortable.
>
> If you share a file with a group, there should be a single entry in the
> database, like @group. The members should be evaluated dynamically, IMO.
>
> Dirk
>
>
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20120201/a2102a9a/attachment.html>