#212 Selecting new CommOps Mindshare representative for F34-F35
Closed: not possible 2 months ago by bt0dotninja. Opened a year ago by bt0dotninja.

Summary

Select a member of the CommOps team to serve as Mindshare Committee representative for Fedora 34 and Fedora 35

Background

Per past precedent, we agreed the CommOps seat on the Mindshare Committee would last two release cycles (i.e. one full year) before it is open again for new nominations. Note we did not set the "term limit" requirement mentioned in the linked comment.

I do not plan to nominate myself again for the Mindshare Committee seat from CommOps.

This ticket is a chance for us to collect nominations and begin a process of selecting a team member to serve as the Mindshare Committee representative for the next two Fedora release cycles, Fedora 34 and Fedora 35. This will take effect after October 2020.

We did not time box how long we run the nomination period. Thus, I would like to propose we open a general call for nominations for one month (i.e. ending on July 03, 2020). After this, we can confirm the next representative and also work on on-boarding the future representative to the Mindshare Committee.

Any sponsored member of the CommOps FAS group is eligible for the Mindshare Committee seat. A team member may nominate someone else, or someone may self-nominate themselves too. For now, we will collect nominations in this ticket. After July 03, we will move forward with confirming the next representative.

Outcome

Select a new CommOps representative to Mindshare Committee, focus on smooth on-boarding of new representative and off-boarding of the previous representative for October 2020 handover


This ticket is a chance for us to collect nominations and begin a process of selecting a team member to serve as the Mindshare Committee representative for the next two Fedora release cycles, Fedora 33 and Fedora 34. This will take effect after October 2020.

I'm confused. The Fedora 33 cycle ends in October 2020. Are we really talking about selecting reps for the Fedora 34 and 35 cycles?

We did not time box how long we run the nomination period. Thus, I would like to propose we open a general call for nominations for one month (i.e. ending on July 03, 2020). After this, we can confirm the next representative and also work on on-boarding the future representative to the Mindshare Committee.

I'm on board with this as a one-off. I'd suggest in the future we basically track the elections timeline for simplicity's sake. I can create an election that only group members can vote in if we need to have a voting process.

Any sponsored member of the CommOps FAS group is eligible for the Mindshare Committee seat. A team member may nominate someone else, or someone may self-nominate themselves too. For now, we will collect nominations in this ticket. After July 03, we will move forward with confirming the next representative.

This raises the question of "should people be removed from the FAS group after some period of inactivity?" (where the period and the definition of "inactivity" are very difficult problems to solve).

So I made my previous comment before I saw that Mindshare#218 was opened. The outcome of that issue might change the charter and membership of the CommOps group in non-trivial ways, so perhaps it's better to put a hold on this process until that is resolved.

I have to focus on CommOps related things for the new changes than are coming. This internal CommOps process has much time in the hold and now is the best moment to put the correct contributor resources in the right place.

Fixed the releases, thanks for point it :)

Metadata Update from @jflory7:
- Issue priority set to: next meeting (was: awaiting triage)
- Issue tagged with: needs feedback, team - commops, team - mindshare, type - internal organization, type - onboarding

10 months ago

I will close this ticket and reopen it when the revamp was ended and we have more active contributors in CommOps.

Metadata Update from @bt0dotninja:
- Issue close_status updated to: not possible
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.

Metadata