Tahoe-LAFS logo and branding assets #3724
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
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#3724
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
After reading through older Trac tickets https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1185 and repository files, I couldn't find the original source files for the Tahoe-LAFS.
I am now working on creating a new Tahoe-LAFS logo and all the branding assets, including usage for social media purposes, templates, communication assets and more.
I will most likely come with 2-3 proposals for a new logo and we can discuss it here, one of them being the current logo but re-created.
This plan will be laid out on a document, sort of a style guide, which will help everyone regarding how and what to use when it comes to comms, both inside and outside the organization.
To add to the discussion, the font-face used for the current logo is not openly licensed, so that can create problems down the line. A new font face will have to be used, preferrably from Google Fonts or any other service that offers OFL fonts.
The current Tahoe-LAFS logo has been reconstructed and is using the Poppins font, licensed under OFL. Included are also assets to be used on social media accounts. https://github.com/tahoe-lafs/new-website-prototype/tree/main/brand-assets
I heard back this morning from Kevin Reid, the creator of the original logo (Kevin's response below my quoted text):
[included hyperlinks to the relevant original discussions.]I've
It was based directly on the same “Tahoe-LAFS Architecture” diagram currently on the site and documentation — the relied-upon client/gateway (red) using the numerous storage servers (black). I do not think there were any other specific sources; the remainder of the design was integrating the diagram and “Tahoe” in a way that looked good ("LAFS" was a later addition). Perhaps there was some “hot air balloon/parachutes” in it.
I'm pleased by my work having served well for 11 years. If you're planning to revise it, I'd just ask you to keep in mind that the original circles and arrows — and the usage of color within that portion — have the abovementioned specific meanings. That's just a suggestion, of course — it's licensed CC-BY-3.0 and also under the project's GPL license and so you're free to create any derivative work you want.
Thanks maylee, that's good to know. I'll add the CC-BY-3.0 license terms on the repo and also write about the changes that were made to the logo.