Add copyright and license headers on look #2685

Open
nico.rikken wants to merge 2 commits from feature/license-annotations into master
Collaborator

Provide copyright and license headers for the files related to the look of the website. This includes the Bootstrap framework and fonts.
Licenses are included in the LICENSES directory as a step towards REUSE compliance.

Signed-off-by: Nico Rikken nico.rikken@fsfe.org

Provide copyright and license headers for the files related to the look of the website. This includes the Bootstrap framework and fonts. Licenses are included in the LICENSES directory as a step towards REUSE compliance. Signed-off-by: Nico Rikken <nico.rikken@fsfe.org>
nico.rikken added 1 commit 8 months ago
continuous-integration/drone/pr Build is passing Details
d801e58edc
Add copyright and license headers on look
Poster
Collaborator

Some comments on this PR

I didn't know what would be the beginning year for the FSFE styles, so I didn't include a date in the copyright annotations. If anyone knows that would certainly improve the quality of the annotations.

The share button styles originate from a separate repository. For now I've kept the AGPL-3.0-or-later license defined there: https://git.fsfe.org/FSFE/share-buttons Considering that we decided on CC0-1.0 for the styles, that could also apply there and the license could be updated in this repository.

### Some comments on this PR I didn't know what would be the beginning year for the FSFE styles, so I didn't include a date in the copyright annotations. If anyone knows that would certainly improve the quality of the annotations. The share button styles originate from a separate repository. For now I've kept the `AGPL-3.0-or-later` license defined there: https://git.fsfe.org/FSFE/share-buttons Considering that we decided on `CC0-1.0` for the styles, that could also apply there and the license could be updated in this repository.
nico.rikken added 1 commit 8 months ago
continuous-integration/drone/pr Build is passing Details
f4e0d64d4c
Improve license information of Roboto fonts
Owner

Thanks for working on this!

As author of the share-buttons and also the one who chose the license, I would be fine with re-licensing them to CC0-1.0. Shall I do this first so you can update this branch here accordingly?

Thanks for working on this! As author of the share-buttons and also the one who chose the license, I would be fine with re-licensing them to CC0-1.0. Shall I do this first so you can update this branch here accordingly?
Poster
Collaborator

@max.mehl yes please, good suggestion.

@max.mehl yes please, good suggestion.
Owner

Alright, please find the relicensed upstream here: https://git.fsfe.org/FSFE/share-buttons

Alright, please find the relicensed upstream here: https://git.fsfe.org/FSFE/share-buttons
Collaborator

@nico.rikken: thank you very much for taking care of this. I was wondering what the current state is and if there are any blockers?

@nico.rikken: thank you very much for taking care of this. I was wondering what the current state is and if there are any blockers?
Poster
Collaborator

The discussion on unlicense vs CC-1.0 was a blocker. Now I just need to update the pull-request.

The discussion on unlicense vs CC-1.0 was a blocker. Now I just need to update the pull-request.
Collaborator

The discussion on unlicense vs CC-1.0 was a blocker. Now I just need to update the pull-request.

nice :) and thank you very much! let me know if you need anything and I will try my best to help.

> The discussion on unlicense vs CC-1.0 was a blocker. Now I just need to update the pull-request. nice :) and thank you very much! let me know if you need anything and I will try my best to help.
All checks were successful
continuous-integration/drone/pr Build is passing
Required
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
Sign in to join this conversation.
Loading…
There is no content yet.