modules/ROOT/pages/welcome/welcome.adoc

@@ -1,49 +1,97 @@
 include::ROOT:partial$attributes.adoc[]
 
+image::https://pagure.io/fedora-join/WelcomeToFedora/raw/main/f/Artwork/Welcome-to-Fedora-banner-Feb2022.png[alt="fedora-banner", width=100%]
+
 = Welcome to Fedora!
-:page-aliases: commops:handbooks:join-sig-member.adoc
 
-Welcome to the Fedora community!
-We are the people that make the Fedora operating system (and all the other cool stuff around it)!
+Fedora is not just an Operating System.  It is the future.  A future for how we work, how we play, how we make and how we communicate.  The technology that Fedora builds first is integrated into some of the world's most important infrastructure.
+
+We are the people that build Fedora.  Some of us came here to make something we just had to, some for a life-long career and some to be with people with similar skills and interests.
+
+People join Fedora with all kinds of skill sets.  Some are advanced engineers with many years experience, others have just left high school.  Wherever you are in your journey, Fedora welcomes you to participate in our community.   We welcome people from all over the planet.  We support diversity of all types as it strengthens the whole.
+
+If you support the link:https://docs.fedoraproject.org/en-US/project/code-of-conduct/[code of conduct] and link:https://docs.fedoraproject.org/en-US/project/[core values] of Freedom, Friends, Features and First there will likely be somewhere for you to fit in. If you want to know what makes a good contributor to Fedora, link:https://docs.fedoraproject.org/en-US/fedora-join/contribute/successful-contributor/[we have a section on that].
+
+Fedora is not strictly speaking a software development centre. One of our core principles is link:https://docs.fedoraproject.org/en-US/project/upstream-first/[Upstream First]. This is so we can give back to the broader Linux community.
+
+== What we do:
+Fedora is divided into a number of working areas.  You can see our link:https://docs.fedoraproject.org/en-US/project/orgchart/[organization chart].
+We do everything from running servers and writing code to design and event management.
+
+If you would like to be part of our community, you do not need to know everything or promise much.  We want you to learn, connect and identify what you would like to become.  We will not give you a job.  We will help you find your way around the Fedora ecosystem to find a group or project that fits your skills.
+
+You do not need to sign up to do this yourself.  Feel free to join in on our link:https://chat.fedoraproject.org/[Matrix Channel] or our link:https://discussion.fedoraproject.org/[discussion forums].
+It is a good idea to read the link:https://docs.fedoraproject.org/en-US/docs/[docs] (plus other places!) and have a good look around before contacting us.
+
+== Getting Started:
+As a newcomer to Fedora, all your access starts with an account. link:https://accounts.fedoraproject.org[Sign up here]. You will be asked for your name and a username.  The name and username you put in may be public, but you can put in whatever you like.  You can change your name later, but you cannot easily change your username.
+
+It really helps us if you introduce yourself on Matrix or on the forums.  We want to know who you are so we can work together better.
+Don't be afraid of saying too much, if you like cooking or anime as well as Python and Inkscape many of us will too!  A good working environment lets you talk about all the things that interest you (as long as it fits the code of conduct).  Just don't publish your home address or passwords!
+
+Feel free to approach people in your areas of interest.  We want to double the number of contributors we have, and we want to make sure Fedora has an active and engaging future.  When approaching people, write as much as you can.  Lay out neatly and succinctly and give as much information as you want to receive.  People here like to read, and the more you tell us the more we can tell you.
+
+You will be 'Fedora' when you have found and made your first contribution to a project or group.
+
+== Onboarding:
+Once you have decided you would like to stick around, or would like a hand getting introduced, we can 'onboard' you.  This means we will give you a little bit more access to systems and can introduce you to teams.  The 'behind the scenes' process is detailed below, it's up to you if you want to know how we do it.
+
+To begin the onboarding, we need to know your username.  All you have to do is
+
+1) Login to link:https://pagure.io/fedora-join/WelcomeToFedora[Pagure] with your Fedora account once, and
+2) Reachout via link:https://matrix.to/#/%23join%3Afedoraproject.org?via=fedora.im&via=matrix.org&via=4d2.org[Join Fedora on Matrix] or on the link:https://lists.fedoraproject.org/archives/list/fedora-join@lists.fedoraproject.org/[mailing list which you can subscribe]
+
+And that is it!  You are one of us now, for as long as you would like.
+
+Remember, there is no minimum commitment.  Take the time to look around.
+
+> *We would of course recommend you to use Fedora :)*
 
 
-We have a process to welcome new community members to make them feel at home and quickly learn enough about the Fedora community to find areas they are interested in getting involved in.
-The idea is summarised in https://communityblog.fedoraproject.org/fedora-join-is-trying-a-new-people-focused-workflow-for-newcomers/[this Community Blog post].
+== Onboarding New Joiners (workflow for the Join SIG team)
 
-Please contact us on any of our <<index.adoc#communication, communication channels>> and we can help you get started.
+When a new person joins the Fedora community, they may not know what they want to do.
+The Join SIG aims to help people to explore the community and find their area of interest.
 
-image::https://pagure.io/fedora-join/WelcomeToFedora/raw/main/f/Artwork/Welcome-to-Fedora-banner-Feb2022.png[]
+We go through the following steps with the new person.
+
+1) We tag tickets.
+- Tags starting with "S:" track the status of the ticket from their perspective.
+- Tags starting with "C:" track the status of the ticket from the community's perspective.
+- Tags starting with "I:" track their interests.
+
+2) We ask $USER to subscribe to the Fedora Join mailing list.
+This is so people can interact via e-mail if they wish, and can stay informed on what happens in the community. The associated tag is: link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+Subscribed[S: Subscribed].
+
+3) We open a new "Hello Fedora World" ticket for the $USER and add them to the `fedora-join` group in Pagure. The associated tag is: link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+Hello+Fedora+world[S: Hello Fedora World].
+
+4) We ask the $USER to introduce themselves, preferably via the mailing list. The associated tag is: link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Introduction+requested[C: Introduction requested].
+When $USER have introduced themself, we mark the ticket with the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+Introduced+myself[S: Introduced myself] tag.
+
+- People can comment on their tickets whenever they need to ask questions, to give feedback, or just to chat.
+
+- When the $USER need a response, they can use the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Needs+response[C: Needs response] tag to gain the community's attention.
+
+- The $USER then spend time exploring Fedora, speaking to people, learning how things work; all at their own pace. $USER is not expected to do any tasks at this time. The idea is to get comfortable with the Fedora community and ecosystem before contributing.
+
+5) Every two weeks we check to see how the $USER is doing. Each time we do so, we set a new tag.
+At the first progress check, we will set the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Progress+check+1[C: Progress check 1] tag.
+If we do not hear from the $USER in approximately two weeks, we do a second progress check and set the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Progress+check+2[C: Progress check 2] tag.
+
+- If we do not hear from the $USER again for another two weeks, we do a final progress check. We set the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Progress+check+3+-+Final[C: Progress check 3 - Final] tag.
+
+- If we do not hear from the $USER in the total of 6 weeks, we assume that the $USER is inactive and close the ticket with the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+User+unresponsive[S: User unresponsive] tag.
+
+6) Some infrastructure in Fedora requires users to be part of a team or group on the Fedora Account System.
+We can give temporary membership to the "Fedora-Join" FAS group if a new user requires.  This can be requested by setting the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Temporary+membership+needed[C: Temporary membership needed] tag. After discussing the situation, if temporary membership to the FAS group is given, we will mark the ticket with the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Temporary+membership+approved[C: Temporary membership approved] tag, and grant the temporary membership.
+
+7) When $USER feel that they no longer need our help or don't have the time, we can close the ticket.
+If $USER decide to exit the Fedora community we will close the ticket with the tag link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+User+closed[S: User closed]. The $USER can re-engage with the community or re-open the ticket anytime.
+
+8) As the $USER learn about the community and ecosystem, they will hopefully find tasks and teams that interest them.  When the $USER have joined a team, they has become a contributing Fedora community member! We mark the ticket as link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+I+am+Fedora[S: I am Fedora] to celebrate this.
+
+9) We collect feedback from new community members at any time and at close of ticket. For this, we use the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+Feedback[S: Feedback].
+
+10) When $USER comments that they don't have time to interact with the community, we can close the ticket. Let them know that they can have it reopened once they have some time to spare.
 
 
-== Workflow Summary
-
-- When a new person, say Jane, joins the Fedora community, she may or may not immediately know what she wants to do. If she doesn't, the Join SIG aims to help to explore the community and find a part that suits her interests.
-- So, when Jane gets in touch with the Join SIG, we go through the following steps together. Jane does not need to know any of this. We, the community, will handle it all :)
-- We use *Tags* to mark the status of each ticket. Tags starting with `S:` track the status of the ticket from Jane's perspective. Tags starting with `C:` track the status of the ticket from the community's perspective. Tags starting with `I:` track Jane's interests.
-- First of all, we ask her to create a link:https://accounts.fedoraproject.org/[Fedora contributor account]. We then add Jane to the Fedora Join group on Pagure. This gives Jane permissions to interact with the Pagure projects that Fedora Join has.
-- Then, we open a new "Hello Fedora World" ticket for Jane on the link:https://pagure.io/fedora-join/WelcomeToFedora[Welcome-to-Fedora Pagure repository]. The associated tag is: link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+Hello+Fedora+world[S: Hello Fedora World].
-- We also add Jane to the link:https://pagure.io/group/fedora-join[Fedora Join group on Pagure] so that Jane and other newcomers all get notifications from their tickets. This will help them all beware of what everyone is doing, and they can all go through the process together.
-- We ask Jane to tell the community a little about herself so that people can get to know her. The associated tag is: link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Introduction+requested[C: Introduction requested].
-- When Jane has introduced herself, we mark the ticket with the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+Introduced+myself[S: Introduced myself] tag.
-- Jane can comment on the ticket whenever she needs to ask questions, to give feedback, or just to chat. When Jane needs a response, she can use the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Needs+response[C: Needs response] tag to gain the community's attention.
-- Jane then spends time exploring Fedora, speaking to people, learning how things work; all at her own pace. Jane is not expected to do any tasks at this time. The idea is for Jane to get comfortable with the Fedora community first and then dive into contributing by doing work.
-- From time to time, we check to see how Jane is doing. Each time we do so, we set a new tag:
-  * At the first progress check, we will set the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Progress+check+1[C: Progress check 1] tag.
-  * If we do not hear from Jane in sometime, such as two weeks, we do a second progress check and set the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Progress+check+2[C: Progress check 2] tag.
-  * If we do not hear from Jane again, say for another two weeks, we do a third and final progress check. We set the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Progress+check+3+-+Final[C: Progress check 3 - Final] tag.
-  ** If we don't get a response in the next 7 days, We would tell her that we've not seen activity and we'll have no choice to close the ticket.
-  ** Closing the ticket is only a formal and operational task, then if Jane likes, they can get in touch with us again using the xref:project::communications.adoc[various communication channels].
-  * If we do not hear from Jane here also (so, in total for about 6 weeks), we assume that Jane is inactive and close the ticket with the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+User+unresponsive[S: User unresponsive] tag.
-- Some infrastructure in Fedora requires Jane to be part of a team or group on the Fedora Account System. We will give her temporary membership to the link:https://admin.fedoraproject.org/accounts/group/view/fedora-join[fedora-join FAS group] if required. This can be requested by setting the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Temporary+membership+needed[C: Temporary membership needed] tag to the ticket. After discussing the situation, if temporary membership to the FAS group is given, we will mark the ticket with the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=C%3A+Temporary+membership+approved[C: Temporary membership approved] tag.
-- As Jane learns about the community, she will hopefully find tasks and teams that interest her. When she has joined a team, she has become a contributing Fedora community member! We mark the ticket as link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+I+am+Fedora[S: I am Fedora] to celebrate this.
-- We collect feedback from new community members. For this, we use the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+Feedback[S: Feedback] tag.
-- Finally, when Jane feels that she no longer needs our help, we can close the ticket.
-- If, due to certain circumstances, Jane decides to move on from contributing to the Fedora community, we will close the ticket with the link:https://pagure.io/fedora-join/WelcomeToFedora/issues?tags=S%3A+User+closed[S: User closed] tag.
-
-
-== How the team manages this workflow
-
-The team has a few Scripts to accomplish this task and verify user's activity:
-
-1. https://github.com/pypingou/fedora-active-user
-2. https://pagure.io/fedora-join/Fedora-Join/blob/master/f/scripts