@theprogram @ankursinha
please review it and let me know if it needs any changes/updates

I'm good with it.
I made a couple of minor edits over the last couple of days (which are here in the merge).
I'll let @ankursinha sign off on it or merge it as I am new.

Thank you @thisisyaash for your help.

sometimes the $USER comments "I don't have time now, for interact with the community", we can close the ticket and tell the $USER you can come back wherever you want or he/she have spare time activated the ticket again

we don't need to add newcommers to the join group to be part of the community ony login on pagure and open a ticket in the welcome repo for that purpose

Tags stating with "S:" track the status of the ticket from $USER perspective.
Tags starting with "C:" track the status of the ticket from the community's perspective.
Tags starting with "I:" track $USER interests.

Thank you @thisisyaash for your help.

@thisisyaash could you make these edits @hhlp suggests?
Under point 1), I was wanting the lines to be layed out, 1 tag to each line, the same way that Hector has it displayed in his comment above.

I should be on Matrix if you PM me for anything.

@hhlp : yeah sure I will change it now
@theprogram : thanks for reminding me :)

So, I will update the changes to:
1. using bullet points for the tags
2. since we're not going to add the newcomers to the group, I'll just continue with (3) asking the newcomers to subscribe the ML.
3. add another line: when the newcomer doesn't have time we'll close the ticket and they can have it activated once they some time to spare!

@hhlp

we don't need to add newcommers to the join group to be part of the community ony login on pagure and open a ticket in the welcome repo for that purpose

It'll be hard for the newcomers to interact with other people/projects right?
or
we're planning to make them complete the on-boarding steps and add them to the group (like checking whether they are interested or not)

@hhlp I have pushed the changes here, so please review it and let me know if there are any other changes needed!

@hhlp

we don't need to add newcommers to the join group to be part of the community ony login on pagure and open a ticket in the welcome repo for that purpose

It'll be hard for the newcomers to interact with other people/projects right?
or
we're planning to make them complete the on-boarding steps and add them to the group (like checking whether they are interested or not)

Yes, I think Hector's point is that we add them to 'Welcome to Fedora' but not to Fedora-Join or Join SIG, unless the show interest in this area and ask for membership.

Yes, I think Hector's point is that we add them to 'Welcome to Fedora' but not to Fedora-Join or Join SIG, unless the show interest in this area and ask for membership.

so my doubt is that "we add them to 'Welcome to Fedora' but not to Fedora-Join or Join SIG" , means we're just opening a ticket right? seems like that's enf to communicate with the $USER and after they show interest we can add them to the Fedora Join group right?

Yes.

On 16/2/25 19:10, Yashwanth Rathakrishnan wrote:

thisisyaash commented on the pull-request: updated README.md by MatH that you are following:
``

Yes, I think Hector's point is that we add them to 'Welcome to Fedora' but not to Fedora-Join or Join SIG, unless the show interest in this area and ask for membership.
so my doubt is that "we add them to 'Welcome to Fedora' but not to Fedora-Join or Join SIG" , means we're just opening a ticket right? seems like that's enf to communicate with the $USER and after they show interest we can add them to the Fedora Join group right?

``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-join/WelcomeToFedora/pull-request/53

@hhlp

we don't need to add newcommers to the join group to be part of the community ony login on pagure and open a ticket in the welcome repo for that purpose

It'll be hard for the newcomers to interact with other people/projects right?
or
we're planning to make them complete the on-boarding steps and add them to the group (like checking whether they are interested or not)

Yes, I think Hector's point is that we add them to 'Welcome to Fedora' but not to Fedora-Join or Join SIG, unless the show interest in this area and ask for membership.

To clarify this:

we:

• create a "welcome to fedora" ticket
• we add them to the fedora-join pagure group: https://pagure.io/group/fedora-join . The idea here is that they then get notifications about other welcome to fedora tickets and so on (and this PR, for example) so that they're aware of what else is going on. If they only have a ticket but aren't added to the pagure group, they're still isolated---all they have is their ticket, and they can't even modify metadata in it.

Does that make sense?

Note that there's a different fedora-join-admin pagure group, and this is for folks who are helping newcomers. Members of this group have admin rights on all fedora join repositories: https://pagure.io/group/fedora-join-admin . We do not add newcomers to this group initially.

The new text is absolutely excellent. Thanks @theprogram and @thisisyaash for working on this!! :clap:

Yes that makes sense.
We will update the readme and will instruct people to add newcomers to fedora-join.

I mistook it for fedora-join-admin as you suggested.
My reasoning for supporting not adding to groups strait away is to keep it easier to find the people to help with join tasks. And I think lots of Fedora groups should be trimmed to keep things current.

Thank you for your kind words.

There is also a Docs copy of the workflow at https://docs.fedoraproject.org/en-US/fedora-join/welcome/welcome/

We should update the workflow, and optionally the above the line part too.

There is also another version of the workflow at https://communityblog.fedoraproject.org/fedora-join-is-trying-a-new-people-focused-workflow-for-newcomers/ which we could either delete or update.

The docs should be kept in sync, yes. Once we merge this one here, we can update the docs too.

The commblog post I guess will stay as is. It's an early explanation of the process, and like every other blog post out there, it's a snapshot in that moment of time and cannot be continouusly updated.

There is also a welcome page on the Wiki https://fedoraproject.org/wiki/Welcome

I just edited the wiki to remove the Telegram link

We could just add a link to https://pagure.io/fedora-join/WelcomeToFedora or we could add the full text there on the wiki.

There is also a welcome page on the Wiki https://fedoraproject.org/wiki/Welcome

I just edited the wiki to remove the Telegram link

We could just add a link to https://pagure.io/fedora-join/WelcomeToFedora or we could add the full text there on the wiki.

Probably better to add a link to us, so there's one less copy to keep up to date? Ideally, the wiki page should now redirect to this page: https://docs.fedoraproject.org/en-US/project/join/

Not sure why it doesn't already, but we could check with folks and set up the redirect.

Definately does not redirect. I tested on a non-logged in device as well as my logged in box.

I support a redirect. The wiki is as I understand it is intended for development purposes.

should I squash the commits?

Should we link to the group URL, just so people know which one it is (and not try to add people to the admin group)?

https://pagure.io/group/fedora-join

Yeh, please feel free to squash the commits etc. A good commit message would be useful for people that see all of this in the future. How about something like this (please add more info to it as you think appropriate---the idea is that someone in the future that looks at the commit should have a good understanding of what was done here):

feat: re-write readme
The readme file has been re-written to make it more relevant for newcomers who will be funnelled to the Welcome to Fedora process. The onboarding process has also been clearly noted to provide a step by step pipeline for SIG members to follow.

My go-to page for reminding myself how to write good commit messages is here:

https://cbea.ms/git-commit/

We use conventional commits in some projects, but not yet in the Fedora Join repos. Worth knowing about:

https://www.conventionalcommits.org/en/v1.0.0/

wow thanks for sharing it :D
I will update the commit msgs now

I'll go with the msg you provided above (easily understandable)