Patch to add a favicon to the web UI #1592
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1592
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
I came up with a small (almost trivial) git branch to add a favicon to the web UI. More information is available at the commit page on github.
I reviewed the XHTML changes on the git branch and they look good. I confirmed that those are all the XHTML files that need to be changed. I also like the favicon (if we're staying with Kevin Reid's icon more generally).
CC BY 3.0 Unported is not compatible with GPL, primarily because of the attribution requirement. (I hate acting the part of license compatibility enforcer, but care about getting updates to Tahoe-LAFS into distributions like Debian that are strict about that.) This probably means that Kevin Reid's icon needs to be relicensed, so that the derived favicon can be.
I was afraid of the licensing issues and totally understand (hence the long-winded git comment). Bad things happen to projects with sloppy copyright. Have you contacted kreid about relicensing?
If he agrees, you've got the go-ahead from me to relicense my derivative (the 16x16 icon) under whatever conditions he chooses.
Dear Kevin: may we please have permission to use your Tahoe-LAFS logo contributions under the same licences as Tahoe-LAFS itself? Actually, would you mind granting the Tahoe-LAFS Software Foundation permission to use it however that entity sees fit, with little or no restriction? Thank you!
(The reason we're asking is to include a favicon derived from your logo in the Tahoe-LAFS distribution to include in the WUI.)
I hereby give permission for my Tahoe logo designs and SVG files (all material at http://switchb.org/kpreid/2009/tahoe/ ) to reused, modified, and distributed under the same license(s) as Tahoe-LAFS itself, including any future relicensing or other such change which the developer community has consensus upon.
Any idea when/whether this will be landed?
I removed the
licensing
keyword. Thanks, Kevin! I don't see either areview-needed
keyword or areviewed
keyword so I can't tell instantly what state this ticket is in. Someone please push this ticket further along! https://tahoe-lafs.org/trac/tahoe-lafs/wiki/PatchReviewProcessmarcusw: your changes are still under the license at https://github.com/marcuswanner/tahoe-lafs/commit/b3ee8882f0819cab0efdcf1b7620bc9c74b2ff2f . You need to relax that license, as kpreid did.
I hereby give permission for my Tahoe logo designs and SVG files previously referenced in this ticket and that git commit message to be reused, modified, and distributed under the same license(s) as Tahoe-LAFS itself, including any future relicensing or other such change which the developer community has consensus upon. This release is in addition to the one on the git branch message.
The same applies to the files linked to in (@@https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1185#comment:-1@@)
Thanks. Reviewing.
Oh, I already reviewed it in comment:86519. OK, I'll land this now.
In changeset:054374400e28cb00:
I added some tests in changeset:531f562fcfcb7b68. Review needed for those, and also for a cleanup patch changeset:4618571389c62d2f.
Reviewed changeset:4618571389c62d2f and changeset:531f562fcfcb7b68.