TPVD/Developers Group Agenda

Add agenda requests at the end, and please put your SL Name in the request so Oz's know who to contact for any clarification
Use --~~~~ to insert your signature

Next meeting: Noon SLT, 3 February at the Hippotropolis Theater^🖈

Important: Because Oz will be on vacation on February 17th, the next meeting will be February 24th

New:

1. Fmod upgrade.. (Oz Linden)
2. Developing in-world Viewer Test resources (Oz Linden)
3. TPVD Directory (Arrehn Oberlander)
   • Should TVPDs be required to declare a license statement for their distributed binaries? Currently LL only requires a privacy policy.
4. Coarse Location Improvements (Arrehn Oberlander)
   • https://jira.secondlife.com/browse/SVC-7645. This change breaks existing fielded TPVD viewers, including Firestorm and Phoenix, when alternative changesets such as that offered by Ansariel Hiller accomplish the same result without breaking existing viewers. Can we please have a reasonable, two-way discussion on this topic?
5. Re https://jira.secondlife.com/browse/SVC-7655 - Offer non premium users support for server related issues. (Ed Marryman)

---

Discussion

Some viewer developers have historically taken the position that any open source is automatically fair game to use at any time. This has sometimes lead to some changes being used either before the originator considered them ready for general use, or to other bad feelings.

I have asked that Linden Lab changes, even when in public repositories, not be used by TPVs before they are merged to viewer-development, and in the case of new features not before they are in a released viewer (though that difference is normally very small).

• When is it appropriate to import a feature developed outside your viewer?
• Should TPVs explicitly get permission?
• Should there be a protocol for this?

---

Open Items:

1. STORM-1800 The vertex weights of the default character mesh could be better? --Kadah Coba
2. Profile/People API
3. Any update on legacy services shutdown timeframe? --Kadah Coba 09:48, 11 November 2011 (PST)
4. Communications reliability issues
   • VWR-25940 HTTP communication with grid capabilities router is unreliable at times affecting HTTP Textures
   • SVC-6917 Apache2-worker/caps router on sim hosts is relaying 499 HTTP status codes back to clients - not a valid wire status code
   • SVC-6760 Apache2-worker/caps router on sim hosts is experiencing a high failure rate leading to service interruptions
   • VWR-25145 asset/texture download scenarios that work badly
   • VWR-26218 Windows viewer is experiencing DNS issues while attempting to fetch textures

   and the 499/caps failures? Can someone find out why do a few users see these issues so much? --Kadah Coba 12:38, 31 May 2011 (PDT)

   • Seeking feedback on good/bad experiences and networking hardware here:
     • VWR-25426 Friendlist displays users as Unknown or (loading), teleports fail, assets will not save
   • SVC-4968 Group won't load - too many members