On Sun, Feb 09, 2020 14:13:57 -0000, Alisha Mohanty wrote:
<snip>
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?
Hrm, I was thinking that after the introduction has been received (tagged: S: Introduced myself), we could move on to the "how to contribute to fedora" link.
That way, they:
- first learn about FOSS and Fedora in general - then, we get them slowly started with "how to contribute".
If we give them this link right at the start, they are likely to skip all the others and try to find tasks again.
The apps link is useful for people that show interest in the infra side of things. Otherwise, it'll be "too much information".
I'd leave wcidff as the last one, and the optional one. It again tries to point people *quickly* to teams and tasks without people speaking to us. So, this sort of goes against the idea of letting them get comfortable with the people of Fedora first.
What do you think?
+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?
+1, always good to bump tickets. As we'll all have seen, the Council are working on the Vision statement at the moment, and I expect once that task is complete, the rest of all this will also be done, since it's all related. Feel free to bump the ticket though :)
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.
Awesome :)
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?
This is meant to be it: https://fedoraproject.org/wiki/Join
It includes:
- roles, - requirements, - tasks, - teams linked to roles,
It's basically a one page version of wcidff. I'm not a fan of this either. It throws everything there is to do at people, and that doesn't help newbies---probably confuses them.
Each team has their own bits on the wiki or docs, and this at the moment cannot be helped. The "Hubs" project was supposed to be sort of a centralised app to help with all this, but that got shelved.o
https://pagure.io/fedora-hubs/
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.
At the moment, Easyfix is a static page that is simply regenerated regularly:
https://github.com/fedora-infra/fedora-gather-easyfix
It can certainly be improved to make it more useful. It doesn't give us any information on whether the tasks are being accepted and completed:
- does not mark new tasks, - does not tell us how many new tasks were added, and when, - does not tell us what tasks were taken up by people and completed.
So, we can't easily write a blog post each week that says "New tasks added this week". It'll have to be done manually at the moment.
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,
- Update the ticket-template
- Try to update the easy fix
+1: tasks that can be done quickly and have high impacts.
Should we discuss improvements to easyfix in a new thread?