FSFE/fsfe-website
24
30
Fork 88
Code Issues 62 Pull Requests 10 Wiki Activity

Add copyright and license headers on look #2685

Closed
nico.rikken wants to merge 2 commits from feature/license-annotations into master
pull from: feature/license-annotations
merge into: FSFE:master
Conversation 7 Commits 2 Files Changed 141 +955 -4
nico.rikken commented 2022-06-14 06:58:50 +00:00
Member
Copy Link

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 2022-06-14 06:58:52 +00:00
Add copyright and license headers on look
All checks were successful
continuous-integration/drone/pr Build is passing
Details
d801e58edc 
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 commented 2022-06-14 07:01:07 +00:00
Author
Member
Copy Link

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 2022-06-14 20:23:59 +00:00
Improve license information of Roboto fonts
All checks were successful
continuous-integration/drone/pr Build is passing
Details
f4e0d64d4c 
There is more accurate information in the MATADATA.pb files in the font repositories:

https://github.com/google/fonts/blob/main/apache/roboto/METADATA.pb
https://github.com/google/fonts/blob/main/apache/robotoslab/METADATA.pb

Signed-off-by: Nico Rikken <nico.rikken@fsfe.org>
max.mehl commented 2022-07-27 14:15:59 +00:00
Owner
Copy Link

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?
nico.rikken commented 2022-07-27 20:30:26 +00:00
Author
Member
Copy Link

@max.mehl yes please, good suggestion.

@max.mehl yes please, good suggestion.
max.mehl commented 2022-07-28 09:22:07 +00:00
Owner
Copy Link

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
bonnie commented 2022-10-12 12:24:38 +00:00
Member
Copy Link

@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?
nico.rikken commented 2022-10-12 19:30:26 +00:00
Author
Member
Copy Link

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.
👍 2
bonnie commented 2022-10-13 08:24:23 +00:00
Member
Copy Link

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.
tobiasd closed this pull request 2024-05-23 09:21:10 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

   
build

   
cgi Scripting

   
design

   
disruptive

Requires careful coordination and documentation changes

  
documentation

   
duplicate

   
easy

   
feature-request

   
help wanted

   
javascript

   
priority/low

   
question

   
system-hackers

   
tagging

   
text

   
translations

   
wait/bugfix

   
wait/inprogress

   
wait/misc

   
wait/proofread

   
wontfix

   
xsl
No Label
bug
build
cgi Scripting
design
disruptive
documentation
duplicate
easy
feature-request
help wanted
javascript
priority/low
question
system-hackers
tagging
text
translations
wait/bugfix
wait/inprogress
wait/misc
wait/proofread
wontfix
xsl
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FSFE/fsfe-website#2685
No description provided.
Delete Branch "feature/license-annotations"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?