Distribute the library

[pelle]

Hi everybody,
Does anyone know what are the rules/limits/procedure if I wanted to distribute/sell a library for Rhapsody?
maybe @d-healey ;) knows something

thanks

[d.healey]

If you're using my boilerplate code then it needs to be released under the GNU GPLv3. Samples can be released under a different license.

Regardless of the license you use it will always be possible to unpack the expansion back to a folder - your code will always be publicly viewable, so don't include any sensitive information like encryption keys.

[pelle]

@pelle
What did you mean with boilerplate code?
There is a way to avoid the GPLV3 thing?

Best,
F.

[Christoph Hart]

@pelle said in Distribute the library:

There is a way to avoid the GPLV3 thing?

No.

[d.healey]

@pelle said in Distribute the library:

@pelle
What did you mean with boilerplate code?
There is a way to avoid the GPLV3 thing?

Best,
F.

Ignore what I said. I was wrong it seems.

[pelle]

@Christoph-Hart Thanks for your reply. So if I want to avoid the GPLv3 I have to pay the licence also for Rhapsody?

Thanks

[d.healey]

@pelle said in Distribute the library:

I have to pay the licence also for Rhapsody?

There is no proprietary version of Rhapsody available

[pelle]

@d-healey @Christoph-Hart
Sorry if I am stressing you out. So, if I wanted to distribute a Rhapsody library:

• I don't need to distribute versions for all operating systems (since I don't have to compile), but should I put the GPLv3 license inside the product?
• Can I sell it?

Thanks

[Christoph Hart]

@pelle yes to both questions.

[d.healey]

@pelle said in Distribute the library:

should I put the GPLv3 license inside the product?

Yes, you should include a license header in your scripts and a license file in your repo/project folder. Here's an example - https://codeberg.org/LibreWave/TheShepherdsFlute

@pelle said in Distribute the library:

Can I sell it?

Yes absolutely!