The next steps for this ticket would be :

• Send an email to the EPEL team’s mailing list about Onboarding process, how having a defined onboarding process is important for newcomers interested in the team, and how CommOps can assist them in creating one and if they would like it. [You can find an example mail on Python SIG ML for their Onboarding]
• Start a discussion with the EPEL team members about what some example tasks for newcomers could be and if they already have a brief example for this on their wiki page via Mailing lists, IRC and attending their meetings.
• Comment the updates/ progress for team in this CommOps Pagure issue and let others know about the progress in weekly CommOps meetings.

It was decided in CommOps meeting on 2017-09-13, that CommOps would work towards an integrated document to guide different teams on how-to create effective onboarding guidelines and provide them with examples.

More Info here -
https://meetbot.fedoraproject.org/fedora-meeting/2017-09-13/commops.2017-09-13-17.05.log.html

Ticket for how-to document to guide different teams on creating and implementing effective onboarding guidelines is here -
https://pagure.io/fedora-commops/issue/117

Accordingly, I am closing the onboarding tickets for individual teams.