#103 Define Fedora D&I team lead role, responsibilities and term
Closed: stale 2 years ago by jflory7. Opened 3 years ago by amsharma.

The intent is to come-up with a clear policy and process for electing Fedora D&I team lead. Defining his/her role, responsibilities and term.
Please refer https://pagure.io/fedora-diversity/issue/89 for guidance.


Metadata Update from @amsharma:
- Issue assigned to jonatoni
- Issue priority set to: waiting on assignee (was: awaiting triage)
- Issue tagged with: difficulty - medium, type - internal organization

3 years ago

@jonatoni hey do you have sometime to create a draft for this one? Maybe @bee2502 can help to start a draft? As we will need it before August if we are planning to have new person for this role. Thanks.

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

2 years ago

Sorry Amita but I cannot work on this now. I can review and give feedback, but not create a draft. @bee2502 can you do it?

I could give a hand if needed. @bee2502 @jonatoni would you like me to give you a hand on the draft?

@tatica It will be great if you can start the draft please. Thanks.

Metadata Update from @jflory7:
- Issue untagged with: difficulty - medium
- Issue assigned to tatica (was: jonatoni)
- Issue priority set to: needs review (was: next meeting)
- Issue tagged with: help wanted, needs info, type - docs

2 years ago

Discussed in 2019-07-01 meeting.


What's next

@tatica volunteered to help out with this. The main point of this ticket is to provide structure and clarity into what the D&I Team lead role is, what the responsibilities are, and how they are selected. In the meeting, we asked everyone to add a few bulletpoints about either what this role means today, or what they think this role should include.

I think this is a sticky ticket because there is correct concern about bias. We want transparency and openness to select a team lead. We also want someone with enough experience to understand the Fedora community and this team to be a successful leader. We also want to avoid pinning too much on one person to avoid burning out the person who does take the leader role.

Consider these question prompts to answer

I am still thinking this one through too. But if you aren't sure what to write or add, help us out by using these questions as prompts:

  • What does it mean to be the team lead? Is it chairing meetings and triaging tickets? Proposing an annual agenda at the start of each year for the D&I Team to focus on? Or something else?
  • What is considered "enough experience"? Is it time-based, like being active over a year in the Fedora community? Or is it team-based, like taking/leading tickets in the D&I ticket tracker and seeing them through? Do we need an external selection process to reduce bias?
  • Do you believe a formal leadership role is useful? Why or why not?

Discussed in 2019-07-01 meeting.

What's next
@tatica volunteered to help out with this. The main point of this ticket is to provide structure and clarity into what the D&I Team lead role is, what the responsibilities are, and how they are selected. In the meeting, we asked everyone to add a few bulletpoints about either what this role means today, or what they think this role should include.
I think this is a sticky ticket because there is correct concern about bias. We want transparency and openness to select a team lead. We also want someone with enough experience to understand the Fedora community and this team to be a successful leader. We also want to avoid pinning too much on one person to avoid burning out the person who does take the leader role.
Consider these question prompts to answer
I am still thinking this one through too. But if you aren't sure what to write or add, help us out by using these questions as prompts:

What does it mean to be the team lead? Is it chairing meetings and triaging tickets? Proposing an annual agenda at the start of each year for the D&I Team to focus on? Or something else?

Yes, + coordinating regular meetings and make sure things are rolling.

What is considered "enough experience"? Is it time-based, like being active over a year in the Fedora community? Or is it team-based, like taking/leading tickets in the D&I ticket tracker and seeing them through? Do we need an external selection process to reduce bias?

Team involvement will make it easier for the person to perform the responsibilities.
It should be more than a year in Fedora and 6 months in the team atleast.

What do you mean by external process? What kind of bias, sorry don't understand that?

Do you believe a formal leadership role is useful? Why or why not?

Yes, For regular progress and to have defined team goals.

Draft ready for review

Fedora Diversity Leader works toward the adaptation of Fedora processes to provide a healthy environment for all our contributors. Fedora is a worldwide community with members from different regions, cultures, languages, ethnics, genders, sexual orientation, physical abilities, religious beliefs and more, and the Diversity & Inclusion team will work continuously into make everyone feel welcome.

Diversity & Inclusion Leader Roles:

  • Build awareness inside the Fedora Project.
  • Provide Mentorship to Team leaders to promote and encourage participation on each area and address unconscious bias.
  • Encourage contributors to share their experiences within the project to spread inclusion efforts.
  • Make it easy for Diverse contributors to participate, by working as a bridge into creating awareness inside teams.
  • Coordinate the D&I team into activities such as surveys, events, mentoring and maintain general support for our Diverse community.
  • Act as spokesperson to raise awareness of inclusion efforts inside and outside the Fedora project.
  • Reaching out other Diversity & Inclusion teams to gather recurrent feedback and create wider strategies for Inclusion
  • Coordinate Meetings and regular activities to keep track of initiatives within the Team.

Thanks @tatica that was quick :)

I moved the content to a google doc for the ease of the review - https://docs.google.com/document/d/1sNwE2Xmmh8NxL8q8MXHEiCSPLKr7EqbkGFrmq5cp1eo/edit?usp=sharing
and left few comments.

Thanks @tatica that was quick :)
I moved the content to a google doc for the ease of the review - https://docs.google.com/document/d/1sNwE2Xmmh8NxL8q8MXHEiCSPLKr7EqbkGFrmq5cp1eo/edit?usp=sharing
and left few comments.

Thank you so much!!!

I tried to solve all questions raised up, and also added a couple of extra lines. If you're all kind to take a new look and let me know if I should work a bit more on this.

Thanks again for your time @tatica on this.
Changes look good to me. Left a few minor comments.

There is a need for a native speaker to have a look once, @jflory7 may want to help here.

Thank you @tatica for jumping on so fast and writing a draft!

@amsharma:
There is a need for a native speaker to have a look once, @jflory7 may want to help here.

I need more time to review. I believe this doc needs to be clear about specific responsibilities and tasks of the team lead. Being concrete is helpful. I love the ideas in the draft, but aren't many of these things doable by anyone in the team? Anyone can build awareness, anyone can provide mentorship, and we want everyone to encourage others to participate and share their voices and thoughts. I do not want it to seem like only the team lead can do these things, because we all are doing this in our own ways already. :smile:

A lot of this could be added as improvements to the Goals section of the About Diversity and Inclusion Team docs page.

I am taking some time to think more about the draft and come back with actionable suggestions next week. Curious to know if my feedback so far makes sense to the rest of you too.

I am +1 @jflory7 's suggestions on a better boundary between what are responsibilities of team lead vs what are goals for everyone in the team. Also, some points are complex, talk about multiple issues in a single point and can be divided into smaller actionable items eg.

  • Provide Mentorship to all Fedora Teams leaders (Docs, Design, Packaging, Ambassadors/Advocates/Websites/etc) and Council to promote and encourage participation on each area and address unconscious bias.

Additionally, to me it looks like there is a lot of overlap in responsibilities mentioned here for Team Lead vs the responsibilities of Diversity Advisor on Fedora Council especially. Since these are two different roles since 2018, it would be great if there is a better divide between responsibilities for both roles. As I understand, the role of Team Lead is more towards managing and driving intiatives and efforts of the team vs the role of Diversity Advisor is more towards communication and outreach - both internally and externally.

The following points mentioned in the doc look like primary responsibilities of Diversity Advisor on Fedora Council to me :
- Provide Mentorship to all Fedora Teams leaders (Docs, Design, Packaging, Ambassadors/Advocates/Websites/etc) and Council to promote and encourage participation on each area and address unconscious bias.
- Make it easy for Diverse contributors to participate, by working as a bridge into creating awareness inside teams.
- Listen to unconscious bias or discrimination complains
- Act as spokesperson to raise awareness of inclusion efforts inside and outside the Fedora project.

Let me know if this makes sense.

Thanks @jflory7 for the feedback and @bee2502 for following up.

I think, It will be great if you can provide a deadline for this so that it will not be stalled.

Personally, It makes it lot easier to get comments in the google doc to compare and think. For example - "The following points mentioned in the doc look like primary responsibilities of Diversity Advisor on Fedora Council to me" and listed all the points again in ticket again.

I agree with this - "some points are complex, talk about multiple issues in a single point and can be divided into smaller actionable items" As it should be easier to the person reading it and want to take up the role. They should be able to understand clearly what they need to do.

Let's help @tatica in the best way to complete this. As it will be good to appoint our lead during the time of diversity advisor elections, WDYT?

Can we agree also on the term used and be consistent? I would suggest Fedora Diversity and Inclusion Team Lead and Fedora Diversity and Inclusion Advisor (or Fedora Council D&I Rep)

@amsharma: There is a need for a native speaker to have a look once, @jflory7 may want to help here.
Please!

@jflory7 : but aren't many of these things doable by anyone in the team?
I felt the same when starting write the draft, but discussion had to start somewhere.

@jflory7 : A lot of this could be added as improvements to the Goals section of the About Diversity and Inclusion Team docs page.
Yes. Probably would be a good idea to use the same draft as not just roles for the Team Lead, but to enrich our Team description.

@bee2502 : Additionally, to me it looks like there is a lot of overlap in responsibilities mentioned here for Team Lead vs the responsibilities of Diversity Advisor on Fedora Council especially. Since these are two different roles since 2018
Makes perfect sense. I didn't knew they had separate both roles.

Just added some minor changes to the doc based on the comments. Glad to be helpful!

Team thinks that we still need this role in our team?
Considering current situation, we are very small team, I don't think we need this at the moment but may be in future. Thoughts?

As I expressed my opinion at Flock'19, I think that there are only 2 options available in here:

  • Having a board instead a single leader
  • having a single role lead (as I understood, there were two -advisory- D&I seat-)

As @amsharma says, it's a small group, and keeping it simple would be the ideal.

This ticket is over a year old and the last comment was six months ago. The most recent comments are open questions over whether we need to define the Team Lead role explicitly, or if it is a role we have bandwidth to fill each release cycle.

So, I am going to close this ticket as stale because our past conversations make me believe this is something we are no longer interested in documenting, and instead, we can invest more resources into the D&I Advisor role, a la #89.

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

2 years ago

Login to comment on this ticket.

Metadata