@amsharma I am ok with this process, for now. However, I think the question you are skipping (mindshare vs council) is critical and we need to figure that out. That may also influence who wishes to volunteer, if this is hte process.

@amsharma I am ok with this process, for now. However, I think the question you are skipping (mindshare vs council) is critical and we need to figure that out. That may also influence who wishes to volunteer, if this is hte process.

In today's meeting we discussed to open this ticket and first have someone to represent. (we have other ticket to decide on either mindhshare or council or both, where others are sharing their opinion, you raised a right question in that ticket #25 )

@amsharma can i join ? would love to

An update here: we've officially updated the Council charter from Diversity Advisor to Diversity Team Representative. That should be live on the docs website soon; in the meantime, you can see the change here.

Thanks @mattdm

Discussed in 2017-11-17 meeting.

I updated the title of this ticket to be more clear.

Council and Mindshare

This topic was discussed together for both tickets #25 and #46. The Fedora Diversity Team is focusing our efforts on the auxiliary seat on the Fedora Council. The team believes we can connect our goals with the higher-level project direction at the Council. However, we also noted that our team representative is always welcome to participate in the future Mindshare meetings, just without voting privileges.

A new ticket is about to be filed for us to collect nominations for the Diversity Team Representative seat, as noted in Fedora Council charter.

Nominations open

In the meeting, we decided to open the call for nominations until our next meeting. At our next meeting, we will make a final decision / vote on the Diversity Team Representative for the Council.

The seat is open to any sponsored member of the Diversity Team FAS group. In the event of multiple candidates, we will figure out some sort of voting system.

Who is interested in this position? If you are interested, please nominate yourself below. You are also welcome to nominate someone else, but please ask them first before nominating them.

i am not sponsored in diversity FAS group should i nominate my self @jflory7 ?

i ve been sponsored in cvsl10n Group

This has been discussed with the core members of the diversity team and we came out with a long term solution. We all agreed that, to take care of this role's responsibilities actively, we would like to serve one by one for a tenure of 6 months (for each Fedora Release Cycle) for this role.

Decided order of the service will be ( can be modified as per need and as per council's suggestion ):

1. @amsharma
2. @bee2502
3. @jonatoni

https://docs.fedoraproject.org/fedora-project/council/charter.html defines the role. Here is the snippet for reference -

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 connects the team’s efforts to the
Council.

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

Though most of the team members agree with this decision made, I would request everyone to please vote here in the ticket or raise concerns if any.
I would request council ( @bex ) too to please review this decision and share feedback. If everything goes fine, this decision will be effective from 11th December.

@amsharma said…
Though most of the team members agree with this decision made, I would request everyone to please vote here in the ticket or raise concerns if any.

I edited the comment to remove my name from the list. As it is now, I am +1 to this proposal, assuming the first candidate begins their term in the F27 cycle.

@amsharma said…
I would request council ( @bex ) too to please review this decision and share feedback. If everything goes fine, this decision will be effective from 11th December.

If the team has made a final decision, we need to file a new ticket on the Council Pagure to confirm our decision. The Council confirms the seat once we file a new ticket with our final decision.

+1 even from my part

I am concerned by only one thing. A single release is a very short tenure, and I wonder if it is practical to have impact with what will seem like a "rotating door" of people. This would mean practically that every 22 meetings or so we have a new council member with the same mandate. I don't think that is good.

@bex I understand that concern and I think it's fair. I know the underlying concern for choosing one release cycle over another is that for some of our core team members, they were able to see six month periods where they could realistically handle the responsibility, but it wasn't as clear if a full year commitment were possible for some of us.

Do you have an idea for how we could find a compromise on this?

I don't have a good solution so my default is to "try it and see what happens." Perhaps this will reflect a model that can increase participation in other groups.

The reason behind the shorter term is that everyone would like to do it with dedication and 6 months is a reasonable time when one can commit herself/himself with full dedication for this role. And yes, not to forget that Fedora releases sometimes take more than 6 months.

Discussed in 2017-12-08 meeting.

Confirmation submitted

Fedora-Council#157 confirms the Diversity Team charter to the Fedora Council for Fedora 27 by @amsharma. This finalizes the decisions made above and in our meeting. Closing ticket as we are awaiting Council feedback on next steps to confirm the charter in the Council ticket.

Need to write a blog post for this one. I am doing it by today EOD.
@jflory7 request you to please review the same and publish. Thanks

@amsharma Let's open a new ticket for that, if needed. Since this ticket covered the selection process for the seat, I think we can keep it closed.