
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Relates
|
|
This issue Relates to:
|
|
|
MISC-1277 Request for policy clarification concerning cross-grid copying of assets
|
|
|
|
|
|
This issue is related to by:
|
|
|
SVC-701 Copyright/license/notes fields on assets, to allow proper attribution and provide license and configuration information.
|
|
|
|
|
|
SVC-2621 Meta-Issue: New/modified permissions
|
|
|
|
|
|
|
| Linden Lab Issue ID: |
SL-56004
|
Being an open sourcer and also being intrigued by the creativity sparkled by open environments (e.g. the ability to remix/mashup CC content) what I'd really like to see is a GPL style permission inside SL.
So far permissions in SL seem to exist primarily to serve commercially oriented creators. It is of course possible to leave builds full perm but from my experience a whole lot (and far too many) end up in boxes or remixed with commercial builds, to the point where some stuff which started free/full perm is hard to find in it's original form.
In the real world, open content has established sort of a parallel continuum where creation exists apart from commercial interest an where creativity and cooperation is creating results which match or even surpass the quality of the commercial realm. Part of this success seems to come from the fact that the tools (licenses) now exist (tagging something as GPL, MIT or CC) to serve the intent of creators who wish to contribute to that part of life.
My suggestion therefore is to create a permission flag for SL content that expresses the intent of the creator that the creation shall remain free and open, available for reuse/mix/mashup but only with other parts and results remaining the same (free and open).
This could work in the same way as the current "next owner" rights, probably with two additions:
- splitting resell and give away into two permissions, ensuring that the item may be given away but not sold.
- next owner may not restrict permissions (limiting to the next owner's ability to set any of the "no" flags)
There are probably other combinations which I'm overlooking or details I'm missing that can be worked out through the comments on this JIRA but essentially with those extended permissions it should be prevented to link or embed the builds into/with other builds that do not carry the Open Content flag.
It's also clear that this can be circumvented in the same way as current permissions (that is copybotting, texture copying, etc.). It may also become difficult in terms of scripts, but scripts have the benefit of being able to include a license header into the script to express the creators intent and this seems to work sufficiently well already with AO scripts.
So, I don't expect it to be more successful than the current permission set in that regard, but now with Linden Labs making a clear commitment to Open Source with the system itself (viewer source, other parts), I think there should be an equivalent in world that gives open content creators the same tools that closed content creators currently have.
I'd like to solicit discussions of details here, this is intended merely as a starting point to sort out the details.
|
|
Description
|
Being an open sourcer and also being intrigued by the creativity sparkled by open environments (e.g. the ability to remix/mashup CC content) what I'd really like to see is a GPL style permission inside SL.
So far permissions in SL seem to exist primarily to serve commercially oriented creators. It is of course possible to leave builds full perm but from my experience a whole lot (and far too many) end up in boxes or remixed with commercial builds, to the point where some stuff which started free/full perm is hard to find in it's original form.
In the real world, open content has established sort of a parallel continuum where creation exists apart from commercial interest an where creativity and cooperation is creating results which match or even surpass the quality of the commercial realm. Part of this success seems to come from the fact that the tools (licenses) now exist (tagging something as GPL, MIT or CC) to serve the intent of creators who wish to contribute to that part of life.
My suggestion therefore is to create a permission flag for SL content that expresses the intent of the creator that the creation shall remain free and open, available for reuse/mix/mashup but only with other parts and results remaining the same (free and open).
This could work in the same way as the current "next owner" rights, probably with two additions:
- splitting resell and give away into two permissions, ensuring that the item may be given away but not sold.
- next owner may not restrict permissions (limiting to the next owner's ability to set any of the "no" flags)
There are probably other combinations which I'm overlooking or details I'm missing that can be worked out through the comments on this JIRA but essentially with those extended permissions it should be prevented to link or embed the builds into/with other builds that do not carry the Open Content flag.
It's also clear that this can be circumvented in the same way as current permissions (that is copybotting, texture copying, etc.). It may also become difficult in terms of scripts, but scripts have the benefit of being able to include a license header into the script to express the creators intent and this seems to work sufficiently well already with AO scripts.
So, I don't expect it to be more successful than the current permission set in that regard, but now with Linden Labs making a clear commitment to Open Source with the system itself (viewer source, other parts), I think there should be an equivalent in world that gives open content creators the same tools that closed content creators currently have.
I'd like to solicit discussions of details here, this is intended merely as a starting point to sort out the details. |
Show » |
made changes - 24/Sep/07 11:52 AM
| Field |
Original Value |
New Value |
|
Summary
|
Creative Commons/Open Content/GPL style permission for SL Items
|
"Open Content" (Creative Commons/Open Source/GPL style) permission for SL Items
|
made changes - 24/Sep/07 12:27 PM
|
Description
|
Being an open sourcer and also being intrigued by the creativity sparkled by open environments (e.g. the ability to remix/mashup CC content) what I'd really like to see is a GPL style permission inside SL.
So far permissions in SL seem to exist primarily to serve commercially oriented creators. It is of course possible to leave builds full perm but from my experience a whole lot (and far too many) end up in boxes or remixed with commercial builds, to the point where some stuff which started free/full perm is hard to find in it's original form.
In the real world open content has established sort of a parallel continuum where creation exists apart from commercial interest an where creativity and cooperation is creating results which match or even surpass the quality of the commercial real. Part of this success seems to come from the fact that the tools now exist (tagging something GPL or CC) to serve the intent of creators who wish to contribute to that part of life.
My suggestion therefore is to create a permission flag for SL content that expresses the intent of the creator that the creation shall remain free and open.
This could work in the same way as the current "next owner" rights, probably with two additions:
- splitting resell and give away into two permissions, ensuring that the item may be given away but not sold.
- next owner may not restrict permissions (limiting to the next owner's abiltiy to set any of the "no" flags)
There are probably other combinations which I'm overlooking or details I'm missing that can be worked out through the comments on this JIRA but essentially with those extended permissions it should be prevented to link or embed the builds into/with other builds that do not carry the Open Content flag.
It's also clear that this can be circumvented in the same way as current permissions (that is copybotting, texture copying, etc.). It may also become difficult in terms of scripts, but scripts have the benefit of being able to include a license header into the script to express the creators intent and this seems to work sufficiently well already with AO scripts.
So, I don't expect it to be more successful than the current permission set in that regard, but now with Linden Labs making a clear commitment to Open Source with the system itself (viewer source, other parts), I think there should be an equivalent in world that gives open content creators the same tools that closed content creators currently have.
I'd like to solicit discussions of details here, this is intended merely as a starting point to sort out the details.
|
Being an open sourcer and also being intrigued by the creativity sparkled by open environments (e.g. the ability to remix/mashup CC content) what I'd really like to see is a GPL style permission inside SL.
So far permissions in SL seem to exist primarily to serve commercially oriented creators. It is of course possible to leave builds full perm but from my experience a whole lot (and far too many) end up in boxes or remixed with commercial builds, to the point where some stuff which started free/full perm is hard to find in it's original form.
In the real world, open content has established sort of a parallel continuum where creation exists apart from commercial interest an where creativity and cooperation is creating results which match or even surpass the quality of the commercial realm. Part of this success seems to come from the fact that the tools (licenses) now exist (tagging something as GPL, MIT or CC) to serve the intent of creators who wish to contribute to that part of life.
My suggestion therefore is to create a permission flag for SL content that expresses the intent of the creator that the creation shall remain free and open, available for reuse/mix/mashup but only with other parts and results remaining the same (free and open).
This could work in the same way as the current "next owner" rights, probably with two additions:
- splitting resell and give away into two permissions, ensuring that the item may be given away but not sold.
- next owner may not restrict permissions (limiting to the next owner's ability to set any of the "no" flags)
There are probably other combinations which I'm overlooking or details I'm missing that can be worked out through the comments on this JIRA but essentially with those extended permissions it should be prevented to link or embed the builds into/with other builds that do not carry the Open Content flag.
It's also clear that this can be circumvented in the same way as current permissions (that is copybotting, texture copying, etc.). It may also become difficult in terms of scripts, but scripts have the benefit of being able to include a license header into the script to express the creators intent and this seems to work sufficiently well already with AO scripts.
So, I don't expect it to be more successful than the current permission set in that regard, but now with Linden Labs making a clear commitment to Open Source with the system itself (viewer source, other parts), I think there should be an equivalent in world that gives open content creators the same tools that closed content creators currently have.
I'd like to solicit discussions of details here, this is intended merely as a starting point to sort out the details.
|
made changes - 24/Sep/07 02:02 PM
|
Summary
|
"Open Content" (Creative Commons/Open Source/GPL style) permission for SL Items
|
Copyleft/share-alike permission for SL Items
|
made changes - 24/Sep/07 02:03 PM
|
Linden Lab Issue ID
|
|
SL-56004
|
made changes - 22/Dec/07 01:59 AM
|
Workflow
|
jira
[ 15496
]
|
jira-2007-12-21
[ 23884
]
|
made changes - 22/Dec/07 02:10 AM
|
Workflow
|
jira
[ 23884
]
|
jira-2007-12-21
[ 24543
]
|
made changes - 22/Dec/07 03:05 PM
|
Workflow
|
jira-2007-12-21
[ 24543
]
|
jira-2007-12-22
[ 30903
]
|
made changes - 22/Dec/07 03:28 PM
|
Workflow
|
jira-2007-12-21
[ 30903
]
|
jira-2007-12-22
[ 32860
]
|
made changes - 22/Dec/07 08:15 PM
|
Workflow
|
jira-2007-12-22
[ 32860
]
|
jira-2007-12-22a
[ 37990
]
|
made changes - 22/Dec/07 08:39 PM
|
Workflow
|
jira-2007-12-22
[ 37990
]
|
jira-2007-12-22a
[ 39457
]
|
made changes - 22/Dec/07 09:32 PM
|
Workflow
|
jira-2007-12-22
[ 39457
]
|
jira-2007-12-22a
[ 41951
]
|
made changes - 22/Dec/07 09:54 PM
|
Workflow
|
jira-2007-12-22
[ 41951
]
|
jira-2007-12-22a
[ 43318
]
|
made changes - 11/Mar/08 10:17 AM
|
Link
|
|
This issue is related to by SVC-701
[ SVC-701
]
|
made changes - 08/Jul/08 07:30 PM
|
Key
|
VWR-2571
|
SVC-2626
|
|
Project
|
1. Second Life Viewer - VWR
[ 10003
]
|
2. Second Life Service - SVC
[ 10002
]
|
|
Component/s
|
Permissions
[ 10028
]
|
|
made changes - 08/Jul/08 07:32 PM
|
Link
|
|
This issue is related to by SVC-2621
[ SVC-2621
]
|
made changes - 12/Aug/08 04:35 PM
|
Component/s
|
|
Permissions
[ 10221
]
|
made changes - 13/Nov/08 12:03 PM
|
Workflow
|
jira-2007-12-22a
[ 43318
]
|
jira-2008-11-14
[ 80345
]
|
made changes - 13/Nov/08 04:27 PM
|
Workflow
|
jira-2008-11-14
[ 80345
]
|
jira-2008-11-14a
[ 86247
]
|
made changes - 13/Nov/08 04:41 PM
|
Workflow
|
jira-2008-11-14
[ 86247
]
|
jira-2008-11-14a
[ 90478
]
|
made changes - 13/Nov/08 04:50 PM
|
Workflow
|
jira-2008-11-14
[ 90478
]
|
jira-2008-11-14a
[ 93428
]
|
|