Hi,
On Tue, Apr 6, 2010 at 5:46 AM, JB Hancroft wrote:
> Progress on SNOW-495 is good news - thank you! Is that against the 1.4
> codebase, or Snow V2?
>
Snowglobe 2.0. I don't think there's much value to do that for 1.4 though
I'm pretty sure the branding script will be easily adaptable to th
Thanks, Merov.
Using Dzonatas' SNOW-375 will be a great way to extend the viewer
capabilities.
Progress on SNOW-495 is good news - thank you! Is that against the 1.4
codebase, or Snow V2?
Thanks,
- JB
On Tue, Apr 6, 2010 at 12:56 AM, Philippe (Merov) Bossut <
me...@lindenlab.com> wrote:
> Hi,
Thanks Merov! That cleared up a lot of confusion.
Could you please check the word "*and*" in your following paragraph?
On Tue, Apr 6, 2010 at 5:56 AM, Philippe (Merov) Bossut wrote:
>
> - Distributing Binaries: That indeed creates a TPV and TPV Policy will
> apply if the viewer plans to connec
Philippe (Merov) Bossut wrote:
>
> - Commit of SNOW-375 in Snowglobe: This is a big patch and, since we
> don't have a CLA for Dzonatas on file, it can't be integrated as long
> as that's not cleared. Note that, to the best of my knowledge, such
> CLA are asked for contributions to most FLOSS pr
Hi,
On Mon, Apr 5, 2010 at 11:17 AM, Morgaine wrote:
> While that may be his intention, you can't make a new Snowglobe by placing
> a patch in Jira, applying the patch to Snowglobe sources, and then
> distributing the resulting viewer as if it were a new version of Snowglobe,
> exempt from being
Dzonatas, I still want to know what your TPV is called, to assist our
discussion.
You are distributing a TPV made by patching Snowglobe sources with the
SNOW-375 patch. The archive you are distributing unpacks as
"Snowglobe-i686-1.4.0.0", but I rather doubt that you have permission to be
distribu
Please note from the jira: "The purpose of this jira is to help further
the process to bring the patch to release quality." At that time, it may
be desirable to commit it to Snowglobe. Until then, the patch is offered
for community development (not as some conspiracy theory to bypass TPV).
If y
While that may be his intention, you can't make a new Snowglobe by placing a
patch in Jira, applying the patch to Snowglobe sources, and then
distributing the resulting viewer as if it were a new version of Snowglobe,
exempt from being a TPV.
If that were possible then everyone would do likewise w
That's correct.
Michael Dickson wrote:
> Actually his intention could be to contribute the patches *to* snowglobe
> in which case it's not a new TPV and a very reasonable example of
> cooperation with a company sponsored open source project.
>
> That's actually very likely his intention since the
Actually his intention could be to contribute the patches *to* snowglobe
in which case it's not a new TPV and a very reasonable example of
cooperation with a company sponsored open source project.
That's actually very likely his intention since the patches *ARE*
SNOW-375 and not MY_TPV-375 or some
Nope, client-side scripting and an HTTP/REST server are not in Snowglobe.
Your patch SNOW-375 when applied to Snowglobe sources created a derived work
from Snowglobe. The derived viewer is clearly a TPV.
This is why I am asking you what this new TPV is called, since it is not
Snowglobe but only b
Has client-side scripting and an HTTP/REST server been offered in
Snowglobe before patch SNOW-375? I'm not sure how you are able to
determine such features as "derived" from Snowglobe.
The SNOW-375 patch
Morgaine wrote:
> That sounds pretty interesting, Dzonatas.
>
> What is your viewer called,
That sounds pretty interesting, Dzonatas.
What is your viewer called, this TPV derived from Snowglobe with an extra
patch?
Morgaine.
=
On Sat, Apr 3, 2010 at 6:43 PM, Dzonatas Sol wrote:
> This is a build of Snowglobe with SNOW-375 patch applied. T
13 matches
Mail list logo
