[sldev] Code review for those of you with commit access

[Glen]

LOL! Naw, it wasn't me who was tough, it's the guys who are submitting 
the regular patches who will be. I have huge faith in open development 
in that it tends to produce code far more robust than deadline-based 
"get it out the door" commercial production-based development. The guys 
who go elbows-deep in it tend to become fast experts in their chosen 
portion of the project!

Therefore I thought "concrete" was fitting :)

--GC

Philip Rosedale wrote:
> Man Glen, you are tough!  "humor the ex-CEO"... really?  Actually I very 
> much wanted to work more on open source.  I feel like it is a huge 
> chance for greatness, but that we (as a company) need to do more to 
> support it.
> 
> Also, I think that the broader question of how people do great work 
> together in an environment which is more open than the conventional work 
> relationship/organization is an important opportunity.  There haven't 
> been many open source projects as compared to companies or societies - 
> seems like a change for doing something really great.
> 
> I want to help create a high-value viewer that lots of people use.  That 
> means we can't just put every random thing into it, given we 
> (collectively) have limited time and people.  Right?  So we thought 
> stabilizing the new map code and getting that viewer out there was a 
> good starting point.
> 
> P
> 
> Glen wrote:
>> How about "Project Concrete"?
>>
>> Rob Lanphier wrote:
>>> On 3/31/09 3:49 PM, Mike Monkowski wrote:
>>>> Maybe I'm missing something.  The blog post seems to talk about an
>>>> alternate viewer where all kinds of ideas could be quickly
>>>> implemented.  But then, this post points to the HTTP texture 
>>>> project. There's one disconnect.  
>>> We're in the process of coming up with a name for the project.  More
>>> details soon on that front.  In the meantime, we're using the
>>> "http-texture" name as one that will almost certainly not stick, so that
>>> we're not stuck with our working title as the name of the project.
>>>
>>> We do want to be focused on HTTP texture and general stability for a
>>> while, since moving to HTTP delivery of textures is a big architectural
>>> win, and it's going to take determination and focus to get this code to
>>> production quality.
>>>
>>>> And then how do changes in this alternate viewer get into the official
>>>> viewer?  Or is this just a way to humor the ex-CEO.  Tell him he can
>>>> do his project, but don't give haim any people to work with him, so he
>>>> has to get volunteers to code his project.
>>>>
>>>> What, me cynical? ;-)
>>> No kidding!  :)
>>>
>>> This isn't an "all hands on deck" thing, but it's more than a token
>>> project.  We don't have all of the details sorted out as to how the
>>> changes get into the mainline viewer, but there are a lot of us that are
>>> motivated to get those details sorted out.
>>>
>>> Are you thinking about helping?
>>>
>>> Rob
>>>
>>>> Rob Lanphier wrote:
>>>>> Hi folks,
>>>>>
>>>>> As you probably saw in Philip's blog post (which if you haven't 
>>>>> read it,
>>>>> do so[1]), we're going to be doing a lot more development out in the
>>>>> fishbowl, in a branch with community members who have direct commit
>>>>> access.
>>>>>
>>>>> There's a few of you that already have commit access, and others 
>>>>> that I
>>>>> imagine will be asking for it.  Here's the procedure we'd like to 
>>>>> follow
>>>>> for commits for new committers to the http-texture:
>>>>>
>>>>> *  File the patch in JIRA if it isn't already there
>>>>> *  Mail sldev with a link to the JIRA issue, and noting you'd like to
>>>>> commit the patch
>>>>> *  Nag me in a couple of days if we haven't responded
>>>>> *  Assuming you get the nod, commit the change
>>>>>
>>>>> This isn't set in stone....there's a number of aspects about this
>>>>> process I'm going to guess we haven't thought of.  We want to be 
>>>>> nimble,
>>>>> but we also want to make sure there's lots of eyeballs on every 
>>>>> commit.
>>>>>
>>>>> More info can be found here:
>>>>> https://wiki.secondlife.com/wiki/HTTP_Texture_Development
>>>>>
>>>>> Comments welcome.
>>>>>
>>>>> Rob
>>>>>
>>>>> [1]  Philip's blog post:
>>>>> https://blogs.secondlife.com/community/technology/blog/2009/03/30/intensifying-open-source-efforts 
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Policies and (un)subscribe information available here:
>>>>> http://wiki.secondlife.com/wiki/SLDev
>>>>> Please read the policies before posting to keep unmoderated posting
>>>>> privileges
>>>>>
>>>>>
>>> _______________________________________________
>>> Policies and (un)subscribe information available here:
>>> http://wiki.secondlife.com/wiki/SLDev
>>> Please read the policies before posting to keep unmoderated posting 
>>> privileges
>>>
>> _______________________________________________
>> Policies and (un)subscribe information available here:
>> http://wiki.secondlife.com/wiki/SLDev
>> Please read the policies before posting to keep unmoderated posting 
>> privileges
>