#137 New wording for diversity advisor
Closed: approved 7 years ago Opened 7 years ago by mattdm.

Existing:

Diversity Advisor

Fedora's Diversity Advisor works on initiatives to assess and promote equality and inclusion within the Fedora contributor and user communities, and helps develop project strategy on diversity issues. Additionally, the Diversity Advisor administers and is the point of contact for Fedora's participation in third-party outreach programs and events.

This position is appointed by the Fedora Project Leader, with the approval of the Council.

Proposed:

Diversity Team Representative

The Fedora Diversity Team works on initiatives to assess and promote equality and inclusion within the Fedora contributor and user communities, and helps develop project strategy on diversity issues. The Diversity Team Representative [represents] the team's efforts on the Council.

This position is appointed by members of the Fedora Diversity Team, with the approval of the Council.

Please bikeshed on words now. Particularly "The Diversity Team Representative [represents] the team's efforts on the Council." should be made more better.


Metadata Update from @mattdm:
- Issue tagged with: policies

7 years ago

thoughts:

  • The Diversity Team Representative reflects the team's efforts on the Council.
  • The Diversity Team Representative shares the team's efforts with the Council.
  • The Diversity Team shares their progress and needs through the Diversity Team Representative to the Fedora Council.

Should we combine this into the section with the other representatives and make it more parallel in structure? Alternately, should we rewrite those to be more parallel to this?

<bikeshed>
The Diversity Team Representative serves as a liaison between the team and the Council.
</bikeshed>

My thinking for not making it parallel the other two is that I think there's a natural split in the project between engineering and the corresponding os-release-cycle-focused-stuff and the outreach/mindshare side. Diversity/inclusion is not really a third such group; it's something that goes across the whole project.

Not saying I can't be swayed. That's just my logic in how it came to be this way.

My thinking for not making it parallel the other two is that I think there's a natural split in the project between engineering and the corresponding os-release-cycle-focused-stuff and the outreach/mindshare side. Diversity/inclusion is not really a third such group; it's something that goes across the whole project.

It seems that it fits in the same way that the elected reps and the selected reps are together. The diversity rep is selected by a team and has a set of requirements similar to those of the other positions. It seems weird to leave it in the Auxiliary role.

While I understand your split analogy, the elected reps is what sways me.

Metadata Update from @mattdm:
- Issue assigned to mattdm

7 years ago

Metadata Update from @mattdm:
- Issue private status set to: False (was: True)

7 years ago

https://pagure.io/Fedora-Council/council-docs/pull-request/8

Here's the proposed change. I suggest we go forward with this now; we can look at rearranging the overall org chart later. (That would combine mindshare, engineering, diversity into one section ("area representatives"? "topic representatives"?), with the elected representatives in their own section.)

PR above is merged. @bex will open ticket for grander rearrangement.

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

7 years ago

Log in to comment on this ticket.

Metadata