#305 Selecting new CommOps Mindshare representative for F37-F38
Closed: complete a month ago by jflory7. Opened a year ago by bt0dotninja.

== Summary

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

== 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 37 and Fedora 38. This will take effect after December 2022.

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 December 15, 2022). 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 December 15, 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 January 2022.


Metadata Update from @bt0dotninja:
- Issue assigned to bt0dotninja

a year ago

Metadata Update from @bt0dotninja:
- Assignee reset

a year ago

Metadata Update from @bt0dotninja:
- Issue assigned to bt0dotninja

a year ago

Discussed in 2022-11-22 Mindshare meeting.


We discussed this in the Mindshare meeting today and agreed that we should look to expanding the search for the CommOps seat more widely. I have an action to start a CommBlog draft to get a conversation going on the CommOps seat in Mindshare.

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

a year ago

I am closing this as complete, given that @bt0dotninja was onboarded again as the CommOps team representative and the Council officially approved this proposal:

https://pagure.io/Fedora-Council/tickets/issue/474

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

a month ago

Login to comment on this ticket.

Metadata