• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-585
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Soft Linden
Votes: 25
Watchers: 11
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

Use same group policy for group-owned and group-shared objects

Created: 27/Aug/07 04:26 PM   Updated: 17/Jul/09 12:05 PM
Component/s: Groups, Simulation
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates
 


 Description  « Hide
At present, group objects behave in different ways:

Group-set objects = no extra group permissions
Group-shared objects = anyone in a group can manipulate or return
Group-deeded (-owned) objects = only members in roles with various permission can manipulate or return

The group-shared role is confusing, as per the constantly resurfacing SVC-121 issue.

The proposal is to treat group-shared objects the same as group-deeded objects, so that extra permissions are only granted to members with manipulate or return permissions.

Would this be more clear? Can any point to existing group usage this would break?

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Soft Linden made changes - 27/Aug/07 04:27 PM
Field Original Value New Value
Link This issue is related to by SVC-121 [ SVC-121 ]
Rob Linden made changes - 22/Dec/07 01:05 AM
Workflow jira [ 14902 ] jira-2007-12-21 [ 20854 ]
Rob Linden made changes - 22/Dec/07 01:31 AM
Workflow jira [ 20854 ] jira-2007-12-21 [ 22323 ]
Rob Linden made changes - 23/Dec/07 12:16 AM
Workflow jira-2007-12-21 [ 22323 ] jira-2007-12-22a [ 48358 ]
Rob Linden made changes - 23/Dec/07 12:35 AM
Workflow jira-2007-12-21 [ 48358 ] jira-2007-12-22a [ 49420 ]
Harleen Gretzky made changes - 31/Jan/08 10:46 PM
Link This issue is related to by SVC-1366 [ SVC-1366 ]
McCabe Maxsted made changes - 12/Aug/08 07:23 PM
Component/s Groups [ 10222 ]
McCabe Maxsted made changes - 13/Aug/08 05:40 PM
Link This issue is related to by VWR-5491 [ VWR-5491 ]
Sue Linden made changes - 13/Nov/08 12:02 PM
Workflow jira-2007-12-22a [ 49420 ] jira-2008-11-14 [ 80274 ]
Sue Linden made changes - 13/Nov/08 04:27 PM
Workflow jira-2008-11-14 [ 80274 ] jira-2008-11-14a [ 86176 ]
Sue Linden made changes - 13/Nov/08 04:40 PM
Workflow jira-2008-11-14 [ 86176 ] jira-2008-11-14a [ 90199 ]
Sue Linden made changes - 13/Nov/08 04:49 PM
Workflow jira-2008-11-14 [ 90199 ] jira-2008-11-14a [ 93002 ]
Soft Linden made changes - 23/May/09 11:10 PM
Description At present, group objects behave in different ways:

Group-set objects = no extra group permissions
Group-shared objects = anyone in a group can manipulate
Group-deeded (-owned) objects = only members in roles with "manipulate" permission can manipulate

The group-shared role is confusing, as per the constantly resurfacing SVC-121 issue.

The proposal is to treat group-shared objects the same as group-deeded objects, so that extra permission is only granted to members with "manipulate" permissions.

Would this be more clear? Can any point to existing group usage this would break?
 At present, group objects behave in different ways:

Group-set objects = no extra group permissions
Group-shared objects = anyone in a group can manipulate or return
Group-deeded (-owned) objects = only members in roles with various permission can manipulate or return

The group-shared role is confusing, as per the constantly resurfacing SVC-121 issue.

The proposal is to treat group-shared objects the same as group-deeded objects, so that extra permissions are only granted to members with manipulate or return permissions.

Would this be more clear? Can any point to existing group usage this would break?
Soft Linden made changes - 17/Jul/09 12:05 PM
Link This issue is original of duplicate SEC-410 [ SEC-410 ]

Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators