[sldev] remove

[Jeff]

remove




________________________________
From: "sldev-request at lists.secondlife.com" <sldev-request at lists.secondlife.com>
To: sldev at lists.secondlife.com
Sent: Thursday, April 30, 2009 12:00:05 PM
Subject: SLDev Digest, Vol 28, Issue 57

Send SLDev mailing list submissions to
    sldev at lists.secondlife.com

To subscribe or unsubscribe via the World Wide Web, visit
    /index.html
or, via email, send a message with subject or body 'help' to
    sldev-request at lists.secondlife.com

You can reach the person managing the list at
    sldev-owner at lists.secondlife.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of SLDev digest..."


Today's Topics:

   1. Re: About the http-texture project (Mike Monkowski)
   2. Re: http-texture project - how far until complete? (this    will
      totally Rawk SL!) (Philippe Bossut (Merov Linden))
   3. Re: About the http-texture project (Mike Monkowski)


----------------------------------------------------------------------

Message: 1
Date: Thu, 30 Apr 2009 14:43:01 -0400
From: Mike Monkowski <monkowsk at watson.ibm.com>
Subject: Re: [sldev] About the http-texture project
To: "Philippe Bossut (Merov Linden)" <merov at lindenlab.com>
Cc: Second Life Developer Mailing List <sldev at lists.secondlife.com>
Message-ID: <49F9F135.7070007 at watson.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed

Philippe Bossut (Merov Linden) wrote:
> Not sure which missing documentation you're referring to but we have 3  
> at the moment:

OK, let's say Joe Sldev (I think the name is Serbian) has a great idea 
that he want's to get into the SL viewer.

Is this new open source viewer (aka http-texture) his new open source 
portal or is it a sneaky underhanded backdoor to infiltrate the viewer 
codebase?

He has a PJIRA entry with a patch file.  How does that make its way to 
the SVN project?  Does he have to worry about getting it into the SVN 
branch?  Are there gatekeepers along the way?  What if someone objects? 
    Do we end up with SVN wars like Wiki wars?

When the project gets merged to the branch, and the branch to the trunk, 
and the trunk to the RC, and the RC to the standard viewer, who does all 
that merging?  Does anyone test it along the way?  Does everything in 
the project get merged at once, or do selected patches get merged 
separately?

Does anybody document what's going on?  Does anyone even document the 
new or modified functionality?  Where?  At what point of the process?

Enough for now.

Mike


------------------------------

Message: 2
Date: Thu, 30 Apr 2009 11:58:22 -0700
From: "Philippe Bossut (Merov Linden)" <merov at lindenlab.com>
Subject: Re: [sldev] http-texture project - how far until complete?
    (this    will totally Rawk SL!)
To: Second Life Developer Mailing List <sldev at lists.secondlife.com>
Message-ID: <183E1020-2668-4F08-9F08-C7271354C92B at lindenlab.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes

Hi,

To answer the concerns expressed on this thread: yes, we take all  
those issues very very seriously (IP snooping, hot linking, griefing,  
phishing, etc...) and, as I said, that's why we won't push "URL on a  
prim" without careful examination of all the threats it presents and  
the possible mitigations. The good news is that web browsers have been  
down that road already and the threats and mitigating methods are  
known. The bad news is that web browsers don't have perfect solutions  
(it's a constant arm race with the griefers) *and* SL introduces new  
challenges of its own as you could get exposed to bad content just by  
walking by. Let's keep in mind though that, despite the issues, this  
technical possibility is very much desired by residents in some  
markets like education (exhibit A: Fire's email).

On Apr 30, 2009, at 11:15 AM, Stickman wrote:
> I suppose the first step is to brainstorm a list of safety and privacy
> concerns, and then brainstorm how to solve them. Have we played that
> game yet? Is this the place for it?

There has been a couple of internal brainstorm meetings on "how to  
open without compromising security" internally. This is such a *huge*  
issue though and I'm wondering what's the best way to start the  
discussion without overwhelming the list. I'm thinking that a  
collaborative wiki page would be a better channel so that we could  
keep track of each potential threat/mitigation. What do you guys think?

Cheers,
- Merov



------------------------------

Message: 3
Date: Thu, 30 Apr 2009 14:59:35 -0400
From: Mike Monkowski <monkowsk at watson.ibm.com>
Subject: Re: [sldev] About the http-texture project
To: "Philippe Bossut (Merov Linden)" <merov at lindenlab.com>
Cc: Second Life Developer Mailing List <sldev at lists.secondlife.com>
Message-ID: <49F9F517.6010307 at watson.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed

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?

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?

Mike



------------------------------

_______________________________________________
SLDev mailing list
SLDev at lists.secondlife.com
/index.html


End of SLDev Digest, Vol 28, Issue 57
*************************************



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20090430/af371df5/attachment.htm