#222 Formalize and document process to add new people to the DEI team
Closed: complete 2 years ago by jflory7. Opened 2 years ago by riecatnor.

Overview
In the last DEI meeting, the topic of how to join the DEI team came up. Aiui, so far its been an informal process: if folks do stuff and hang around for a while, someone adds them to the FAS group at some point because it makes sense. Although its sorta worked so far, an established process would help the team in a couple ways:
- newcomers know what is expected to join the team (easier to onboard folks)
- the team has an established way to add people (we don't need to reinvent the wheel each time)

The general process we discussed on the call was the following:
- interested contributor hangs out for a while
- comes to meetings
- does tasks (we should probably define an expectation here)
- someone from the team nominates them for group membership
- team vote

Next Steps
Let's put together a hackmd doc with a draft and review as a team. Once we are happy with it, let's push it to our docs.


We discussed this in today's DEI team meeting and felt this was a high priority ticket. Because our meeting time is best for everyone to get together, we would like to use the next few meetings to get something drafted for this.

Please join the next 2-3 calls if you would like to be involved in writing these docs :) if you are unable to make the calls but have input for DEI Team membership docs, please leave your feedback here!

In today's meeting, we did a lot of work on this docs update HackMD pad.

Metadata Update from @jflory7:
- Issue priority set to: next meeting (was: awaiting triage)
- Issue tagged with: improvement, type - docs, type - onboarding

2 years ago

I have merged @siddharthvipul1's PR which had the changes from the HackMD pad. Also, I made some small fixes here https://docs.fedoraproject.org/en-US/diversity-inclusion/ (changed the meeting times and where to find the D.E.I team). Is there anything else that needs to be updated? If not, we can close the issue :100:

Metadata Update from @jflory7:
- Issue assigned to siddharthvipul1
- Issue priority set to: waiting on assignee (was: next meeting)

2 years ago

@siddharthvipul1 @riecatnor and @jflory7 talked about this in todays DEI meeting

We agreed the work for this ticket is complete, thanks to @siddharthvipul1's PR in #229. :clapper:

Metadata Update from @jflory7:
- Issue close_status updated to: complete
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata