On Tue, Jan 28, 2020 16:12:34 -0000, Alisha Mohanty wrote:
I agree with most of this. I only have one point to note. Traditionally, when newcomers came, they already went straight to the onboarding process. (CommOps spent a lot of resources on helping each team improve their onboarding documentation). This wasn't working too well. People came in, jumped straight to tasks. The expectation was that through these tasks, they'd get integrated in the community.
The problems were:
- first, most newcomers, who you correctly identify as shy, are also too timid to take up tickets;
- next, if they do, they're still too shy to ask queries.
- third, if they don't make friends in the community, after their few tasks, they leave.
So, we flipped this around. We don't want people to take up tasks and then meet people. We want them to first become Fedora community members, meet the people, and *then* take up tasks.
Hopefully, our new process reflects this idea :)
The new ticket template now includes information to help newcomers learn about FOSS and the community. It can be seen here. Please feel free to suggest improvements to this.
Thanks for the clear outlay of the objectives. So, for now, I can clearly see we are heading towards the right direction (with tracking their journey through Tickets). I was thinking if we can add the below links to the template which will also help newcomers. whaticandoforfedora(https://whatcanidoforfedora.org/) Fedora Apps(https://apps.fedoraproject.org/) (optional) How to contribute to Fedora? ( https://fedoramagazine.org/how-to-contribute-to-fedora/)
In addition to the community links to help to get to know Fedora Community, these links will make them stick to the purpose of onboarding. Let me know what you think regarding adding these links?
+1. This is still a WIP. Ideally, the landing page should be this: https://docs.fedoraproject.org/en-US/project/join/
As you see in #161, there is a PR waiting on the council-docs for this. The PR also suggests that wiki/Join be moved to wiki/Roles, which is really what it is.
I took a look into the discussion for the Fedora Mission https://pagure.io/Fedora-Council/council-docs/pull-request/63# . I think we should take a progress check on the ticket. What do you think?
Some of the ideas @hhlp has suggested in the post would help I guess: https://discussion.fedoraproject.org/t/what-to-do-with-wcidff-warning/13302
This works, but we only point people to this page when they sort of know a few people in the community and are comfortable enough to jump in to tickets/tasks.
As you note also, this won't be around for much longer. So we should wait to see what happens here before making any plans around it.
This sounds like a great idea but it is a very big one. We (the Join SIG) do not have the man power to run something of this magnitude, though. It'll need more of the community to help---how do we ensure that?
I am totally getting it. I this should be a later goal and not our priority for now.
I'm not sure I understand this one. Could you please elaborate?
I meant, the areas which are introduced in https://whatcanidoforfedora.org/en like design, community ops, coding should be described properly. For example, what the group does, who can be a part of it, what is the aim of the group, etc. Currently, we don't have any page which clearly tells about the different areas. Am I making sense? Are you able to get what I am trying to convey?
Also, for the easy fix, what do you think will be the requirements to make update once in a while ? I am up for finding some time regularly to check on the status of tickets issued in the easyfix with your and other Fedora Join SIG member’s help. I was thinking if the easyfix requires the community people to jump into and add some tickets, how about posting it in Fedora Program Update weekly posted in Fedora Community Blog to draw attention of people in the community. I am not sure if it's the right place to do it, but this can be a good way to keep it updated and under attention. Let me know what are your views regarding it.
Maybe. It's a simpler version of wiki/Join, so maybe we can just add wiki/Join to the new-issue template? (I've personally always felt that wiki/Join was far too detailed and not appropriate for newcomers.)
Someone is already working on it from what I remember.
Thanks---that is very useful. So, all our ideas/initiatives must keep in mind that fact that we're very limited on man-power. So, taking that into account, if we are to think about implementing these ideas, how would you prioritize them to make the most impact?
For what I am seeing, there are a couple of things that are dependent on others, which might take a while to get started. Shortlisting these, from all of the ideas which we can do for now, 1. Update the ticket-template 2. Try to update the easy fix
Thanks Alisha