Please review folks:

@mkittermantgd @hhlp @alciregi (and all of the join-sig in general)

I like this! The change I would make is to let people know about the fedora.im homeserver for using FAS in matrix

We could link to this page, which is where info on communicating lives?

https://docs.fedoraproject.org/en-US/project/communications/

That links to chat.fp.o, and then maybe we can add some info there on using FAS to login to it?

We could link to this page, which is where info on communicating lives?

https://docs.fedoraproject.org/en-US/project/communications/

That links to chat.fp.o, and then maybe we can add some info there on using FAS to login to it?

That's a great idea! Two thumbs up here.

From the fedora-join mailing list:

Some of the text there needs to be updated to clarify how the
many-to-many mentoring in the community works. At the moment, it does
seem to indicate one-to-one mentoring, and that's because some teams do
require sponsors, for example the package maintainers team:
https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/#_understand_the_sponsorship_model

Would it be beneficial to add this clarification to the successful contributor guide as well? As someone interested in being a maintainer, I only found out that I need a sponsor because I happened to meet one at a conference. It would be nice if there’s a vector to know that through the guide!

Would it be beneficial to add this clarification to the successful contributor guide as well? As someone interested in being a maintainer, I only found out that I need a sponsor because I happened to meet one at a conference. It would be nice if there’s a vector to know that through the guide!

Hrm, so the "successful contributor" page is generic, and should apply to all of Fedora. I'm only actually aware of 2 teams that have a formal sponsorship model because they require infra access---the package maintainers and the infrastructure team.

At the moment, I only have this line in here:

https://pagure.io/fedora-join/fedora-join-docs/blob/update-successful-contributor/f/modules/ROOT/pages/contribute/successful-contributor.adoc#_203

Some teams may have sponsorship models in place where another community member may be responsible for another's initial contributions.

Your starting point for package maintenance should have been the package maintenance guide here:
https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/

So maybe the visibility of the package maintainers documentation is the issue here? Were you pointed to this page, or just the package maintainers guide by someone (other than the mail that you've linked to?)

Your starting point for package maintenance should have been the package maintenance guide here:
https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/

So maybe the visibility of the package maintainers documentation is the issue here? Were you pointed to this page, or just the package maintainers guide by someone (other than the mail that you've linked to?)

Good point. Yes, it might be a visibility issue. Or, rather, a reachability maybe? Looking back at https://fedoraproject.org -> Contributors -> New Contributors, it is not clear to me how to become a new contributor via becoming a new maintainer.

The issue I personally had, which may or may not be common, was that I didn't know the barrier of entry (or lack thereof) of being a maintainer. Like, I didn't know that was something I might have what it takes to do.

I assumed that "New Contributors" should be my starting point, which is probably true, as I am now more comfortable taking a shot at making rpm's after submitting a few tweaks here and there.

Perhaps the structure is fine as-is and I could just https://www.google.com/search?q=fedora+new+maintainer& ?

I also just discovered that I could arrive at the page linked above via:
https://fedoraproject.org
-> Contributors
-> Contributor Guides
-> Packaging Guidelines
-> Join the Package Maintainers

It was not obvious to me at first that all sections apply to new contributors, not just the "New Contributors" so for example I assumed "Contributor Guides" is something to look into for existing contributors. But I don't have any ideas better than the current structure as-is.

Is there a place in there that lists some of the things like package maintenance or docs?
That could give folks a launch point if they are in that, "I'll do whatever it takes" going on.

Is there a place in there that lists some of the things like package maintenance or docs?
That could give folks a launch point if they are in that, "I'll do whatever it takes" going on.

the organization chart should indicate what teams there are in the community, which should give an idea of what tasks are being done:

https://docs.fedoraproject.org/en-US/project/orgchart/

(This is included in the links the welcome-to-fedora tickets have)

My tab completion would like it if we dropped this file altogether from the file tree. :)

@mattdm FYI, for our ongoing conversation about "how to measure contributions in Fedora." :)

Looks right to me.

It would be nice to mention something here about gaining new skills and building a portfolio in early career or after a career pivot. Personal satisfaction is a thing, but line 108 also captures well the benefits in a professional context too. It would be nice to expand that more.

I could also write some of this text too, but I am wondering what the best format for proposing changes would be? Do you want me to add commits to this branch, address them in a comment, or make a subsequent PR?

I propose removing the script file altogether.

s/various communication channels, provided in this SOP./xref:project::communications.adoc[various communication channels]./

Is this still working, or is it very active? Is there a strong reason to not encourage people to use Matrix instead? I think it would be easier for a newcomer to explore other Fedora rooms and teams through Matrix instead of Telegram. I say this knowing very well that I was likely the person who set up the bridge in the first place. :P

How active is the IRC room after the bridge downtime? Is anyone keeping an eye on things over there?

Maybe omit this, since Matrix is having a hard time connecting over to IRC? Or comment it out in case we ever get it back? I am giving permission to not link out to an article I wrote. :P

Does the Join SIG have any presence on Fedora Discussion?

I suggest one-sentence-per-line here:

[TIP]
====
How much ever time you can put aside for volunteering is fine.
There's no right amount, and the amount should change depending on your circumstances.
====

s/quit/step back/ ?

Quitting sounds serious and permanent, but stepping back feels less intimidating (to me).

These lines look like they were accidentally duplicated?

This one is good. :)

@ankursinha Thank you for tackling this one, this page is important. Going through it, I realized how old some of the content here is. I appreciate your go at modernizing it!

I left feedback in-line. Most of my feedback is small, but I was wondering about the chat platforms part. I was not sure if Telegram is still actively used by the team or if a lot of people come through there still. I am thinking it might be more wise to funnel people into Matrix so they can connect with the entire Fedora community from one place. It is hard to discover other teams and groups from Telegram, and there are also some unscrupulous Telegram groups positing to be "official" Fedora when they are not. So, I would like to discourage that if at all possible, to avoid people getting funneled in somewhere that does not follow the Fedora Code of Conduct.

That is my biggest piece of feedback, but happy to chat more about my suggestions too. I might take a go on this doc with some of my ideas too, after this PR is merged.

Hi @jflory7 , thanks very much for your feedback. I've made all the necessary changes (I think).

I agree---I've completely removed IRC and Telegram from the pages for the moment. Let's funnel people into the matrix channel instead.

Please feel free to push to this branch if that's the easiest thing to do. We can merge it in once we're ready.

I'm going to merge this now, and we can continue to improve it as we go.