Learn more about these different git repos.
Other Git URLs
Unfortunately I don't know, but I know when they should be shipped and where ;)
If my talk gets accepted, I'd need them at oSC which will happen in Nürnberg / Germany on May 24 - 26, 2019 and I'd need them by that date.
There are stickers "Fedora Loves Python", we might go with the same idea for rust. Or have some hexagon ones like "Fedora Loves DotNet". I'm not sure which one would suit better.
Here's the Rust logo with usage guidelines: https://www.rust-lang.org/policies/media-guide
https://www.rust-lang.org/logos/rust-logo-blk.svg
We can probably somehow merge Fedora and Rust logos in one, I really don't know what would be the best :)
I probably don't understand this question, so I don't have any.
Yes. But it is not specific to that event because we can use it later.
openSUSE Conference 2019 Nürnberg / Germany May 24 - 26, 2019 https://events.opensuse.org/conference/oSC19
There doesn't have to be a text, but if there would be -- that must be an English.
For apparel or products
Apparel or product type
Number of colors to use
Background color of the object
Might be either Fedora colors or the Rust ones.
Print or embroidery
Print area size (printer can provide this)
Templates (if provided by printer)
If you can design the Fedora/Rust 3d model, that would be awesome too!
I assume at this point that we will ship F30 with the current Fedora logo, and use the new logo with F31. In that case, it makes sense for this design to use the current logo, and just not print up too many thousands of them.
I just heard that oSC usually has 200-300 people so I think we could print batch of 100-200 stickers and then print with a new logo more. Depends when are we going to print new ones.
Mindshare is looking at approving a print run of 75-100 to be bought via stickermule.com -- Ideally in this FY - if this design can be ready that would be awesome!
Here's a design similar to the fedora loves python stickers. Per Rusts guidelines, so long as the stickers aren't sold, then explicit approval is not needed. <img alt="fedora-loves-rust.svg" src="/design/issue/raw/files/f96fb0b3088d62452c5b30e9c0d6307a580efa40ee28bff96cad939f912f4b2a-fedora-loves-rust.svg" />
Can we try that with the inside of the Rust logo made opaque? It looks a bit odd to me with the heart showing through. It might also look odd if that doesn't show, but we can compare...
@robbiespeed very nice, i agree with @jistone - i think if you can do a white fill on the interior of the rust logo we're good.
No problem it was a pretty quick edit, also rounded the bottom of the heart a little to match the rounded corners of the rust logo, and to some extent the fedora one. I am leaning towards the opaque version, it looks less busy. <img alt="fedora-loves-rust_v2.svg" src="/design/issue/raw/files/8ffa0bc804b086628aeefe982a9810131ba9e24ec5a690e22abf7d4cf0e2a4af-fedora-loves-rust_v2.svg" />
@duffy @robbiespeed so what needs to happen in order to get the final approval? (I'm not experienced with the processes).
@ignatenkobrain hey i can approve it, can you post a png? i dont have a laptop this weekend and i cant open svg on my phone. for printing youll also need to import the svg into scribus and prep it for print in cmyk.
<img alt="fedora-loves-rust.png" src="/design/issue/raw/files/2858059ce5c6434a3b4a03b657d7a2237694759486e5458a6e6cb7d31e5aeb63-fedora-loves-rust.png" />
for printing youll also need to import the svg into scribus and prep it for print in cmyk.
That sounds complicated... Are there some instructions?
@duffy ping?
I followed the guidelines here https://fedoraproject.org/wiki/How_to_set_CMYK_color_on_a_design_for_printing
I'm not an expert on print, but I think this pdf should work <img alt="fedora-loves-rust.pdf" src="/design/issue/raw/files/1cf437512878e38b7ffb3b7eb33a7ba6b9a9711afb7cbbd8b98f8caed3e7ade8-fedora-loves-rust.pdf" />
@robbiespeed yep that's the tutorial i meant to point you at - you did a great job this looks perfect, approved from our end.
it looks like this is done so i'm going to go ahead and close the ticket.
Metadata Update from @duffy: - Issue assigned to robbiespeed
Metadata Update from @duffy: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.