-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identification stickers for hardware #7
Comments
@Shrinks99 how do you feel about having no logo for now and perhaps you (and maybe Io) will come up with a new logo, or at least decide on an existing one, but we don't need to put them on the sticker for now. Instead decide on a wordmark and font that we'd use consistently across spaces? @darkdrgn2k do you need these by Thursday? |
@benhylau This is exactly what I was planning to do, wordmark & design will be similar to the proposal doc's styling. Are we choosing the 75 mm x 50 mm for $86/100 stickers option from Stickermule? Once I have confirmation on this I'll make it today. |
I would suggest keeping them as small as possible. Our hardware is not that big. |
Here's the two smallest sizes next to some stuff from my desk for reference. @darkdrgn2k The 50x25 is pretty much asset tag size, do you think the 75x50 would fit on everything or is it too big? |
I would say either that or 50x50, but definitely get at least 200. One deployment is 10 stickers, so we'll run out in no time. If you can make them nice enough we can dual-use them for marketing, in which case just print 500 of them. If the grant falls thru I'll cover your cost for it. Also, round corners are perhaps harder to peel. |
200 asset tags have been ordered, they will be sent directly to @darkdrgn2k and should arrive on (or before) Friday August 14th. Asset tag files have been made available in the design repo |
This initial comment is collaborative and open to modification by all.
Task Summary
ποΈ Re-ticketed from: #
π Due date: 7/22/2020
π― Success criteria: Stickers ready to be applied to hardware.
...
To Do
The text was updated successfully, but these errors were encountered: