I have a draft, and I also revised the 'below the line' text for readability. (darn arts grads just can't help 'emselves)
Where do I submit a draft for comment (on Monday-ish)?

Wherever works for you really. You could open a pull request on the repo (that's the git way of doing things) or chuck it on hackmd or something where multiple people can see/review it

Welcome to Fedora:
Fedora is not just an Operating System. It is a 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 worlds 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 code of conduct https://docs.fedoraproject.org/en-US/project/code-of-conduct/ and core values https://docs.fedoraproject.org/en-US/project/ 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, have a look at https://docs.fedoraproject.org/en-US/fedora-join/contribute/successful-contributor/

What we do:
Fedora is divided into a number of working areas. You can see our org chart at https://docs.fedoraproject.org/en-US/project/orgchart/
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 Matrix at chat.fedoraproject.org or our forums at https://discussion.fedoraproject.org/
It is a good idea to read the docs at https://docs.fedoraproject.org/en-US/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.
Sign up at https://accounts.fedoraproject.org. 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 recieve. 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 https://pagure.io/fedora-join/WelcomeToFedora with your Fedora account once,
and 2) reachout via Join Fedora on Matrix https://matrix.to/#/%23join%3Afedoraproject.org?via=fedora.im&via=matrix.org&via=4d2.org or on the mailing list which you can subscribe to https://lists.fedoraproject.org/archives/list/fedora-join@lists.fedoraproject.org/

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 use Fedora :)

---

How we onboard new Joiners (workflow for the Join SIG team)

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.

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 add them to the Fedora Join group on Pagure.
This gives them permissions to interact with the Pagure projects that Fedora Join has.

3) We ask them 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: S: Subscribed.

4) We open a new "Hello Fedora World" ticket for them. The associated tag is: "S: Hello Fedora World".
We also add them to the Fedora Join group on Pagure so that they and other newcomers all get notifications from their tickets. This will help them all be aware of what everyone is doing, and they can all go through the process together.

5) We ask the newcomer to introduce themselves, preferably via the mailing list. The associated tag is: "C: Introduction requested".
When they have introduced themself, we mark the ticket with the "S: Introduced myself" tag.

People can comment on their tickets whenever they need to ask questions, to give feedback, or just to chat.
When they need a response, they can use the "C: Needs response" tag to gain the community's attention.

They then spend time exploring Fedora, speaking to people, learning how things work; all at their own pace. They are not expected to do any tasks at this time. The idea is to get comfortable with the Fedora community and ecosystem before contributing.

6) Every two weeks we check to see how they are doing. Each time we do so, we set a new tag.
At the first progress check, we will set the "C: Progress check 1" tag.
If we do not hear from them in approximately two weeks, we do a second progress check and set the "C: Progress check 2" tag.

If we do not hear from them again for another two weeks, we do a final progress check. We set the "C: Progress check 3 - Final" tag.

If we do not hear from them in the total of 6 weeks, we assume that they are inactive and close the ticket with the "S: User unresponsive" tag.

7) 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 "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 "C: Temporary membership approved" tag, and grant the temporary membership.

8) When they feel that they no longer need our help, we can close the ticket.
If they decide to exit the Fedora community we will close the ticket with the tag "S: User closed"

9) As they learn about the community and ecosystem, they will hopefully find tasks and teams that interest them. When they have joined a team, they has become a contributing Fedora community member! We mark the ticket as "S: I am Fedora" to celebrate this.

10) We collect feedback from new community members at any time and at close of ticket. For this, we use the "S: Feedback".

I have as you see added the new text to the ticket. No need to go to another site :)
This is my first time looking at the Git workflow, so I tried to do a pull request but it said 'no-diff'.
I do not necessarily need to learn this right now.
Maybe @thisisyaash could explain to me or do it for me when ready?

I have tried to tell a story about motivation. I have provided minimal information and links to show the sign up workflow for the new Joiner.

I updated the ticketting text from "Jane" to "They" as I (and my wife, who is a woman) felt it was more appropriate for the zeigeist. We felt the "Jane" was a bit forced. I also think it reads better now without a hypothetical subject.

I am open to changes, modifications and suggestions. I was thinking of embedding the links in hypertext to 'hide' them. But I also like to see where I am linking to with-out 'mousing over'.

Edit: I think we need to talk about how much help we are giving newcomers. People are signing up expecting some help, but we pretty much refer them to a set of documents and tell them to explore by themselves. They of course have the option of asking questions, which the self-starters do. There are others that need more guidance but WILL become active with guidance.

I have the idea not of a 'cohort onboarding' but a monthly / bimonthly 'tour' of Fedora... Where we virtually take a non-signed-up cohort to various channels and introduce to existing contributors...

This is my first time looking at the Git workflow, so I tried to do a pull request but it said 'no-diff'.
I do not necessarily need to learn this right now.
Maybe @thisisyaash could explain to me or do it for me when ready?

hey, sorry I was handling some college related stuffs and kind of occupied with that for couple of days.

So, the process for making a PR to WelcomeToFedora is:

I don't know how you got the "no-diff" log, but I'll explain how I would do it

• Let's fork and clone the forked repo
• Switch to a new branch

git switch -c <your-branch-name>

• Update the README.md with you changes
• Stage & Commit the changes

git commit -am "commit message" 

use -S for signing the commimt

• Let's push the branch

git push <your-branch-name

• Now your changes will be reflected in the forked repo
• On top right side of the forked repo, you see a btn "Open PR" and click upon it
• Select the branch you are working and then create the Pull request. or create a "New Pull Request" if you don't see your branch and then select them manually

That should do it without any problems :)

ping me if you face any errors

Or, I could do it for you?
if you are busy with other stuffs :eyes:

*I see you are doing lot of works

The docs team has these pages for both GitLab and Pagure based tweaks. It's more for docs, where each page has a "edit button", but similar principles apply:

https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/tools-file-edit-pagure/

https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/tools-web-ide-ui/

We have done classrooms on Git/Bash and so on before. We could do them again if folks think that'll help:

https://fedoramagazine.org/fedora-classroom-session-git-101/
https://fedoramagazine.org/fedora-classroom-session-git-101-with-pagure/

(no recordings for these, they were done in the IRC days XD)