To address some of the points made by Ilan in the other thread...
I'm assuming that the main cost here would be the time that has to be put in fixing issues when they occur. I don't have any idea how the financing would play out, but with a slightly elevated pricing for group worlds perhaps it'd be off-set?Ilan Tochner wrote:A single-manager world has less potential issues than a multi-manager world (which means it costs us less to support).
I'd suggest only allowing backup/export of content to group-owned objects only in such a world.Ilan Tochner wrote:Proper group collaboration support also requires various features which we didn't mention in this thread (such as bulk user provisioning, ability to backup/export content that is owned by multiple different people not just the single world manager, etc.).
There will always be a chance of fall-outs - it comes with the territory. The solution I think here is to put in place the same type of management system you see on the Estate Tools. One person would be listed as the owner of the group-owned world, and the others would be listed as managers - all with the same rights as the owner except for deletion of the world/account. I'm not sure how the fees would be handled between all the people on the account, but it might be simpler to again fall back to the group owner.Ilan Tochner wrote:The world manager is held personally accountable for what happens in his or her world but fallouts between once-trusted friends are quite common in virtual worlds. The more accounts with access to potentially harmful rights you add the more risk you expose your world to. Allowing other people to use functions that can destroy worlds they don't manage and aren't held accountable for is a potential source for a lot of grief both for well meaning world managers and for us.
As far as I know, those settings/functions are importing/exporting raw files and a few others, but in the scope of Kitely that includes being able to kick a world out of mega-mode and waiting on your partner(s) to come online to deal with it or other issues that could be potentially time sensitive can be a problem. The other problem that we have run into is that some of the work-arounds don't work - such as those with land management.Ilan Tochner wrote:There is some cost to collaboration projects that result from those safety policies but working around them is a lot less painful than you might think (settings/functions that are world-manager only are usually updated very infrequently).