We have been discussing about a strategy to grow the team for quite some time now. This ticket is an extension of #2.

== KEY TAKEAWAYS ==

• Different strategy for existing Fedora community members and newcomers. Community experience should be an incentive not an entry barrier.
• Being a part of the D&I team is not a requirement to support D&I efforts in Fedora.

== PROPOSAL ==

=== To involve new contributors to Fedora ===

• Encourage participation to other Fedora subprojects
  For example, they can explore and collect Fedora Badges to get to know different areas in Fedora community. We should also encourage them to get involved and communicate with different teams in Fedora to better aid their D&I oriented efforts.

• Seek help for tasks where we need support from other Fedora subprojects
  For example, these contributors can support us with Design, translation, video creation and captioning. #33 could be a good example ticket here.

• Leveraging their local network and FOSS involvement for outreach events like FWD

Similar to the process followed by Design team, we can include them in FAS group after they successfully help us with few tasks related to our ongoing work and are active in atleast one other subproject in Fedora. I don't think we should let the duration of involvement with Fedora community be a barrier here - someone can create a FAS account a year before and do nothing while others can just contribute a lot in first few months.

=== For an existing Fedora community member ===

I think we should let the community member decide their path forward here. Here are a few areas where we could leverage their experience:

• Facilitate cross-team communication across Fedora

• Leveraging their local network and FOSS involvement for outreach events

• Members who are also involved with other open source projects beyond Fedora can help us learn more about successful D&I practises in other projects.

A key note here is that during our communication with the rest of Fedora community we should emphasize that being a part of the D&I team is not a requirement to support D&I efforts in Fedora. This way someone can help with a part of one effort without necessarily increasing their workload by too much.

• Pathways to get more community members involved

I like @bex 's suggestion to have one action item for community members during Fedora podcast. Broadly, we can publish a 'call for help' with clear and concise action items at some intervals.