Learn more about these different git repos.
Other Git URLs
Hello team,
For the next release party (April 30th & May 1st), We want to create a presentation (and a talk) about how to join as a contributor to the Fedora community.
I'm opening this ticket to coordinate the work with the join SIG to give an amazing talk
We need:
The related ticket on commops is https://pagure.io/fedora-commops/issue/226.
@bt0dotninja,
I can help deliver the presentation. (Expressed interest in the commops ticket comment https://pagure.io/fedora-commops/issue/226#comment-724848 as well)
Do let me know if you need any assistance with the deck and/or the outline as well and I will be glad to coordinate.
Thanks, @t0xic0der. Sure, I will need a lot of assistance here :smile:
I update an agenda proposal here: https://hackmd.io/@ZBDPuu-UTnWdVWbWwAl6qg/SJigddLBd
Please, everyone, take a look. Any comments are welcome.
Here's a draft deck.
@ankursinha @bt0dotninja @hhlp @alciregi @nasirhm @ramyaparimi @jflory7 @siddharthvipul1 and everyone else, please take a look.
<img alt="How_to_Join_Fedora.pdf" src="/fedora-join/Fedora-Join/issue/raw/files/c014b957638af40253967f3003fd6b81ac2657d88238f444a2b0f10a6c2d565f-How_to_Join_Fedora.pdf" />
Metadata Update from @t0xic0der: - Issue assigned to t0xic0der
I have submitted the deck for review by the design team here https://pagure.io/design/issue/753.
Hi @bt0dotninja and @ramyaparimi,
While I make changes suggested by @riecatnor to the slide deck, could you please look into writing speaker notes for our presentation?
(I know, the event is on 30 April but the sooner we start, we can afford to do things slowly as well as be able to run the speaker notes through multiple rounds of review to ensure polish)
Here's a revised draft.
<img alt="How_to_Join_Fedora_REV_1.pdf" src="/fedora-join/Fedora-Join/issue/raw/files/b349a1bf603a6d516a95e0857403895d413b85c62d2ebc8a33521b392ffcda00-How_to_Join_Fedora_REV_1.pdf" />
If there are content related changes that you wish to propose or if there is a discrepancy/typo etc., do let know. :)
I like the draft's content +1
for the design side, We need to follow the design ticket
You do a great job with this deck.
Hey, I would love to help in drafting and giving the presentation as well.
I have a bit of an experience in oration. Do let me know if any help is needed!
Heya, sorry---busy week at work (in fact there's a conference on now too!)
The slides look very good! Some notes/suggestions (they don't have to be accepted :D)
"keep yourself busy" -> remove? similar to the time commitment point?
the CoC bits seem a bit scary to me, as in they're like "be in Fedora, but remember!" type warnings? Can we make them more cheerful/positive so it makes people look forward to joining? Like "Be welcoming/open", "We're all friends", you know?
I've just realised I was looking at the first version, not the new one so some of these may already have been taken care of :)
do we want to use "mentor-mentee" in the slides? Most people tend to think of one-on-one mentoring when they read that and we aren't into one-on-one mentoring?
I must be in the minority in this regard and it must have something to do with the poor teacher-student count ratio in India, I think :P. But let us clarify it when we are delivering the presentation that it is one-on-many mentor-mentee focus. @adhiksha could you add this as one of the keypoints for slide no. 4 please?
i understand the idea behind "look for potential, not polish", but I wonder if that's still something that may make a newbie wonder if they do have the potential in the first place. The only thing we look for is the willingness to volunteer some time---we don't actually ever look to see if someone has "potential" and we certainly don't "reject" people if they don't have it etc. So I'm wondering if we need to move away from the "potential, not polish" speak we've traditionally used
I believe that potential is something which is quite dynamic and is likely to change on the basis of how much time they spend with the community, how committed they are committed to what they do inside the community and if they have found something that is interesting to work on - none of these factors can be looked into for a newcomer when they are just entering. I hope this makes sense?
Unless you're using a personal example, like we use "Jane" in the docs and so refer to Jane as "she", I'd use the gender neutral "they" to include everyone. (Perhaps we should update our docs to use "they" instead of "she" too as a separate task)
A total +1 to this suggestion. I would skim through the decks to confirm that the pronouns are generalized.
do you think the slides are a bit text heavy? For example: maybe an image of an example "Welcome ticket" would give a better idea of it? With too much text you risk people not listening to you because they're busy reading the text. In general, all the sentences you've put in their should be your notes to remind you of what to say, but they shouldn't be in the slides for the audience to read.
They kind of are. But the subtitles are kept in a lighter fontface to have them out of focus. I really wish I had some images in my disposal to put there.
the design team would perhaps point this out: perhaps use more colour? For example "Introduction" "Exploration" "Interaction" "I am fedora" could be in 4 different colours to catch the eye---similar to how you've done the "non-technical sub-projects"? same for the technical projects?
Good point. What do you think @riecatnor?
related to the text-heavy point: can we use the new orgmap riecatnor has done up to show the various teams instead of text descriptions (zoom in to the necessary areas for each slide?)
We definitely can but I could use some assistance in making it happen, now that we do not have much time left.
"Time commitment" -> "Reserve time for volunteering" (as in, make these into actions/verbs so they are suggestions to people)
Noted. I will make these changes.
"Get permission from work/family" -> I'd remove this entirely. The text description doesn't go with the point title either for me
Umm. Let me take a quick look into that slide and figure out the changes. If it does not make sense even after multiple re-reads, I would remove it.
"Joining" -> is this necessary too? The text here also looks like it should go under the next "Observe" point? I'd remove the "Joining" point perhaps, and just use the "observe" point.
Noted. Will remove/replace it.
"Pick what you want to work on" -> "Find tasks that interest you" or something of that sort, since that's what the text description seems to say?
Noted. Will rephrase it.
"Dont jump into the deep end" -> "Start simple"?
"Find a mentor/sponsor" -> "Build relationships in the community"? again just to reduce the one-to-one mentoring implication
Will make sure to the cover it with the speaker notes to confirm we are not implying that. CC @adhiksha
It is somehow different as it deals with picking up another task once the one that they initially picked up gets over. Could use more opinions to ensure we are not beating around the bush with multiple similar meaning points.
I think that's the limitation of the slide which we can address when we are delivering the actual presentation. Should we add more to that slide to ensure that it sounds friendly as well as something to keep in mind at the same time - the slide can potentially become more wordy.
Welp, I had a movie lined up so it would be a while before the updates show up.
and yes, thanks for the review @ankursinha. :D
Hi @adhiksha, how far have you come with the speakernotes? :)
Do share us the link of the hackmd file as a comment here.
Hey @siddharthvipul1 @t0xic0der , I have worked a bit on the speaker notes and have contributed as per my understanding. Request everyone to please check it out once, and suggest any changes that could be made . If there are any typos/discrepancies. https://hackmd.io/@WxOPMoFUSzmdUsg5WIw--w/By3If4xPO Thanks :)
Awesome, thanks @adhiksha
@thunderbirdtr has been working on the recordings and they would be out pretty soon (i think) and I believe that this session was a grand success! Closing this ticket as complete.
Metadata Update from @t0xic0der: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.