chore: add copyright notice to all files

[mschoettle]

No description provided.

[AntonGladyr]

Would it make sense to have just one LICENSE file in the root of the repository where we would state that the repository has two different licenses. Or at least we should mention it in the README.

[mschoettle]

Would it make sense to have just one LICENSE file in the root of the repository where we would state that the repository has two different licenses. Or at least we should mention it in the README.

True. I added them only for GitHub, so that it shows up on the repo. But we could simply state it at the bottom of the README. Or, add a LICENSE file where we say that the repo uses the REUSE specification and so on...

[AntonGladyr]

Would it make sense to have just one LICENSE file in the root of the repository where we would state that the repository has two different licenses. Or at least we should mention it in the README.

True. I added them only for GitHub, so that it shows up on the repo. But we could simply state it at the bottom of the README. Or, add a LICENSE file where we say that the repo uses the REUSE specification and so on...

Btw, the licenses are not shown correctly in the repo - it should appear at the About summary, and also the names of the licenses should be included at the top of the README (currently it's just LICENSE instead of the license name; see nextcloud for example: https://github.com/nextcloud/server)

[mschoettle]

Btw, the licenses are not shown correctly in the repo - it should appear at the About summary, and also the names of the licenses should be included at the top of the README (currently it's just LICENSE instead of the license name; see nextcloud for example: https://github.com/nextcloud/server)

Good catch! It depends what we want.

Option 1:

We put the AGPL license in LICENSE. A custom text (similar to what Nextcloud has) we put into LICENSE-README.

Option 2:

We just put custom text in LICENSE.

[AntonGladyr]

Good catch! It depends what we want.

Option 1:

We put the AGPL license in LICENSE. A custom text (similar to what Nextcloud has) we put into LICENSE-README.

Option 2:

We just put custom text in LICENSE.

I like more option two since all licenses will be listed in one file. Also, we won't have Unknown licenses found like in nextcloud repo.

In fontawesome repo they just have one LICENSE file with custom text: https://github.com/FortAwesome/Font-Awesome#License-1-ov-file

[mschoettle]

I changed to a custom LICENSE file and also brought the branch up to date.

[AntonGladyr]

LGTM!