Create a contributor t-shirt #24
Comments
|
I've played a bit with the idea on Printful, and I came up with the following draft concepts :) Something we could use at the next in-person Open edX conference for example, to allow people to identify contributors and core committers easily? Note that the concepts below haven't gone through the expert hands of an actual designer yet -- so this is just a rough concept, to agree on it, especially on what we want to show and write exactly. Once we are good, I'll ask someone better than me at this to make it look better :p Front: Back: What do you think? As for who could get the t-shirts, to not restrict it too much, this could be something that anyone with at least one merged pull request on the edX org could ask for? To cover the costs, maybe one/several of our organizations could pay for it, and handle ordering them? Since it could be something ongoing, maybe we could establish a rotation for this, with a different organization taking care of it? OpenCraft could handle the first year. CC @felipemontoya @regisb @pdpinch @sambapete @BbrSofiane @ziafazal @OmarIthawi @nedbat @nasthagiri @gabrieldamours @e0d @sarina @idegtiarov @angonz @arbrandes @bradenmacdonald @pomegranited @symbolist |
I think this is a lovely idea! I'd wear my t-shirt with pride. The "design" works for me too. Just want to make sure we're not limited to male T-shirt cuts -- lots of different shapes and sizes in this community, and so "unisex" doesn't suit all :) |
|
@antoviaque if funding is an issue, I think we could set up a free custom print site so everyone will pay their own cost and order it. Not sure how the cost structure would work, but I know a company in Amman, Jordan (mlabbas.com) that would let us do this:
The cost is mostly 20$ for a regular shirt (hoodies, mugs, etc have different price) and 15$ for global shipping: Disclaimer: The owner is a friend of mine and I didn't do any research to compare other options.
|
|
Thanks @antoviaque. This is cool. I don't know if writing "staff" in the back would make it confusing for people at a conference. Maybe they think we are local staff knowing where to find something that we also have no idea.
|
|
@pomegranited Good point - what do you think should be the different types of cuts we need to include? I've selected that one because it looked a bit nicer than the usual "straight T t-shirt with one color", but we could definitely have different versions. @OmarIthawi Thanks for the tip! I'll have a look to compare it there when I do my next pass on this ticket.
That was actually part of the idea actually :) -- to make sure we belong more to the "staff" of the conference, as after all this is the Open edX conference... Even if we don't know where everything is, we would probably be able to figure it out, and it's nice to feel like we are part of one big team imho, rather than edX staff vs the rest of the community. |
I checked out Printful, and they have a women's cut version of the one you chose that I'd happily wear. Not sure about other people, but maybe we just need to make sure that whatever printing supplier we go with has options?
Yes, I liked that too :) And if we can be more involved in the conference itself, so we can answer questions there too. |
I understand now. I also think it would feel nice to be part of the big conference team. |
|
I said this in a contributors' meeting, but repeating here to keep it all in one place: I think "Open edX Conference Staff" would be fine, but "Open edX Staff" would be confusing. And we have to consider the "trademark as adjective" rule. |
|
@nedbat What do you find confusing about "Open edX Staff"? Core committers are more than just staff for the Open edX conference, so that would be limiting to use "Open edX Conference Staff" I think, especially because that's a t-shirt that could be used outside of the conference setting. If people from edX are staff from the conference just because of being from edX, isn't there something similar about core committers, also being staff at the Open edX conference because of that? But also more than just conference staff, the way a catering company staff would be? Not sure if I'm being clear here, let me know if that doesn't make sense. :)
How can we test for that rule? |
|
I get what you're going for with Just my 2c. I like "Open edX Conference Staff" or "Open edX Contributor". I think I'd prefer to wear a shirt that said "Open edX Contributor" year-round than any shirt that mentioned "staff". And to @pomegranited's point, I'm 200% more likely to wear the shirt if it comes in women's sizes 😄 |
|
I'm a bit confused and seeking clarity. Why would we not go forth with T-shirts saying "Open edX Core Committer"? |
|
By the way, I love the idea of gifting a newly minted Core Committer with a T-shirt that says they are one now! |
|
@sarina @nasthagiri To explain a bit, the main idea with "staff" is to have a name that a broad audience of people understand -- vs "core committer" which might be more difficult for someone without a technical background to relate to. The context of the conference was an example -- so that we could wear it there (among other places, like meetups for example), and everyone would understand that we are part of the Open edX "staff", ie the people who manage Open edX and make it exist. The blending is voluntary -- I thought it would be nice to present ourselves as one team, all working together under the Open edX umbrella, without the main differentiation being about who is employing who, who is paid or not, etc. (we still have the affiliation listed in front to clarify that, though). Ie to show that we are one big team who builds Open edX together. It's symbolic, but it can mean a lot in terms of recognition imho. If it's complicated we can drop it and just use "Core committer" or "Contributor", depending on who we give it to. I just wish we could find a way to appear as one team in Open edX events, rather than highlight divides like edX vs the rest of the community - especially in events we organize all together. But maybe I care too much about those things. :) |
|
I could even add my 2 cents. I'm currently a "Contributor" but I am still
no "Core Committer". Looking at the definitions and discussions for "Core
Committer' on Confluence by @sarina, I have to wonder if I will still fit
in as a "Core Committer" at some point.
Le ven. 14 mai 2021, à 21 h 31, Xavier Antoviaque ***@***.***>
a écrit :
… @sarina <https://github.com/sarina> @nasthagiri
<https://github.com/nasthagiri> To explain a bit, the main idea with
"staff" is to have a name that a broad audience of people understand -- vs
"core committer" which might be more difficult for someone without a
technical background to relate to. The context of the conference was an
example -- so that we could wear it there (among other places, like meetups
for example), and everyone would understand that we are part of the Open
edX "staff", ie the people who manage Open edX and make it exist. The
blending is voluntary -- I thought it would be nice to present ourselves as
one team, all working together under the Open edX umbrella, without the
main differentiation being about who is employing who, who is paid or not,
etc. (we still have the affiliation listed in front to clarify that,
though). Ie to show that we are one big team who builds Open edX together.
It's symbolic, but it can mean a lot in terms of recognition imho.
If it's complicated we can drop it and just use "Core committer" or
"Contributor", depending on who we give it to. I just wish we could find a
way to appear as one team in Open edX events, rather than highlight divides
like edX vs the rest of the community - especially the ones we all organize
together. But maybe I care too much about those things. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACD6PLPK7J46OYTLE2BVDS3TNXFHXANCNFSM4ZQYOR5A>
.
--
Salutations / Regards ,
Pierre Mailhot, M.Sc., CISSP
514-916-9558
|
|
@sambapete I shared with you a draft of a blogpost that we'll soon publish. There, you will see that we plan to expand the Core Committer program to include multiple roles, those who have demonstrated the following:
To create a successful platform and product suite, it takes many different people with different expertise and different perspectives and different contributions. Our community-wide Open edX Team includes not only code-committers, but testers, documenters, project managers, designers, researchers, etc, etc. @sarina, @nedbat, I, and others have been working this past week to get early support and input from various functions at edX on crafting the expansion. We'll provide an update at our regular Tuesday's contributors meeting. |
|
@antoviaque Thanks for the additional context. Yes, it seems there is continued concern of "core committer" not being an approachable term to non-technologists. And, I am 100% with you on building a collaborative team together! Just as there is concern about the word "committer" not being widely understood, there is also concern about the connotation of the word "staff". "Staff" implies workers who serve the needs of others. Whereas, for us, we want our community to be "empowered" to "drive" to "create" and to "make" Open edX the best it can be. Here is another alternative, which I think may satisfy our various needs:
What do you think? Otherwise, here are a few other variations:
|
|
Thanks @nimisha, I will definitely have a look at it. Unfortunately, I
won't be able to attend this week's contributors meeting because of a
scheduling conflict with an internal meeting within EDUlib. But don't
worry, I'll watch the recording as soon as it is made available.
Le sam. 15 mai 2021, à 11 h 29, Nimisha Asthagiri ***@***.***>
a écrit :
… @sambapete <https://github.com/sambapete> I shared with you a draft of a
blogpost
<https://docs.google.com/document/d/1FKShKH_SnT3QJxBDNb9Stfem9giqgR0JzrECvD4fJL4/edit?ts=60916dd1#>
that we'll soon publish. There, you will see that we plan to expand the
Core Committer program to include multiple roles, those who have
demonstrated the following:
- *commitment* - continued dedication to the platform
- *conduct* - good judgment in their behavior and decisions
- *caliber* - high standards and quality in their work.
To create a successful platform and product suite, it takes many different
people with different expertise and different perspectives and different
contributions. Our community-wide *Open edX Team* includes not only
code-committers, but testers, documenters, project managers, designers,
researchers, etc, etc.
@sarina <https://github.com/sarina>, @nedbat <https://github.com/nedbat>,
I, and others have been working this past week to get early support and
input from various functions at edX on crafting the expansion. We'll
provide an update at our regular Tuesday's contributors meeting.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACD6PLILNOQUVGM5FMYKEHDTN2HOFANCNFSM4ZQYOR5A>
.
--
Salutations / Regards ,
Pierre Mailhot, M.Sc., CISSP
514-916-9558
|
|
I don't have a strong opinion on this topic but just wanted to suggest "crew" as an alternative, candidate term. |
|
@nasthagiri I see what you mean about the word "Staff", it's true that it conveys a part that doesn't fit (workers who serve the needs of others). "Team" could work yes -- I also actually really like your suggestion for "crew" @regisb, which is more specific than "team", without the meaning we want to avoid. Would that one work? |
|
"Crew" works for me. It may seem more informal than "Team"; I don't have a strong opinion about it. |
|
Quick note that during the meeting on Tuesday, we discussed going with "Crew", unless further objections were raised here within the next couple of days. If not, we'll move forward to the next step, which will be to get the current concept/content being properly designed, to make it look nice :) |
|
I like "Crew" a lot! Great solution. |
|
@ali-hugo I was able to create templates on Printful using your file. I'll just need the back design, since I need to edit the front design for each individual user. It's just text, so that will be easy. Had you noted what font was used, so I can create/edit the front design myself on Printful? I'll also take care of changing "Core Committers" to "Core Contributors" to adopt the new terminology. |
|
@gabrieldamours thanks for noting the changed terminology! Is this shirt going to just be for Core Contributors, or for anyone who's worked on the software? If everyone (which I fully endorse!), we shouldn't use the "Core" at all - possibly just "Open edX Contributor" or something like that. |
|
@sarina The intent is to have it for core contributors. Though we could also consider non-core contributors, but then have a different title (and maybe t-shirt color?) to reflect the difference. |
|
@antoviaque thanks for the clarification. I wasn't sure as we discussed it in the Contributor's Meetup which isn't restricted to core contributors. |
|
@gabrieldamours
Be Vietnam is a Google Font. You can download it here. |
|
Thanks @ali-hugo. Would you also be able to send the template in .ai or psd, so that I can use it as a template? The Be Vietnam font isn't available in Printful, so I'll need to edit the front designs using another software. |
|
Sure @gabrieldamours. You can access the Illustrator file here. Please let me know if you need anything else. P.s. When you receive the test print, please check to see if it would look better if I removed the black outlines from the illustration (so that the black of the shirt shows through, rather than relying on the black details being printed). It's always difficult to decide which route would be the best to take. Thanks for handling this 🌻 |
|
Sample on the way :) |
|
I received my sample, and it looks good. The print is of good quality (not ultra top-notch, but good enough).
I'll start collecting people's info and then place orders. |
|
(post edited) |
|
@gabrieldamours Thank you! :D Looks like you've got a special collector edition of the t-shirt :) For collecting the addresses, since this is specifically for the core contributors, it would be better to reach out directly to the confirmed core committers. @sarina is there an authoritative list somewhere? |
|
@gabrieldamours Ah, that looks cool! Do you think it would look better if I removed the black outlines? Then only the white sections would be printed, and the black of the shirt would replace the black ink. Let me know what you think. Otherwise, I think it looks good as is. 👌 Thanks for organising! |
|
@antoviaque ok, I'll write to core contributors directly. @ali-hugo yes, let's do that. Can you send me the back design without the outlines? Vector/PDF (same format as these) works fine. Thanks! |
|
@symbolist @ziafazal @bradenmacdonald @OmarIthawi @pdpinch @regisb @idegtiarov @arbrandes @cmltaWt0 @BbrSofiane @giovannicimolin @Agrendalath @xitij2000 @jfavellar90 @ghassanmas As Core Contributors, can you please fill out the following form so that I can have your contributor t-shirt printed and sent? Thanks! |
|
@gabrieldamours |
That's a lot of PII to put in a publicly-accessible document. I think we should rethink how we're collecting this information. |
|
Point taken @xitij2000 — let's use the following Google Form instead. |
|
T-shirts were sent to every one who submitted their info. Please allow a few weeks for shipping (some countries take longer than others). I'm thinking of closing this task, but where should we indicate that core contributors can receive a free t-shirt? I'm happy to process orders on a regular basis — I get a ping every time someone fills out the form. |
|
@gabrieldamours I think this ticket can be marked as done. When I add new core contributors, I can direct them to your survey. Question: are we imagining this is only for core contributors who commit code, or for all core contributors in the program (right now we additionally have translators, project managers, and as of today, one UX/UI designer) |
|
I think we need a group picture where all core contributors pose with their t-shirts :) (we should sync our laundry days) |
|
Perfect, thank you @sarina :) My assumption is that everybody who signs a Core Contributor Agreement gets a t-shirt. Accordingly, I've sent t-shirts to Non-Technical Contributors as well. edit. Where is the "close issue" button? |
|
@gabrieldamours I've hit the "Close issue" button. I can re-open if that's a mistake. Thanks for running this errand 😃
|
At https://trello.com/c/JBi4cUB5/56-contributors-meetup-june-4th-agenda it was suggested creating a contributor t-shirt. It could be customized for each contributor, and include things like:
(Original issue on Trello)
The text was updated successfully, but these errors were encountered: