If someone i.e me, would like to join the Fedora Diversity & Inclusion team as a Member, there's not much or a process document is available, like other SiG's where the process and prerequisites are well defined.
Looking forward to be a part of Diversity & Inclusion team to make Fedora more Diverse & Inclusive, as the Best Communities are Diverse & Inclusive
Metadata Update from @jflory7: - Issue priority set to: needs review (was: awaiting triage)
Metadata Update from @jflory7: - Issue tagged with: new change, type - docs, type - internal organization, type - onboarding
Is this Doc for getting involved : https://docs.fedoraproject.org/en-US/diversity-inclusion/get-involved/ There's not a managed way available, Let's think about ideas which would improve it.
I think the challenge is we need to better define "good first issues" for this team. There was a similar discussion started by @bcotton on the mailing list:
https://lists.fedoraproject.org/archives/list/diversity@lists.fedoraproject.org/thread/67XWSRJ6IDOVPCMZMGF3Q7IXRQH2O2RO/
"good first issues" sounds like a great idea for encouraging newcomers to be a part of the D&I Team. As you mentioned on the mailing list the most structured thing we have here is the FWD Event. I think we need to think about some newer ideas under the D&I team.
And having a well structured process for joining the D&I Initiative is an essential part too.
From my perspective, when existing fedora contributors would like to join the team as a member, having a process for that would make it best for both the diversity team and the individual. For example we either have elections for it or we can also introduce a process like we have in Join SiG where people meeting a specific criteria can open a membership request and other members can either +1 or -1 it accordingly.
For new comers, I quickly gone through the closed issues here and found some interesting issues which newcomers could take as a good first issue, Here's an example: https://pagure.io/fedora-diversity/issue/102
good first issue
Here in the objectives team defined for 2019-2020 : Most of them are achieved, We have a good decision making process too but we don't have a good newcomers onboarding type of process, Introducing it can make it more inclusive.
Have a Good Day guys :D
It would be great to also have some kind of "job description" to communicate what members would be doing.
+1 to it, that would make it easier for the person joining to know what his job would be :)
I'd like to add to @narasim and @till's point here.
I think the challenge is we need to better define "good first issues" for this team.
There seems to be no clear demarcation of responsibilities as of now to an outsider (like me).
Thanks for your insight. I understand how this might seem more clear to existing members than others.
I'd like to add to @narasim and @till's point here. How does one become an official "member" of Fedora's D&I team? What is the criteria for being a member? Anyone who organizes any events are automatic members? Are members same as volunteers?
How does one become an official "member" of Fedora's D&I team? What is the criteria for being a member? Anyone who organizes any events are automatic members? Are members same as volunteers?
Most D&I Team members are volunteers just like rest of the Fedora community. But a volunteer can be a member of multiple teams eg. I am a part of D&I, CommOps.
What's the goal of the D&I team? 3.1 Is it to increase diverse Fedora contributors (by organizing specific events) OR 3.2 Create event ideas and manage people who volunteer to organize these events? What are the responsibilities (job description as till mentioned) of the D&I team?
The goals are mentioned here: https://docs.fedoraproject.org/en-US/diversity-inclusion/ and we work on projects which can help us drive our goals. Apart from communicating our progress to the Fedora leadership and the community, I don't think there are any specific responsibilities for the team as a whole apart from these at the moment.
Are there elections/interviews if someone wants to be a part of it?
I think the process is documented here: https://docs.fedoraproject.org/en-US/diversity-inclusion/get-involved/ but it might seem confusing. There is no election or interview.
I think the challenge is we need to better define "good first issues" for this team. Do you mean "good-first-issues" for: 6.1 the members of the D&I team to work on OR 6.2 people who want to join the D&I team OR 6.3 people who want to volunteer for events created by D&I team but not be a part of the D&I team (like organizing FWD) OR 6.4 people who are under represented and want to contribute to Fedora?
Do you mean "good-first-issues" for: 6.1 the members of the D&I team to work on OR 6.2 people who want to join the D&I team OR 6.3 people who want to volunteer for events created by D&I team but not be a part of the D&I team (like organizing FWD) OR 6.4 people who are under represented and want to contribute to Fedora?
I think by first issues we mainly mean 6.2 people who want to join the D&I team. They can ofcourse be from an underrepresented group (as mentioned in 6.4) or not.
Apart from the challenge about 'new first issues', I think to be more clear on the membership process we also need to do edit our team docs to be more clear. I like @till's suggestion on role description for interested newcomers. We can add something like the text below in the beginning on the Get Involved page of our docs.
Diversity and Inclusion Team always welcomes new contributors. Whether you are a newcomer or an old-timer, whether you can contribute frequently or sporadically, there are ways to get involved. As a Diversity and Inclusion team member, you can
These are just my initial ideas. Feel free to edit the text or add more examples of what a Diversity and Inclusion Team member does.
For good first issues, here are my few ideas:
Documentation editing issues (I think we will have some hence soon since some text needs updates or links are broken etc.)
I also like @nasirhm's idea of Commblog post as a first issue maybe it can be a team update (plus the newcomer talking about their experience in the team) or the newcomer can interview someone from an underrepresented group in Fedora community and highlight their contributions. This is similar idea to @x3mboy 's How do you do Fedora posts but focused on contributors from underrepresented groups.
They can add new or improve existing resources to our resource pack for event organizers eg. something like Opensource 101 seems missing from resource pack right now.
Members who are also involved with other open-source projects beyond Fedora can help us learn more about successful D&I practices in other projects.
Maybe after a few weeks, they can try to
Chair a D&I meeting! I know this sounds difficult but really isnt with the meetbot script here: https://docs.fedoraproject.org/en-US/diversity-inclusion/meetings/
Give feedback on one of our existing initiatives
What does everyone think?
+1 to the proposed good first issues. I'll be happy to consolidate these into the docs once all the good first issues get discussed.
Thanks for PR #141 @orionstar25! :fountain:
There was discussion on good first issues on #122 as well and overall the first 3 ideas (which were the ones we discussed) received good feedback. I think next steps for this would be
Talk to @siddharthvipul1 and ask if he is looking at resuming 'How do you do Fedora' column by @cprofitt. Once we know this, we can either collaborate with him on the task or start creating new template questions to provide to newcomers interested in the commblog post task.
Reaarange the text of the ideas to be more action focused and include details on how to do it. Eg. "Documentation editing issues" to "Our docs are getting old! Help us provide accurate and up-to-date information by updating our team's documentation. Found some inaccurate information? Submit a PR to our docs repo. If not, here are some beginner friendly issues to get started: https://pagure.io/fedora-diversity/issues?status=Open&tags=good+first+issue. "
Yes, we are doing it. There are 2 great volunteers helping me (turns out I was too slow with all the other infra work going on and their help just accelerated the process). There is one interview in final process and 2 in the Q&A stage. I am happy to work closely with you all and help in any way I can. So far I had the idea to cover all different fields (like dev, design, infra, commops etc) and this idea fits right in with my "hopeful plan"
:100: thanks @siddharthvipul1 for the quick reply - that's great to hear! Then we can point newcomers interested in Commblog task to support you :)
💯 thanks @siddharthvipul1 for the quick reply - that's great to hear! Then we can point newcomers interested in Commblog task to support you :)
@bee2502 It's on Fedora Magazine
Quick update on this ticket after going through all existing comments:
I think this is taken care of for now, we have plenty of good-first-issues for volunteers to work on.
good-first-issues
We can add something like the text below in the beginning on the Get Involved page of our docs.
This has been incorporated.
Add new or improve existing resources to our resource pack for event organizers eg. something like Opensource 101 seems missing from resource pack right now.
This will be taken care of after #168 gets structured and I pull out relevant information from #122. Will follow this up on the new ticket.
@nasirhm's idea of Commblog post as a first issue. Can be a team update (plus the newcomer talking about their experience in the team) or the newcomer can interview someone from an underrepresented group in Fedora community and highlight their contributions.
@nasirhm can you please create a ticket for this? This will potentially be added to the Get Involved Page with relevant details.
Get Involved
Chair a D&I meeting!
This is already present in the Get Involved page.
I feel that our Get Involved page should be the source of truth and go-to resource if someone wants to deep dive into diversity initiatives. We will restructure it in the coming weeks to keep it precise and not overwhelm newcomers with lots of TO-DO information.
TO-DO
I am closing this ticket as completed.
Metadata Update from @orionstar25: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.