Hi NickyP,
On Tue, Mar 30, 2010 at 7:28 PM, William Nickels wrote:
> I have been building SG2 with VC++ Express 2008 (VC90) using boost
> libraries version 1-36. I have completed the build of secondlife-bin.exe and
> it runs error free. However, when I attampt ALL_BUILD and try to build
> setup.e
Iceweasel crashes when attempts are made to post any message in the
forums. It happens as soon as the javascript editor loads.
Nyx Linden wrote:
> Forums for discussing multi-wearables and related issues can be found
> here:
> https://blogs.secondlife.com/community/forums/open-source/open-devel
I have been building SG2 with VC++ Express 2008 (VC90) using boost libraries
version 1-36. I have completed the build of secondlife-bin.exe and it runs
error free. However, when I attampt ALL_BUILD and try to build setup.exe I
encounter dependency issues with the build trying to use VC80 microso
Carlo Wood :
> This is VERY good David.
>
> Someone should get the lawyers AND the management of LL to read this.
Well, thanks very! :)
(And as I notice that I've been posting these things from my work email, I
should also mention that all of these statements are purely my own
opinions as an
Yes, I will be developing in viewer-public.
Nyx
Carlo Wood wrote:
> You mean he'll be developing in viewer-public then?
>
> On Mon, Mar 29, 2010 at 09:44:09PM -0700, Philippe (Merov) Bossut wrote:
>
>> Nyx stated he wanted to develop this feature "in the open" which means that
>> he'll be deve
Agree, TPV mean warranty for users, a copybot feature is a malicious
volontary written code, not a bug
Bugs are license free :)
--
Sent by iPhone
Il giorno 30/mar/2010, alle ore 17.31, malachi ha
scritto:
> just my 2 cents.
>
>
> * Second Life Viewer Source Code
> * The source code i
TPV is a license to login LL grid with a 3rd party viewer, not about
code itself
--
Sent by iPhone
Il giorno 30/mar/2010, alle ore 17.31, malachi ha
scritto:
> just my 2 cents.
>
>
> * Second Life Viewer Source Code
> * The source code in this file ("Source Code") is provided by
> L
This is VERY good David.
Someone should get the lawyers AND the management of LL to read this.
On Tue, Mar 30, 2010 at 11:22:36AM -0400, David M Chess wrote:
>
> I want to weigh in very briefly here, because I was voiciferously arguing with
> Morgaine in AWG the other night, but having considere
just my 2 cents.
* Second Life Viewer Source Code
* The source code in this file ("Source Code") is provided by Linden Lab
* to you under the terms of the GNU General Public License, version 2.0
* ("GPL"), unless you have obtained a separate licensing agreement
* ("Other License"), fo
I want to weigh in very briefly here, because I was voiciferously arguing
with Morgaine in AWG the other night, but having considered the TPV policy
as a whole (and not just believed what it says about itself), I think
there is more of a problem here than I originally thought.
In theory, the GP
Hi merov, did you also take care of the SVN properties, in particular
svn:eol-style.
I just did a commit to 1.4 trunk: hunderds of files did not have this
property set. Apparently it is common practise to add new files without
setting this property. Probably the same for binary files, and executabl
Developers reply to LL if their code is malicious, not if a user mod
the viewer code and violate tos/cs
11/12 mean developer don't write intentionally bad code...
--
Sent by iPhone
Il giorno 30/mar/2010, alle ore 15.13, Marine Kelley > ha scritto:
Naturally but do they apply to the dev
Naturally but do they apply to the developer ? They should void only
for the original dev who implemented the feature intentionally, if
any. Keeping in mind that the servers are as responsible to protect
the data add the viewers are responsible to not attack them. To me
developers (paid by
Am 30.03.2010 um 14:52 schrieb Simon Disk:
> I think I have read a different TPV policy than most people here. I
> do not see how clauses 11 and 12 are being overridden. Both clauses
> stipulate that the GPL cannot be used to violate the law. So when
> you use a TPV and connect to the SL grid
I think I have read a different TPV policy than most people here. I do not
see how clauses 11 and 12 are being overridden. Both clauses stipulate that
the GPL cannot be used to violate the law. So when you use a TPV and connect
to the SL grid and then steal content that you did not create or disrup
I read a different TPV policy than you did, I do not see where this is true.
On Tue, Mar 30, 2010 at 8:29 AM, Lance Corrimal
wrote:
> Am Dienstag 30 März 2010 schrieb Harleen Gretzky:
> > On Tue, Mar 30, 2010 at 6:55 AM, Robert Martin
> wrote:
> > > Under the 3PV policy Kirsten would be banned f
Am Dienstag 30 März 2010 schrieb Harleen Gretzky:
> On Tue, Mar 30, 2010 at 6:55 AM, Robert Martin
wrote:
> > Under the 3PV policy Kirsten would be banned for writing a
> > "copybot" viewer that she/he did not actually write. This is the
> > core of what is wrong with the policy as written.
>
>
You mean he'll be developing in viewer-public then?
On Mon, Mar 29, 2010 at 09:44:09PM -0700, Philippe (Merov) Bossut wrote:
> Nyx stated he wanted to develop this feature "in the open" which means that
> he'll be developing in viewer-internal which is exported on each successful
> build (so we av
quick reminder 6am for the start of Tuesday's session on Virtual Worlds
Workshop. Topics will include realXtend. Presenters will include Python
Morales from realXtend and Zha Ewry from IBM
http://slurl.com/secondlife/IBM%20Business%20Center2/65/1/27
http://vw.ddns.uark.edu/X10/X10--Schedule.html
On Tue, Mar 30, 2010 at 6:55 AM, Robert Martin wrote:
>
> Under the 3PV policy Kirsten would be banned for writing a "copybot"
> viewer that she/he did not actually write. This is the core of what is
> wrong with the policy as written.
>
>
Kristen's source code and binaries are published, LL woul
On Tue, Mar 30, 2010 at 6:51 AM, Marine Kelley wrote:
> That's my opinion and that's why, so far, I am not quitting yet despite all
> the fuss around the policy (that was for Jesse *winks*).
>
Thanks Marine!
I am blaming it on alzheimers!
Jesse Barnett
___
On Tue, Mar 30, 2010 at 6:10 AM, Morgaine
wrote:
> Marine, you raise a good question, but it's hard to give a reasonable answer
> to a "what if" question about a totally unreasonable TPV policy. :-)
>
> The fact that the TPV document places the burden of liability for LL's own
> bugs (and many ot
Well LL cannot possibly write a clause that shifts the liability onto the
users for their own bugs, this would be an abusive clause, and I really
don't think that is what they tried to achieve. As I said, an abusive clause
does not stand in court anyway, so this point is rather moot. What they want
Marine, you raise a good question, but it's hard to give a reasonable answer
to a "what if" question about a totally unreasonable TPV policy. :-)
The fact that the TPV document places the burden of liability for LL's own
bugs (and many other things) on TPV developers' shoulders despite the
extrem
Well sure, if I stated that I agree to be responsible for whatever
defect, past present and future, the SL viewer may introduce, but I'm
not crazy, and I doubt anybody else would be either. This is called an
abusive clause and that does not stand in court. Therefore, I do not
see the "no wa
> It wouldn't stand in court anyway, to expect second hand code to be liable
> when first hand code is not.
Any precedent on that? Surely it's better to have the policy rewritten
rather than rely on it not standing up in court
___
Policies and (un)subscr
I agree, there is no question of distributing a binary + it's code
with a warranty, but to do so LL must remove the "no warranty" clause
from the original code or else our own code, if based on theirs, must
mention it as well, voiding our own liability. It cannot be one
without the other.
It would be wise to stay on the side of caution and presume anyone who
distributes the viewer is liable, even if they are not the ones who
introduced the original defects.
Even with that being said though, personally I would never dream of
giving away software free of charge if it includes a warran
28 matches
Mail list logo
