Re: [opensource-dev] Fixing the Assets

2010-08-07 Thread Gwynn Gunawan
:)

> lol I knew it ! This text IS actually a Markov chain !
>
> That or it is aimed at a subset of the members of this list who actually
> know the encryption key to extract the hidden message. But to the rest of
> us, this is just nonsense.

Count me in with the latter gang plx, k, thnx, bye
But I thought it entertaining, of perhaps in the wrong place, but I
aint gonna be naggin' about it

:-D

~gg
>
>
>
> On 7 August 2010 17:34, Dzonatas Sol  wrote:
>>
>> Oz Linden (Scott Lawrence) wrote:
>> >   On 2010-08-06 17:28, Dzonatas Sol wrote:
>> >
>> >> Here is the proposal, as a routine. The written logical explanation in
>> >> English with normalized words defeats the purpose of the routine for
>> >> every reason that supports it.
>> >>
>> > Clarity is never wasted.
>> >
>> > You have not given any hint at all as to what problem you are trying to
>> > solve - without at least that, there is no way to even start thinking
>> > about what you've written.
>> >
>>
>> Thanks!
>>
>> Sometimes the concept is never understood when the meaning to the word
>> concept is not understood. If the content is money, it means nothing, to
>> We, who appreciate the honey.
>>
>> We use use the spoon to eat the honey.
>>
>> Bend the spoon?
>>
>> Easy.
>>
>> --
>> --- https://twitter.com/Dzonatas_Sol ---
>> Web Development, Software Engineering, Virtual Reality, Consultant
>>
>> ___
>> Policies and (un)subscribe information available here:
>> http://wiki.secondlife.com/wiki/OpenSource-Dev
>> Please read the policies before posting to keep unmoderated posting
>> privileges
>
>
> ___
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>



-- 
Don't fight back. Fight forward.
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges


Re: [opensource-dev] Open Viewer Development Announcement

2010-08-15 Thread Gwynn Gunawan
Gang,

ok, sorry, cool, but I still feel uncomfortable. Viewer 2 was for
users, less so for creators. Creating got harder. I might be cursing
in church but 'd like to see a Viewer, for Joe Random Sixpack crossing
the street, and a Creator. You don't create web pages in a browser.
You don't create video's in youtube. "If you would also like to create
content for Second Life, click here to download the additional tools"
I don't, in general, like to fork.
I like the way LL is heading with this, and it's OS commitment but I'm
starting to think we try to kill too many birds with not enough
stones.

Also, I'm now in a pub (in Glasgow) and respond a bit impulsively.

regards
~gg

On Sun, Aug 15, 2010 at 5:25 PM, Oz Linden (Scott Lawrence)
 wrote:
>
> What’s Next For The Second Life Viewer?
>
> Linden Lab spent the better part of the last two years revamping the Second
> Life Viewer to create Viewer 2. Some of the changes were important new
> features, and some were controversial - some were both. The bulk of the
> design and engineering work was done with only limited, indirect
> participation from the open source and resident communities, which has left
> many in those communities feeling alienated and disenfranchised.
> In recent months we have released both Viewer 2 and a 2.1 update; Linden Lab
> has also been through a major reorganization. We are now evaluating the
> results of all of this work, and we are making significant changes to the
> way we design and build the viewer.
>
> Introducing Snowstorm
>
> Linden Lab has created a new team whose goal is to develop the Second Life
> Viewer in the open and in response to the needs of our Residents. Here are
> our goals:
>
> Show Residents continuous visible progress
>
> Work in the open by sharing not only our code, but our process publicly --
> this includes our backlog and our discussion about it.
> Engage with the open source community and aggressively accept good work the
> community does into our product.
> Release new ‘Development’ Viewers frequently -- our initial target is
> bi-weekly.  All builds from the ‘Development’ branch are visible and
> available for testing.
>
> Improve the user experience
>
> Make continuous improvements to the design and implementation of the
> Viewer’s user interface.
> Import desirable patches and features from Snowglobe and other Third Party
> Viewers.
> Add small features and fixes that have high value and low cost, while still
> remaining consistent with an overall product vision.
>
> Renew and deepen our relationship with the community
>
> Integrate community work directly into our main line Viewer rather than
> routing it through Snowglobe first.
> Demonstrate rapid responsiveness to feedback and patches from community.
> Engage continuously with the community to develop new project proposals and
> provide resources that open source developers need to be effective.
>
> How Snowstorm Works
>
> Viewer development has moved to a single open source model
>
> There are no longer internal ‘private’ and external ‘public’ versions.
> Viewer source (with the exception of one wrapper library we cannot legally
> release), is now in public Mercurial source repositories. All viewer
> integration is happening in the Development repository at
> ‘http://hg.secondlife.com/viewer-development’. It is used by all Linden Lab
> viewer development teams, and open source developers are encouraged to pull
> from that repository and submit changes for integration to it.
>
> Code in the Development repository is now released under version 2 of the
> GNU LGPL
>
> This allows community developers greater freedom to use the viewer code,
> including incorporating it into products that also include closed source.
>
> Accepted contributions go directly into the official Second Life Viewer
>
> There is no longer a two-step process of contributing to Snowglobe and then
> hoping that the contribution is imported to the Linden viewer. Viewer
> development efforts within Linden Lab go through the same integration queue
> and into the same repository that open source contributions use.
>
> Innovations from Snowglobe are being imported to this new viewer
>
> Some changes may be left behind or modified in order to fit into Viewer 2;
> Linden Lab will work with open source contributors to harmonize
> contributions with the product goals of the Linden viewer. The plan is to
> import as much as possible of the excellent work that has been done in
> Snowglobe as quickly as possible (this rate does depend on help from you).
>
> Snowstorm team plans and priorities are open
>
> We publish both what we’re working on (in public Jira issues and on our
> Sprint Backlog) and the projects we’d like to do (our Product Backlog).
> These projects are available for open source contributors to take on, and
> the Snowstorm team coordinates getting access to any Linden review and
> collaboration resources that are needed. Community members are encouraged to
> propose additions