GSoD mentees swag idea #60
Comments
|
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
|
@mcturco @Barbanio @fmvilas @derberg Hey folks, was talking with our lovely GSoD folks and @thulieblack made a really good suggestion. She explained she would love to have a hoodie instead of a t-shirt for swag. (When she said that, basically everyone in the call got excited and seconded her idea.) Since everyone in '22 GSoD REALLLLYYYYYY wants/hopes for a hoodie, can we make this happen for them? |
All for having a hoodie instead of a t-shirt 🤩 Next question is, does everyone prefer a zip-up hoodie or a pullover? |
Definitely a pullover for me 😄 |
|
I prefer a pull-over, not sure about others though. |
Pullover for me as well😁! |
mcturco
added
🎨 design
I also prefer a pullover |
|
we definitely have to calculate costs, as if we give it to GSoC participants, we should do the same with AsyncAPI Mentorship. And these designs are custom, so we won't be able to use normal service that we work on now atm. @Barbanio thoughts? |
|
Yes, I think we should unify this type of swag with all kinds of programs. We could use Printful, the company we have been using this year. What budget do we have for this? |
|
Hi! I have a rough composition of what I think could work on a hoodie for this Swag piece. Let me know if you all like this art direction and I can work to refine the details!
|
|
The main thing that comes to mind is …I wonder if we can make sure to reference not just Google but also AsyncAPI 😬🎈🎈🌈 |
|
This is beautiful indeed, but I do agree with Ale. It would be great if it could be more of AsyncAPI than GSoD 💜 |
|
One hoodie would cost approximately $50, including shipping. Having different designs makes the products more expensive. The more products we buy, the cheaper they will be. What if we have one design for all programs? GsoD, Ambassadors, AsyncAPI Mentors...? |
|
6 mentees from GSoC, 10 AsyncAPI mentorship, approx 6 mentors = at least $1200 and we cannot use our delivery we work on atm as this requires preorder of at least 50 items. As @Barbanio wrote. Maybe we are to ambitious here, and to custom. Maybe we should have one design like "AsyncAPI Intern" for all long running mentorship programs (we can then use it for outreachy too once we get accepted) and one design like "AsyncAPI Community Hero" that we would only give away to mentors or ambassadors. And yes, "community hero" is just a name I quickly invented |
|
Let's just make sure we do not actually use the phrase community hero because that is the literal term that AWS uses for their program. So we should make sure that we use our own unique term for our community members. |
|
@Barbanio @derberg Completely agree, unifying a design across several programs we run through the year is the best bet for budgetary concerns in swag production. I think that it makes sense for one of the designs to be either "asyncAPI Intern" or "asyncapi mentee" across our diff programs like GSoD, GSoC, and our own mentorship program. This way we do not have to create a design specifically for the different programs and this should definitely bring down production costs. |
|
@Barbanio Have you considered Custom Ink? I used this production company for my own organization swag when I had to mass produce for different conferences and events we ran. They ship internationally and most orders have a smaller minimum number of 20ish, which is considerably smaller than other companies that request a minimum of 50 or more products. Ex:
|
|
I agree, we should just use one artwork for mentees of all programs. Would it make sense to just use this graphic then?
My thoughts about it:
Let me know what you guys think! |
I love the idea of using this design that you already created across all of our programs because I do think it represents asyncAPI well and the design is beautiful. I just don't feel 100% convinced about keeping the phrase mentorship program on it because I think that's confusing given the fact that we have a program called that. My vote would be to select one phrase to represent all programs across the board and without causing confusion. |
Gotcha! Or, we could simply replace "Mentorship Program" text with "AsyncAPI Initiative" and then the "Mentee" text can stay there. And we can either choose to leave the year there and get a new printing screen every year, or we can replace that with something else. |
|
@mcturco Oh I have to admit that I do love the idea of having the shirts include the year number if possible, based on production cost constrictions of course. That's another good idea… We could simply say asyncAPI initiative and keep it simple by only adding "mentee." 🤔 curious to see what other people in the community vote on this. |
|
Attaching some artwork to show everyone what that would look like! One Color - Dark One Color - Light Full Color (Stickers) |
@alequetzalli What if the term also encompasses the Ambassador Program? Then we would only have one word for all the programs, and we could reduce costs even more. I can't think of a name, any suggestions? On the other hand, I would also remove the year in the design. I love it, but I think it's more realistic to make it as efficient as possible. For example, if we order 50 hoodies and have three left this year, we wouldn't be able to use them for next year. What do you think?
It seems a good option, but we are currently working to create the new AsyncAPI store with Pinnacle Branding, the company with which the Linux Foundation works. I think it would be ideal to work all swags with the same company, not only for management purposes but also because they will know more about the project's image. While this materializes, for small orders, we are using Printful, which does not have a minimum number of orders. |
This is a very valid point. I've made an option without the year
|
omg I forgot @mcturco already have a great name and a design -> Community Gardener!!! very original, and can by a give away to mentors and ambassadors! just a question: what is a better phrase for mentorship participants, |
Should we only reserve that theme for the Ambassadors so it feels like a "special club"? I understand the problem with keeping costs down, but IMO Mentees and Ambassadors should remain separate because maybe there is a case where the Ambassador is not a Mentee and vice versa.
Valid thought! Maybe we should ask the Mentees of the Mentorship Program and see what they would prefer. "Intern" is a better front-facing term for those trying to add experience to their resume, so maybe we should just use this instead. So it would read "AsyncAPI Initiative Intern" in the design, and then they can share this on linked in 😄 |
|
Yeah I love @mcturco idea of naming ambassadors Community Gardeners! I agree with her that this is a special name that would be better if we can reserve just for the ambassadors. Hmmm yeah @derberg i'm kind of thinking that it might be better if we use the word intern over mentee too 🤔... I think that the word internship will help them in their job searches more. |
hmmm, I wrote
exactly! and |
Okay, I think at that point then we should just make all Mentors -> Ambassadors (Community Gardeners) to keep it simple. We don't want to use the term "Community Gardener" to represent all different groups of people as I feel like that could get confusing. So, they will still be considered Mentors in the Mentorship program, but they will be invited to the Ambassador Program as well. Does that idea make sense? |
|
oh, I know what you mean, but not sure I agree 😄 Ambassadors are like normal ambassadors, out there, in front of users, helping to spread message about AsyncAPI and educate users. They have swag packs and stuff like that. Mentors have totally different impact, so they would get just a hoodie without all the other goodies Ambassadors get |
|
Yes, I think the work between mentors and ambassadors is very different. I understand the Ambassador Program as the high of contributors level, so I think the recognition should be higher. |
@derberg Interesting 🤔 Because before you were suggesting that we should call both Ambassadors and Mentors
Maybe it would help to have this discussion over a live stream? That way we can make a decision together faster than back and forth messages, and then move forward with a design plan.
@Barbanio agreed! This is why I think we should reserve the |
|
So the thing is that Ambassador and Mentorship are different programs. But for me, at least from my perspective, it doesn't conflict with
and just list down rules, that is it, clearly write that Mentors just get a hoodie while Ambassadors get a hoodie and other goodies (he he).
we can definitely come up with proposal quicker during live stream but not make a decision there 😉 |
|
@mcturco Yes, I understand what you are saying, and I think it makes sense. I even like that idea better than the unification of the design for both programs. I defend it to make it more efficient and reduce costs.
This sounds good, and I think the Community Gardeners concept fits well with this idea. |
|
Lemme try summarizing this thread. We discuss hoodies for different parties:
Ad1. I think we have a clear agreement that, we want one design - the one that @mcturco already created, and it will say Ad2. Here we have more opinions. A. either we do Mentors and Ambassadors separate Motivation for A as far as I understand is that Ambassador swag was supposed to be unique. I just want to add that it will be anyway, as ambassadors do not only get a hoodie but a huge pack of different swags worth over $100 Morivation for B is that we have some limits in budget. We want to organize everything with the Swag store we want to start cooperating with. There we need to buy at least 50 hoodies, which means $1885. So calculation is simple, if we go with separate hoodie for Mentors and separate hoodie for Ambassadors then we need to order 100 hoodies, which is almost $4k. And this is a lot as we have more spending related to setup of the swag store + we do mentorship this year forth $15k and also organize a conference in person. So yeah 😅 Do we really need to go with A, I really believe that design from @mcturco for Community Gardener is a perfect umbrella for a swag that is for Ambassadors and Mentors. Alternative: Maybe Alternative solution would be the best in the end? and |
|
Thank you SO much @derberg for your detailed recap 🙌
I am fine with B after giving it some thought... we should just make sure then that we have some budget left over for "normal" swags, like logo tees and such |
|
@alequetzalli thoughts? |
|
I'm gonna go ahead and vote for the financially smoother option of... |
|
awesome, @Barbanio will update the budget and we can prepare in next days for TSC voting on setting up a kick-ass swag store 💪🏼 |
|
Sure! I'm waiting to know the price of printing these hoodies. As soon as I have this information will update the budget 🙂 |
|
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Contribution Ask: GSoD 2022 swag 😬✌🏽
Missy designed some neat mentee swag for the AsyncAPI 2022 Mentorship program. Because GSoD mentees should also receive AsyncAPI swag, I was hoping we could ask for a design contribution for the GSoD mentees' swag.
Timeline ✨
If approved, whenever? 😄😂
Delivery process
To be handled separately from design; it will be a follow-up item with @Barbanio after/if/when design approves taking up this task
The text was updated successfully, but these errors were encountered: