[sldev] About the http-texture project

[Philippe Bossut (Merov Linden)]

Hi,

On Apr 30, 2009, at 11:59 AM, Mike Monkowski wrote:
> Philippe Bossut (Merov Linden) wrote:
>> On Apr 24, 2009, at 3:36 PM, Philippe Bossut (Merov Linden) wrote:
>>> "branches" is the parking repository for the "vendor" version, the
>>> code that gets exported by LL into the OSS realm. That's where code
>>> lands when they throw it over the wall (<disclaimer>I'm being
>>> facetious here with my use of vocabulary and, in that particular
>>> instance, that's me throwing code over the wall</disclaimer>). We  
>>> (as
>>> open source developers) are not supposed to modify branches ever.  
>>> They
>>> are sacred and represent what comes from Lindens. We build it though
>>> to make sure it's not evil, that our changes don't get stomped by
>>> Linden updates and that we like it enough to merge it into our   
>>> projects.
>> Rob followed by a post of his own and updated the wiki describing  
>> the  branches:
>>    http://wiki.secondlife.com/wiki/Source_branches
>> I hope this clears the objective of the svn hierarchy.
>
> So "Merov Linden" is "we" the open source developers?  Not a Linden?

Yes, "We, the people", the concerned Open Source contributors to that  
project. That includes Lindens (like me) but not only.

> The wiki page has a Note! and a Warning! that basically say don't  
> believe anything you read there.  Concerning "projects" all it says is
>> linden/projects/* Later on, Linden Lab wanted to have a more  
>> serious project that was more of a shared effort that they were  
>> conducting with an external vendor in the public repository, so  
>> they created the projects area.
>
> Am I seeing something different from what you're seeing?

The note and warning is to say that the writing is a work in progress:
- about the Note! clearly, we'll go with a better name than "http- 
texture" and Rob already mentioned that. This is a temporary name  
hence the writing under the Note! is temporary too.
- about the Warning! it's just to say that we know this patch flow  
description is out of date but we haven't had time to correct it. It  
also mentions that anyone with understanding of the patch flow can fix  
the writing. This is where you should hook up to make your proposal on  
the subject.

Cheers,
- Merov