Talk:Geometry and Physics VAG

Metadiscussion

• For now, I think geometry and physics are too closely related to be split. However, I can certainly understand a perspective that there might be two closely related viewpoints here. Geometry really doesn't need material properity information or have to participate in a physics engine. On the other hand, physics really has not meaning at the user level without something to act on. So in the end, I see geometry that has optional physical properties and a single viewpoint the covers both. Do others have thoughts on this? --Burhop Piccard 19:04, 16 October 2007 (PDT)

• I liked the structure of your VAG and so used it as a template for Scalability and QA VAGs ... well done. :-) --Morgaine Dinova 02:56, 18 October 2007 (PDT)
  • Always good to be emulated :-) BTW, I tweaked the usecase part a bit to hopefully give a bit of structure. --Burhop Piccard 06:32, 18 October 2007 (PDT)

• The use of the name VAG is unofficial still. There are issues about it that have gone unanswered as a "group" structure. The use of these "VAGs" in their current state is like force implementation without any design. The concerns are expressed about the VAGs being implemented, but they are not being addressed. If that kind of progress mimics any future software design and implementation, I'd say this already demonstrates that goals won't be followed. I hope that not be the case, and I urge that these VAGs evolve into a methodology that can follow the goals. I think you, Burhop, have put a lot of work into this and it deserves the right attention and implementation. Dzonatas Sol 07:36, 18 October 2007 (PDT)
  • Yes, I saw the discussions but didn't want to sit idle while it gets resolved. If VAG changes to something else I'll be glad to update the pages. If a VAT/VAG methodology becomes more clear I would expect us to line up with this too. I think the core information we are collecting now (i.e. usecases, JIRAs, links, etc.) will keep us busy while some of these organizational issues are resolved (as long as you don't take too long :-) --Burhop Piccard 08:26, 18 October 2007 (PDT)

• There is no place to put design related jira issues right now. The projects listed in jira.secondlife.com do not have space for the AWG project. I get the hint from LL that they are pleased to incubate this project, but AWG needs to quickly evolve into its own hosted site. That evolution needs design and consensus. Without such design and consensus, these VAGs will continue to use LL's resources to "keep us busy" while the organization needs to be resolved. It appears a few others understand that hint. =) Where will AWG related jira issues get entered? Dzonatas Sol 08:36, 18 October 2007 (PDT)

• There are some discussions on the content of a VAG/VAT related to the architecture. Essentially, the key point is for the VAG/VAT to be more user than architecture oriented. See http://wiki.secondlife.com/wiki/Talk:Viewpoint_Advocacy_Groups for more information. --Burhop Piccard 15:58, 21 October 2007 (PDT)

List of concerns addressed by this viewpoint

• Burhop, does "Efficient communication of Geometric and physical properties" include client communication efficiency? From the scalability perspective, I'm interested in anything related to reduction or optimization of server->client object traffic, including negociated reductions in that traffic for example. --Morgaine Dinova 01:33, 22 October 2007 (PDT)