Food for thought:

I dont see recruitment being the main issue. I think there are more recruits than we have capacity to mentor. Rather I think the follow up is what we should work on improving. Eg a mentee posts smtg to a ticket for feedback.... and it gets lost in the noise. Recruits / mentees should have a shorter time period to wait for feedback, their stuff should be higher priority. We should check in with them regularly and have a good way to track who needs checking up on.

I think we should fix that first before bringing in a bigger pool. Does that make sense?

@riecatnor I think the ideas you have generated are great and I think @duffy makes a good point as well. What kind of help do you need from mindshare to make this happen? I am trying to understand the scope of the request.

Food for thought:
I dont see recruitment being the main issue. I think there are more recruits than we have capacity to mentor. Rather I think the follow up is what we should work on improving. Eg a mentee posts smtg to a ticket for feedback.... and it gets lost in the noise. Recruits / mentees should have a shorter time period to wait for feedback, their stuff should be higher priority. We should check in with them regularly and have a good way to track who needs checking up on.
I think we should fix that first before bringing in a bigger pool. Does that make sense?

@duffy - thanks for jumping in, I feel you have the knowledge base to truly understand the issue that I am perceiving. I agree with you on improving mentoring, included as one of the ideas I suggested. I know first hand you are an amazing mentor, so any ideas you have regarding how to improve that aspect would be great.

From my perspective with badges: we have now been running badges meetings (almost) every two weeks for about a year, ensuring to look at the newly modified issues. This is the strategy to hopefully ensure new activity does not get overlooked. With almost 150 open issues, this is basically all we really have time for. I do think that there are some badge design contributors (with drafts) still active within Fedora(but not so active with badges), so would be good to go through all issues and re-triage, check-in, etc. Wondering if this is something I should do solo, or maybe we could consider a small event? I know the sysadmin side has plenty of things to do as well, so could be more than just the design aspect.

@duffy, going to Flock this year and being one of only a couple design team people was discouraging. Usually we have at least a handful. Have you experienced this before? (I am guessing, yes?) Maybe it's not really an indicator of anything, and more of a fluke.

@riecatnor I think the ideas you have generated are great and I think @duffy makes a good point as well. What kind of help do you need from mindshare to make this happen? I am trying to understand the scope of the request.

@bex, I opened this ticket to the mindshare committee at your suggestion. A lot of stuff going on last week :), so reminder, I brought up this issue during the open forum at the closing session at Flock. You suggested that I open a ticket here to get some help/ideas. I think the scope of the request includes some of the following things(but not limited to, as I think @duffy may have more thoughts, and potentially answers to these questions):
- Cross examination of the issue. Is it an issue for Fedora overall? Do people feel their design requests are being addressed? Do people want to more design assets for other parts of Fedora? Do people wish to see a greater emphasis on design within Fedora? (across all platforms/spaces)
If it is determined it is an issue we want to address/work on:
- What do other parts of Fedora wish to see from the Design team?
- How can we use the existing network/infrastructure/teams to recruit/mentor more effectively?
- What kind of events would it be worth it for us as Fedora design team and Fedora overall to attend to gain more interest?
- What kind of strategies does Fedora use to revitalize interest for past contributors already? If we have an inactive member, what can we do to bring them back?
- Would it be a good idea/use of resources to create a pretty looking Fedora design site to interest more contributors? (not a wiki - If I didn't have the Outreachy internship/@duffy at the beginning, this would have been a barrier to entry for me)
- How do other parts of Fedora overcome the issue with providing critiques that are ill received?

Hope that helps to clarify-- and this is really mostly from my perspective. I'm looking forward to hearing others thoughts.

@riecatnor

i had a random idea but couldnt post it before. what of we had a ticket system for mentees / new contributors. if you want to join the team you file a ticket. the ticket assignee is your mentor (or contact point if mentor is too heavy ) the mentee ticket gets closed when the mentee becomes a mentor themselves 😁 it could also be closed or deferred if they get too busy. would be cool to have a bot or something to do a checkin at regular intervals... remind the mentor to check in w mentee and or vice versa. we could monitor how many mentees per mentor and balance the load and hand off this way so a mentee doesnt have any gaps. anyway with so many tix in the badge system, if you organized mentorship by mentee its going to be smaller and easier to manage i think. eg during a triage meeting could for instance do every other... first ticket triage from mentee queue, next ticket triage from badge tickets queue (does that make sense?) or every other meeting, one meeting is badge tix the next is mentee tix.

the other idea i forgot are design team bounties. they do work and i think lead to good retainment. they take a long time to set up tho. too heavy for badges but for larger or one off projects theyre good.

i think a mentee triage event of sorts is good for clean up but i think we need something to maintain and not accumulate so much debt over time?

i felt like there were a lot of us designers at flock last year. moreso in fact than i recall ever being colocated before besides the design FAD. so its a bummer there was just the two of you there. i dont know much about how this years flock was organized, so i dont know if its a matter of designers wanting to come and not being able to secure funding or if the location was more challenging for our design community to travel to (broadly speaking) than US events or what. I will say if its any solace that I dont necessarily see a trend but I do travel a lot less these days personally. Generally i think we're the minority in the broader open source community... eg my big trip this past year was ohio linux fest.... i didnt meet any other designers there - period - that i can recall. usually at gnome events its a handful. lgm is probably the biggest grouping of floss designers in one place ive encountered. i dont know if thats reassuring. And maybe we're doing smtg right compared to these others in that we tend to have more women than men where men still seem to be the majority in other floss communities of designers.

in the past weve also loosely coordinated / planned going to events together like lgm in madrid or flock last year. outreach to invite designers to participate / coordinate / just light social pressure to encourage them to come helps.

Re: your set of excellent questions -

1) I want to see greater emphasis on design within Fedora. As ostensibly the person who should have been working on this all along (and definitely the longest) I alternate between despair at being such a failure on this count and helplessness in terms of design rarely getting a seat at any major decision making tables save for branding (altho this is alarmingly increasingly less as i see branding decisions being made wo our consultation or involvement) and websites / infra web apps. I also would love for us grow beyond the logo / swag grind (which is fun but after 15ish years of it at least for me is getting less fun esp when strategy and decisions around it are further out of reach) and really include UX / interaction / strategy (changing the name from fedora art team to fedora design team was a hopeful reach for this, back in like 2007 or 2008) but I dont think its really happened yet. UX tho is hard to do with volunteers at the short term / toe dip committment level and graphic design esp badges is so very good thanks to the guidelines, assets, workshops, and tutorials you have put together for badges. Maybe to expand / foster ux involvement on our side we plan a schedule of say 2 funded engagements a year (maybe an outreachy and a rht internship or whatnot) in recognition ux is a long term ki d of involvement necessarily.

THE PROBLEM is designing UX that there is no or faltering project level committment for. I have brilliant designs out together by mentees that never got coded bc there was nobody to do it or priorities shifted. (Eg the hubs work Suzanne did for ambassadors and regional Fedora communities.) And where the work and resources are actually working, I feel (perhaps unfairly you tell me) design doesnt get a seat at the table until said projects want a logo or a sticker and thats the extent of our involvement.

THAT IS NOT A DESIGN CULTURE.

You and Maria do amazing work with the badge art. You also enforce.good guidelines / decisions higher level about what makes sense to be a badge and what is fair / strategic and have some autonomy there. I want that for us as designers in Fedora at a broader scale. Where maybe you could see my overall frustration with Fedors and design these days.... is the badge app itself. The UI probably needs an update. We only had 22 devconf us badges claimed, a 400+ person event... how can we get.more interest / engagement in the platform. Is it working to encourage contribution? Is anyone actively working on improving the codebase? Is it being invested in? Where will it be in 5 years? Do you feel you have a seat at the table where such decisions would or could be made? Is badges an important initiative for Fedora strategically?

When Im dead I dont want my legacy to be a pile of Fedora branded crap in a landfill. Maybe im just really f-in burned out though 😓

2) Exisiting infra to recruit mentors more effectively... a think a combo of your idea about blogging in the community blog and maybe my wacky mentee ticket queue idea?

3) What kind of events to get more interest.... I dont know. For what Im looking for I think getting the devs and designers in a f2f setting is good but i dont know the most productive context. I guess, rather ralking about engaging designers in a box of stickers logos swag and boxing in the entire discipline i instead want to see us included in a broader project context instead of limited to design specific fads and design sessions at flock. id like to see fedora design team members also consider themselvds members of the project teams of specific tech we work on.

4) revitalizing members... i dont think we do much. i do think our social media accts help keep ppl engaged. maybe we should do a review of design group fas accts and send out nice notes to folks we havent heard from in a while to check in?

5) website... i dont think its necessary for the mentorship capacity we have now but if we had a larger set of regulars actively participating in weekly meetings (say 6-8) maybe smtg to think abt. fedora hubs was the long term plan for this and its been canned so we need and dont have a plan b.

6) theres this crucial conversations training tjing i did at red hat that has a pretty good structure for providing critique and working thru when its ill received. do you see critique as a conflict inducing issue in badges? i tend to be pretty free w crotique in the main design queues tickets and cant think of any times it was poorly received bit maybe i was oblivious :-/ do you think critique is the issue you have sustaining "repeat customers"? or could it be smtg else?

@duffy Thanks for your honest feedback.

The original goal for Mindshare was to be an enabling force for teams like Design and Marketing to have input on strategic goals and objectives more widely in the Fedora Project. I suggest considering what we as a cross-project Committee can focus on to follow better design culture across the project.

I agreed it was disappointing that useful, detailed, and thorough design work was left unrealized for Fedora Hubs. What were the factors that resulted in this situation? In retrospect, are we better able to identify what was successful and what was not? I think answering this question, extracting the painful points, and breaking them into actionable items lets us start working at making visible improvements to the issues raised here.

Re-reading @riecatnor's original ticket, these seem like suggestions because of past experience receiving frequent requests for this type of work. They are small suggestions to represent the Design Team's input to Mindshare for potential connection points between strategic and tactical teams. These suggestions move us closer to supporting the Design Team by better connecting the common tasks and activities that receive attention in the Design Team to other effective areas of contributions not yet considered.

This also pairs with a fedmsg question we are trying to answer in CommOps, about drive-by contributions and what they show us about high activity, low complexity contributing entry points in the community. This could be leveraged for the Design Team too.

I think our next steps should be to compare workflows to (1) ensure Mindshare is structured to fairly balance a strategic design input from the Design Team, and (2) identify high-value contributing possibilities to help sustain contribution options for Design Team members.

Thoughts?

@jflory7

I can't think of a context ive operated in where a third party committee enabled design successfully so I'm at a loss as to how mindshare can help. Where design is most successful is a tight loop between design, client, devs, and users. I guess one of the issues is who is the client (generally, in fedora) nd what problem are they looking to have design solutions for?

What exactly can mindshare offer here? What can mindshare do?

We - design - currently engage at a microlevel with clients. The problem is it results in disjointed work. Eg people somehownfind money to order items that I find myself frequently questioning is this a good value for the money and does this really align with and support our strategic goals?

Fedora is driven (as much of FLOSS is) by itch scratching, but we do have strategic project wide goals. How those are being set and planned for, Im not real sure, probably a combo of the Council and FESCo, and any subgroups theyve enabled / tapped / whatever in the resourcing and realization of the work.

Ive seen design enabled in that kind of context a few ways (generally, outside of fedora)... right now we have fedora feature pages which i think serve as a reqs doc of sorts. Ive worked in context where design gets a sign off on reqs documents. Have also seen design have representation when high level goals and projects are decided on. Eg during release planning meetings for a product. The biggest thing for those who do not have a voice is for those who do to speak up for them.

I dont think fedmsg is the right level to be looking at for figuring out design engagement. I think the issues are pretty obvious, but as is the overarching theme we dont have technical resources to realize the things we think could solve the problem. We have technical resources to maintain fedoras infrastructure in terms of building packages, updates, packaging, release mgmt, etc but we dont have technical resources - afaik - with a primarily charter of enabaling community, doing things like implementing hubs (which in my view was always short changed and never considered critical compared to the distro building components of the infra) or writing scripts to automatically follow up with new mentees, or providing a dashboard to let mentors manage their mentees,.or creating other community mgmt centric stats. If Im wrong if Im.being unfair please correct me but this is how Ive seen things work out in practice.

I also think monitoring contributions at a fedmsg level misses the high level / strategic stuff that is really the biggest problem here. I hope this makes sense

Because mindshare afaict doesnt have technical resources to assign, i dont think mindshare can help with the community mgmt tools. Can mindshare help w getting design a seat at the table where strategic goals and plans are being made? I dont know. Those decisions arent being made in mindshare. Does mindshare have influence where they are?

I dont know what you mean by compare workflows. What workflows? Compared to which other workflows?

What do you mean by high value contributing possibilities?

@duffy @jflory7 @bex

Hello, all. Apologies, as it has been some time since there has been any activity here from me. There are a lot of questions and thoughts to process on this ticket. I think to some extent I went in with a general overview and a LOT of questions, and I think specifics could make this more constructive.

Here are some questions I think the mindshare committee could address to help work towards increasing design team retention/contributions:

Ambassadors
- Feedback loop on what individual pocket communities need to encourage and bring people who currently contribute to Fedora to the design team. What kind of resources/stories/mentors are needed to tap into this resource? Connecting individuals from these communities to design mentors

Marketing
- What platforms is the marketing team currently using that we can also use to gain/inspire current and new contributors? What kind of content would they want from the design team? What kind of content is successful on what platforms?

Design
- Who is willing to mentor? Who are our potential mentees, and how do we work to get them involved? How to inspire inactive members to come back to contribute more?

CommOps
- On the data science side- can we generate stats regarding the design team to learn more about what has been successful versus not in the past? What can we learn from these stats? On the community side- telling stories of successful designs/designers, making our designs more visible

Docs
- Creating a design & badges docs page. I think the a badges docs page has been initiated. I think this would be great to do for the design team as well. Creating a place for new/inactive members to understand the current process for contributing design.

Websites
- What can the design team do to be more involved in actively supporting the UX of the websites subproject? What kind of resources could be helpful?

I think these questions can help focus what I hoped to achieve by opening this ticket. I am looking forward to others thoughts.

What platforms is the marketing team currently using that we can also use to gain/inspire current and new contributors? What kind of content would they want from the design team? What kind of content is successful on what platforms?

I know @x3mboy is doing the Fedora Podcast as an example of a new medium. There is a ticket for a new website. The take-away cards are also an example of content the Marketing team is working with. Perhaps @bt0dotninja or @bcotton could also weigh in here.

On the data science side- can we generate stats regarding the design team to learn more about what has been successful versus not in the past? What can we learn from these stats? On the community side- telling stories of successful designs/designers, making our designs more visible

This is something I'd like to work towards doing more of again and need to work with the team on enabling. Doing data analysis with the tools we have today was a big part of our session at Flock (sneak preview of our upcoming CommBlog report).

If the Design Team could come up with a set of criteria to measure for, this helps us move forward. Additionally, if there are suggestions for a specific time window to look at (e.g. after a specific change to workflow or something else notable happened), that helps. Examples of criteria could be:

• Mailing list activity
• Pagure activity
• IRC meetings
• Other things used by Design Team also tracked in fedmsg?

Ideally, all of these things would be great, but starting with one gives us a realistic scope to start with by focusing on specific criteria and broadening out as we build a process for these requests.

I think the a badges docs page has been initiated.

This is started here.

I think this would be great to do for the design team as well. Creating a place for new/inactive members to understand the current process for contributing design.

It is quick to convert some wiki pages into the new docs site to help as a starter. I think knowing the top 10-15 relevant wiki pages to initially convert is helpful to know from the Design Team.

Hello from an old contributing reactivating itself.

I know this is an old ticket, but seems to be still alive, so here are my inputs from an outside viewer trying to get back to work:

• Aye, probably the most uncomfortable part when I was active was having designs that never went to development.
• We are only useful when needed, but then... nothing else happens. This gets frustrating even on a work environment.
• New tasks that don't get a quick answer or get a solved message ASAP. If someone comes with the push to make a task, then that task should be followed by someone until it's done (btw, thx for the infographics... that makes a great example.)

From what I see, main issue is to do things that get a real result (either designs, classrooms, FADs, etc) and have a recurrent optimization roadmap, so the team doesn't get stuck doing the same things over and over again. So here are some suggestions to increase participation, since I agree with @duffy that it's probably a best practice to organize the house before inviting people.

• Badges: The fact that you have to claim a badge has always seem to me a bit of a pain. Having something automated people can QR or sign at the registration table would make this easier... and making the process of getting the badge easier will make the will to improve them larger. A higher demand on badges, or a change on how we show them up would also do the trick. A badge feed for your blog or about page? A badge sticker for your laptop when attending a conference? Possibilities are endless, but people only want designs they want to showcase.

• Websites: I come from a 3 year time-off period, and was really happy to see the changes to the full structure (both sides, design and workflow), however, right now... was hard to catch up with everything. A lot of places to report everything, a lot of instances... Everyone seems to have their own group and to interact between 2 or more teams or groups you have to duplicate tickets for everything. Might be my bad, just take it as someone new output.

• Swag: I've always ALWAYS struggle with swag on my region, specially my country. When swag started everyone was busy making swag for conferences, meetings, wallpapers, tshirts, etc. Having a central swag design repo (by event, release, or X) would help focus the efforts of the design team?

• Info: I updated last week the main wikipage for our official wallpapers. It was outdated and stopped on F27 I think. Our main pages on the wiki are kinda forgot, and there's a lot of things to add, new process, links and people that could find a useful resource there to contribute, but the fast grow of the infra structure left that section kinda forgotten.

Final thoughts: Probably because @duffy was my mentor since 2004 I think I understand her point of view, probably because I lived that in LATAM being the only designer doing artwork for so many years, even if I got several new contributors... the main issue with those new contributors was that there were no new exciting things to do, besides badges (which I personally love) and the main wallpaper design which "seemed too much responsibility for someone new". I didn't even got them interested on translating the official artwork because many of them didn't speak English. To resume, I see is a lack of motivation into do new things... cause everytime something edgy comes to the table, there's no enough interest to get it done.

Is this something the Design team with the help of members from other teams could change in the near future? what are the real issues that get the Design team growing at a slower pace than other groups?

Hope not to interrupt with this long text an old ticket. If not useful, just dismiss :)

Salute you @tatica

You make great points. I will reply in-line to have better answers and context:

Hello from an old contributing reactivating itself.

Welcome back!

I know this is an old ticket, but seems to be still alive, so here are my inputs from an outside viewer trying to get back to work:

It's old but still alive and valid.

From what I see, main issue is to do things that get a real result (either designs, classrooms, FADs, etc) and have a recurrent optimization roadmap, so the team doesn't get stuck doing the same things over and over again. So here are some suggestions to increase participation, since I agree with @duffy that it's probably a best practice to organize the house before inviting people.

+1

Badges: The fact that you have to claim a badge has always seem to me a bit of a pain. Having something automated people can QR or sign at the registration table would make this easier... and making the process of getting the badge easier will make the will to improve them larger. A higher demand on badges, or a change on how we show them up would also do the trick. A badge feed for your blog or about page? A badge sticker for your laptop when attending a conference? Possibilities are endless, but people only want designs they want to showcase.

I'm not sure about this, maybe @jflory7 know more about this, but the way badges are claimed is not responsibility of the design team, but it's still a great point. Maybe we can brainstorm ways to earn badges and provides the community with this ideas to use it where they fit better.

Websites: I come from a 3 year time-off period, and was really happy to see the changes to the full structure (both sides, design and workflow), however, right now... was hard to catch up with everything. A lot of places to report everything, a lot of instances... Everyone seems to have their own group and to interact between 2 or more teams or groups you have to duplicate tickets for everything. Might be my bad, just take it as someone new output.

It's awefull. Look at fedora-marketing#283 to see an example of things I had to do, and even like that, the job is still not done. And idea here could be to create procedures to work with an specific team and procedures to have common tasks done.

Swag: I've always ALWAYS struggle with swag on my region, specially my country. When swag started everyone was busy making swag for conferences, meetings, wallpapers, tshirts, etc. Having a central swag design repo (by event, release, or X) would help focus the efforts of the design team?

I think we talk about this in the 1st Mindsahre FAD, and several wiki pages were taken down. I still think that a central design assets repo is the better way to attack this. There is even a pagure repo that could serve for this https://pagure.io/designassets but is unused.

Info: I updated last week the main wikipage for our official wallpapers. It was outdated and stopped on F27 I think. Our main pages on the wiki are kinda forgot, and there's a lot of things to add, new process, links and people that could find a useful resource there to contribute, but the fast grow of the infra structure left that section kinda forgotten.

Wiki pages are slowly going obsoletes in favor of docs' sites. Not sure if design have one, but it would be nice to move the main wiki page to the docs system.

Final thoughts: Probably because @duffy was my mentor since 2004 I think I understand her point of view, probably because I lived that in LATAM being the only designer doing artwork for so many years, even if I got several new contributors... the main issue with those new contributors was that there were no new exciting things to do, besides badges (which I personally love) and the main wallpaper design which "seemed too much responsibility for someone new". I didn't even got them interested on translating the official artwork because many of them didn't speak English. To resume, I see is a lack of motivation into do new things... cause everytime something edgy comes to the table, there's no enough interest to get it done.
Is this something the Design team with the help of members from other teams could change in the near future? what are the real issues that get the Design team growing at a slower pace than other groups?

That's what we want to address with this and @riecatnor was asking for help form us about it.

Hope not to interrupt with this long text an old ticket. If not useful, just dismiss :)

Thanks for bringing it back.

Badges: The fact that you have to claim a badge has always seem to me a bit of a pain. Having something automated people can QR or sign at the registration table would make this easier... and making the process of getting the badge easier will make the will to improve them larger.

Right now the claim process is scan a QR code, login in, get badge. How would you simplify this?

Swag: I've always ALWAYS struggle with swag on my region, specially my country. When swag started everyone was busy making swag for conferences, meetings, wallpapers, tshirts, etc. Having a central swag design repo (by event, release, or X) would help focus the efforts of the design team?

We have done a TON of work to get shipping working to the entire world. I think we have had one failed package in the last 6 months. Part of the goal for this was to help the design team. As I understood it from @duffy , the design team is not just concerned with the actual artwork, but they want to make sure that the final item is also of high quality. We have centralized swag production to allow us to produce more items of higher quality cheaper and then we ship them (RH is subsidizing that cost for us) to contributors as needed.

Again, as I understood @duffy , the reason to not provide a central repository of designs is to encourage/require people to work with the design team each time. This way they can manage the end-to-end quality.

Thanks for your feedback, keep it coming :)

Again, as I understood @duffy , the reason to not provide a central repository of designs is to encourage/require people to work with the design team each time. This way they can manage the end-to-end quality.

Maybe I'm wrong, but if the design team manage the process in a git work flow, the quality should be guaranteed. Or maybe the concern is that making it too available will cause people to take the work and modify it outside the repository?

@tatica:
Badges: The fact that you have to claim a badge has always seem to me a bit of a pain. Having something automated people can QR or sign at the registration table would make this easier... and making the process of getting the badge easier will make the will to improve them larger. A higher demand on badges, or a change on how we show them up would also do the trick. A badge feed for your blog or about page? A badge sticker for your laptop when attending a conference? Possibilities are endless, but people only want designs they want to showcase.

@x3mboy:
I'm not sure about this, maybe @jflory7 know more about this, but the way badges are claimed is not responsibility of the design team, but it's still a great point. Maybe we can brainstorm ways to earn badges and provides the community with this ideas to use it where they fit better.

@bex:
Right now the claim process is scan a QR code, login in, get badge. How would you simplify this?

I see a short-term and long-term answer to the Badges-end.

The short-term answer is we could set up a check-in form at the registration with something like Google Forms / Google Sheets. When someone checks in, they fill out the form with their FAS username. Tahrir, the Badges web app, accepts a comma-separated list with a badge name and FAS email to award badges in bulk. Theoretically, we could export the spreadsheet as a CSV, prefix the badge name to each @fedoraproject.org email address, and everyone is awarded the badge. This reduces work on the Badge claimers end but adds more work to the event organizers' end. This might work well for small events where a contributor is less familiar with the Fedora community but might be more challenging for a large event like Flock where I assume most people have a basic knowledge of Fedora Badges.

The long-term answer is the Fedora Badges app needs a lot of software engineering love to reduce the number of headaches and pains that exist today. As far as I understand, there is no engineer dedicated to work on this project, other than the part-time efforts of @sayanchowdhury and @cverna. As I understand the problem, it is not only engineering love but also leadership / management to focus and prioritize Fedora Badges / Tahrir development. @sayanchowdhury has mentioned several times that he does have time to work on the project but is overwhelmed about what to work on and what is most important to start on. There is a huge backlog of Fedora Badges bug fixes and feature additions and it is overwhelming even to me. Unfortunately, I don't have an action item for the long-term answer because I believe this is a question of allocation of resources (i.e. paid developer/project manager time) versus something that reasonably can be led by the community.

cc: @riecatnor

@bex no not opposed to a central repo of self-service approved designs at all. the UX design for this is going to be @terezahl's summer project starting next month. the ticket is https://pagure.io/design/issue/638

@x3mboy the idea is we'd have a repo of pre-approved print ready designs for swag and collateral that literally is meant to be handed off to a vendor and printed up with no modifications. anything that requires customization we really would want to go through this team, ideally via a ticket in this pagure issues tracker!