Idea: T-Shirt for conferences where we don't have a booth #99
Labels
No labels
category
budget
category
docs
category
limesurvey
category
meta
category
physical events
category
swag
category
virtual events
charter
ambassadorship
charter
events
charter
recognition
good first issue
help wanted
needs
event report
needs
reporter feedback
needs
vote
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
team
advocates
team
ambassadors
team
commops
team
council
team
design
team
docs
team
g11n
team
marketing
team
mindshare
team
websites-apps
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Blocks
Reference
mindshare/tickets#99
Loading…
Add table
Add a link
Reference in a new issue
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?
Hey there,
@gridhead and I were chatting this morning and we came up with an idea for fedora participants where we e.g. do not have a booth. Hence here the idea pitch.
Have a t-shirt with "ask me about fedora" & a QR code which e.g. links to https://www.fedoraproject.org/ on the back (preferably not front as it could be awkward for e.g. women).
This would be a great chance to
It would be great to have this in a standardized format for a uniform representation.
Cheers,
Julia
Edit: this could/would also be a Design request but I suppose having a mindshare decision first might make sense (as advised by @gridhead )
@ekidney is this something that we can loop into #115? We do not need to print a tee shirt just yet, of course, but having the design at hand and reviewed by folks before Flock To Fedora 2026 would be super awesome.
Speaking of reviews, I know I need not ask this, but @jbley, would you be willing to help out guide the direction of the design from a superficial level while the Fedora Design team works its magic on the presentable draft?
@t0xic0der wrote in #99 (comment):
We can loop it into #115 - however the design team is currently at full capacity leading up to Flock, so we won't be able to provide a design before the event.
I’m happy to open a design ticket to get this looked at after Flock. We should discuss the logistics beforehand though and have a plan for production and distribution to ensure the design work will get used :)
Let's not plan for having a distribution now. I understand that would be an unreasonable ask. Since Flock is anyway a Fedora Project event, it wouldn't really make sense to push it to have it until then.
If you could open a ticket for the same and perhaps provide updates on it, that would be great to support other regional events. I am adding this one as a dependency for #115, if that's fine by you?
Apologies if I was unclear, I meant we should discuss this more and have a fully fleshed-out plan / proposal before bringing it to the Design team to be designed. The design team has quite a backlog and I want to ensure any printed design request has a production and distribution plan rather than just be a 'nice-to-have' idea. This is so the Design team can prioritise and work on tickets with the most community impact.
Here are some Qs that the Mindshare team can discuss to help develop a proposal:
The answers to these questions will help define the specific deliverables for the design ticket too. Once a more fleshed out plan is created, I can open a design ticket.
@ekidney No confusion there, to be honest. I was planning on bringing it up for the Fedora Mindshare fortnightly meeting, but now, thanks to the clear questions, folks can partake in this conversation without having to participate there. I do understand that the hands of the Fedora Design team are occupied right now and I do not intend to add to it. If anything, we do not stand to lose much, if we were to get the details on this ticket a little later than we were supposed to, but it is good to have it on the radar.
Hi Emma,
I think the idea is a bit simpler. It is to have a layout source people can print on their own t-shirt/hoodie.
So what would be needed
People then can print it individually and wear it (and spread more awareness) at any event they attend (e.g. open source conferences, meet ups). I believe most of it is already available anyway and "just" needs to be put together along with the proper guidelines/recommendations.
I hope this clarifies a bit and I am happy to work with anyone once the design ticket is up.