[opensource-dev] Viewer Policy Changes

[Kadah]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I think the general rule is here that if its something like Emerald's
multi-attach where it doesn't work or causes artifacts for other
viewers, it needs to go through LL, get PO approval and a project for
getting effected APIs added or changed, as well as viewer support
added to V-D for everyone to pull from.


On 2/24/2012 4:55 PM, Celierra Darling wrote:
> (I am not a lawyer, but...)
> 
> From the text in the blog post, it looks like it's intended to be
> an anti-fragmentation measure.  I don't think it's literally a
> desire to make the TPV devs wait until the official viewer catches
> up (and definitely not to make TPV people "develop [features] for
> the LL viewer").
> 
> To help allay the concern, though, I think there could be some sort
> of "with specifications released by LL" exception - once an API has
> been hashed out and released, I can't think of any benefit to
> making the TPV wait.  That'd make the rule a little more tightly
> focused on getting TPVs to make specs that LL's willing to endorse
> and use.
> 
> Celi
> 
> 
> On Fri, Feb 24, 2012 at 7:18 PM, Jessica Lyon 
> <jessica.lyon at phoenixviewer.com
> <mailto:jessica.lyon at phoenixviewer.com>> wrote:
> 
> Actually, under 2.k, features like breast physics, secondary 
> attachments, shared parcel WL etc, would have never been permitted 
> to exist. And this means that any feature in the future to which a 
> TPV may conjur up, which effects the shared experience (Ie. 
> something one user could see but another couldn't) will need to be 
> developed for the LL viewer by TPV devs, accepted by LL, released
> by LL before a TPV may release it themselves. Another example would
> be the Mesh deformer from Qarl, if LL were not interested in it..
> none of us would be allowed to release it in our viewers.
> 
> Jessica Lyon Project Manager The Phoenix Viewer Project, Inc.
> 
> On Fri, Feb 24, 2012 at 7:00 PM, Cinder Roxley 
> <cinder at cinderblocks.biz <mailto:cinder at cinderblocks.biz>> wrote:
> 
> Yes, you're mistaken. The key phrase there is "alters the shared 
> experience of the virtual world".  A tpv can alter individual 
> user's experiences, (UI, build tools, controls, graphics 
> enhancements) but not the shared experience of the world.  IE, 
> exposing information such as the friend online visibility of *other
> users*.
> 
> Kind regards, -Cinder
> 
> 
> On 2/24/2012 4:44 PM, Nalates Urriah wrote:
>> Does this new policy essentially eliminate the reason for the 
>> existence of 3rd party viewers:
>> 
>> 2.k : You must not provide any feature that alters the shared 
>> experience of the virtual world in any way not provided by or 
>> accessible to users of the latest released Linden Lab viewer.
>> 
>> http://community.secondlife.com/t5/Second-Life-Viewer/Third-Party-Viewer-Policy-Changes/m-p/1399141
>>
>>
>> 
This seems to say all changes can be submitted to LL but not
>> implemented until and unless LL approves them and adds them to 
>> the SL viewer. Am I mistaken?
>> 
>> -- Nalates Urriah (SL AV)
> 
> 
> _______________________________________________ Policies and
> (un)subscribe information available here: 
> http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the
> policies before posting to keep unmoderated posting privileges
> 
> 
> 
> 
> -- Jessica Lyon Phoenix Viewer Project Inc 
> http://phoenixviewer.com
> 
> 
> _______________________________________________ Policies and
> (un)subscribe information available here: 
> http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the
> policies before posting to keep unmoderated posting privileges
> 
> 
> 
> 
> _______________________________________________ Policies and
> (un)subscribe information available here: 
> http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the
> policies before posting to keep unmoderated posting privileges
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPSDaGAAoJEIdLfPRu7qE28awH/2OXWBVu4B49rHTipeIzUcax
j91sLFRMHTaUd3oiwFzkQkWMDPjvhahceRzLIWLcP0nkIQIfg4yRvjuiFTNdlJuZ
NuqGuu0ozkVbTh29MbvC1lm50xwx2xucxd0OYpsUiGXKTFRaH4f3aouLKIfdSX9G
VvpcqrddohwznNsoyzMtACu7k/L82vd49nmFrQLqHGSB2X3gZZjDhS5JMf7hyLEP
cCd5zeqqin9wOYHX7IumF6j0rm+9SkwiVDiGmJQ+G2u6e/+ZQBwOdfkyb+h+Ij0B
LkNcQTLUle4AoTWU4AXFj0prIIL1pacOijTPxvN0AurhCxE5eXwQIgRrqfdb35Q=
=axPl
-----END PGP SIGNATURE-----