[sldev] Working on an installer, anybody figured out licensing yet_

[Chance Unknown]

LL has a branding policy you need to follow for use of their images on other
hosted media such as websites, assume that you would have to follow
something to use their copyrighted images. in as far as it goes, you might
just want to get your own mascot for installer branding and avoid their
images.

since you are forking and rebuilding from open source - erm sources - its
worth considering how to differentiate your viewer. different versioning is
confusing, and is the intent to identify to the grid, the user, or ___?
since they havent identified how forks are to connect to their grid, this is
a great question. if you rebuild using their sources without change, then
you will identify just as the official viewer does. caveat emptor.

what you are describing is a fork from the original baseline? are you going
to track version numbers or use your own? are you adding only bug fixes (in
which case, whats the problem with submission back to the original
baseline)? the group or team that forks from the original baseline generally
assumes the responsiblity for licensing compliance on the forked project, is
it your intent to follow up on that as part of the fork? if you are just
pissed at the installer, then open source yours and submit it to replace the
one that resembles the nullsoft installer?

On 7/8/07, dale at daleglass.net <dale at daleglass.net> wrote:
>
> Hiya :-)
>
> I've been working on an installer again. Previous approach was ugly and
> required .NET, so I got rid of that.
>
> Instead I decided to tackle two problems at once: Redistribution
> restrictions, and updates.
>
> Both are solved in the same way:
>
> Installer just carries a file list with it, with filename and MD5 sum.
> When you install, it checks whether the file is already there. If not,
> or the md5sum is wrong, it checks all SL installs and tries to find it
> there. If not, it downloads.
>
> The files that can't be redistributed aren't on my server, so if they're
> needed and can't be found locally, the install fails.
>
> All this is coded in NSIS with a MD5 and a file decompression plugin.
>
> This way, even the first install of my version of the viewer will grab
> already installed files, and further updates will be just what changed.
> No more 25MB downloads.
>
>
> Now, I'd like to make my installer include as many files as possible to
> make sure it doesn't need very specific official SL versions to be
> installed.
>
> So, anybody figured out what can be redistributed yet? If so, a wiki
> page on it would be very helpful.
>
> A number of DLLs in the package don't come with the source, but I think
> that some of them must be redistributable.
>
> These are the files in the main directory:
>
> dbghelp.dll, msvcp71.dll, msvcr71.dll: Microsoft runtime stuff, I assume
> redistributable.
>
> fmod.dll: Not sure, might be. Could be specifically downloaded from the
> fmod website, I suppose.
>
> freebl3.dll, js3250.dll, nspr4.dll, nss3.dll, nssckbi.dll, plc4.dll,
> plds4.dll, smime3.dll, softokn3.dll, ssl3.dll, xul.dll: Mozilla stuff,
> given the Mozilla license I assume they're redistributable.
>
> app_settings/mozilla: I assume redistributable
>
> xpcom.dll, gksvggdiplus.dll: Definitely redistributable, license stated
> as "License: MPL 1.1/GPL 2.0/LGPL 2.1".
>
> llkdu.dll: Apparently not redistributable.
>
> So, at first glance, except llkdu.dll and perhaps fmod.dll, everything
> else should be fine to redistribute?
>
>
> Questions for LL:
>
> Other than library redistibution restrictions, what other things are
> there to have in mind when releasing a custom viewer?
>
> Can I just package the results of the complication as-is, or do I need
> to do something more?
>
> For example, can I leave the SL icon as it is, or I'd have to have my
> own branding?
>
> Should my viewer identify itself as a third party viewer to the grid?
>
> Do I need to remove or disable anything (crash reporter, for example)?
>
>
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20070709/b8ddfe32/attachment.htm