search

ortiza5 / modding-vivaldi

A not-even-WIP-anymore collection of guides about modifying the Vivaldi browser
The Unlicense
7 stars 1 forks source link

License #2

Closed ghost closed 3 years ago

ghost commented 3 years ago

We need to choose a license as well. The upside of strong copyleft licenses is – well, copyleft. The downside of them is that people have to be careful when copying content.

I would recommend using a software license even though most of the content won’t be code, because there will be a fraction that will be code.

What do you suggest?

code3z commented 3 years ago

Of course I'm going to suggest unlicense-ing it. The problem with the strict licenses is dealing with strict licenses. Would it hurt you if someone used this repository commercially, for a closed source project, or without proper attribution? Probably not. But it's up to you.

Another possibility is a separate license for code vs text. Since all code will be inside markdown code elements, they are easy to distinguish legally. There could be a cc-by for text and "No Rights Reserved" for code.

ghost commented 3 years ago

Hmm, probably yes. But I’ll keep this issue open for other ideas.

ortiza5 commented 3 years ago

I would say go with Unlicense as well. The distinction between code and text isn't an issue for me. If someone is following a guide that includes a segment of code, they should be able to copy it and use it however they wish.