next »

[Ian @ un4seen]

That's my main concern - I *know* that people tend to skip those texts even though they know they're required to read them.
I want to make sure your licence is unmissable. I think the easiest way is that I don't include anything with my package, but direct them to a download page where a single package (like radio42 outlines) can be downloaded.

I'm not really a fan of the separate package idea - it's extra maintenance, when releasing updates, etc... I guess you could package the DLLs yourself though (is that what you meant?), and make that a separate download, with the appropriate notices/etc...

By API, do you mean documentation? It shouldn't be necessary since they won't interact directly with Bass, but through my generic sound system wrapper.

Yep, the documentation, but also headers, and even examples. Basically, everything that isn't the DLL

[Jonas Beckeman]

Doh! I should've concluded from earlier comments that packaging myself for separate download could be an option, but it just didn't occur to me...

So I'll put the dll's in a zip, with the license.txt for each one next to them. Is it OK if I rename the license.txt so they're in pair with the dlls?

Contents
Bass.dll
Bass_License.txt
Bass.Net.dll
Bass.Net_License.txt
Bass_fx.dll
Bass_fx_License.txt

Who's in charge of the wma dll? Could I include that too?

[radio42]

Which "Bass.Net_License.txt" did you use?

Since the original package of BASS .NET API did NOT have any "license.txt" - but only a "LICENSE.rtf" !
Did you use that one - or what did you use?

In addition I would also recommend, that you state somewhere in your Development Environment very clearly, that using BASS and/or BASS .NET in any kind of commercial context will require seperate licenses!
E.g. you could note that in you Download, Installer, Web-Site etc.!

WMA is also Ian's (Un4seen) baby...

[Jonas Beckeman]

Haven't used anything yet, 'twas just a proposal - but is it OK if I rename your LICENSE.rtf to Bass.Net_Licence.rtf so it can easily be identified for the end user?

> that you state somewhere

I could add that info to the documentation of my SoundManager.CreateSystem(string systemName) method:
/// <summary>
/// [blabla...] (Note that using Bass for shareware or commercial projects require separate licenses - see www.un4seen.com/bass)

With these two solutions they should be well aware of the licenses.

Another thing - ATM, my source is available only from the codeproject page:
http://www.codeproject.com/csharp/Endogine.asp
Could I add the Bass.zip to that list, something like this:
Download Bass sound system + license texts

[Ian @ un4seen]

Who's in charge of the wma dll? Could I include that too?

Yes, that's fine.

[Jonas Beckeman]

Do I just ignore license paragraphs such as

> You may freely distribute the BASSWMA package as long as NO FEE is
charged and all the files remain INTACT AND UNMODIFIED.

? Since I only redistribute the dll and the license.txt, it'll look as if I'm breaking the license (the other files are listed in the license). Could you rewrite the license texts? Or should I edit them and send to you for approval?

Thanks

[radio42]

Haven't used anything yet, 'twas just a proposal - but is it OK if I rename your LICENSE.rtf to Bass.Net_Licence.rtf so it can easily be identified for the end user?

-> Yes, that is okay!

I could add that info to the documentation of my SoundManager.CreateSystem(string systemName) method:
/// <summary>
/// [blabla...] (Note that using Bass for shareware or commercial projects require separate licenses - see www.un4seen.com/bass)

-> Please also add:
Note that using BASS and/or the BASS .NET API for shareware or commercial projects require separate licenses:
- see www.un4seen.com/bass (see Bass_Licence.txt)
- see www.ten53.de (see Bass.Net_Licence.rtf)

my source is available only from the codeproject page:...

-> I tought the new zip should be downloaded from here?!

[Jonas Beckeman]

OK, I'll add those notes to the <summary>!

-> I tought the new zip should be downloaded from here?!

I'd prefer that, but after Ian's comment...

> I guess you could package the DLLs yourself though (is that what you meant?), and make that a separate download, with the appropriate notices/etc...

I thought you wanted to be relieved of as much practicalities as possible, so I offered to do it myself.
Is there anything else you want me to do, or is now the time when I just start waiting for you to present the URL for download?

[Jonas Beckeman]

I kind of miss a final vertict on the matter... Should I create the package myself and host on my server, or will you do it? I don't mind waiting, but I got the feeling you didn't reach a common decision.

[Ian @ un4seen]

You can go ahead and package the DLLs yourself

[radio42]

Oki doki, so go ahead... ;-)

[Jonas Beckeman]

OK, thanks, I'll post a comment when done!

[Jonas Beckeman]

OK, I've got a package for your approval now. It's the 4 dlls I've asked about, and their respective license texts. I'd rather mail you the 250 kB zip than post a link - if there's a problem with the package it shouldn't be publicly available. Please mail me at jonas at jobe.nu, and I'll send it right over!

Modifications of readmes:

**Files that you should have found in the <NN> "package"
Removed all but the txt and dll references (since they're not there)

**Using <NN>
Instructions for compiling the source code - removed (as the source isn't included)

MacOSX requirements - removed


Added:
<NN> source code
================
is available for download - see Latest Version


Note: The Bass.Net LICENCE.rtf is included and unmodified (but renamed to Bass.Net.LICENCE.rtf)