#SL Viewer Policy Change Meeting

49:00 – There is an idea that many of the features in SL have only been implemented because TPV Dev’s pushed the issue. See 40:00.  (? Linden) points out that many of problems with the Lab’s management that are brought up are about an entirely different management team. Things have changed since then.

50:00 – Jessica (I think – I’ve heard her often enough I think I recognize her voice.) asks some pointed questions on the time needed to get changes to the shared experience made. You will need to listen to this section of the audio to form your own opinion.

I believe this is going to be an ongoing area of contention and drama. However, I understand the Lab’s position. First the Lab has to keep all the stuff added to SL working and working efficiently. This means they have to be able to maintain the code and understand it. Additionally they mush make it work with the rest of the system. Remember. The servers’ code is proprietary. Only Lab employees know it and how the databases and system are setup and work. They are the ones that can see the performance stats and heard all the user complaints. It is with this undisclosed information that the Lab makes decisions.

For those reasons it is likely TPV Dev’s and the Lab will disagree from time to time. So no matter what we (users and TPV Dev’s) think or how we disagree, we will always be disagreeing with those better informed than us.

53:00 – Part of the answer to how changing policy will affect development is the Lab will work as fast as they can on the server side as TPV Dev’s work on the viewer side of a shared experience changes.

54:30 – A primary motivation for the rule changes are based on user confusion over the different experiences of the world when using different viewers. This is something the Lindens want to correct. It is about how the user sees the world behaving. Not about which user interface or render features.

56:00 – Backward compatibility is something the Lab tries to maintain. But, old viewer compliance with new viewer policy is not an issue. It just old viewers falling behind. It is felt older viewer use will die out. Also, as time passes older viewers will break.

1:00:30 – There is nothing in the current viewers to trigger any enforcement actions. New viewer releases that violate the policy will create a problem between the developer and the Lab.

1:01:00 – Jessica on slowing down feature delivery.

1:02:50 – (? Linden) is saying the Lab, in spite of poor past performance, is going to do new shared experience features as well and as quickly as possible.

1:04:00 – Two Linden Labs: old and new. Give them some slack.

1:05:00 – Parcel Windlight – Long discussion on implementation. The possibility of volumetric Windlight came up. Volumetric Windlight is about having a bright desert planet with a blinding sun. Basically all the outside is washed out color and maximum bright. Walking inside a building one could set the buildings volume to be dark and dingy. The volume of the building is what the Volumetric is about, defining spaces for a Windlight setting. We’ll see Parcel Windlight implemented before we see volumetric.

4 thoughts on “#SL Viewer Policy Change Meeting

  1. Pingback: New TPV policy changes - Page 19 - SLUniverse Forums

  2. Hmmmmmm… “trust us we are the new and resident responsive LL”. I’ll believe it when I see it, they have to overcome a lot of negative inertia.
    I did a tally of the New Feature catagory at the jira, OVER HALF are labeled Awaiting Review — (~4000). If LL really intends to be more responsive to feature requests they need to have a better system than the jira. Right now the best avenue we have is to tell the TPV teams, they listen; oh, or we can hire Qarl (if he will ever do it again with all the attitude he has gotten).

    • I understand the negative inertia. Once burned and all… The Lindens are aware of the problem.

      The JIRA is integrated into the work flow of LL. It is also the primary bug reporting and feature requests processes for numberless software projects both commercial and open source. It is pretty high end software for this type of work. It has developed over years. So, what would suggest?

      I know many think the JIRA does not work and the Lindens ignore it. But that is not the case. Go to the JIRA and select any of the Projects from the top menu and check the summary. It gives you items reported and items fixed within the project. As of today there are 67 new issue reports and 42 resolved in the last 30 days.

      That brings us to the ongoing problem of whether to add new features or fix problems with existing features and services. The Lab’s resources are limited. I doubt we will every be happy with adoption rate of requested features.

Leave a Reply

Your email address will not be published. Required fields are marked *